Choose your operating system, then confirm your processor architecture. Use a GUI client for everyday tasks; see the core section for servers and routers.
Installing for the first time? See the Getting Started guide →
Each platform lists clients, package formats, and architecture details. Share the current URL to keep your platform selection.
For a new install, start with Clash Plus. When migrating an existing setup, quit the old client and turn off its system proxy first to prevent both apps from changing network settings. The desktop installers below are primarily for x64.
A good fit if you want to get started with subscription imports, rule modes, and everyday proxy switching. After installing, enable a config and check that the system proxy is on; there’s no need to adjust DNS or TUN right away. See product details at clashplus.io.
A good fit for desktop users who need to manage configs, overrides, and rules. After importing an existing config, check the core logs and confirm that policy group names match the rule references. Follow the client’s prompts to install or start service components before enabling features that require elevated permissions.
A good fit if you want a similar workflow across desktop and mobile. Import a subscription and select a config before choosing an outbound policy. Installer and portable builds may store data differently, so check the config directory before migrating.
Includes desktop config management and proxy controls. Make sure the selected core supports your subscription’s fields. If you’ve copied overrides from an older client, enable them one at a time to make errors easier to track down.
Kept here for compatibility checks with existing setups. For a new install, choose a client that’s still maintained. The older core has limited support for newer protocols and config fields; a successful subscription download alone doesn’t mean the config will work.
| Check | What to choose and do |
|---|---|
| System and architecture | Install on a supported Windows 10 or 11 x64 system where possible. Check the client’s release notes for the minimum version. On ARM devices, confirm x64 app compatibility separately. |
| Package format | Follow the installer for EXE files. For ZIP files, extract the entire archive to a separate folder before launching the app; don’t run it from the archive preview. |
| Permissions and ports | Standard proxy and TUN features have different permission requirements. If startup fails, check the logs and make sure another app isn’t using a configured listening port. |
Open About This Mac to check your chip. M-series Macs use Apple Silicon builds; choose x64 for Intel models. Open the downloaded DMG, drag the app to Applications, then launch it from there.
Choose the build for your chip and import a config before enabling the system proxy. To use TUN, grant the required permissions when prompted, and make sure another network extension isn’t already handling traffic. See product details at clashplus.io.
A good fit for managing multiple subscriptions, rules, and overrides. Both architecture links in the current download list point to x64 files. On Apple Silicon, check Rosetta compatibility first; for a native ARM build, consider Clash Plus above.
A good fit if you use both mobile and desktop. Both Mac architecture links in the current list serve amd64 files; check compatibility requirements on Apple Silicon. After installing, test browsing in rule mode before adding custom settings.
For users checking an existing menu bar setup. Both architecture links point to archived x86_64 builds, not native ARM packages. For a new install, consider a maintained client and migrate subscriptions and rule settings separately.
| Check | What to choose and do |
|---|---|
| Chip type | Use native ARM64 builds on Apple Silicon and x64 builds on Intel. Check the actual filename and release notes; a download link doesn’t guarantee a native build. |
| macOS version | Minimum macOS versions vary by client. Check the app’s requirements before installing. If it won’t launch on an older system, verify OS compatibility instead of repeatedly granting permissions. |
| First launch | Launch the app from Applications. If you see a security warning, first verify the file’s source and read the system prompt, then address it in System Settings. Avoid running terminal commands from unknown sources. |
Most recent phones use ARM64. After installing the APK, the first connection will ask for VPN permission so Android can create a local traffic-routing tunnel. Usually, only one app can use this VPN tunnel at a time.
The ARM64 download is suitable for most 64-bit Android phones. Import a subscription before connecting. If the connection drops often when the screen is locked, check the system’s background activity limits. See product details at clashplus.io.
Choose a build for your device architecture. If you’re unsure, use the universal build, which is usually larger. After importing a config, check the proxy policy and app coverage to ensure the apps you want to route aren’t excluded.
Available for ARM64 and ARMv7. Check your device’s supported app architecture before installing, then import a config. If you need a persistent background connection, adjust battery optimization settings as needed; there’s no need to enable every keep-alive option.
A good fit if you already have a Surfboard-compatible config. Its config syntax differs from Clash YAML, so you can’t import any Clash subscription as-is. Confirm the format with your config provider and use a compatible subscription link.
| Check | What to choose and do |
|---|---|
| App architecture | ARM64 uses arm64-v8a; ARMv7 uses armeabi-v7a. A 64-bit processor doesn’t necessarily mean the OS supports 64-bit apps, so check the system as well. |
| Install permission | Follow the system prompt to allow the current browser or file manager to install apps. You can revoke this permission afterward if you like. Check the installer and app documentation for the minimum Android version. |
| Connection permission | Approve the VPN permission when connecting for the first time. Disconnect any other VPN app before testing, and adjust background restrictions only if you need a persistent connection. |
Open the Clash Plus App Store listing on your iPhone or iPad to install it. Import a compatible subscription, select a policy, then add a VPN configuration when prompted by iOS.
Check the App Store listing for compatible devices, system requirements, and release notes. On first use, add a config and approve the VPN permission when connecting. If a subscription includes unsupported fields, adjust it based on the app’s guidance instead of reinstalling repeatedly. Official site: clashplus.io.
| Check | What to choose and do |
|---|---|
| Device and OS | Check the App Store listing for compatible devices and the minimum OS version. Make sure you have enough free storage before installing. |
| Prepare your config | Use a subscription or local config supported by the app. A list containing only node addresses isn’t a complete rules config. |
| Confirm the connection | Allow the app to add a VPN configuration before connecting. If access stops working after a network change, reconnect and check the app logs to confirm the subscription and outbound route are still valid. |
If you have a desktop environment, start with a GUI client. The packages below are for AMD64; Debian- and Ubuntu-based systems typically use DEB, while Fedora and other RPM-based systems use RPM. For headless servers, see the Mihomo core.
A good fit for managing subscriptions and rules on a Linux desktop. Choose the package format for your distribution and install it with the system installer or package manager. If the app won’t open, launch it from a terminal to check for missing dependencies before blaming the proxy config.
A good fit for users on DEB-based desktop distributions who want a workflow similar to mobile. After installing, test config imports and standard proxy mode before setting up TUN. Check service permissions, the desktop session, and system proxy variables separately.
| Check | What to choose and do |
|---|---|
| Processor | Run uname -m to check the architecture; x86_64 corresponds to AMD64. These desktop packages aren’t for ARM routers or single-board computers. |
| Distribution and dependencies | Choose a DEB or RPM package supported by your system and let the package manager handle dependencies. Check the client documentation for minimum distribution and runtime requirements. |
| Desktop and networking | GUI clients require an active desktop session. The system proxy may not cover terminal apps; command-line tools may need proxy environment variables set separately. |
For users managing their own configs on servers and routers. The core parses configs and handles connections, but doesn’t include a GUI, subscription manager, or system tray. Most desktop users should choose one of the GUI clients above.
| Platform | Architecture and format | Package |
|---|---|---|
| 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 Apple Silicon 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 / Routers | MIPS-softfloat · GZ | Download MIPS-softfloat GZ |
| Check | What to choose and do |
|---|---|
| Package format | Extract ZIP files to access the program. GZ files are compressed executables; extract them and set execute permissions. Install DEB packages with your distribution’s package manager. |
| Config and directories | Prepare a complete YAML config and make sure the working directory is readable and writable. Rule files, databases, and relative paths referenced by the config must be available in the runtime environment. |
| Permissions and traffic routing | Verify standard listening ports first, then configure TUN, routing, and DNS. Before changing networking on a remote server, keep a backup management path to avoid locking yourself out with a bad rule. |
First make sure the app starts, then verify the config and connection. Change one type of setting at a time so it’s easier to roll back.
Get a client-compatible config from a trusted source, then import and enable it. A successful subscription update only means the content was retrieved; check that the config also parses correctly. Don’t share full links that contain personal access credentials.
Choose a working policy, then enable the system proxy or mobile connection. Rule mode routes traffic according to the config; global mode is useful for temporary comparisons and troubleshooting, while direct mode doesn’t use a proxy. The selected mode alone doesn’t confirm a successful connection.
Test a direct-access site and one that requires a proxy, then check the connection log to see which rule matched. If browsing works but another app doesn’t, check whether it follows the system proxy. Consider TUN to route more traffic only after that.
Know the difference between installers, configs, and proxy services to avoid reinstalling unnecessarily.
Most desktop and mobile users should start with a GUI client. Clients provide subscription imports, mode switching, and logs. The Mihomo core is intended mainly for servers, routers, and users who manage their own configs; you’ll need to prepare a config file and runtime environment separately.
Check your processor type in system settings first. Windows x64 builds are for 64-bit Intel or AMD systems; Macs come in Apple Silicon and Intel versions. On Android, ARM64 is the usual choice, while older 32-bit devices need ARMv7. On Linux, choose based on the output of uname -m. Check the filename and the app’s actual compatibility, not just the button label.
Check your browser’s downloads list to see whether the download started, then check available storage and your network connection. Reload the page and try again, or use your system browser. If a download was interrupted, delete the incomplete file and download it again. Don’t run a saved HTML page as an installer.
The installer only provides the client; it doesn’t include a working proxy service. Before use, get a compatible config from a trusted source, import a subscription URL or local YAML file, enable the config, then choose a policy and proxy mode. Subscription links may contain personal access credentials, so don’t share them in public comments or screenshots.
Save your subscription URL, local config, rule overrides, and any required port settings first. Turn off the old client’s system proxy and startup launch, then install the new client, reimport your config, and check the logs. Don’t overwrite an entire data directory between different clients; check compatibility for fields specific to the old core.
Whether your data is retained depends on the client, installation method, and data directory. Before upgrading, export or back up your config, overrides, and custom rules, then quit the running app and install the build for your architecture. Afterward, check the active config, system proxy, TUN permissions, and startup settings. Remove old files only after confirming everything works.