CLIENT / PACKAGE / ARCHITECTURE
Choose your operating system, then check the CPU architecture. Use a GUI client on desktop and mobile; for servers and routers, see the Mihomo core packages.
Clash Plus is the top pick on supported platforms. Choose another client based on its interface, configuration management, and core compatibility. Run only one client per device to avoid conflicts between proxy ports and virtual network adapters.
The GUI clients listed here are primarily x64 builds. Go to Settings > System > About and check System type before downloading. On ARM devices, also confirm that Windows can run x64 apps.
A good fit for desktop users who want to get started by importing a subscription. After installation, add a remote subscription or local configuration, choose an exit in the proxy group, and enable the system proxy if needed. To verify your first connection, check the connection list for matched rules rather than relying on the toggle alone.
clashplus.ioA desktop client built on the mihomo ecosystem, suited to users who need configuration management, rule inspection, and overrides. Before enabling TUN, make sure service mode is working. After changing rules, reload the configuration and check the exit in the connection details.
Offers a cross-platform interface for users who want a similar experience on desktop and mobile. The installer is usually the easiest option. Extract the ZIP archive fully before launching the app; don’t run it from the archive preview window. When migrating, check the local data path and permissions.
For Clash ecosystem users who need desktop configuration management. Core options and settings may vary between releases. Before importing a configuration, check that the selected core supports its protocols and extended fields. Being able to load a file in the GUI doesn’t mean every field is supported.
Kept for existing workflows, reproducing legacy configurations, and migration reference. The original project is no longer maintained, so changes to operating systems and protocols may cause compatibility issues. For a new installation, choose a client listed above. When migrating away, save your original configuration and rule overrides; don’t copy the entire old data directory over the new project’s files.
| Check | What to look for | Recommendation |
|---|---|---|
| Operating system | A modern 64-bit Windows desktop environment | Check the selected client’s current release notes. Older versions of Windows may lack required runtimes. |
| Processor | x64 and AMD64 are equivalent architecture labels | On ARM64 devices, confirm x64 emulation support. An x64 package is not a native ARM64 build. |
| Permissions and networking | You can usually set the system proxy in your user session | TUN or service installation may require administrator approval. Quit other clients before letting one take control of the network. |
Check your chip under About This Mac in the Apple menu. Verify the file architecture for Apple Silicon and Intel separately. Some downloads listed here share an x64 file; this is noted next to the buttons. They are not labeled as native ARM64 builds.
Separate ARM64 and x64 installers are available. Open the DMG and follow the installer prompts to move the client to your Applications folder, then launch it from there. After importing a subscription, check the active mode. When switching configurations, make sure the default proxy group is still selected.
clashplus.ioA good fit for desktop users who need configuration overrides, rule management, and core settings. Both download options currently point to the same x64 file. Before using it on Apple Silicon, check compatibility with Rosetta 2 and the release. Read the system’s authorization prompts before enabling network extensions or helper services.
For users who want a consistent experience across desktop and mobile. Both downloads currently use the same AMD64 package; Apple Silicon requires a compatible translation environment. On first launch, add a configuration and check that it parses before enabling the proxy. This helps distinguish configuration errors from installation problems.
For reference when migrating existing menu bar workflows or older setups. The project is no longer maintained, and the current listing contains an x86_64 file; the two download options are not separate native builds. If you run into helper, permission, or protocol compatibility issues after upgrading macOS, consider switching to a maintained client.
| Check | What to look for | What to check |
|---|---|---|
| Chip architecture | Choose ARM64 for Apple M-series chips and x64 for Intel | Downloads labeled as translated builds are x64 files and require Rosetta 2. |
| Operating system version | Check the client’s release notes for the minimum macOS version | Minimum requirements may differ for GUI frameworks and service components. |
| Install location | Install from the DMG to your Applications folder | Don’t run the app from the disk image long-term. On first launch, follow system prompts to verify the source and grant permissions. |
Most modern phones use ARM64, but check the device model, processor, and system bitness together. When installing an APK for the first time, grant install permission only to the current source. The VPN permission requested when connecting establishes a local traffic-routing tunnel.
For Android devices that support arm64-v8a apps. After installation, import a compatible configuration, choose a proxy group, and start the connection. If it disconnects when the screen locks, check the system’s battery optimization and background activity restrictions for the client. Settings names vary by device.
clashplus.ioOffers packages for multiple architectures, making it a good fit for users with existing Clash Meta configurations. Choose the package that matches your device when possible. If you’re unsure, consider the universal package, which is usually larger. Once the configuration parses successfully, start the VPN connection and check DNS and rule matching in the logs.
A good fit for users who already use FlClash on desktop and want a similar interface on Android. The x86_64 package is for compatible devices or some emulators, not the default choice for standard ARM phones. When migrating configurations, check file access permissions and keep subscription links secure.
Check that your subscription uses a compatible format before installing. Surfboard uses a different configuration format from Clash YAML; changing the file extension won’t convert it. Choose this download only if you already have a Surfboard-compatible configuration, and check protocol support, rule syntax, and your provider’s import instructions.
| Check | What to look for | What to check |
|---|---|---|
| App architecture | arm64-v8a, armeabi-v7a, or x86_64 | The app architecture supported by your system is a more reliable guide than the processor name. A 32-bit system can’t run ARM64 packages. |
| Operating system version | Check the client’s latest release notes for Android requirements | If the package won’t install, check that it downloaded completely and matches your device architecture. |
| Network access | VPN permission must be approved by the user | You usually can’t run another app that uses the same VPN interface at the same time. |
Install Clash Plus from the App Store. Check the store listing for compatibility, the current version, and other details. After installation, import a compatible configuration from your service provider.
After installation, add a subscription or compatible local configuration and check that the proxy groups include a usable exit. Follow the system prompts to add a VPN configuration. If the connection acts up when switching between Wi-Fi and cellular, check the client logs and current exit. Don’t assume every app is routed as expected based only on the status bar icon.
clashplus.io| Check | What to look for | What to check |
|---|---|---|
| Device and operating system | Refer to the compatibility list on the App Store listing | Check your iOS version in Settings, then see whether the App Store allows you to install the app. |
| Configuration source | A working subscription or compatible configuration is required | Installing the client doesn’t provide a proxy service. Your service provider maintains the subscription content. |
| Connection permission | Follow the system prompts to add a VPN configuration | After connecting for the first time, check the proxy group and rule mode. If troubleshooting, first make sure no other VPN app is running. |
The GUI packages below are for AMD64 / x86_64. Debian- and Ubuntu-based systems usually use DEB packages; distributions with RPM package management use RPM. Check your distribution, desktop environment, and dependencies before installing.
A good fit for Linux users with a desktop environment who want a GUI for subscriptions and rule management. Whether the system proxy covers an app depends on the desktop environment and the app itself. TUN also requires service permissions and routing setup. If dependencies fail to install, use your distribution’s package manager to investigate; don’t force packages from another distribution.
For users who want a similar interface across platforms. Before installing, check your package management system and CPU architecture. After launch, verify that the configuration loads and check the listening port. Command-line tools may not use desktop proxy settings, so you may need to configure proxy environment variables or options separately.
| Check | How to check | Recommendation |
|---|---|---|
| CPU architecture | uname -m | The GUI packages listed here are for x86_64. For ARM servers, see the core packages below. |
| Distribution | cat /etc/os-release | Choose DEB or RPM for your distribution. Check the client’s release notes for the minimum system version and dependencies. |
| Runtime environment | A supported graphical desktop and its required dependencies | Headless servers usually use the core and system services rather than a GUI client. |
CORE / MANUAL DEPLOYMENT
For server, router, and self-hosted service users. The core parses configuration, matches rules, and handles proxy connections; it doesn’t include a desktop management interface. Most users should choose a GUI client above instead of setting up duplicate background services and network routing.
| Operating system | Architecture / format | Use case | Download |
|---|---|---|---|
| Windows | AMD64 · ZIP | 64-bit x86 devices; manage from the command line after extraction | Download AMD64 ZIP |
| Windows | ARM64 · ZIP | Native Windows ARM64 environment | Download ARM64 ZIP |
| macOS | Intel AMD64 · GZ | Command-line use on Intel Macs | Download Intel GZ |
| macOS | Apple Silicon ARM64 · GZ | Native core for Apple M-series chips | Download ARM64 GZ |
| Linux | AMD64 · DEB | Compatible Debian-based package management systems | Download AMD64 DEB |
| Linux | AMD64 · GZ | Manual deployment on 64-bit x86 servers | Download AMD64 GZ |
| Linux | ARM64 · GZ | 64-bit ARM servers and compatible devices | Download ARM64 GZ |
| Linux | ARMv7 · GZ | Compatible 32-bit ARMv7 systems | Download ARMv7 GZ |
| Linux | MIPS softfloat · GZ | Only for devices with matching ABI, endianness, and soft-float support | Download MIPS GZ |
The core needs a valid configuration file. Prepare the configuration directory and rule resources, then validate the syntax and start it in the foreground. Check the listening address, ports, DNS, and TUN permissions individually. Don’t expose the management API to the public internet without access controls.
GUI clients may include their own core update mechanism. Before replacing a core manually, check interface compatibility, the program path, and how to roll back. An older GUI may not correctly edit fields supported by a newer core. See the protocol reference for details on protocols and cores.
EXE, DMG, APK, DEB, and RPM describe distribution or installation formats, not processor architecture. A DMG can contain an ARM64 or x64 app; an APK may support just one app architecture. Check the filename, button description, and device system information together. If the system reports an error, note the full message before checking whether the cause is the format, architecture, runtime dependencies, or permissions.
Record your subscription source, auto-update settings, local rules, override scripts, and ports. Subscription URLs may contain access credentials, so don’t share them in public screenshots or support posts. When switching clients, import the subscription and confirm it parses before migrating local changes one at a time. Configuration directories also contain UI state and cache; copying the entire directory can introduce incompatible data.
On first launch, run only one client. Import a configuration, then choose a rule mode and an exit in the proxy group. The system proxy usually affects only apps that follow system proxy settings. TUN coverage depends on routing, DNS, and permissions. If your browser works but the terminal doesn’t, first check whether the terminal tool uses proxy settings; reinstalling may not be necessary. See the user guide for setup instructions and the help center for common errors.
Most desktop and mobile users should start with a GUI client. GUI clients let you import subscriptions, switch proxy groups, and toggle the system proxy. The Mihomo core package is for server and router users who manage configuration, processes, and system services themselves. You’ll still need to import a working configuration after installing a client.
x64 and AMD64 usually refer to the same 64-bit x86 architecture; it isn’t limited to AMD processors. ARM64 is for 64-bit ARM devices, while ARMv7 is used by some older 32-bit ARM devices. In Windows, check System type in Settings > System > About. On macOS, check the chip under About This Mac. For phones and routers, verify the device specifications and system architecture.
For some apps listed here, the Apple Silicon download currently points to the same x64 file as the Intel download; the button is labeled as a translated build. The download category doesn’t mean the file is a native ARM64 build. Before using it, check compatibility with your macOS version, client, and Rosetta 2. Clash Plus currently offers a separate ARM64 package.
First, check your browser’s downloads and make sure the transfer is complete. Then verify your operating system, architecture, and file format. If a download fails, try again later or use a reliable network. Read any system security warning carefully and verify the file’s source—don’t simply disable system protection. If your device is managed by an organization, follow your administrator’s guidance.
Save your subscription URL, local configuration, and overrides. Note your ports, proxy groups, and TUN settings. Quit the old client before installing the new one to avoid multiple clients taking control of the system proxy. When switching projects, don’t overwrite the entire data directory. Import your configuration again and check that its fields are supported.
The installer provides the client app, not a working subscription or proxy service. Import a compatible configuration from your service provider, choose an exit in the proxy group, then enable the system proxy or TUN mode as needed. If the connection fails, check the logs and configuration parsing results. For setup instructions, see this site’s user guide.