Clients / Installer formats / Processor architectures
Choose your operating system, then select a client and architecture.
Clash Verge Rev is for desktop. For mobile, choose a Clash ecosystem client below. Check your device’s processor architecture before downloading, then import a subscription or local YAML configuration after installation.
First-time setup: See the subscription import guide →Install one client per device. Before switching, quit the current app and turn off its system proxy to avoid port conflicts and overlapping network routing.
The desktop installers below are primarily for x64. Check System type under Settings > System > About, and make sure your processor and OS are compatible before downloading. After installation, open the client from the Start menu. Import a subscription before enabling network routing.
A good choice for managing subscriptions and proxy settings through a graphical interface. Run the installer and follow the prompts. On first launch, import your configuration, then choose a proxy group.
When switching from another client, keep your subscription URL and local rules. Product details: clashplus.io.
Powered by the Mihomo core, with pages for configuration, proxies, connections, rules, logs, and settings. For local overrides, rule-based routing, or TUN mode, follow the step-by-step Advanced Config guide on this site.
If the window doesn’t load properly, check that the WebView2 runtime is available on your system. TUN services and standard system proxies have different permission requirements.
A good fit if you want a similar interface across desktop and mobile. After importing a subscription, check the active configuration, proxy mode, and selected proxy group before connecting.
AMD64 and the commonly used x64 label refer to the same architecture; the processor doesn’t have to be made by AMD.
Includes a desktop interface for managing configurations and proxies. Choose it based on your preferred interface, after confirming that your subscription is compatible.
Quit the current client before switching. Don’t overwrite another client’s interface settings or data directory.
Kept for migrating legacy setups and checking compatibility with existing configurations. This project is no longer maintained; for new installations, choose a client above that suits your current needs.
Older cores may not recognize newer configuration fields. If parsing fails, check whether the protocol and fields are supported rather than repeatedly reinstalling.
| Check | What to look for | After installation |
|---|---|---|
| System and architecture | Windows 10 or 11 is recommended. The installers here are primarily for x64; check the client’s release notes for its minimum supported version. | On ARM devices, confirm that Windows can run the relevant application through compatibility support. |
| Runtime | Clash Verge Rev requires a working WebView2 runtime for its interface. Installing services may require administrator privileges. | Test the standard system proxy and TUN separately. First confirm that a basic connection works. |
| Ports and configuration | Check the actual mixed port in the client settings. Don’t reuse a port from another client. | Enable the configuration and check the logs before setting up a proxy in individual apps. |
Open About This Mac from the Apple menu to check your chip. Apple Silicon and Intel Macs use different processor architectures. After downloading, open the DMG, move the client to Applications, and launch it from there.
Choose an ARM64 or x64 installer to match your chip. After importing a subscription for the first time, check that the configuration is enabled, then set up the proxy mode your apps need.
Quit the app before updating. Product details: clashplus.io.
Manage Mihomo configurations, rules, and connections through a desktop interface. The system proxy works with apps that support proxy settings. To route other traffic, configure TUN using the guide.
The fallback file currently available is x64. Before installing service components, check the system permission prompts and verify the source of the app.
Use a familiar subscription management workflow across devices. Once the configuration imports, check your proxy groups and rules mode before enabling network routing.
The fallback file currently available is AMD64. If you have connection issues, check architecture compatibility before reviewing the configuration.
Useful for checking legacy menu bar workflows and existing configurations. This project is no longer maintained, and may not support all current Mihomo configuration fields.
The fallback file currently available is x86_64. When migrating, keep your standard YAML file and subscription URL; don’t copy internal app data directly.
| Check | What to look for | What to check |
|---|---|---|
| Chip | Apple M-series chips are Apple Silicon; choose x64 for Macs with an Intel processor. | The download link label doesn’t guarantee the file’s architecture. Check the notes on the actual files in this section. |
| OS version | Minimum macOS versions vary by client. Check the installer and release notes. | A DMG opening successfully doesn’t mean the app is fully compatible with an older version of macOS. |
| Installation and permissions | Move the app to Applications. Don’t keep running it from a mounted DMG. | Grant permissions as prompted by macOS. Test the system proxy before configuring TUN. |
Most current Android phones use ARM64; older devices may require ARMv7. When installing an APK, allow installs from the download source when prompted. On first connection, approve Android’s VPN request. Usually, only one VPN service can be active at a time.
For devices that support arm64-v8a. Import your configuration, check the selected proxy, then connect and approve the system permission request.
Check battery settings for background restrictions. Product details: clashplus.io.
For Android users with Clash YAML configurations. If you’re unsure of your device’s architecture, choose the universal package. It’s usually larger than a single-architecture build but avoids choosing the wrong architecture.
After adding a link, wait for the configuration to download. Select it before starting the service. Saving a link without enabling its configuration won’t route traffic.
Includes a mobile interface for managing configurations and choosing proxies. Before use, make sure your subscription is in a format the client can read, then check your proxy groups and connection status.
If the connection drops when your screen locks, check battery-saving settings and background permissions before assuming the APK is at fault.
For users with existing configurations compatible with Surfboard. Its configuration syntax differs from Clash YAML; changing the file extension alone won’t make it importable.
Before downloading, confirm that your subscription service provides the required format. If you already have a Clash configuration, use one of the clients above that can read it directly.
| Check | What to look for | What to do |
|---|---|---|
| Device architecture | arm64-v8a is ARM64; armeabi-v7a is 32-bit ARM. | Check your device specifications, or choose a client with a universal package if you’re unsure. |
| OS compatibility | Minimum Android versions vary by client. Follow the installer prompts. | If the APK won’t parse or install, check your Android version and make sure the download completed. |
| Connection permissions | The client uses Android’s VPN interface to route traffic. | Turn off other VPN services first, then approve the connection request for this client. |
Open the product page in the App Store to check current compatibility, app details, and release notes. After installing, import a supported configuration and add a VPN configuration when prompted by iOS.
Install the app from the store, then get a subscription URL or configuration file ready. Before connecting, check the active configuration and proxy selection, approve the iOS VPN prompt, and test access.
Official site: clashplus.io. Check the current App Store listing for supported devices and in-app features.
| Check | Where to check | After installation |
|---|---|---|
| OS version | Check the minimum iOS version in the compatibility section of the App Store listing. | Install after confirming your device meets the system requirements. |
| Configuration source | Get a subscription URL or local configuration supported by the client. | Select the configuration after importing it. Don’t share your subscription URL publicly. |
| VPN permission | On first connection, follow the iOS prompt to add a VPN configuration. | Check that another VPN connection isn’t active, then test network access. |
First check whether your distribution uses DEB or RPM, then run uname -m to check the architecture. The desktop packages here are AMD64 / x86_64. For servers and routers, see the standalone core downloads below.
For Linux desktop environments where you want graphical configuration management. DEB is for distributions that support that package format; RPM is for distributions using RPM. The two formats aren’t interchangeable.
Use your distribution’s package manager where possible so it can handle dependencies. TUN also requires the relevant network permissions.
For desktop environments that use DEB packages. After installation, open the app from the application menu. If no window appears or the app exits immediately, launch it from a terminal to see the error details.
Don’t install a desktop package on a server without a graphical environment. For background traffic routing, the standalone Mihomo core is a better fit.
| Check | What to look for | What to do |
|---|---|---|
| Package format | Debian and Ubuntu typically use DEB; Fedora and similar distributions use RPM. | Check your distribution and package dependencies, not just the file extension. |
| Processor architecture | uname -m typically returns x86_64 for AMD64 systems. | Don’t install the AMD64 desktop package on an ARM64 device. |
| Desktop and permissions | GUI clients require a compatible desktop environment and runtime libraries. | Check the system proxy, service mode, and TUN separately. If something fails, keep the terminal output for troubleshooting. |
Standalone core / servers / routers
This section provides the command-line core, not a graphical interface. Most desktop users should choose a GUI client above. For a self-managed deployment, prepare a configuration file and decide where the core will run, what permissions it needs, and how to manage its process.
| Platform | Processor architecture | File 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 soft-float | GZ | Download MIPS GZ |
A GZ file usually extracts to an executable, not an installer with a setup wizard. On Linux, check execution permissions and system compatibility. For MIPS devices, verify the endianness and floating-point ABI; don’t choose based on the router brand alone.
Start the core with a complete configuration before setting up a service or automatic startup. If you enable the external controller, restrict its listening address and set access credentials; don’t expose it directly to the public internet. For rules, DNS, and TUN settings, see the Advanced Config guide.
Get the configuration loading correctly before changing proxy settings. Troubleshoot installation, configuration, and network issues separately instead of reinstalling every time a connection fails.
On the Configuration page, paste a subscription URL or choose a local YAML file. Wait for it to download and parse, then select the configuration you want to enable. If a subscription update fails, first check that the URL is valid.
Check the selected proxy group on the Proxies page. Rule mode is a good starting point for everyday routing. Enable the system proxy as needed. If an app doesn’t use the system proxy, consider a manual proxy or TUN instead; avoid changing several settings at once.
Test the destination you need to reach, then use the logs to tell whether the issue is DNS resolution, establishing a connection, or matching a rule. If a port is already in use, quit other clients first. If needed, change the listening port and update the app settings to match.
These answers cover essential steps before and after installation. For DNS, proxy group, and local override settings, see the Advanced Config guide.
You’ll need a valid subscription URL or a local configuration file. The installer provides the client only; it does not include a proxy service. Import and enable a configuration, choose a proxy group on the Proxies page, then turn on the system proxy or TUN mode as needed.
On Windows, check System type in Settings > System > About. On macOS, check the chip or processor in About This Mac. On Android, check your device specifications; if you’re unsure, choose the universal package for Clash Meta for Android. On Linux, run uname -m. x86_64 usually means AMD64, and aarch64 means ARM64. Always check the architecture supported by the actual installer.
For the same client, you can usually install an update over the existing version by following the installer prompts. First back up your subscription URL, local rules, and overrides, then quit the running client. When switching clients, import a standard configuration file rather than overwriting another client’s program directory or internal database.
Check your OS version, processor architecture, and installer format, then review system alerts and client logs. On Windows, check that the WebView2 runtime is available. On Linux, launch the app from a terminal to see which dependencies are missing. If the core fails to start, check configuration syntax, port conflicts, and permissions. Don’t run multiple proxy clients at the same time.
Choose a GUI client to manage subscriptions, proxies, and rules through an interface. The Mihomo core package is primarily for servers, routers, and users who manage their own configuration. You’ll need to provide a configuration file and set up how the core starts and accesses the network. Downloading the core alone does not provide a desktop interface.
A successful installation doesn’t mean the configuration is active. Check that the subscription imported, the configuration is enabled, a valid proxy group is selected, and the system proxy or TUN is on. Then review the logs for DNS and connection errors. Apps using a manual proxy also need the address and port the client is actually listening on.