Check your device and processor, then download the matching client. New users can start with Clash Plus; choose the mihomo core if you need a command-line deployment.
Choose a platform to see available software. Each card lists download links first, followed by the best-fit use cases.
Open Settings → System → About to check your system type. The desktop installers below are x64 builds. On ARM devices, check application compatibility first; an x64 installer is not a native ARM app.
A good choice for setting things up through a graphical interface. After installation, import your subscription, confirm the configuration is enabled, then choose a rule mode and proxy group. For your first connection, enable only the proxy handling you need so you can verify each step.
clashplus.io
For users who want to manage subscriptions, rules, and connection logs in one desktop app. If prompted to enable service mode or TUN, first confirm that a basic system-proxy connection works. Then configure the service as prompted to keep troubleshooting focused.
A good fit if you use both desktop and mobile and want a similar experience on each. AMD64 is also commonly called x64. Even with the same subscription, check the mode, ports, and startup settings on each device—local settings don’t transfer automatically with the link.
Another Windows graphical client option. When switching, export custom rules and overrides from your current client, then import the subscription again. Don’t copy the entire configuration folder; clients may store settings differently.
Use this archived download to migrate an existing setup, reproduce an older configuration, or refer to legacy instructions. As the client is no longer maintained, compatibility with future system updates and configuration fields is not guaranteed. For new installations, choose an actively maintained alternative above. Save your subscription source before migrating.
| Check | Requirements and notes |
|---|---|
| Processor | This section provides x64 / AMD64 installers. They won’t work on 32-bit systems. |
| OS version | Use a supported 64-bit version of Windows. Check the selected client’s current release notes for its minimum version and runtime requirements. |
| Installation permissions | Installing services and enabling the TUN virtual adapter may require administrator approval. On managed devices, follow your organization’s policies. |
Open About This Mac from the Apple menu. Choose Apple Silicon if the chip is listed as an Apple M-series processor, or Intel if the processor is listed as Intel. Open the downloaded disk image and follow the installer prompts to move the app into Applications.
Separate ARM64 and x64 disk images are available. After installation, check that your subscription loaded, then approve any requested network permissions. If you’re switching from another client, disable its auto-start and system proxy first to prevent both clients from taking over when you next sign in.
clashplus.ioA good choice for users who want desktop configuration management and connection logs. The current Apple Silicon option is not a native ARM build, so check compatibility before installing. If macOS blocks the app, read the specific warning and verify the source and system requirements rather than disabling system security protections wholesale.
A good fit if you want a similar interface across your devices. AMD64 in the current filename means x64 architecture. After installation, import your configuration again; system proxy and permission settings from other devices won’t sync with it.
Kept for existing installations and migration needs. This client is no longer maintained, so check compatibility with current systems, permissions, and configuration requirements before use. For a new installation, choose one of the clients above. When migrating, keep your subscription URL and custom rules; there’s no need to retain the old app folder.
| Check | Requirements and notes |
|---|---|
| Chip type | Choose Apple Silicon or Intel, and check the actual download for an arm64, x64, or amd64 label. |
| System compatibility | Check the app’s current release notes for its minimum macOS version. Rosetta does not replace the minimum OS requirement. |
| Network permissions | System proxy, background services, and TUN have different permission requirements. Grant access only for the features you use. |
Most recent phones use ARM64, but check your device details to be sure. After downloading the APK, grant installation permission only to the browser or file manager you’re using. The first time you connect, Android will ask for VPN permission; confirm the app name before approving.
A good choice for getting started on an ARM64 phone. After installation, import your subscription, select a configuration, and connect. If the connection drops when the screen locks, check the app’s background activity and battery restrictions instead of reinstalling repeatedly.
clashplus.ioChoose from architecture-specific or universal builds. If you can’t identify your device’s architecture, consider the universal build, but still check the app’s minimum OS requirement. If Android won’t install it over an app with the same name, back up your configuration and check the signing source; don’t clear app data without checking first.
Choose the ARM64 or ARM 32-bit build to match your phone. Before connecting, disconnect other apps using Android’s VPN service. If the configuration imports but no usable proxy groups appear, check the subscription contents and compatibility; switching package architecture alone won’t fix it.
For users with a compatible configuration. Surfboard uses a different configuration format from Clash, so arbitrary Clash YAML files won’t necessarily import. Confirm the supported format with your configuration provider before installing to avoid trial and error across clients.
| Check | Requirements and notes |
|---|---|
| Processor | ARM64 corresponds to arm64-v8a; ARM 32-bit usually corresponds to armeabi-v7a. A universal build does not support every Android version. |
| System permissions | Installing an APK requires permission for the source app. Establishing a local VPN connection requires Android’s approval. |
| Background activity | Allow the background activity the app needs under your device’s battery settings. Also check whether another VPN app is connected. |
Install Clash Plus from the App Store. Check the store listing for compatible devices and system requirements, then open the app to import your configuration. When adding a VPN configuration for the first time, review the system permission prompt and confirm it was requested by the app you’re using.
After installation, get a subscription or configuration from a trusted source and confirm it imports before connecting. If iOS shows the VPN as connected but an app still can’t reach its destination, check the proxy group, rules, and DNS. The connection icon alone doesn’t prove that every request is being routed as expected.
clashplus.io| Check | Requirements and notes |
|---|---|
| System and device | Check the App Store listing for currently supported devices and the minimum OS version. |
| Connection permissions | Add the VPN configuration when prompted. Organization-managed devices may restrict this feature. |
| Configuration source | Get a subscription or configuration supported by the app. Installing a client does not provide proxy service. |
Check your distribution and processor before choosing a package format. Debian- and Ubuntu-based systems typically use deb; Fedora and other RPM-based distributions use rpm. The GUI clients below are for AMD64 devices with a desktop environment. For server deployments, see the core section.
For desktop users who want a tray icon, subscription management, and logs. Install through your distribution’s package manager where possible to handle dependencies. If the interface works but traffic isn’t being proxied, check the desktop system proxy and terminal environment variables separately; they may not share settings.
For users on Debian-based desktop distributions. Check that your distribution meets the app’s runtime requirements before importing a configuration. If the installer reports missing dependencies, save the full error and resolve them through your distribution’s repositories. Don’t mix in library files from other distributions.
| Check | Requirements and notes |
|---|---|
| Processor | This section provides AMD64 / x86_64 graphical clients, not ARM64 packages. |
| Distribution | Use cat /etc/os-release to check your distribution. The package format, system libraries, and desktop dependencies must all be compatible. |
| Permissions and environment | Installing software requires appropriate permissions. TUN needs additional network permissions; for a command-line-only environment, use the core. |
For server, router, and self-managed service deployments. The core parses configuration, matches rules, and forwards connections. It does not include a subscription management interface or automatically configure the desktop system proxy when started. Most users should choose a GUI client above.
| System | Architecture / 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 |
Name the executable mihomo and place it in your chosen directory. On Unix-like systems, make it executable. Save a trusted configuration to ~/.config/mihomo/config.yaml, then run the test command below. A successful test confirms that the configuration parses; it does not verify the remote service or routing results.
mihomo -d ~/.config/mihomo -t
mihomo -d ~/.config/mihomoWatch the logs in the foreground first, then consider running mihomo under a service manager. By default, proxy and control ports listen only on the local machine. For LAN access, configure the listen address, firewall, and authentication for your use case. Never expose the control interface directly to the public internet or share subscription credentials in public support posts.
Start with one verifiable connection, then add custom rules and advanced traffic handling.
Paste the link on the client’s configuration or subscription page. Once it updates, set that configuration as active. Subscription links often contain credentials, so protect them like passwords. After a successful import, check that proxy groups are available. If you see a configuration name but no usable content, check the subscription response first.
Start in rule mode so requests use the outbound selected by your configuration’s rules. A proxy group is a set of outbound options that rules can refer to; make sure the selected group has a usable option. Global mode can help with short-term troubleshooting, but it won’t fix incorrect rules. Direct mode does not route requests through a proxy.
On desktop, start with the system proxy. On mobile, approve the VPN connection when prompted. Open a target app and check the connection logs to see whether its requests reach the client, which rule matches, and which outbound is used. Terminal programs may ignore the system proxy; configure environment variables or the app’s own proxy settings separately.
Keep a working copy of your configuration. Change DNS, rules, or TUN settings one at a time and test each change before proceeding. If the device loses internet access after you quit the client, check for a leftover system proxy and restore your previous network settings. Don’t reset everything at once.
Start with a graphical client. It lets you import subscriptions, choose proxy groups, and toggle the system proxy. The mihomo core is mainly for server and router users who manage configuration files, startup options, and background services themselves.
Check your device’s processor architecture first. AMD64 and x64 usually refer to the same 64-bit architecture; ARM64 is a different one. If you can’t identify the architecture on Android, choose the universal build if available. Also check the minimum OS version.
In the current download list, some clients link to the same x64 file from both their ARM and Intel options. An ARM-labeled option does not guarantee a native ARM build. If you need a native ARM version, consider Clash Plus, which offers an arm64 file. Check the filename and app requirements before installing.
You’ll need a subscription link from a trusted provider or a compatible configuration file. This page provides software downloads, not subscription services. After importing your configuration, choose a rule mode and proxy group, then enable the system proxy or approve a VPN connection if prompted.
Back up your subscription source, custom rules, and essential settings first. Configuration folders and UI settings don’t always transfer between clients, so don’t overwrite the old folder directly. Quit the old client and disable its proxy handling before installing the new one. Then re-import your configuration and test the connection.
Check that the file downloaded completely, your OS meets the app’s requirements, the installer matches your device architecture, and your device’s management policy allows installation. On Linux, also check the package format and dependencies. Note the exact error, then follow the troubleshooting guide for your symptoms.