Client installers · platform and architecture
Choose a client by operating system, then check the processor architecture. Use a GUI client on desktop or mobile; choose the Mihomo core separately for servers and routers.
CLIENT PACKAGES
Share links by platform. Installers deploy the app; subscriptions, rules, and local proxy settings must be configured afterward.
The desktop installers below are mainly for x64. Check your system type under Settings → System → About, and quit other proxy clients before installing to prevent them from overwriting each other's system proxy settings.
A good fit if you want to import configs, switch proxy groups, and manage everyday connections through a GUI. Run the installer and follow the prompts. On first launch, import a config before deciding whether to enable the system proxy. Official site: clashplus.io.
A desktop configuration manager powered by Mihomo, suited to users who need config overrides and service mode. The system proxy and TUN handle traffic differently. First confirm that standard proxy mode works, then install the service component and configure TUN if needed.
A good choice if you want a similar experience across desktop and mobile. AMD64 and the commonly used x64 label refer to the same processor architecture. If you choose the ZIP, extract it fully before launching; running it from inside an archive viewer can prevent dependency files from loading.
Another desktop configuration manager. Before switching, export your config and overrides from the old client. Don't copy its live data directory directly: clients may store subscription refresh settings, custom rules, and core options differently.
Kept for reproducing existing setups and migrating legacy configs. This archived client doesn't reflect the current Mihomo protocol and field support, so newer configs may not load as expected. For a new setup, choose a client above. After migrating, remove the old app and its system proxy settings.
| What to check | Before installing |
|---|---|
| System and architecture | Use a supported version of Windows 10 or 11 where possible. The installers here are for x64 / AMD64; check the installer for the exact minimum Windows version. |
| Permissions | Installing a system service or enabling TUN may require administrator approval. You don't need to run the app as an administrator for everyday use. |
| Proxy conflicts | Let only one client manage the system proxy at a time. Turn off the system proxy before uninstalling to keep your browser from pointing to a closed local port. |
Check your chip under Apple menu → About This Mac. Apple M-series means Apple Silicon; choose x64 for Intel Macs. Some compatibility links still provide Intel builds, which are identified below by their actual filenames.
Separate ARM64 and x64 disk images are available. Open the DMG and drag the app to Applications, then launch it from there. Follow macOS prompts to grant network permissions during setup. Official site: clashplus.io.
A good fit if you need desktop config management and Mihomo options. Both links currently point to the same x64 file. Apple Silicon users may need Rosetta; compatibility does not mean this is a native ARM64 build. Check the active config after installation, then enable the system proxy.
Both macOS links in this list currently point to AMD64 disk images. Apple Silicon users may need Rosetta. If the old client is still running, quit it and turn off its system proxy first to avoid mismatches between the new app's toggle and the actual system setting.
Useful for keeping an existing menu bar workflow or migrating legacy configs. Both architecture links point to an archived x86_64 build, not a native ARM64 package. The capabilities of this older Meta client shouldn't be assumed to match current Mihomo; check protocol and field compatibility before using a new config.
| What to check | Before installing |
|---|---|
| Chip architecture | Native Apple Silicon builds should be labeled arm64. x64, x86_64, and AMD64 generally indicate Intel architecture. |
| macOS version | macOS requirements vary by client; follow the app's installer prompts. Switching architectures won't make an older macOS version compatible. |
| System permissions | Only allow system changes for apps from a source you trust. Approve network extensions, system proxy access, and service installation individually as prompted; don't disable macOS security features globally. |
Most recent phones use ARM64; older 32-bit ARM devices use ARMv7. Allowing an app to install from a source and granting VPN connection access are separate steps. After installation, import a config and approve the connection request.
For ARM64 Android devices. Open the downloaded APK with the system installer and allow installs from the current download source when prompted. You can revoke that source's install permission afterward. Make sure a config is selected before connecting for the first time. Official site: clashplus.io.
Offers installers for multiple processor architectures, suited to Android users who prefer managing config files and proxy groups. The universal APK includes builds for multiple architectures and is usually larger; choose a specific build when you know your device architecture. After importing, check that the config updated successfully—don't rely only on the download confirmation.
A cross-platform option for users who want a similar interface on desktop and mobile. If connections drop, check background activity and battery optimization restrictions as well as your config. Change background settings only for apps that need to stay connected, and avoid running multiple VPN apps at once.
Surfboard uses its own config format and feature set; it isn't a drop-in replacement for Clash YAML. Before choosing it, make sure your config provider supports Surfboard, and check for differences in proxy groups, rules, and DNS syntax. Changing a file extension alone won't convert the format.
| What to check | Before installing |
|---|---|
| Processor and OS | Make sure your OS can run ARM64 or ARMv7 apps. A 64-bit-capable processor doesn't guarantee that the installed OS supports the corresponding apps. |
| Connection permission | The Android VPN confirmation dialog sets up a local traffic tunnel. In most user environments, only one VPN service can be active at a time. |
| Installing over an existing app | An APK signed differently may not install over the existing app. Back up your config first, then decide whether to uninstall; removing the app may also delete its data. |
Check the App Store listing for app details, device compatibility, and current availability. After installing, import a supported config and approve the system VPN configuration the first time you connect.
Check the App Store listing for the app name, developer, and system requirements. On first use, add a config, then choose a rule mode and proxy group. Availability and features are subject to the store listing and in-app information. Official site: clashplus.io.
| What to check | Before installing |
|---|---|
| Device compatibility | Check the App Store compatibility section and make sure your iOS version meets the app's requirements before installing. |
| Network permissions | Follow the system prompts to add a VPN configuration when connecting. If you already use other network extensions, make sure they won't conflict. |
| Config and privacy | Subscription URLs may contain personal access credentials. Don't share the full URL in public screenshots or support requests. |
For Ubuntu and Debian-based desktops, look for a deb package; Fedora and other RPM-based distributions need rpm. These packages are for AMD64. For ARM servers, use the core downloads below—not the desktop AMD64 installers.
A good fit for Ubuntu and other desktop Linux environments. Install through your distribution's package manager to handle dependencies. After launch, test a basic proxy connection before configuring system services and TUN. GNOME tray visibility depends on desktop extension support; a missing tray icon doesn't necessarily mean the core isn't running.
A good fit for Debian-based desktop users who want a consistent experience across desktop and mobile. If the app won't launch, check dependency and desktop session errors in a terminal instead of repeatedly reinstalling it. Uninstalling through a software manager may leave personal config directories behind, so back them up before migrating.
| What to check | Before installing |
|---|---|
| Distribution and architecture | Run uname -m to check your architecture. x86_64 matches the AMD64 package here; deb and rpm packages aren't interchangeable by changing the file extension. |
| Desktop environment | GUI clients require a desktop session and their runtime dependencies. Headless Ubuntu Server is better suited to the Mihomo core. |
| Traffic routing | The system proxy may not cover terminals or every app. TUN requires additional permissions and routing configuration; check for route conflicts with other VPNs first. |
For deployment options and service setup, see Deploy the mihomo core on Ubuntu: desktop and systemd options →
MIHOMO CORE
For servers, routers, and users who manage their own services. The core has no desktop configuration interface; most users should choose a GUI client above.
Before deployment, check your operating system, CPU architecture, and existing network services. After extracting an archive, you'll need to prepare a config, set execute permissions, and choose how to start the core. Linux deb packages are installed by the package manager, but you still need to check the config path and service status. MIPS router builds also depend on endianness and floating-point ABI; the label “MIPS” alone doesn't confirm compatibility.
Try loading the config in the foreground first to catch startup errors, then hand it off to systemd or another service manager. Before enabling TUN, check device permissions and routing. Bind the controller API only to trusted addresses—never expose it directly to the public internet. For protocol compatibility and core details, see the protocol reference.
| Operating system | Architecture | Format and usage notes | Download |
|---|---|---|---|
| Windows | AMD64 | ZIP · common x64 PCs | Download ZIP |
| Windows | ARM64 | ZIP · Windows on ARM | Download ZIP |
| macOS | Intel AMD64 | GZ · extracts to the core executable | Download GZ |
| macOS | Apple Silicon ARM64 | GZ · native build for M-series chips | Download GZ |
| Linux | AMD64 | deb · install with Debian / Ubuntu package manager | Download deb |
| Linux | AMD64 | GZ · manage the binary and service yourself | Download GZ |
| Linux | ARM64 | GZ · 64-bit ARM systems | Download GZ |
| Linux | ARMv7 | GZ · 32-bit ARMv7 systems | Download GZ |
| Linux | MIPS softfloat | GZ · check router endianness and ABI first | Download GZ |
INSTALLATION NOTES
Downloading the client is only the first step. Open it and import a subscription you're authorized to use or a local YAML file. Make sure the config appears in the list and select it. A successful subscription download doesn't mean the core loaded successfully: unsupported fields, invalid indentation, or failed rule resource requests can all prevent a config from activating.
Start with rule mode to verify the setup. Check that the proxy group has a suitable outbound selected, then enable the system proxy. If you changed mixed-port, update any proxy port set manually in your browser or terminal as well. The system proxy affects only apps that honor it; one command-line tool connecting directly doesn't mean the whole client has failed.
If you don't need to route all apps, leave TUN off for now. Enable it only if needed, then check permissions, routes, and DNS. When something goes wrong, check the client logs to distinguish installation, config, and connection issues. Avoid changing ports, DNS, mode, and rules all at once, or it will be hard to tell what caused the problem. For the full setup sequence, see the Clash getting started guide; for general troubleshooting, see FAQ.
DOWNLOAD FAQ
Check your operating system and architecture first, then review installation permissions, config import, and connection settings.
Desktop and mobile users should start with a GUI client. Try Clash Plus on Windows, macOS, Android, or iOS, and Clash Verge Rev on Linux. The Mihomo core is for server and router users who can manage config files, startup options, and service permissions themselves.
x64 and AMD64 usually refer to the same 64-bit x86 architecture. ARM64 is used by many phones, Apple Silicon Macs, and some servers; ARMv7 generally means a 32-bit ARM device. Check your system information and the installer's actual filename—don't identify the architecture by device brand alone.
Use the architecture of the actual installer. Some current Apple Silicon download links for macOS still point to x64 or AMD64 files, as noted on the page. These aren't native ARM64 builds and may require Rosetta. For a native installation, choose Clash Plus with an arm64 build.
Installation only sets up the client. You'll also need to import a subscription you’re authorized to use or a YAML config, check the rule mode, proxy groups, and local ports, then enable the system proxy or TUN if needed. Installers from this site don't include subscription service. See the getting started guide for setup steps.
Export your config first, and keep any custom rules, override scripts, and proxy group selections. Subscription URLs may contain access credentials, so store them somewhere private and secure. After upgrading, check that the right config is selected and review the system proxy, service mode, and TUN permissions.
Make sure you downloaded the deb for your system architecture, then launch the client from a terminal to see any errors. Check system dependencies, your desktop session, and system tray support. Don't run the entire desktop client as root. For a headless server, use the Mihomo core instead of a GUI installer that depends on a desktop environment.