Choose your operating system, then pick an installer. Mac users can start with Clash Plus and compare other clients for the same platform if they need a different interface or configuration workflow.
These GUI client installers are primarily for x64. Check your system type in Settings, then quit any running proxy clients before installing to avoid multiple processes changing system proxy settings or competing for the same listening port.
A good starting point for a new installation. Import your configuration after installing, then make sure a proxy group has an available outbound before enabling the system proxy. Turn off the current client’s proxy handling before switching to another.
clashplus.io
For users who want a GUI for managing configurations and rules. System proxy and TUN are separate traffic-routing methods. If you enable TUN, read the client’s service and permission prompts; installing the app doesn’t mean all traffic is being routed through it.
A good fit if you want a similar workflow across devices. You can reuse configurations, but check Windows ports, permissions, and network adapter settings separately. Don’t copy an entire app data directory from another device.
An alternative if you prefer a different interface and workflow. Before migrating, export or note your subscription sources, then restore custom rules one by one. Configuration handling may differ from other clients, so check the active configuration after the first launch.
Archived download for migrating existing setups and checking older configurations. For new installations, choose one of the clients above. Don’t assume the old core supports the same fields as current Mihomo, or overwrite its config directory with another client’s files.
| Check | Installers on this page | Before installing |
|---|---|---|
| Processor architecture | x64 GUI clients | Check the system type in System Information. Confirm compatibility separately for ARM devices. |
| System compatibility | Minimum version varies by client | For older systems, check dependencies and runtime requirements. Don’t infer compatibility from the package name. |
| Network permissions | System proxy or client-supported TUN | Grant permissions as needed for each feature. UWP loopback restrictions require separate configuration. |
If your browser connects but Store apps don’t, don’t rush to reinstall. First check whether the app follows the system proxy, then read the Windows UWP loopback guide to distinguish proxy coverage from node connectivity.
Open Apple menu → About This Mac and check the chip or processor name. Clash Plus offers separate arm64 and x64 installers. Some architecture options in other clients’ current listings point to the same x64 file, so read the notes on each card before downloading.
For a new Mac installation, start here. Choose the arm64 package for Apple M-series chips and the x64 package for Intel processors. Open the DMG, move the app to Applications, launch it, and import a subscription or YAML configuration.
clashplus.io
For GUI configuration management and traffic routing. Both Mac options in the current listing download an x64 file. Apple Silicon users should check Rosetta compatibility; this listing does not provide a native arm64 build. After installing, check the system proxy or TUN settings.
A good fit if you prefer a similar interface across platforms. Both Mac options in the current listing point to an amd64 file. Apple Silicon users should check compatibility before installing. Even when reusing a configuration, set local ports and traffic routing separately.
Archived download for migrating older setups and comparing menu bar workflows. Both architecture options currently point to an x86_64 file; Apple Silicon users should check Rosetta compatibility. For a new installation, choose a client above and keep a copy of the original configuration before migrating.
| Check | How to check | What to choose |
|---|---|---|
| Apple Silicon | About This Mac shows an Apple M-series chip | Prefer a native arm64 package. For an x64 package, check Rosetta and app compatibility. |
| Intel | About This Mac shows an Intel processor | Choose an x64, x86_64, or amd64 build—not arm64. |
| macOS version | Check the macOS version in About This Mac | Minimum requirements vary by client. They don’t all support the same macOS versions. |
| Installation and permissions | Applications folder and Privacy & Security settings | Install the app normally first. If you need TUN, grant helper service permissions as directed by the client. |
After installation, test a browser connection in rule mode before enabling TUN. Permission prompts, service installation, and DNS settings depend on the client. See the TUN setup guide for instructions.
Choose an APK that matches your device’s supported ABI. Most newer devices use arm64-v8a; older devices may need armeabi-v7a. If you’re unsure, choose a client that offers a universal package, though it’s usually larger.
This is the arm64-v8a installer. When connecting for the first time, approve the VPN permission prompt. This lets the client route network traffic on your device; it doesn’t mean you have working proxy nodes.
clashplus.ioARM64, ARM, and universal APKs are available. If installation fails, check your device architecture and Android version. When updating an existing app, the signing certificate must also match. Don’t delete a configuration you need just to get around a signature conflict.
Installers are available for different ARM devices. If the connection drops when the screen locks or you switch apps, check background activity and battery restrictions before blaming the proxy rules.
A universal APK is available for users with a compatible configuration. Surfboard uses a different configuration syntax from Clash YAML; changing a Clash config file’s extension won’t make it compatible. Before downloading, check which formats and protocols your configuration provider supports.
| Check | What to check | Notes |
|---|---|---|
| Device architecture | arm64-v8a or armeabi-v7a | A 64-bit-capable processor doesn’t guarantee that the installed OS supports 64-bit apps. |
| Android version | Installer prompts and client release requirements | Minimum Android versions vary by app; there is no single version that applies to all. |
| Runtime permissions | VPN permission and background activity | Avoid enabling another app that also uses the VPN connection. |
When installing an APK from a file manager, Android may ask you to allow installs from that source. Install only files from sources you trust, then reset the source permission if needed. Back up your configuration before uninstalling to avoid losing local overrides and rules.
Check Clash Plus in the App Store for device compatibility, current release information, and installation options. After installing, import your configuration and follow the system prompt to add a VPN configuration. Check the connection status and selected proxy group in the app.
Install and update through the App Store. After importing your configuration, check that it’s complete and that proxy groups have selectable options before connecting. The desktop system proxy and mobile VPN permission work differently; don’t copy all your Mac settings over.
clashplus.io| Check | Where to check | What to do |
|---|---|---|
| System and device | App Store compatibility section | Check the current minimum iOS version and supported devices shown in the App Store. |
| Connection permissions | System VPN configuration prompt | Confirm the app name before granting permission, and check for conflicts with other VPN configurations. |
| Configuration source | Your subscription or local configuration | Subscription URLs may contain access credentials. Hide the full URL when sharing screenshots. |
These installers are for amd64 / x86_64 systems with a desktop environment. Choose deb for Debian- and Ubuntu-based distributions, or rpm for RPM-based distributions. For servers and routers, go to the Mihomo core section to manage the service process yourself.
Available in deb and rpm formats. The package manager handles dependencies during installation. If the desktop proxy setting doesn’t take effect, check your desktop environment’s proxy mechanism and the client’s listening port. TUN permissions are separate from standard app permissions.
This is the amd64 deb installer for users who want to manage configurations from a desktop. A headless system doesn’t need a GUI just to run the core. Before enabling autostart, make sure the configuration and connection work when started manually.
| Check | How to check | How to choose |
|---|---|---|
| Processor | uname -m | If the system reports x86_64, choose the amd64 package here. Don’t force-install it on another architecture. |
| Distribution | cat /etc/os-release | Choose deb or rpm based on your distribution’s package manager. |
| Desktop dependencies | Installer dependency checks | Check the client’s requirements for UI components, system libraries, and minimum versions. |
The system proxy is usually a desktop session setting. It may not apply to SSH sessions, background services, or every command-line tool. If those programs need a proxy, check their environment variables or service configuration. Don’t assume the desktop toggle routes traffic for the whole system.
For server and router users who manage their own service process. Desktop users should choose a GUI client. The standalone core requires you to provide a configuration file and manage startup commands, logs, and the process yourself; it doesn’t include a full system settings interface.
| Platform | Architecture and format | Compatibility notes | Download |
|---|---|---|---|
| Windows | AMD64 · ZIP | For x64 systems; extract and run manually | Download AMD64 ZIP |
| Windows | ARM64 · ZIP | Native ARM64 systems | Download ARM64 ZIP |
| macOS | Intel · GZ | darwin amd64; extract and make executable | Download Intel GZ |
| macOS | Apple Silicon · GZ | Native darwin arm64 core | Download Apple Silicon GZ |
| Linux | AMD64 · DEB | x64 systems using deb packages | Download AMD64 DEB |
| Linux | AMD64 · GZ | x64 binary; manage the runtime directory yourself | Download AMD64 GZ |
| Linux | ARM64 · GZ | 64-bit ARM servers and compatible devices | Download ARM64 GZ |
| Linux | ARMv7 · GZ | Confirm that the system and processor support ARMv7 | Download ARMv7 GZ |
| Linux | MIPS softfloat · GZ | MIPS big-endian soft-float target; not the same as mipsle | Download MIPS GZ |
Name the extracted executable mihomo and prepare your own configuration. Check its syntax in test mode, then run it in the foreground and review the logs. The commands below use a file in the current directory and don’t include a ready-to-use proxy configuration.
./mihomo -t -f ./config.yaml
./mihomo -f ./config.yamlDon’t expose proxy ports or the controller interface to the public internet just to make server debugging easier. Check listening addresses, firewall rules, and access controls before configuring a background service. TUN requires additional network permissions; grant them according to your environment.
See the port fields → See the rule syntax →A successful installation only means the app can launch. Check configuration validity, traffic routing, and rule-based outbound selection separately. Follow these steps to avoid repeated uninstalling and reinstalling.
Use a configuration source you’re authorized to access. If the configuration won’t download, check whether the URL has expired, the network can reach it, and the response is actually YAML. A web error page isn’t a proxy configuration. Subscription URLs may contain credentials, so don’t share them publicly.
Start with the system proxy and rule mode, then test a browser connection. If you need to cover apps that don’t follow the system proxy, check whether the client supports TUN. Toggle names, permission prompts, and DNS handling vary by client.
Check the selected proxy group and which rules and outbound match your requests. When testing is done, quit the client and confirm the system proxy has been restored. If the network stops working, check for leftover proxy settings and port conflicts before reinstalling.
Troubleshoot architecture, system permissions, and configuration migration separately. Version labels appear only when the manifest provides a value. Confirm installation details using the downloaded file and the app’s own information.