Clash Plus
Top pickA good fit if you’re importing a subscription for the first time and using the system proxy. After installation, select the configuration you want to use and check that the system proxy is enabled.
clashplus.ioChoose your operating system, then check the processor architecture. For everyday use, choose a client with a graphical interface. For servers or routers, see the Mihomo core.
These desktop installers are for x64 systems. Check your system type under Settings → System → About before downloading. On ARM64 devices, verify compatibility with the app and its helper services separately.
A good fit if you’re importing a subscription for the first time and using the system proxy. After installation, select the configuration you want to use and check that the system proxy is enabled.
clashplus.ioUses the Mihomo core and suits users who want to manage rules and overrides in a desktop interface. If you plan to enable TUN, make sure your account can authorize the required service when prompted.
The installer is the easiest option for typical desktop use. For the ZIP version, extract all files to the same folder before launching the client. Don’t run it from the archive preview.
Includes desktop configuration and connection logs. When migrating, import one configuration first and check that its proxy groups appear correctly before adding other subscriptions or local overrides.
Use this archived installer to reproduce an old setup or check historical configurations. For a new installation, choose a maintained client. Back up YAML files and custom rules when migrating; don’t copy the entire app data directory.
| Item | What to check |
|---|---|
| Operating system and architecture | Maintained x64 clients are best used on 64-bit Windows 10 or 11. On Windows ARM64, some x64 apps may run under emulation, but check TUN and helper service compatibility separately. |
| Runtime components | If a client that relies on WebView2 reports a missing runtime, install it as prompted before opening the app. On managed computers, check your organization’s policies before installing software or services. |
| Proxy mode | Start with the system proxy and test apps such as browsers that follow system proxy settings. Enable TUN separately if needed, and avoid changing several network options at once. |
Open About This Mac from the Apple menu. Choose an Apple silicon build for a Mac with an Apple chip, or an Intel build for a Mac with an Intel processor. The options below distinguish native builds from Intel builds.
There’s a DMG for each processor type. Open the disk image, move the app to Applications, then launch it and import your configuration.
clashplus.ioIncludes subscription, rule, and override management. Both links currently point to the same Intel build. On Apple silicon, check compatibility with Rosetta and related network components.
A good fit if you want a similar interface on desktop and mobile. Both links currently point to the same Intel build. Before switching clients, quit the old app and turn off its system proxy.
For reference when checking configuration behavior in the legacy menu bar client. Both links are archived Intel builds. Older helper components may not work on newer systems, so this isn’t recommended for new installations.
| Environment | What to check |
|---|---|
| Apple Silicon | Prefer an ARM64 installer. If only an Intel build is available, check that Rosetta is supported on your version of macOS and that the required network components are available. |
| Intel Mac | Choose an x64 or x86_64 installer. Minimum macOS versions vary by client and build; check the release notes for the version you’re downloading. |
| System settings | After installation, test the connection on a network you use regularly. If you use multiple network locations, check the proxy settings again after switching locations. |
Choose an APK that matches an ABI supported by your device. Most newer phones use arm64-v8a, while some older devices support only armeabi-v7a. Emulator architecture depends on the selected system image.
For devices that support 64-bit ARM apps. When connecting for the first time, make sure the Android VPN request comes from the client you just installed.
clashplus.ioFor users who need Clash Meta configurations on Android. The universal package supports multiple architectures included in this release, but still requires a compatible Android version.
These three APKs are built for different architectures. Even if your host computer has an Intel or AMD processor, use the ABI reported by the Android virtual device.
For devices with an existing Surfboard-compatible configuration. Surfboard uses a different configuration syntax, so you can’t directly use any Clash YAML file in its place. Check that your subscription supports the required format.
| Item | What to check |
|---|---|
| App architecture | Check which ABIs your system supports. A 64-bit processor doesn’t guarantee that the system can install a package containing only ARM64 libraries; some systems run 32-bit apps only. |
| Installation and updates | When installing an APK manually, Android may ask you to allow app installs from the current file manager or browser. To update an existing app, the old and new packages must have matching signatures. |
| VPN status | Before connecting, check whether another VPN is already using the current user’s connection. Test Wi-Fi and mobile data separately to avoid mistaking a network-specific issue for an installation failure. |
Check the app name and system compatibility on its App Store page, then install it through the store. The App Store delivers the appropriate build for your device, so you don’t need to choose a processor architecture.
After installation, import an existing subscription in the app. When you connect for the first time, iOS will ask to add a VPN configuration. Check which app made the request before allowing it.
clashplus.io| Item | What to check |
|---|---|
| Device and OS | On the App Store page, open Compatibility to check which devices and minimum OS version are supported by the current release. |
| VPN configuration | Organization-managed devices may restrict adding VPN configurations. If you see a system policy warning, check with your device administrator first. |
Desktop packages are for x86_64 graphical environments. Check the package format used by your distribution as well as the processor: Debian and Ubuntu typically use DEB, while Fedora and some other distributions use RPM.
Includes graphical configuration management. Both packages target the same processor architecture and differ only in package format. If your package manager reports missing dependencies, check your distribution version and required graphics libraries.
This desktop package is for Debian-based distributions. It isn’t a background service package; on a headless host, use the standalone Mihomo core instead.
| Environment | What to check |
|---|---|
| AMD64 desktop | Run uname -m to check the architecture; a common output is x86_64. Then check /etc/os-release to identify your distribution and package format. |
| Desktop session | Graphical clients require a working desktop environment. Whether the system proxy affects a particular app depends on the desktop environment and whether the app reads its proxy settings. |
| Host or container | If there’s no graphical session, or you need to run a service, use the Mihomo core. For containers, check the image architecture rather than relying only on the host architecture. |
For servers, routers, and desktop setups where you manage processes yourself. The standalone core requires you to provide a YAML file, log directory, and startup method. For everyday use on a personal computer or phone, choose a client with a graphical interface above.
| Operating system | Processor architecture | Download |
|---|---|---|
| Windows | AMD64 / x64 | Download ZIP |
| Windows | ARM64 | Download ZIP |
| macOS | Intel / AMD64 | Download GZ |
| macOS | Apple Silicon / ARM64 | Download GZ |
| Linux | AMD64 / x86_64 | |
| Linux | ARM64 / aarch64 | Download GZ |
| Linux | ARMv7 | Download GZ |
| Linux | MIPS softfloat | Download GZ |
Most devices only need one client. You can keep multiple clients on the same system, but if more than one enables the system proxy, TUN, or VPN, the last one started may overwrite the other’s settings or compete for the same local port. Run one at a time to make differences easier to track down.
Check the operating system, processor architecture, and package format separately. The OS determines which system interfaces a program uses, the architecture determines whether it can run, and the package format determines how it’s installed. For example, a Linux amd64 DEB and a Windows x64 EXE may target similar processors, but they aren’t interchangeable. ARM devices don’t necessarily support every ARM build, especially with older system images or lightweight firmware.
After importing a subscription or local YAML file, make sure the configuration is active, not just listed. Then test the connection with a specific proxy group. If the client provides connection logs, check the destination domain, matched rule, and actual outbound connection when visiting a site you expect to work. A system tray or VPN icon alone doesn’t confirm that traffic is taking the intended route.
If your browser connects but one app still fails, first check whether it uses the system proxy settings. There’s no need to start by reinstalling when only one app is affected. If all apps are affected, check the local port, system VPN status, and configuration logs. For the full setup sequence, see Quick Start.
A subscription update may replace remote configuration content without preserving manually edited fields. Save custom rules, DNS settings, and local ports separately, and note your proxy group selections. Don’t assume two clients merge overrides in the same order. Import the original configuration first, then restore changes one by one. Check the effective settings and rule order against the Configuration File Reference.
On a personal computer or phone, choose a client with a graphical interface for your platform. Clients typically manage the core, configuration, and connection status. The standalone Mihomo core is better suited to servers and routers where you manage configuration files, startup, and logs yourself.
x64, x86_64, and AMD64 usually refer to the same 64-bit x86 architecture, found in many Intel and AMD computers. ARM64 is a different architecture, common on Apple silicon Macs and newer mobile devices. Check both the operating system and architecture before downloading: a 64-bit device won’t necessarily run every 64-bit installer.
The files currently listed on these cards are x64 or x86_64 builds, not native ARM64 packages. Compatible Intel apps may run through Rosetta, but check compatibility separately for network extensions and helper components. For a native build, choose an option explicitly labeled Apple silicon.
First check that both packages are for the same client and release channel, and confirm your device architecture. Apps with the same package name but different signing keys usually can’t be installed over one another. If you need to switch channels, back up your configuration and custom rules first, then follow the system prompts to remove the existing app without losing local data.
Installers contain only the client or core. After installation, import a subscription link you obtained separately or an existing YAML configuration. Subscription links may contain credentials, so don’t share the full URL in public screenshots, examples, or support posts.
Back up your subscription URL, local YAML files, overrides, and custom rules. Also note your local ports and proxy group selections. Clients may handle overrides differently; after migrating, check the effective configuration and rule order. Then disable the old client’s system proxy or VPN and test the new client on its own.