Downloads · Platforms and Architectures
Choose your device’s operating system, then pick an installer. For desktop and mobile devices, start with a GUI client. For servers, routers, and systems you manage yourself, see the Mihomo core downloads.
Clients are listed in a set order for each platform. The top pick is a place to start, not a one-size-fits-all recommendation; read the architecture notes on each card before downloading.
These desktop installers are for x64 systems. Check System type under Settings → System → About. On Windows on ARM, also confirm the system can run x64 apps; an x64 installer is not a native ARM64 build.
A good fit if you’re getting started by importing a subscription. Install and open the client, then import a compatible configuration and check the rule mode and system proxy. If you need to route traffic from apps that ignore the system proxy, look into TUN mode.
Project website: clashplus.io
For users who want to manage subscriptions, rules, and desktop proxy settings. Service mode and TUN require system permissions; follow the client’s prompts after installation. If another proxy tool is running, quit it before testing the connection.
For users who want a similar experience across desktop and mobile. Cross-platform doesn’t mean every option works the same way; check permissions, configuration storage, and traffic routing separately after installation.
Another desktop client option. When migrating, first import a standalone configuration and confirm the core starts correctly, then restore your preferences one by one. Don’t assume override scripts from another client will work unchanged.
An archived download for recreating older setups and migrating configurations. Use it only if you specifically need the behavior of the older client; it’s not recommended as the default for new devices. An older core can’t gain support for every new protocol just by updating a subscription.
| Check | What to look for |
|---|---|
| Processor | These downloads are x64 / amd64; they won’t work on 32-bit systems. Check compatibility separately on ARM devices. |
| System and components | Check the selected client’s current release notes for its minimum Windows version. If a runtime component is missing, follow the installer’s instructions. |
| Permissions | Running the interface normally requires different permissions from installing a service or enabling a virtual network adapter. Grant permissions for the features you use. |
| After installation | Import a configuration and confirm the core starts before enabling the system proxy. If a port is already in use, check for an older process. |
Check your chip under Apple menu → About This Mac. Apple Silicon and Intel use different native architectures. Some download links currently provide x64 files, as noted on their cards; don’t assume a link provides a native build based on its label alone.
Download the DMG for your chip, move the app to Applications, then open it. After importing a subscription for the first time, make sure the right configuration is selected. Follow the on-screen prompts to grant permission if you need system proxy or TUN mode.
Project website: clashplus.io
For desktop users who need subscription and rule management. Both downloads currently provide x64 files. Apple Silicon users should check Rosetta compatibility; this page does not label these as native ARM builds.
Offers a configuration workflow similar to the versions on other platforms. Both downloads currently provide amd64 files. On Apple Silicon, check Rosetta support before use. When migrating configurations, recheck macOS proxy and network permissions.
For reference when keeping an older menu bar workflow or migrating configurations. This download is for x86_64; Apple Silicon users should check compatibility. Past compatibility does not guarantee it will run on current macOS versions.
| Check | What to look for |
|---|---|
| Chip | Choose a native ARM64 build for Apple silicon and an x64 / amd64 build for Intel. |
| macOS version | Check the client’s release notes for the minimum macOS version. Don’t assume a new build will run on an older system. |
| Running x64 apps | Apple Silicon usually needs Rosetta to run x64 apps. If the app uses network components, check that those are compatible too. |
| Installation location | Move the app to Applications before opening it. Avoid running it long-term from a mounted DMG. |
Android downloads must match both your system and its ABI. Most recent phones support arm64-v8a; older devices may use armeabi-v7a. A 64-bit-capable processor doesn’t necessarily mean the system provides a 64-bit app environment, so check the ABI your device actually supports.
This download is for ARM64. After installing, import a subscription and make sure the configuration loads. Approve the system prompt when establishing a VPN connection for the first time. If background restrictions interrupt the connection, check battery management and background activity settings.
Project website: clashplus.io
Clash Meta client for Android. Choose the build for your device’s architecture if you know it. Otherwise, consider the universal build: it supports more architectures but is usually larger. Check protocol and configuration field compatibility before importing a configuration.
For users who want to use the client on both desktop and Android. Downloads are available for ARM64 and 32-bit ARM. Android routes traffic through the system VPN interface, unlike the system proxy on desktop, so don’t reuse desktop permission settings.
Uses a configuration system different from Clash YAML. Best suited to users who already have a compatible configuration and understand its syntax. Don’t assume a Clash subscription link is a supported format; check the subscription’s output type first.
| Check | What to look for |
|---|---|
| System and ABI | Check the app’s release notes for the minimum Android version. ARM64 and ARM builds are not interchangeable. |
| Installation permissions | When installing from a browser or file manager, grant permission only to the source you’re using. |
| Connection permissions | A system VPN permission prompt must be approved to connect. Another VPN app may already be using the same connection slot. |
| Background activity | Test the connection while the app is in the foreground first. Then address background restrictions based on your device maker’s battery settings; there’s no need to grant every permission at once. |
Check Clash Plus compatibility, app details, and release history on the App Store. Refer to the current store listing for system requirements. After installation, import a configuration and complete the required system network authorization.
After installing from the App Store, prepare a compatible subscription or configuration file, then import it in the client. When iOS asks to add a VPN configuration, check the app name and confirm the request came from the app. Test with an actual app to verify the connection instead of relying on the status toggle.
Project website: clashplus.io
| Check | What to look for |
|---|---|
| System and device | Check the App Store compatibility section to confirm your iOS version and device are supported. |
| Network authorization | iOS requires confirmation to add a VPN configuration. If you use another VPN, check for connection conflicts first. |
| Configuration setup | Make sure the app can read the subscription format. A regular webpage URL is not a configuration URL. |
| Test the connection | Check which configuration and proxy group are enabled, then test the browser and target app separately. |
These desktop downloads are for amd64 / x86_64. Choose DEB for Debian- and Ubuntu-based distributions, or RPM for RPM-based distributions. Headless servers don’t need a GUI client; see the core downloads instead.
For managing subscriptions and proxy settings on a Linux desktop. Choose the package format for your distribution and use its package manager to resolve dependencies. Desktop proxy settings may not cover every terminal or background process, so test them separately.
This section provides an amd64 package for Debian-based systems. If the system reports missing shared libraries or desktop components, use the package manager’s output to resolve dependencies. This amd64 package is not a native app for ARM devices.
| Check | What to look for |
|---|---|
| Architecture | These downloads are for amd64 / x86_64. Run uname -m to check your machine’s architecture. |
| Package format | DEB and RPM belong to different package systems. Don’t install one by simply changing its file extension. |
| Runtime requirements | A GUI client needs a desktop environment and its runtime dependencies. Check the release notes for minimum distribution requirements. |
| Traffic routing permissions | TUN mode or system services may need additional permissions. First confirm the client starts with a basic configuration, then enable features one at a time. |
Mihomo is a core that handles proxy protocols, rules, and DNS—not a desktop client with a graphical interface. These downloads are for users managing their own processes on servers, routers, and other systems. Most desktop and mobile users should choose one of the GUI clients above.
| System | Architecture and format | Use case | Download |
|---|---|---|---|
| Windows | AMD64 · ZIP | For 64-bit x86 hosts where you manage the configuration and process yourself. | Download AMD64 ZIP |
| Windows | ARM64 · ZIP | Core file for Windows ARM64 hosts. | Download ARM64 ZIP |
| macOS | Intel AMD64 · GZ | Command-line runtime for Intel Macs. | Download Intel GZ |
| macOS | Apple Silicon ARM64 · GZ | Native core for Apple silicon Macs. | Download ARM64 GZ |
| Linux | AMD64 · DEB | For compatible Debian-based hosts; install with the package manager. | Download AMD64 DEB |
| Linux | AMD64 · GZ | For 64-bit x86 systems where you set up the runtime directory yourself. | Download AMD64 GZ |
| Linux | ARM64 · GZ | For 64-bit ARM servers or compatible firmware. | Download ARM64 GZ |
| Linux | ARMv7 · GZ | For 32-bit systems with the ARMv7 instruction set. | Download ARMv7 GZ |
| Linux | MIPS softfloat · GZ | For devices where the byte order and soft-float ABI are known to match. | Download MIPS GZ |
ZIP and GZ files are archives; they don’t create a graphical interface. After extracting the files, prepare a configuration, set file permissions, and decide how to manage the process lifecycle. Linux service management differs from router firmware integration. Start the core in the foreground and review any errors before setting it to run at startup; this makes configuration issues easier to distinguish from service permission problems.
When managing a remote device, keep a way to regain access before changing routes, DNS, or transparent proxy settings. Don’t expose the control interface or proxy listener to untrusted networks. Open a listener to your LAN only when needed, and configure access restrictions at the same time.
Explore core families and protocol compatibilityThe installer puts the client on your device; the configuration tells the core how to handle connections. Check those separately to find problems more quickly than by reinstalling repeatedly.
After installation, open the client and make sure the interface loads before importing your subscription URL or local configuration. Get subscription URLs from a trusted configuration provider, and don’t post URLs containing personal subscription details in public forums. After importing, make sure the configuration is selected—not just listed.
Start by testing the connection in rule mode with one traffic-routing method. If a browser works but other apps don’t, check whether those apps use the system proxy, then see if you need TUN mode. Running multiple proxy tools at once makes troubleshooting harder.
Import a subscription and test the connection step by stepBefore migrating, save the original configuration, subscription URL, custom rules, and overrides. Turn off the old client’s system proxy and traffic routing, then quit the process to avoid port conflicts. A new client’s ability to read the same YAML doesn’t mean interface settings, per-app routing, or service permissions will migrate automatically.
If the new client reports an unsupported protocol or field, check the core’s capabilities and configuration format instead of repeatedly trying different installers. Updating the client, core, and subscription are separate tasks; completing one doesn’t mean the others are done.
How protocols, cores, and configuration formats fit togetherFrom choosing an installer to updating or migrating, check your environment first, then troubleshoot the configuration.
Choose your platform based on your device, then start with Clash Plus. Linux users can begin with Clash Verge Rev. Compare other clients if you need a specific interface or configuration feature. Downloads do not include a usable subscription, so you’ll need to import your own configuration after installation.
x64 and amd64 usually refer to the same 64-bit desktop architecture; arm64 is for a different processor architecture. In Windows, check System type in Settings > System > About. On a Mac, check the chip under About This Mac. On Android, choose the ABI supported by your device. If you’re unsure, consider the universal build of Clash Meta for Android.
The client reads your configuration and handles traffic; it doesn’t provide proxy service by itself. First import a compatible subscription or local configuration and make sure it’s enabled. Then choose a proxy group and, if needed, enable the system proxy, VPN, or TUN mode. Test the connection in a browser first, then troubleshoot other apps.
A file extension alone doesn’t tell you whether a configuration is compatible. Check whether the new client’s core supports the protocols, rules, and DNS fields in your configuration, and back up the original first. Interface preferences, service mode, and per-app routing usually need to be set up again in the new client.
Archived clients are mainly useful for recreating older setups and migrating configurations. For a new device, choose a client that’s still maintained. If you keep using older software, check system compatibility, core capabilities, and known issues. Compatibility with older configurations doesn’t mean support for every newer protocol.
Save your subscription URL, configuration files, custom rules, overrides, and any interface settings you need. Quit the old client before updating, and avoid running more than one traffic interception tool at a time. After the update, check that your configuration is enabled, that no listening ports conflict, and that the system proxy or TUN is set up as expected.