Choose your operating system, then check your processor architecture. Clash Plus, Clash Verge Rev, and FlClash packages are listed by platform. Server and router users can switch to the Mihomo core.
The graphical clients listed here are for x64. Open Settings → System → About and check your system type before downloading. If you’re new to Clash, start with Clash Plus. Import a configuration after installation, then enable the system proxy. Avoid running multiple clients that take over network traffic at the same time.
A good starting point for a first install: install the client, import a configuration, then follow the guide to check the rule mode, proxy groups, and system proxy. The client and subscription service are separate; the installer does not include a ready-to-use proxy configuration.
Quit any other client controlling the system proxy before installing. Official site: clashplus.io
For desktop users who want to manage subscriptions, configuration overrides, and the system proxy. After importing, check which configuration is active and review your proxy groups. Before enabling TUN mode, read the service mode and permissions guidance so you don’t mistake a permissions issue for a node problem.
See the Clash Verge Rev guide →
Keep a similar workflow across desktop and mobile. When switching clients, reimport your configuration and check proxy groups, DNS, and rules one by one. A shared subscription does not automatically sync local changes across platforms; save overrides separately.
Choose the installer for a standard setup. The ZIP package is for users who prefer to extract and manage the application directory themselves.
For users who prefer a different desktop layout for managing configurations and proxy groups. Export your existing configuration before switching clients, especially custom rules and references to external rule sets. After importing, check the logs for rule matches before changing DNS or traffic interception settings.
Don’t copy the entire application data directory from another client. Use the configuration import feature instead.
Kept for migrating older setups and comparing interfaces. Since development has stopped, compatibility with newer systems and configuration syntax is not guaranteed. Existing users should back up their configuration and test it in a maintained client. Archived software isn’t recommended for setting up a new device.
Configurations accepted by older clients may not support the full feature set of current mihomo configurations.
| Check | How to choose | Before installing |
|---|---|---|
| System and architecture | GUI packages here are x64. Use a Windows version that still receives system updates. | Check the system type and processor in System Information. Confirm compatibility separately for Windows on ARM devices. |
| Permissions and traffic control | The system proxy and TUN mode have different permission requirements. | Start the client normally and import your configuration first. Grant administrator permissions only when a required feature explicitly asks for them. |
| Runtime requirements | Check the current installer for minimum OS versions and required runtime components. | If a component is missing or the system is unsupported, record the full message instead of repeatedly reinstalling over the existing setup. |
Check your chip type under Apple menu → About This Mac. Choose a native ARM64 package for Apple Silicon and an x64 package for Intel. Some compatibility links in the current distribution list point to x64 files; the architecture shown below reflects the actual file. Don’t assume a link provides native support based on its label alone.
Separate installers are available for Apple Silicon and Intel. Open the DMG and follow the installer window to move the app to Applications, then launch it from there. Confirm the app opens successfully before importing a subscription; don’t confuse macOS installation warnings with configuration or connection errors.
Official site: clashplus.io
For users who need subscription management, rule overrides, and desktop network settings. Both architecture links currently point to the same x64 file. Apple Silicon users should confirm Rosetta and client compatibility before installing. For a native package, choose the ARM64 option above.
Before enabling TUN, make sure the required service is running and macOS permissions have been granted.
Use a similar configuration workflow to FlClash on other platforms. The current macOS downloads are AMD64 builds, not native ARM64 packages. When migrating, keep your subscription and overrides, then check the system proxy status after the first launch.
Check the system’s compatibility message for Apple Silicon requirements.
Kept for migrating older macOS setups and comparing configurations. The current x86_64 downloads both point to the same file. Upgrading macOS may cause compatibility issues. Keep a configuration you can roll back to, and move everyday use to a maintained client.
An archived package does not guarantee ongoing compatibility with current systems or core features.
| Device type | Package to choose | What to check |
|---|---|---|
| Apple Silicon | Choose a native ARM64 package first. | The x64 compatibility package may require Rosetta. Check the client and system messages for runtime support. |
| Intel Mac | Here, x64, AMD64, and x86_64 all refer to Intel 64-bit architecture. | Check the macOS versions supported by the installer. Current builds may not work on older systems. |
| System permissions | Standard app launch and network extension permissions are handled separately. | Read the specific instructions under System Settings → Privacy & Security. Don’t disable system-wide protections to install the app. |
For most newer devices, start with ARM64. Older devices may support only ARMv7; check your system information or use the universal package below if you’re unsure. On first connection, Android will ask for VPN permission. Usually, only one VPN service can be active at a time.
A good starting point for a first Android install: install the app, import a compatible configuration, check your proxy groups, then connect. When Android asks to set up a VPN connection, confirm the request comes from the client you’re using. The VPN icon in the status bar only means the service started; it doesn’t confirm that traffic is working.
Official site: clashplus.io
For Android users with configurations compatible with Clash Meta. Choose the APK for your device architecture, install it, then import and enable your subscription on the configuration page. If connections drop in the background, check battery optimization and background activity permissions before looking at the network or configuration. Change one setting at a time.
Choose the universal package if you’re unsure of your architecture. See the Android getting started guide →
A good fit if you use both desktop and Android. Import the subscription on each device, then set up app-level traffic routing, Android VPN permissions, and background activity separately on your phone. Disconnect any other VPN apps first to avoid services replacing each other and causing connection state to fluctuate.
The ARMv7 package is for compatible 32-bit environments, not the default choice for ARM64 devices.
For users with an existing Surfboard-compatible configuration. Surfboard is not a drop-in replacement for arbitrary Clash YAML files, so check that the configuration format and rule syntax are supported before importing. Don’t just change the file extension, and never submit a configuration containing private subscription URLs to an unknown conversion service.
After installation, use the in-app import instructions and error messages to check whether your configuration is supported.
| Check | Requirements and notes | What to do |
|---|---|---|
| Processor and OS | Check whether your device uses ARM64 or ARMv7. The current APK installer specifies the minimum Android version. | If you see an incompatibility warning, check the architecture and Android version before trying another install. |
| Install permission | When you open an APK from a browser or file manager, Android may ask you to allow installs from that source. | Allow installs only for the source you’re using, and revoke permission after installation if you wish. |
| VPN and background activity | A connection requires Android VPN permission. Reliable background operation depends on your device’s battery management settings. | Check whether another VPN service is active, then allow background activity if needed. |
Install Clash Plus from the App Store. Check the app’s listing for current system compatibility, device requirements, and store availability. You’ll need to provide a compatible configuration, import and enable it, choose a proxy group, and grant VPN permission before checking that connections work.
Use the App Store listing to review the app details and install it. After launch, import a configuration, then follow the in-app steps to allow a VPN connection. If you use another network traffic control tool, check which service is active first; the system VPN indicator doesn’t confirm that a subscription is working.
Client website: clashplus.io
| Check | Where to check | What to do |
|---|---|---|
| System and device support | Compatibility details on the App Store listing. | Check your device’s OS version against the requirements currently shown in the store. |
| VPN configuration permission | The system prompt appears when you connect for the first time. | Grant permission after confirming the request is from Clash Plus. If you declined, check your system settings. |
| Subscriptions and rules | Configuration and proxy group pages in the app. | Confirm the configuration imported successfully and is enabled, then check the selected proxy group and connection logs. |
The graphical packages listed here target AMD64 desktop systems. Choose DEB for Debian, Ubuntu, and other DEB-based distributions; choose RPM for distributions that use RPM packages. Headless servers and routers don’t need a GUI—switch to the Mihomo core section to manage configuration and services yourself.
Manage configurations, proxy groups, and connection settings from your Linux desktop. Use your distribution’s package manager to handle dependencies, then launch the app from the applications menu. If a program isn’t using the system proxy, check whether it reads desktop proxy settings before changing your configuration.
DEB and RPM are different package formats; changing a file extension won’t convert one to the other.
For desktop distributions based on DEB packages. When using multiple devices, import the subscription separately and check local DNS settings and rule overrides. TUN mode affects permissions and routing; first confirm a standard proxy connection works, then enable additional system-level features as needed.
Use your distribution’s package manager to resolve dependency errors. Avoid manually copying library files from other systems.
| Check | Requirements and notes | How to check |
|---|---|---|
| Processor architecture | The GUI packages here are AMD64 / x86_64. | Run uname -m. Don’t use an AMD64 package on an ARM device. |
| Distribution package format | Choose DEB or RPM based on your distribution. | Check your distribution first, then use its package manager to install the app and handle dependencies. |
| Desktop environment and permissions | The GUI requires a compatible desktop environment; TUN requires the appropriate network permissions. | Start the app normally first. Resolve service or permission errors one at a time, following the prompts. |
For users running servers, routers, or proxy processes they manage themselves. Most users should install one of the GUI clients above. The standalone core requires you to provide config.yaml, a working directory, and a service startup method. Successfully extracting the archive does not connect system traffic.
| System | Architecture and use | Format | Download |
|---|---|---|---|
| Windows | AMD64, for 64-bit Intel / AMD systems. | ZIP | Download AMD64 |
| Windows | ARM64, for Windows on ARM. | ZIP | Download ARM64 |
| macOS | AMD64，Intel Mac。 | GZ | Download Intel |
| macOS | ARM64，Apple Silicon。 | GZ | Download Apple Silicon |
| Linux | AMD64, for DEB-based distributions. | DEB | Download AMD64 DEB |
| Linux | AMD64, for managing the binary and service startup yourself. | GZ | Download AMD64 GZ |
| Linux | ARM64, for 64-bit ARM devices. | GZ | Download ARM64 |
| Linux | ARMv7, for compatible 32-bit ARM environments. | GZ | Download ARMv7 |
| Linux | MIPS softfloat; check your firmware’s endianness and ABI. | GZ | Download MIPS softfloat |
Extract GZ files first. On Unix-like systems, make the binary executable. Put the configuration and any required rule files in a clearly defined working directory. Run the core in the foreground and review any startup errors before setting it up as a service. To test a configuration, run mihomo -t -f config.yaml; use the actual binary path for your installation.
The core can load rules and establish connections, but it won’t automatically configure proxy settings for every app. System proxy, app-level proxy, transparent proxying, and TUN are different ways to route traffic. Router setups also involve routing, DNS forwarding, and firewall rules. Change one thing at a time and keep your original network settings so you can roll back.
The installer installs the app; the configuration determines where connections go. Verify the basics first, then enable more advanced traffic control settings.
Compare Clash clients →Before upgrading or switching clients, export your current configuration and save custom rules, overrides, and any important interface settings. Remote subscription updates typically replace only the subscription content; whether local changes are retained depends on the client’s configuration management. Don’t copy an old app’s entire data directory into the new client’s folder.
Prepare a subscription URL you’re authorized to use or a local configuration file. Import it on the Configuration page and set it as active. Open the Proxy page to check your proxy groups, start in rule mode, then enable the traffic routing method suited to your system. If importing fails, check the URL, authorization, and network instead of repeatedly reinstalling the client.
Check the logs after visiting a site. If there’s no corresponding connection, check whether the app is routed through the proxy. If there is a connection but the wrong policy is used, review the matched rule and proxy group. If the rule matches but the connection still fails, check the destination and DNS. The system proxy doesn’t cover every app, and TUN isn’t a universal fix.
Clash system proxy settings → Troubleshooting steps →Check the platform, architecture, and package format before troubleshooting configuration or network issues.
Start with Clash Plus on Windows, macOS, Android, or iOS, and Clash Verge Rev on Linux. Check your operating system and processor architecture before choosing a package. For interface and configuration management differences, see the client comparison →
ARM64 and x64 target different processor instruction sets, so they aren’t interchangeable based on the operating system alone. Android’s ARMv7 package is for compatible older devices; a universal package can help when you don’t know your device’s architecture, but check the installer’s requirements. On Apple Silicon, the macOS x64 package may require Rosetta and is not a native ARM64 build.
A client manages configurations, matches rules, and controls connections; it does not provide a proxy service. You’ll need a subscription link you’re authorized to use or a compatible configuration file. Import and enable it on the configuration page, then choose a proxy group. Don’t share subscription URLs publicly.
Make sure the download finished and the file extension matches the button description. Then check available disk space, system architecture, and any installer messages. Retry an interrupted download. If your system blocks the installer, find out why rather than disabling security protections. If installation still fails, note your OS version, package name, and error message, then follow the Troubleshooting guide.
Clash for Windows and ClashX Meta are mainly useful for migrating older setups or comparing compatibility. Discontinued clients may not support newer OS changes or configuration syntax. For new devices, choose a currently maintained client. Back up your configuration and custom rules before migrating.
Most desktop and mobile users only need a graphical client, which manages its supported core. The standalone Mihomo package is mainly for servers, routers, or environments where you manage the process yourself; you’ll need to set up the configuration, permissions, and service startup manually.