Client downloads · Choose your platform
Check your operating system and processor architecture before choosing a client. Use a GUI for everyday desktop use; choose the Mihomo core for servers and routers.
Before you download
Check your processor in your computer’s system information or your phone’s device information. x64 and AMD64 usually refer to the same 64-bit x86 architecture and aren’t tied to a processor brand. ARM64 is a different architecture, so don’t choose a build based only on the words “64-bit.”
The client reads your configuration and routes traffic; installing it does not create proxy nodes. Have an existing subscription or local configuration ready, then import it using the setup guide. Subscription URLs may contain credentials, so don’t include them in public screenshots or shared documents.
Select an operating system to see its installers. Each card lists download links first, followed by use cases and installation tips.
The desktop builds below are primarily for x64. New users can start with Clash Plus. If you plan to enable TUN, install and authorize the required service as described by your client.
A good fit if you want a GUI for importing subscriptions, choosing proxy groups and using rules. After installation, add an existing configuration and make sure its proxy groups appear before enabling the system proxy. Check the TUN setup guide if you need to route traffic from more apps. There’s no need to change every network setting on your first launch.
A good fit if you need desktop configuration management and overrides. If you already have a subscription, import it and verify the connection before setting up service mode or launch at startup. If Windows Firewall prompts you, check the app’s source and which networks it needs; don’t allow access to every network by default.
A good fit if you prefer a consistent experience across platforms. Use the installer for everyday desktop use. For the ZIP, extract all files to a permanent folder before launching; don’t run the app from the archive preview. When switching clients, import your configuration first—interface settings may not carry over.
A good fit if you already have a Clash configuration and want to try a different desktop interface. Before switching, back up your subscription, override files and port settings, then quit the old client. Options may have different names in the new interface; refer to the actual configuration fields and logs rather than relying on button positions from the old one.
Kept for reproducing legacy environments and migrating existing configurations. This client is no longer maintained; for new installations, choose a maintained client above. Its older core may not support newer protocols or configuration fields. If an import fails, check compatibility instead of repeatedly reinstalling the same archived build.
| Item | Download and installation guidance |
|---|---|
| System requirements | For a new installation, use a Windows 10 or 11 release that still receives updates. Check the selected client’s installer for its minimum version. |
| Processor architecture | The Windows GUI builds on this page are x64. For Windows on ARM, check app emulation and driver compatibility separately. |
| Network permissions | The system proxy and TUN are different ways to route traffic. TUN may require administrator access, a background service and a virtual network adapter. |
If your browser connects after installation but other apps don’t, first check whether those apps use the system proxy. Don’t assume the installation failed; see the TUN guide to check which traffic is covered.
First, check your chip in About This Mac. Clash Plus offers separate builds for Apple silicon and Intel. The other cards list the available downloads and clearly flag cases where both buttons share the same x64 file.
Choose the DMG for your chip. Open it, drag the app to Applications, then launch it from there. Grant any required permissions on first launch, then import an existing subscription. If you later need traffic routing features, enable them one at a time as prompted; system proxy and network extension permissions are separate.
A good fit if you need to manage subscriptions and override rules on your desktop. If prompted to install a service or grant Keychain or network permissions, verify where the prompt came from and grant only what’s needed. Quit any old menu bar process before upgrading; an existing service may hold a port and prevent the new app from routing connections.
A good fit if you want a similar workflow across devices. After installing the DMG, launch the app from Applications, import your configuration and check the proxy groups. AMD64 in the current filename means x86-64; Apple silicon users should check compatibility before installing. Don’t assume the build is native based on the download option’s label.
For reference when maintaining an existing menu bar workflow or migrating an older configuration. This client is no longer maintained; consider one of the clients above for a new device. OS upgrades may cause permission or compatibility issues, and archived builds aren’t kept current with new releases. Keep a copy of your original configuration and check proxy group and rule behavior after migrating.
| Item | Download and installation guidance |
|---|---|
| macOS version | Check the installer’s compatibility notes for your macOS version. Minimum requirements vary by client. |
| Chip | Choose the matching ARM64 build for Apple M-series Macs and x64 for Intel Macs. See the note above for download options that share an x64 file. |
| Installation location | Move the app to Applications, eject the DMG, then launch it. Follow the prompts if the app needs service or network permissions. |
If macOS says the app is “damaged” or can’t be opened, first verify the download source, system compatibility and whether the file downloaded completely. Don’t disable system security entirely. For permission steps, see the user guide.
Most recent phones use ARM64, but check your device information to be sure. Older ARM devices may need an ARMv7 build. If you’re unsure, Clash Meta for Android offers a universal package.
A good fit for importing subscriptions, choosing proxy groups and using rules on your phone. If your browser or file manager asks for permission to install the app, follow the system prompt. On first connection, confirm the app name before granting VPN permission. Import a subscription before connecting so an empty configuration isn’t mistaken for a network issue.
A good fit if you already have a Clash configuration and want to manage configuration files on Android. If you know your device architecture, choose the matching build; universal packages are usually larger. After installation, add a remote subscription or import a local file, then make sure the configuration is selected. Downloading a file to your phone doesn’t enable it in the client.
A good fit if you’re used to FlClash’s desktop workflow. If installation fails with a parsing error, check your device architecture and Android version. If the connection drops frequently, check battery optimization, background activity restrictions and VPN conflicts. Don’t run two apps that both request VPN access; the later one may replace the existing connection.
A good fit if you already have a compatible Surfboard configuration. Its format differs from Clash YAML, so changing the file extension won’t make it compatible. Before installing, check whether your subscription provider offers the required format or read the conversion guide. After conversion, verify proxy groups, rules and protocol support, and keep the original configuration for comparison.
| Item | Download and installation guidance |
|---|---|
| Identify your architecture | arm64-v8a is ARM64; armeabi-v7a is for older ARM devices. Choose a build supported by your device. |
| Install permission | Grant install permission only to the app you’ll use to open the APK. You can revoke it after installation if you like. |
| Background operation | Connecting requires Android VPN permission. On devices with strict background limits, also check battery optimization and background activity settings. |
If an update reports a signature mismatch, don’t rush to uninstall. Export your configuration and check where the original app came from first. Uninstalling usually deletes app data, so you’ll need to import your subscription and restore settings again after reinstalling.
Check Clash Plus compatibility, app details and release notes on the App Store before installing.
A good fit for importing compatible subscriptions and routing traffic by rule on iPhone or iPad. After installation, add a subscription or local configuration and confirm the proxy groups have loaded. Then follow the system prompt to add a VPN configuration. For the first connection test, keep the default rule mode; verify the connection before changing DNS or app-specific settings.
| Item | Download and installation guidance |
|---|---|
| Device compatibility | Check the current App Store listing for minimum iOS version and supported devices. |
| Network permissions | On first connection, follow the system prompt to add a VPN configuration and make sure the app you just installed is the one requesting access. |
| Configuration | Prepare a compatible subscription or local configuration in advance. Installing the app and getting a subscription are separate steps. |
If the list is empty after importing a subscription, check the configuration format, URL expiration and fetch result. A VPN indicator in the system status means traffic routing is active; it doesn’t confirm that every rule or proxy node works. Check the selected proxy group and test actual connectivity.
For a desktop, start with a GUI client. Choose DEB for Debian or Ubuntu and RPM for Fedora and similar distributions. The desktop builds below target AMD64.
A good fit for managing subscriptions and rules on a Linux desktop. Choose the package format for your distribution and let the system installer or package manager handle dependencies. If the app installs but won’t open, check its startup logs and desktop runtime dependencies; a GUI launch error doesn’t necessarily point to a core or subscription issue.
A good fit for Debian-based desktops if you prefer FlClash’s workflow. Check your system architecture before installation, then import a configuration on first launch and confirm the listening port. Terminal programs may not use the desktop system proxy; configure proxy environment variables according to each tool’s support. A working desktop app doesn’t mean every command is routed through the proxy.
| Item | Download and installation guidance |
|---|---|
| Architecture | Run uname -m to check your machine architecture; x86_64 matches the AMD64 desktop packages in this section. |
| Distribution | Choose a package for your distribution’s package manager. Follow the installer’s output for dependency and runtime requirements. |
| Runtime environment | GUI clients require a desktop session. For SSH servers, containers and routers, see the Mihomo core downloads. |
For long-running background use, first make sure the service account can read the configuration directory, then configure a system service. TUN permissions differ from those needed to listen on a local proxy port. Grant only what your deployment requires; don’t run your entire desktop session with elevated privileges.
For servers, routers and command-line deployments. The core has no desktop interface for managing subscriptions, so most users should choose a GUI client from the platform sections above.
| System | Architecture and format | Download |
|---|---|---|
| Windows | AMD64 · ZIP | Download AMD64 ZIP |
| Windows | ARM64 · ZIP | Download ARM64 ZIP |
| macOS | Intel · AMD64 · GZ | Download Intel GZ |
| macOS | Apple silicon · ARM64 · GZ | Download ARM64 GZ |
| Linux | AMD64 · DEB | Download AMD64 DEB |
| Linux | AMD64 · GZ | Download AMD64 GZ |
| Linux | ARM64 · GZ | Download ARM64 GZ |
| Linux | ARMv7 · GZ | Download ARMv7 GZ |
| Linux | MIPS-softfloat · GZ | Download MIPS GZ |
Extract ZIP and GZ files first. On Unix-like systems, make the binary executable and prepare a dedicated configuration directory. Place a valid config.yaml in the target directory, then use the following command to check it. This assumes the current directory contains an executable named mihomo.
chmod +x ./mihomo
./mihomo -t -d ./config
./mihomo -d ./configA successful configuration check doesn’t mean every external resource is ready. Rulesets, geodata and remote subscriptions may still be affected by network access or file paths. Run the core in the foreground first and check its output, ports, rules and DNS behavior before creating a systemd service or firmware startup task. Don’t hide all logs from the start.
If your configuration exposes an external control interface, restrict its listening address and set access controls. For local use, there’s no need to expose the management port to your LAN or the public internet. See the user guide for permissions, directories and background operation.
| Check | Requirement |
|---|---|
| CPU and OS | The binary architecture and operating system must match the device. For routers, also check firmware compatibility. |
| Configuration and data directories | The service account must be able to read the configuration and, as needed, write caches, rulesets and databases. |
| Network permissions | Local proxy ports, TUN and routing changes require different permissions. Configure access for the mode you actually use. |
Separate installation, subscription and traffic-routing issues to troubleshoot more directly.
Configuration source
Add a subscription URL and update it. Confirm that nodes and proxy groups appear, then select the configuration you want to use. Direct edits to a subscription file may be overwritten on refresh; use the client’s override or merge features for persistent customizations.
View the subscription import steps →Connection mode
Rule mode is a good starting point for everyday use. The system proxy mainly affects apps that follow system proxy settings; TUN involves a virtual network adapter, routes and DNS. Test one traffic-routing method first, then troubleshoot apps that aren’t covered. Avoid changing several switches at once.
System proxy vs. TUN →Ongoing maintenance
Before upgrading, back up your subscription source, custom rules and ports, then quit the old client before installing the new one. Don’t let multiple proxy apps manage the system at the same time. If something goes wrong, note the specific error in the logs before deciding whether to change the configuration, fix permissions or roll back.
Troubleshoot subscriptions and connections →Choose and install a build first, then set up your connection.
Start with Clash Plus for Windows, macOS, Android and iOS; for Linux, consider Clash Verge Rev. If you already have a working client, check subscription compatibility and required features before switching. Most desktop users should choose a GUI client rather than download the Mihomo core separately.
AMD64 and x64 usually refer to the same 64-bit x86 architecture, used by most Intel and AMD PCs. ARM64 is for compatible ARM devices. For Android, check whether your device supports arm64-v8a; older devices may need armeabi-v7a. If you’re unsure, check your device’s system information or choose the universal build of Clash Meta for Android.
Check your chip in About This Mac. Clash Plus offers separate Apple silicon and Intel builds. In the current listings, both Mac download buttons for Clash Verge Rev, FlClash and ClashX Meta point to the same x64 file. Apple silicon users should check Rosetta and app compatibility; for a native ARM build, start with Clash Plus.
The installer provides the client, not working proxy nodes. After installation, import a compatible subscription you already have or a local configuration, choose a proxy group, then enable the system proxy or TUN mode if needed. If a subscription fails, check that the URL is complete, that it hasn’t expired, and review the client logs.
Export your current configuration or back up its directory. Note your subscription source, overrides, DNS settings and ports. Quit the old process before installing the new version. Avoid running multiple clients that manage the system proxy or TUN on the same device. To roll back, restore your configuration from the backup.
First confirm that the subscription loaded and that you selected a working proxy group. Then check that the rule mode, system proxy and ports are set consistently. For TUN mode, check service permissions, the virtual network adapter and DNS settings. Quit other proxy apps temporarily, review the logs, and change one setting at a time.