Client downloads / platforms and architectures
Choose your operating system, then check your processor architecture. Use a GUI client on desktop and mobile devices; use the standalone core on servers, routers, and in command-line environments.
Each platform lists popular options first, followed by other clients and archived downloads. Buttons download the installer directly; store links open the app listing.
This section provides x64 installers. Check your system type under Settings → System → About. On ARM devices, verify Windows app compatibility; an x64 installer is not a native ARM64 build.
A good starting point for importing a subscription on Windows. After installing, add your config, then choose a rule mode and proxy group.
Run the EXE installer and follow the prompts. On first launch, make sure your config has loaded before enabling the system proxy. If you enable TUN, grant the requested permissions. Official site: clashplus.io.
Manage subscriptions, proxy groups, and operating modes from a desktop interface. Note your current config and service settings before updating.
If the installer reports missing runtime components, install them as instructed. The system proxy only affects apps that honor system proxy settings; it doesn't route all traffic.
Import configs and manage connections in a graphical interface. Choose the EXE for a standard installation or the ZIP if you want to manage the application folder yourself.
Extract the ZIP completely to a permanent folder before running it. Don't launch the app from within an archive utility. Quit the client before moving its folder to avoid locked files.
An alternative Windows desktop client for users with an existing config who want to compare workflows.
When migrating, recheck the proxy port, config path, and core options. Interfaces vary, so don't rely on the old client's button layout to confirm that the proxy is enabled.
Archived client for comparing older configs and migrating existing setups. For new installations, choose a maintained option listed above.
Older cores may not support newer protocols or config fields. If parsing fails, check compatibility between your config and core before reinstalling.
| Check | What to look for |
|---|---|
| Processor | These x64 / AMD64 builds are for compatible 64-bit Intel and AMD systems. |
| OS support | Use a Windows version supported by the client's current release. Older systems may require additional runtime components. |
| Permissions | Standard proxy use and TUN require different permissions. Installing a service or virtual adapter, or taking over network traffic, may require administrator approval. |
| Port conflicts | Quit other proxy apps before installing. If a port is already in use, change the relevant config; reinstalling Windows isn't necessary. |
Check About This Mac to identify Apple Silicon or Intel. Some architecture links here point to the same x64 file, as noted on the cards. After installation, verify the app's actual architecture and compatibility with your system.
Choose a native build for your chip: ARM64 for Apple Silicon, x64 for Intel. Open the DMG and follow the on-screen instructions to install the app.
On first launch, import your config and check the system proxy status. Quit the app and keep your subscriptions and custom settings before upgrading. Official site: clashplus.io.
Manage desktop subscriptions and proxy policies. Both macOS downloads listed here currently point to x64 DMGs.
The current x64 build may require Rosetta on Apple Silicon. For a native ARM64 build, choose Clash Plus above. The download label doesn't indicate the file's native architecture.
Manage configs and connections in a graphical interface. Both macOS downloads listed here currently provide AMD64 DMGs.
On Apple Silicon, first check that Rosetta can run the app. When enabling network interception for the first time, grant permissions as prompted, then check the client logs to confirm it started successfully.
Archived downloads for maintaining or migrating existing macOS setups. Both links currently provide x86_64 DMGs.
Older apps may not work with newer systems or configs. Back up your config before migrating and note your system proxy and local ports. On Apple Silicon, check compatibility before running this build.
| Check | What to look for |
|---|---|
| Chip | Apple M-series chips use ARM64; Intel chips use x64 / AMD64. |
| macOS version | Check the selected client's current release notes and confirm it supports your macOS version before downloading. |
| Install location | Copy the app to Applications before opening it. Don't run it long-term from a mounted DMG. |
| Compatibility and permissions | x64 builds may require Rosetta on Apple Silicon. Grant permissions for network extensions or helper services when prompted. |
Most recent phones use ARM64, but a 64-bit-capable processor doesn't guarantee the OS runs a 64-bit environment. If you're unsure, choose a client with a universal build and follow the installer prompts.
For ARM64 Android devices. Open the downloaded APK with the system installer, complete installation, then import your subscription.
Approve the system VPN permission when connecting for the first time. If another VPN app is connected, disconnect it before testing this client. Official site: clashplus.io.
Available in ARM64, 32-bit ARM, and universal builds. Choose the matching architecture if you know it; otherwise, use the universal build.
After importing, check that the config parses before starting the connection. If it disconnects in the background, check battery optimization and background app permissions before blaming the subscription.
Available for ARM64 and ARM, with an x86_64 build for compatible devices or emulator environments.
x86_64 isn't a substitute for ARM builds on standard Android phones. After switching clients, recheck the imported config, proxy group selection, and system VPN status.
An alternative rule-based proxy client for Android, available as a universal APK. Its config format differs from Clash YAML, so check that your config source supports it before installing.
Don't assume a Clash config will work in Surfboard. Subscription imports depend on the format and supported protocols; follow your config provider's instructions for the right output format.
| Check | What to look for |
|---|---|
| Architecture and OS | Identify whether your device uses ARM64, ARM, or x86_64, and check that the client supports its Android version. |
| Install permissions | If prompted, grant APK install permission only to the browser or file manager opening the file. You can revoke it after installation. |
| VPN permission | The system must approve the connection on first launch. In typical setups, only one VPN app can handle the connection at a time. |
| Background operation | Check your device's battery settings for background restrictions that could stop the connection when the screen is off. |
Install Clash Plus from the App Store. Check the store listing and your device for compatibility details, app updates, and installation status.
After installing from the App Store, add a subscription or import a compatible config file, choose a proxy policy, and start the connection.
Official site: clashplus.io. Follow the system prompt to add a VPN configuration when connecting for the first time. A VPN icon alone doesn't confirm that rules are working as expected; verify with an actual connection and client logs.
| Check | What to look for |
|---|---|
| Compatibility | Check the compatibility requirements on the App Store listing and make sure your device's OS version meets them. |
| Installation and updates | Install and update through the App Store. Keep your original config source so you can restore it if needed. |
| Connection permissions | Approve the system VPN configuration when prompted. Other VPN connections may interfere. |
| Config requirements | Prepare a valid subscription or compatible config in advance. Installing from the App Store doesn't provide a working proxy service. |
These downloads are for AMD64 desktops. Debian- and Ubuntu-based distributions usually use DEB; Fedora and other RPM-based distributions use RPM. For a persistent server setup, see the core downloads below.
Manage subscriptions and proxy policies from a Linux desktop interface. Choose the package format used by your distribution.
Install with your distribution's package manager and resolve any dependencies. The GUI client needs a desktop session. Whether the system proxy affects an app depends on the desktop environment and the app's proxy support.
AMD64 DEB package for compatible Linux desktop environments. After installing, import your config and check that the core is running.
Terminal apps may not use the desktop system proxy, so you might need to set environment variables separately. Before enabling TUN, check permissions, routes, and existing network services to avoid multiple components changing the network stack at once.
| Check | What to look for |
|---|---|
| Processor | These downloads are for AMD64 / x86_64. Run uname -m to check your machine's architecture. |
| Package format | DEB and RPM packages aren't interchangeable. Choose the format supported by your distribution. |
| Desktop and dependencies | GUI apps need a compatible desktop environment and runtime dependencies. Check the client's release notes for specific requirements. |
| Proxy coverage | Desktop proxy settings, terminal environment variables, and TUN are different routing methods; test each one separately. |
Standalone core / command-line setup
For servers, routers, and custom deployments. Most desktop users should choose a GUI client above instead of installing a standalone core.
| Platform | 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 |
Extract ZIP files before running them. GZ files usually contain a single core binary; on Unix systems, make it executable after extraction. Install DEB files with a package manager, but check the package contents for config locations, startup instructions, and service units. File extensions describe the package format, not whether it includes a usable subscription.
For your first deployment, run the core in the foreground. Check that the YAML parses, the listening port is free, and all referenced proxy groups and rule sets exist. Once it works, configure systemd or your firmware's service manager. Keep a recovery path when working on a router remotely, so you can isolate problems if changes to DNS, routes, and firewall rules cause an outage.
Import a subscription link or local config, then confirm the client shows valid proxy groups before switching to rule mode. A successful subscription update only confirms that the config was fetched and parsed; it doesn't mean every proxy can connect. Choose a working policy, enable the system proxy, and test whether traffic reaches the core.
Use TUN only if you need to route apps that ignore system proxy settings. Before enabling it, note your existing ports, DNS, and routes. After making changes, test the browser, target apps, and DNS resolution separately. If a rule doesn't match as expected, check the target domain and policy in the connection log. Don't change the subscription, DNS, and operating mode all at once.
Save your custom rules and subscription source before upgrading or switching clients. Updates may overwrite subscription files, and clients handle overrides, merging, and persistence differently. After migrating, check mixed-port, proxy group names, DNS enhanced mode, and launch-at-startup settings instead of assuming the old setup still applies.
For step-by-step help, read the Clash setup guide. For timeouts, subscription failures, or DNS issues, see Troubleshooting. If Fake-IP, TUN, or rule sets are unfamiliar, check the glossary to learn what each setting does.
Choosing a client, setting it up, or migrating a config? Check your system requirements first, then troubleshoot the specific issue.
Start with Clash Plus on Windows, macOS, Android, or iOS, and Clash Verge Rev on Linux. Check your processor architecture before installing. For a persistent command-line service or router setup, download the mihomo core separately.
ARM64 is for 64-bit ARM processors. AMD64 and x64 usually refer to the 64-bit x86 architecture used by Intel and AMD processors. Android universal builds include multiple architectures and are useful when you're unsure which one your device needs, but they tend to be larger. Check your OS version and processor architecture separately.
You'll need a valid subscription link or a local config file. The installer provides the client and its features, not a proxy service. Import your config, check the proxy groups and rule mode, then enable the system proxy or TUN if needed.
Back up your config, subscription source, custom rules, and key settings, then quit the old client. Import your config into the new client and check its ports, system proxy, and TUN permissions. Don't run two clients that both take over system networking.
Make sure the download completed and the OS and processor architecture match. Check the system type on Windows, chip type on macOS, OS version and install permissions on Android, and package format and dependencies on Linux. Note the full error and follow the troubleshooting guide. Don't disable system security protections.
Archived downloads are for migrating older setups, comparing configs, and maintaining existing deployments. Clash for Windows and ClashX Meta are no longer maintained, so choose a maintained client for new setups. Support for newer protocols and config fields depends on the core in use.