Download Clash Plus, Clash Verge Rev, and FlClash. Choose your operating system, then check your CPU architecture. For servers and routers, go to the Mihomo kernel.
Desktop and mobileUse a GUI client to import subscriptions, configure proxies, and manage rules.
Servers and routersRun the standalone kernel and manage the configuration directory, service permissions, and network forwarding yourself.
This section offers x64 installers. Check your system type under Settings → System → About. On ARM devices, confirm that Windows can run x64 apps; an x64 installer is not a native ARM64 package.
A good choice for first-time users and anyone who wants a consistent experience across desktop and mobile. Import a subscription after installation, then enable the system proxy. If apps that ignore system proxy settings need to be routed, check the permissions required for TUN mode. Don’t let multiple clients change the system proxy at once.
Official site: clashplus.io
For desktop users who need subscription management, rule inspection, and override settings. Configure the mixed port, system proxy, and TUN mode separately; enabling one does not enable the others. Before using service mode, install the service as prompted by the client and check the virtual adapter status.
Available as an installer or a ZIP archive. Use the installer for a standard desktop setup. For the ZIP, extract the files to a permanent folder before running the app. The portable ZIP does not eliminate permissions required for TUN or system integration. Quit the client before moving its folder.
For users who want a desktop interface to organize configurations and proxy policies. When migrating from another client, import the original subscription first, then restore custom rules. Settings and override formats may not be compatible across clients, so avoid copying the entire old configuration directory.
Kept for compatibility with older setups, configuration checks, and migration. Development has ended, so ongoing fixes and support for new protocols are not expected. For a new installation, choose a maintained client above. Before migrating, save your subscription URL, rules, and port settings, then rebuild your setup one setting at a time.
| Check | What to check |
|---|---|
| System and architecture | Use a supported 64-bit Windows version where possible. Minimum requirements vary by client; check the installer prompts. Packages in this section are x64 / AMD64. |
| Installation dependencies | If the installer reports a missing runtime component, install the specific component it names. Don’t mistake a missing runtime for a subscription problem. |
| Network permissions | The system proxy and virtual adapter are separate routing methods. Enabling TUN or installing a service may require administrator approval. |
| Port settings | Check the client’s actual mixed port, then update your browser extensions or terminal proxy settings to match. Multiple programs can’t use the same listening address and port. |
Check your chip under About This Mac in the Apple menu. Choose a package for your Apple Silicon or Intel Mac. Don’t rely on the architecture label on the download button alone; check the filename and the client’s supported architectures.
Choose the ARM64 package for Apple Silicon Macs and the x64 package for Intel Macs. Open the disk image and drag the app to Applications, then launch it from there. For your first setup, import a subscription and select it as the active configuration. Enable the system proxy or TUN according to your needs.
Official site: clashplus.io
Includes an interface for subscriptions, rules, and desktop proxy settings. Both current fallback links point to an x64 file; they do not provide a native ARM64 package. On Apple Silicon, check Rosetta compatibility or choose a client above that explicitly offers an ARM64 package.
A good choice if you want a similar setup process across devices. Both fallback links currently point to AMD64 files; check the actual file architecture before installing. After updating the app, confirm its system proxy permissions and remove any startup item left by the old client after quitting it.
For checking legacy menu bar settings or migrating an existing setup. The current fallback is an x86_64 file; check compatibility separately on Apple Silicon. Development has ended, so this is not recommended for new installations. Back up your configuration before switching to a maintained client.
| Check | What to check |
|---|---|
| Chip type | Apple Silicon uses ARM64; Intel uses x64 / x86_64. Choose a file that explicitly supports your Mac’s native architecture. |
| System compatibility | Minimum macOS requirements vary by client build. Check the installer and system prompts; requirements for one client may not apply to others. |
| First launch | Read the system security prompt and use the approval option provided by macOS once you’ve confirmed the app’s source. Don’t disable system-wide security for a single app. |
| Proxy and network | System proxy settings may be stored separately for each network service. After switching Wi-Fi, Ethernet, or VPN, check the active service’s proxy settings and extension permissions. |
Most recent phones use ARM64. Older devices may require ARMv7. If you’re unsure of your device’s architecture, choose a package explicitly labeled universal. After installation, grant VPN permission and check background activity settings.
For ARM64 phones. After installation, import a subscription and approve the system VPN prompt. If the connection drops when the screen locks, check battery optimization, background activity, and auto-start settings instead of reinstalling repeatedly or switching proxy modes.
Official site: clashplus.io
Packages are available for multiple CPU architectures. Import a configuration, select it as the active one, then start the connection. Updating a subscription and toggling the connection are separate actions. A universal package supports multiple architectures but may still be incompatible with your Android version, device signature requirements, or device policies.
For phones, start with the ARM64 package. The x86_64 package is mainly for devices or emulators with that architecture. If you use per-app routing, make sure the target app is included in the proxy scope. An app that isn’t routed and an invalid subscription are separate issues to troubleshoot.
For users with an existing Surfboard-compatible configuration. Its format differs from Clash YAML; changing the file extension alone won’t make it importable. Before choosing this app, confirm your subscription provider supports its format, then configure rules, DNS, and app routing.
| Check | What to check |
|---|---|
| CPU architecture | ARM64 corresponds to arm64-v8a, and ARMv7 to armeabi-v7a. Which packages can be installed also depends on whether your Android version still supports running apps built for that architecture. |
| Android version | Check the compatibility details shown by the Android installer. If the package is incompatible, verify your Android version and device architecture rather than repeatedly trying the same file. |
| Connection permissions | Approve the system VPN prompt. Other VPN apps may already be using the VPN slot, so disconnect other routing tools before testing. |
| Background activity | Allow the background activity the app needs in your device settings. Persistent notifications, battery settings, and auto-start options vary by manufacturer. |
Check Clash Plus compatibility for your device in the App Store, then install it. After launching the app, import a subscription and allow it to add a VPN configuration when prompted. Test access for target apps according to your rule mode.
Check the system requirements and supported devices on the App Store listing. Installing a client and getting a subscription are separate steps; you need a valid configuration before connecting. If an import fails, first check that the subscription link is valid and returns the expected format, then check the network path.
Official site: clashplus.io
| Check | What to check |
|---|---|
| System compatibility | Check the compatibility details on the App Store listing to confirm your device and iOS version are supported before installing or updating. |
| VPN configuration | Allow the app to add a VPN configuration when prompted on first connection. If your device is managed by an organization, its management policies determine whether this is allowed. |
| Subscriptions and rules | After importing, make sure the configuration is selected. Updating a subscription won’t automatically fix every custom rule; verify rule matches again after making changes. |
For desktop Linux, choose deb or rpm based on your distribution, then confirm the AMD64 architecture. For ARM, router, or headless deployments, use the standalone Mihomo kernel below. Don’t install a desktop package on an embedded system.
For Linux desktop users who need a GUI to manage subscriptions, rules, and the system proxy. Use your distribution’s package manager to install dependencies. Desktop, terminal, and system-service proxy settings may differ; enabling the desktop system proxy doesn’t mean every command will use it.
For users on Debian- and Ubuntu-based desktop distributions. After installation, launch the app from the application menu and test subscription import and the system proxy before deciding whether to configure TUN. If the window won’t open, check dependency and graphical session errors first, not your subscription.
| Check | What to check |
|---|---|
| Package format | Debian- and Ubuntu-based distributions generally use deb; Fedora and openSUSE typically use rpm. Even with the right package format, check dependency versions. |
| CPU architecture | This section provides AMD64 / x86_64 desktop packages. Run uname -m to check the architecture reported by your system. |
| Desktop environment | GUI clients need a compatible graphical session and runtime dependencies. For headless servers, consider a standalone kernel and service manager instead. |
| Network routing | TUN involves a virtual adapter, routing, and permissions. Firewalls, container networking, and other VPNs can also affect routing. |
For users managing servers, routers, or their own services. Desktop users should start with a GUI client above. The kernel binary has no subscription management interface and won’t configure the system proxy automatically.
| System | Architecture and format | Download |
|---|---|---|
| Windows | AMD64 · ZIP | Download AMD64 ZIP |
| Windows | ARM64 · ZIP | Download ARM64 ZIP |
| macOS | Intel · GZ | Download Intel GZ |
| macOS | Apple Silicon · 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 | MIPS softfloat · GZ | Download MIPS GZ |
After extracting the binary, make it executable on Unix-like systems and prepare your configuration files and required rule assets. Run mihomo -t -d ./config to validate the configuration in the specified directory, then run mihomo -d ./config in the foreground. Check for errors before handing it over to a service manager.
Don’t choose a file based only on whether your router is described as “ARM” or “MIPS.” Check the bitness, endianness, instruction set, and floating-point ABI too. Transparent proxying also requires separate routing, firewall, and DNS configuration; starting the kernel alone won’t route LAN devices through the proxy.
Successful installation only means the program is in place. Configure the subscription, routing method, and rules in that order to troubleshoot configuration errors separately from system permission issues.
Add a valid link on the subscription or configuration page, update it, then select it as the active configuration. A provider’s website URL is not a subscription URL. If import fails to parse, check whether the link returns configuration text or a login page. Subscription URLs may contain credentials, so hide the full link before sharing screenshots or logs.
Start with the system proxy for browsers and other apps that follow system proxy settings. Games, some command-line tools, and apps that ignore those settings may need TUN or separate configuration. “Global mode” does not automatically route every app: proxy mode determines how the kernel handles connections it receives, while the routing method determines whether connections reach the kernel.
Make sure the actual mixed port matches the system proxy address, then visit a target site and check which rules match. If only the terminal fails, check environment variables; if only domain names fail, check DNS; if all apps fail, first check whether the client is listening. Change one setting at a time and keep a record of settings you can roll back.
Choosing an installer, migrating from an older client, and troubleshooting your first connection.