Clash Plus
A good starting point for importing a subscription on Windows. Enable your configuration, turn on the system proxy, then test the connection in a browser.
Choose your device’s operating system, then select the right package architecture. For everyday use, choose a graphical client. Servers and routers can use the standalone Mihomo core.
Browse Mihomo core downloads ↓This section offers x64 installers. To check your system type, search for “System Information” in Settings. Choose an x64 package if it says “x64-based processor” and you’re running 64-bit Windows. If it lists an ARM processor, first check whether the client and its networking components support your device.
A good starting point for importing a subscription on Windows. Enable your configuration, turn on the system proxy, then test the connection in a browser.
Manage subscriptions and inspect rule matches in the graphical interface. To route traffic from apps that don’t use the system proxy, configure TUN as prompted by the client.
A good fit if you already use FlClash on another device. Reimport your subscription, then check the system proxy and local listening port on this device.
Manage multiple configurations in the graphical interface. Before switching, check which configuration is active so you don’t mistake rules from an old one for the results of a new one.
Kept for reference on older systems and configuration migration. For everyday use on a new device, choose a client that’s still maintained.
| Check | What to choose or do |
|---|---|
| Operating system and architecture | The x64 installers in this section require 64-bit Windows. Check the selected client’s release notes for its Windows version requirements. 32-bit Windows cannot run x64 installers. |
| Installation and permissions | You need write access to the installation folder. If you enable TUN features that rely on a service or driver, grant the permissions requested by Windows. |
Open About This Mac from the Apple menu. If it lists a chip and an Apple M-series model, choose ARM64. If it lists an Intel processor, choose x64. Some clients currently offer an Intel build only; check the note below the download button.
Choose the installer that matches your chip. Open the disk image, then follow the window instructions to move the client to Applications.
Both download buttons currently point to an Intel build. On an Apple silicon Mac, if the downloaded file is labeled x64, check Rosetta and client compatibility before running it.
The alternate DMG is labeled amd64, which means it’s built for Intel. Check the downloaded filename before deciding whether to run it in compatibility mode.
Archived for reading older configurations. Both download buttons point to an x86_64 build. Save your existing configuration and subscription URL before upgrading macOS or switching clients.
| Check | What to choose or do |
|---|---|
| Chip | Choose ARM64 for Apple silicon and x64 for Intel. Before running an Intel build on Apple silicon, check Rosetta and client compatibility. |
| macOS version | Check the selected client’s requirements for your macOS version. Being able to open a DMG doesn’t mean the app inside supports your system. |
| Installation location | Move the client to Applications before opening it, then eject the mounted disk image. Before updating, quit the old client if it’s running. |
Choose an APK that matches an ABI supported by your Android system. Select ARM64 only after confirming support for arm64-v8a: some devices have 64-bit processors but ship with a system that supports only 32-bit apps.
A good choice for setting up a 64-bit ARM phone for the first time. Import and enable your subscription; Android will prompt you to authorize the VPN when you connect.
Routes traffic through Android VpnService and supports remote subscriptions and local configurations. Choose the ARM package if your device supports only 32-bit ARM.
Import configurations and switch proxy groups. After moving from a desktop client, test each group selection again; saved choices don’t transfer with the installer.
For users with an existing Surfboard-compatible configuration. Before switching, check subscription format and rule support; changing the file extension alone won’t make it compatible.
| Check | What to choose or do |
|---|---|
| ABI and Android version | Choose ARM64 if your system supports arm64-v8a; choose ARM if it supports only armeabi-v7a. The minimum Android version depends on the client you choose. |
| Install source | If Android asks you to allow installs from this source, grant permission only to the browser or file manager you’re using to open the APK. You can revoke it after installation. |
| VPN permission | Approve Android’s VPN request before connecting for the first time. If another VPN is active, disconnect it before starting this client. |
Check your device and iOS version under Compatibility on the App Store before downloading the client. Import your existing subscription, select a configuration, and follow the prompts to allow a VPN configuration.
Client website: clashplus.io
| Check | What to choose or do |
|---|---|
| macOS version | Check the minimum iOS version listed on the App Store product page. Requirements may change with client updates. |
| Device permissions | iOS must allow app installation and adding VPN configurations. If your managed device restricts these actions, check with your device administrator. |
The graphical client packages in this section are for x86-64 desktop systems. Run uname -m; if it returns x86_64, choose a package for your distribution. DEB packages are for Debian, Ubuntu, and similar distributions; RPM packages are for Fedora and other RPM-based distributions.
Check your distribution and desktop dependencies before installing. If the package manager reports missing dependencies, note them and check whether your system version is supported.
For desktop environments that support DEB packages. After enabling the desktop system proxy, test your browser and terminal separately; terminal apps may not use the desktop proxy settings.
| Check | What to choose or do |
|---|---|
| Processor architecture | Graphical packages in this section use the amd64 or x86_64 architecture. Don’t install them if the result is aarch64. |
| Distribution and dependencies | Choose DEB or RPM based on your package manager, and check the client’s runtime library and desktop environment requirements. |
| Headless systems | To run the rules core directly on a server or router, choose a Mihomo file below that matches the device’s operating system and userspace architecture. |
The standalone core is for servers, routers, or users who want to manage processes manually. For everyday use, choose a graphical client above. With a core package, you’ll need to provide your own configuration file and decide which user runs it, where it reads the configuration, and where to find its logs.
| Operating system | Architecture | File |
|---|---|---|
| Windows | AMD64 | Download Windows AMD64 ZIP |
| Windows | ARM64 | Download Windows ARM64 ZIP |
| macOS | Intel | Download macOS Intel GZ |
| macOS | Apple silicon | Download macOS ARM64 GZ |
| Linux | AMD64 | Download Linux AMD64 DEB · Download Linux AMD64 GZ |
| Linux | ARM64 | Download Linux ARM64 GZ |
| Linux | ARMv7 | Download Linux ARMv7 GZ |
| Linux | MIPS softfloat | Download Linux MIPS softfloat GZ |
Choose one client per device. After launching it, import and enable a configuration, then turn on the system proxy, TUN, or Android VPN. For your first test, avoid changing the routing mode, proxy groups, and DNS all at once; otherwise, it’ll be hard to tell what caused a problem. See the quick-start guide for detailed instructions.
Stick with the original download source and architecture when possible. Save your subscription URL and local configuration, then quit the old client. On desktop, make sure it has also exited from the system tray or menu bar. After updating, check which configuration is enabled before testing the connection, so configuration changes aren’t mistaken for an installation failure.
First, make sure the new client supports your configuration format before importing the old file. Quit the old client and disconnect before starting another to avoid conflicts over ports or the system VPN. If you’re choosing between clients, see the client comparison and narrow down your options by operating system, configuration source, and traffic routing method.
Choose ARM64 if your system supports arm64-v8a; choose ARM if it only supports armeabi-v7a. If both are supported, prefer ARM64. If you’re unsure, try the universal package offered by the same client. Supported architectures vary by publisher, and a universal package does not lower the client’s minimum Android version.
Don’t uninstall it yet. Make sure the package matches your Android version and device architecture, and check that you have enough free storage. If Android reports a signature mismatch, verify the new package’s source, back up your configuration, and save your subscription URL before deciding whether to switch download sources. Uninstalling may erase configurations, proxy group selections, and update settings.
Some client download buttons currently point to the same Intel installer. Treat files named x64, amd64, or x86_64 as Intel builds. Apple silicon Macs may need Rosetta to run these clients, and you should still check that the client supports your macOS version. For native performance, choose a file explicitly labeled arm64.
Usually, you only need one graphical client. Clients that include a core manage its startup and configuration loading for you. The standalone Mihomo core is for servers and routers where you want to manage configuration files, permissions, and logs yourself. Before replacing a graphical client’s core, check that the client supports it.
Installers only install the client. To route traffic through a proxy, provide your own subscription URL or configuration file, then import and enable it in the client. If no proxy groups appear in the preview, first check whether the imported content uses a format supported by your client instead of reinstalling it repeatedly.
Archived versions can help you check an old interface or read an older configuration, but for everyday use, choose a client that’s still maintained. Keep a copy of your configuration before migrating. After importing it into the new client, check your proxy groups, rules, and ports. The exported configuration may not include interface preferences or saved group selections from the old client.
View installation and configuration guides for each platform →