Choose your operating system, then check the processor architecture. Graphical clients are for desktop and mobile; Mihomo core builds are for environments where you deploy and manage the service yourself.
Check your operating system
The package must match your OS
Check your CPU architecture
Choose x64 or ARM64
Prepare a subscription or configuration
The app and proxy service are configured separately
This page brings client downloads together in one place. Buttons identify the package type and target architecture; check the package details for exact compatibility. If this is your first time, configure and test one client before migrating or switching interfaces. This helps avoid multiple apps changing your system proxy at once.
The downloads here are x64 graphical clients. Open Settings → System → About to check your system type. Windows on ARM compatibility depends on your Windows version; an x64 installer is not a native ARM64 app. After installation, import your configuration and check the logs before enabling the system proxy or TUN as needed.
A good starting point for users who want to import a configuration and manage proxy groups in a graphical interface. Choose the Windows x64 installer. Quit any other client managing the system proxy before installation to reduce port conflicts.
Official website: clashplus.io
For users who want desktop configuration management, rule overrides, and service mode. Installing the app and granting service permissions are separate steps. First confirm that a standard system proxy connection works, then set up virtual network interface routing if needed.
Built with Flutter and powered by the mihomo core for managing proxy connections. The installer is the simplest choice for first-time users. The ZIP archive is useful if you prefer to manage the app directory manually, but the system must still provide the required dependencies and permissions.
Another Clash desktop interface for users with an existing configuration who want to compare workflows. When migrating, import the original subscription first, verify rules and proxy groups, then move local overrides over one at a time.
Archived client kept for migrating older configurations and recreating legacy environments. Not recommended as the default choice for new devices. New protocols, configuration fields, and system permission models may not be supported. Keep a copy of your original configuration before migrating.
| Check | Requirements and guidance | Where to check |
|---|---|---|
| OS and architecture | Use a supported 64-bit Windows environment where possible. This section provides x64 packages. | Settings → System → About |
| Installation permissions | Installing a service or enabling TUN may require administrator approval. | Approve only explicit permission prompts from Windows |
| Runtime dependencies | If a runtime library or WebView component is missing, follow the installer’s instructions. | Keep the exact error message to distinguish a missing dependency from an architecture mismatch |
| Existing proxy apps | Only one client should manage the system proxy and TUN at a time. | Quit the old client before launching the new one |
Check your chip in Apple menu → About This Mac. Apple Silicon and Intel downloads are listed separately, but some links in the current release list point to the same x64 file. Check the package’s actual architecture after downloading. To run Intel apps, set up Rosetta if macOS prompts you to.
Choose a DMG for your Mac’s chip. Open the disk image, drag the app to Applications, and launch it from there before importing your configuration. Avoid running the app directly from the mounted disk image.
Official website: clashplus.io
Includes desktop configuration and rule management. The Apple Silicon and Intel links currently point to x64 files; they are not native ARM64 builds. Apple Silicon users should check whether translation is supported on their device.
A good option for users who want a familiar interface across platforms. Both chip options currently point to an amd64 disk image. If the app won’t launch, check the architecture and macOS prompts first; changing subscriptions won’t fix an app startup issue.
Archived macOS menu bar client, kept as a reference for migrating older setups. Both links currently provide an x86_64 build. Importing an old configuration doesn’t guarantee every field is supported; check the active rules and DNS behavior after migration.
| Check | Requirements and guidance | Where to check |
|---|---|---|
| Chip | Identify whether your Mac uses Apple Silicon or Intel; compatibility depends on the package’s actual architecture. | Apple menu → About This Mac |
| macOS version | Minimum version requirements vary by client. A DMG opening successfully doesn’t confirm compatibility. | Check the installer and app startup prompts |
| App location | Copy the app to Applications before launching it. | Finder → Applications |
| Network permissions | Grant permission only to the network extension or helper service you plan to use. | Relevant permission prompts in System Settings |
Most recent Android phones use ARM64, but check the ABI supported by your device. ARMv7 is for devices that still support 32-bit apps; x86_64 is common on some emulators. Installing an APK and authorizing a VPN connection are separate steps. After installation, import your configuration in the client.
ARM64 APK available. Grant installation permission only to the browser or file manager you’re using, and revoke it afterward if you like. When Android asks for VPN permission on the first connection, verify the app name before approving.
Official website: clashplus.io
Choose ARM64, ARMv7, or the universal package based on your device’s ABI. The universal package includes multiple architectures and is usually larger. If you know your device’s architecture, choose the matching build to avoid unnecessary downloads.
Keeps the familiar Flutter client configuration and proxy group interface. If connections drop in the background, check battery optimization and background activity limits. Background disconnections aren’t always caused by a subscription or proxy node issue.
Provides a universal Android package. Surfboard uses a different configuration format from Clash YAML, so an existing Clash subscription may not be compatible. Check with your provider for a supported format before installing.
| Check | Requirements and guidance | Where to check |
|---|---|---|
| Device ABI | Choose an ARM64, ARMv7, or x86_64 package supported by your device. | Device specifications or a trusted system information tool |
| Android version | Minimum Android version depends on the client build. Matching the architecture doesn’t mean your Android version is supported. | Settings → About phone → Android version |
| Install permission | Grant permission specifically to the app opening the APK. | Settings → Install unknown apps |
| Background activity and VPN | Usually, only one VPN app should manage the connection at a time. | System VPN and battery settings |
Install Clash Plus from the App Store. Check the listing for current device compatibility, system requirements, and price. After installation, prepare a working configuration and follow the app’s prompts to authorize the network connection.
For iPhone and other devices listed as compatible on the App Store page. Check the current requirements in the listing before installing. Installing the app doesn’t configure a proxy service; you’ll still need to import a subscription you’re authorized to use and select an outbound.
Official website: clashplus.io
| Check | Requirements and guidance | Where to check |
|---|---|---|
| System and device | Check the compatibility list on the App Store page. | Store listing → Compatibility |
| Installation and updates | Install and update the app through the App Store. | App Store → App listing |
| Connection permission | Approve the system network configuration prompt when connecting for the first time. | Connection action in the app and system permission prompt |
| Configuration source | Use a configuration you’re authorized to access. Don’t share subscription URLs publicly. | Client configuration settings |
If importing succeeds but the connection fails, first confirm that the configuration is selected, then check the proxy group and system VPN status. App installation, configuration updates, and remote connectivity are separate steps. The App Store opening successfully doesn’t mean the subscription service is reachable.
Choose a GUI client for a desktop environment; headless servers can use the Mihomo core. Run uname -m to check your architecture, then choose a package format for your distribution. All desktop packages in this section are AMD64 and aren’t suitable for ARM64 devices.
Choose DEB for Debian, Ubuntu, and compatible distributions; choose RPM for distributions that use RPM package management. Let your distribution’s package manager handle dependencies. After installation, launch the app from the applications menu and verify the GUI and configuration import.
Provides a Flutter desktop interface and tools for managing mihomo configurations. DEB is the primary option here, with RPM and AppImage also available. AppImage still depends on the system environment; it isn’t a self-contained package for every distribution.
| Check | Requirements and guidance | How to check |
|---|---|---|
| Processor architecture | GUI packages in this section are for x86_64 / AMD64. | uname -m |
| Distribution | Choose DEB or RPM based on your distribution and package manager. | cat /etc/os-release |
| Graphical dependencies | Requires a compatible desktop session and runtime libraries. Use the core on headless systems. | Launch from a terminal and keep the full dependency error |
| TUN permissions | Requires a virtual network interface and appropriate network permissions; the exact requirements depend on the client’s service implementation. | Check the service status and /dev/net/tun |
Whether the system proxy works also depends on the desktop environment and whether apps honor proxy settings. Command-line tools may not use the desktop proxy. If a browser connects but a terminal app doesn’t, check that tool’s proxy environment variables before switching packages.
For users managing services on servers, routers, and similar systems. The core doesn’t include a configuration interface; you’ll need to prepare the YAML file, working directory, access permissions, and log output yourself. Desktop and mobile users should use a graphical client above.
Check the operating system, CPU architecture, and firmware ABI before choosing a file. For MIPS devices, also verify endianness and floating-point ABI; the router brand or product family alone isn’t enough to determine compatibility.
| Operating system | Architecture | Format and notes | Download |
|---|---|---|---|
| Windows | AMD64 | ZIP · 64-bit x86 | Download AMD64 ZIP |
| Windows | ARM64 | ZIP · 64-bit ARM | Download ARM64 ZIP |
| macOS | Intel AMD64 | GZ · Compressed executable | Download Intel GZ |
| macOS | Apple Silicon ARM64 | GZ · Compressed executable | Download Apple Silicon GZ |
| Linux | AMD64 | DEB · Install with a package manager | Download AMD64 DEB |
| Linux | AMD64 | GZ · Manual deployment | Download AMD64 GZ |
| Linux | ARM64 | GZ · 64-bit ARM | Download ARM64 GZ |
| Linux | ARMv7 | GZ · 32-bit ARM | Download ARMv7 GZ |
| Linux | MIPS softfloat | GZ · MIPS big-endian, soft-float | Download MIPS GZ |
| Check | Requirements and guidance |
|---|---|
| Runtime environment | The operating system and binary architecture must match. For containers, also check host capabilities and device mappings. |
| Configuration file | Prepare a readable YAML file and data directory. Test the configuration before starting it with a service manager. |
| Network permissions | Ordinary proxy listening and TUN require different permissions. Grant only those needed for the features you use. |
| Listening address | Bind to the loopback address for local use only. For LAN sharing, configure authentication and firewall rules as well. |
Extracting a GZ file gives you an executable; it doesn’t register a system service. First test the configuration from a known data directory and confirm that referenced files are readable. Then configure a persistent service. The commands below assume the file has been extracted on Linux and named mihomo:
chmod +x ./mihomo
./mihomo -v
./mihomo -t -d ./profile
./mihomo -d ./profile./profile is a data directory you create yourself and should contain a prepared config.yaml. A successful test means only that the configuration can be parsed; it doesn’t guarantee a connection to the remote service. Before setting up a service, check listening ports, DNS routing, and which rules are actually matched. See the configuration reference for field details.
The download is an app or core, not a ready-to-use proxy service. Prepare a subscription URL or local configuration you’re authorized to use, import it, and confirm that the client has selected it. If importing fails, check the response and configuration format first; reinstalling repeatedly won’t fix subscription parsing errors.
Subscription URLs may contain access credentials. Hide sensitive parts of the URL before sharing log screenshots. Keep a restorable copy of the original configuration rather than relying only on temporary, merged content inside the client.
A system proxy relies on apps honoring system settings. TUN routes eligible traffic through a virtual network interface. When setting things up for the first time, verify the connection using one method before adding other features. You don’t have to enable both, and having both intercept traffic won’t necessarily fix a connection problem.
If a browser works but another app doesn’t, first check whether that app uses the system proxy. If nothing connects, check the selected outbound, DNS, and logs. See the full Getting Started guide for step-by-step instructions.
Note your subscription source, mixed port, rule overrides, DNS, and TUN settings. Quit the old client before installing or running the new version. Updating one client and migrating to another are different processes; don’t assume they share data directories or settings storage.
After migrating, check proxy group names, custom rule order, and the merged configuration in sequence. Opening the interface isn’t enough to confirm a successful migration; test that both direct and proxied destinations are routed as expected.
If the app won’t start, check the OS version, architecture, and dependencies. If configuration import fails, check the URL and format. If it won’t connect, check DNS, the outbound, and ports. Separating installation errors from network issues helps avoid confusion from repeatedly switching packages.
If a port is already in use, check whether the old app is still running in the background. After changing mixed-port, update the proxy address in any browsers, terminals, or other apps configured manually. See Choosing a Client for client comparisons.
Desktop and mobile users should start with a graphical client, which lets them import configurations, choose proxy groups, and view logs. The Mihomo core is for server and router users who manage configuration, startup options, and services themselves; downloading the core alone does not provide a client interface.
AMD64 and x64 usually refer to the same 64-bit x86 architecture. ARM64 is 64-bit ARM, while ARMv7 is 32-bit ARM. Check both your operating system and processor architecture. The universal Android package can help if you’re unsure of your device’s ABI, but it won’t resolve an unsupported Android version.
Download links follow the available release files, and some macOS architecture options currently point to the same x64 or amd64 file. A button label doesn’t guarantee a native ARM64 build. Apple Silicon users should verify the package architecture and, if supported by macOS, run x64 apps with Rosetta.
Export a restorable configuration and note your subscription source, override rules, mixed port, DNS, and TUN settings. Quit the old client before installing the new one. Clients use different data directories and merge rules, so import the original configuration when migrating rather than replacing the entire app data directory.
The installer provides the client app, not a proxy service. Import a subscription or configuration you’re authorized to use, select an available outbound in a proxy group, then check whether the system proxy or TUN is active. If it still fails, review logs for configuration parsing errors, DNS issues, connection timeouts, and port conflicts—in that order.
Clash for Windows and ClashX Meta are listed only for legacy compatibility and migration reference. For new devices, choose a maintained client. Older apps may not support newer protocols, system permission models, or configuration fields; successful installation alone doesn’t make them suitable for long-term use.