Check your operating system and processor architecture before choosing a client. Use a GUI client for everyday connections; choose the standalone mihomo core for a manual deployment.
The GUI clients in this section are mainly x64 builds. Before downloading, open “Settings → System → About” and check your system type. Don’t treat an x64 desktop package as a native ARM64 build.
A good choice for importing a config first and setting up the system proxy afterward. Once installed, check that the config loads successfully, then choose a policy group. Enable TUN interception separately if needed; there’s no need to change every network setting on first launch.
Official client site: clashplus.io
A good fit for desktop users who manage configs and local overrides. After importing your existing subscription, check that rule overrides still point to valid policy groups. Before enabling service mode, verify system permissions and check whether other proxy apps are running.
AMD64 is the 64-bit x86 architecture and also supports compatible Intel processors. After importing your config, test browser connectivity in Rule mode. Enable TUN only if specific apps don’t follow the system proxy.
Another option for a desktop GUI client. Settings directories and override methods vary between clients. When migrating, start by importing your config file; don’t overwrite the entire application directory or reuse service files from the old client.
Kept for legacy compatibility and config migration reference. This archived release is not actively maintained and may not recognize protocols or fields used in newer configs. For a first-time install, choose one of the current clients above. Save your local config and rule changes before migrating.
| Check | Before installing |
|---|---|
| Processor and OS | This section mainly offers x64 packages. On ARM devices, check whether your OS supports x64 apps. Standalone core packages are available separately for ARM64. |
| Permissions | Importing a standard config requires different permissions from taking over network traffic. Installing a service, creating a virtual network adapter, or changing firewall settings may require administrator approval. |
| Runtime requirements | Check the installer for the minimum OS version and required runtime components. Note any error messages, then install the dependencies they identify. |
Check your chip in “About This Mac.” Clash Plus provides separate builds for Apple Silicon and Intel. Some other clients currently point both download options to the same x64 file, so check the actual package name before downloading.
Choose the package for your chip, move the app to Applications, then launch it. Once your config imports successfully, set up the system proxy. To route apps that ignore the system proxy, check the permissions required for Network Extensions, services, or TUN separately.
Official client site: clashplus.io
For managing desktop configs and rules. If you use local overrides, check the merged config after migrating rather than only confirming that the subscription imported. Apple Silicon users should read the architecture note above first.
Even with the same config across devices, system proxy settings, launch-at-login, and network interception permissions must be configured separately. Similar client interfaces don’t sync system settings. Verify connection logs after installation.
Kept for users preserving an older menu bar workflow or migrating legacy configs. This discontinued client is not a good baseline for compatibility with new features. If your config uses newer mihomo fields, migrate to a client that supports them.
| Check | Before installing |
|---|---|
| Chip architecture | Apple Silicon uses ARM64; Intel uses x64. Check the actual file name and the app’s supported architectures. |
| OS compatibility | Minimum OS requirements depend on the selected app; check its documentation and installer. Different clients may have different version requirements. |
| Permissions and migration | Keep your existing config and confirm the new app launches before switching proxies. If macOS blocks it, check the specific reason instead of disabling security settings in bulk. |
Most recent phones use ARM64, but check your device’s actual architecture. After installing an APK, you’ll usually need to approve the system VPN connection the first time. Typically, only one app at a time can control the system VPN.
A good choice for importing configs and managing connections on your phone. Save the config source, then start the connection and approve the system prompt. If the connection drops in the background, check battery optimization and background activity limits instead of repeatedly reimporting the subscription.
Official client site: clashplus.io
Choosing a package for your architecture can reduce the download size; if you’re unsure, consider the universal package. When updating an existing app, check that the signing certificate is compatible. If installation fails due to a conflict, back up your config before doing anything else, and don’t immediately delete app data.
Even when using similar configs on mobile and desktop, check app routing and background restrictions separately. If the connection fails when switching from Wi-Fi to mobile data, check the logs and DNS results before changing how traffic is intercepted.
Surfboard uses a different config syntax; Clash YAML cannot be imported as a compatible config. Before choosing it, make sure your subscription or local file is available in a supported format. If you only have a Clash config, use one of the compatible clients above.
| Check | Before installing |
|---|---|
| Architecture and OS | ARM64 and 32-bit ARM packages are not interchangeable. Check the installer and app documentation for the minimum Android version. |
| Install permissions | Grant installation permission only to the source you’re actually using. Once the download is complete, open the APK in your file manager and check the installation result reported by Android. |
| Connection permissions | Approve the VPN request when starting a connection. Check for conflicts with other VPN apps or an always-on VPN setting. |
Install Clash Plus from the App Store. Check device compatibility on the store listing, then install the app, import a config, and approve the VPN request. The App Store listing is the best source for current installation requirements.
On the App Store listing, confirm the app name and compatible devices. Installing the app alone doesn’t establish a proxy connection. You’ll also need to import a config you’re authorized to use, choose a policy, and allow iOS to add a VPN configuration. For your first test, keep the default routing settings to avoid changing several options at once.
Official client site: clashplus.io
| Check | Before installing |
|---|---|
| Device and OS | Check the system requirements and compatible devices on the App Store listing. If your OS version isn’t supported, first check whether an update is available for your device. |
| Config source | Prepare a valid subscription or a local config supported by the client. Don’t post subscription URLs containing access credentials in public forums. |
| VPN permission | Approve the configuration when prompted by iOS. If you already use another VPN, check which VPN is active; a status icon alone doesn’t confirm that proxy traffic is working. |
This section provides AMD64 GUI client packages. Choose DEB for Debian- and Ubuntu-based distributions, or the matching RPM package for Fedora, openSUSE, and other RPM-based distributions. For headless servers, see the standalone core packages below.
Use your distribution’s package manager to install dependencies. GUI apps require an available desktop session. If the window won’t open after installation, check the terminal for missing components and error output instead of installing a desktop package on a headless server.
For desktop distributions that support this package and its dependencies. If the app opens but traffic isn’t intercepted, check desktop proxy settings, environment variables, and TUN permissions separately. Command-line apps may not use the system proxy setting from your desktop environment.
| Check | Before installing |
|---|---|
| Processor | Run uname -m to check the architecture; x86_64 usually corresponds to AMD64. The packages in this section are not for native ARM64 installations. |
| Package manager | Use a package format that matches your distribution and let its package manager resolve dependencies. Don’t convert DEB to RPM or vice versa by changing the file extension. |
| Desktop and permissions | Check that the graphical runtime dependencies and desktop session are available. TUN also requires a usable device and the right permissions; container environments may have additional networking restrictions. |
For servers, routers, and users who manage processes themselves. Most desktop and mobile users should choose a GUI client above. Core packages don’t include a config import interface; you’ll need to provide your own YAML, config directory, startup arguments, and service management.
| OS | Architecture | Format | Local 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 ARM64 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 |
ZIP files must be extracted first. GZ usually compresses a single binary; after extraction, you’ll still need to make it executable and specify a config directory. DEB files are handled by a compatible package manager, but the file extension alone doesn’t mean a system service is enabled. Start the core in the foreground and check its output before setting up a background service.
ARMv7, ARM64, and MIPS are not interchangeable. MIPS also depends on byte order and floating-point ABI. The MIPS softfloat package above is not a universal build for all MIPS devices. Before installing, check the firmware architecture, executable format, storage space, and runtime dependencies. Don’t repeatedly try to launch a build for the wrong architecture.
The client, config, and system-level traffic routing are separate steps. Check each in order to avoid mistaking a config issue for an installation failure.
After importing a subscription or local file, check for syntax errors, unknown fields, or missing policy names. An open client window only means the GUI launched; the core must accept the config before choosing a policy is useful. If a subscription update fails, keep the current working config and then investigate network or URL issues.
A common mixed listener port is mixed-port: 7890, but use the value in your active config. An old app may leave behind system proxy settings, or the new app may fail to listen because the port is already in use. Don’t just check whether the toggle is on; make sure the proxy address and port match the core logs.
Before switching clients, turn off the old app’s system proxy and TUN, and make sure any related services have stopped. Test a known destination in Rule mode, then check the matching rule and outbound policy in the connection log. If your browser works but another app doesn’t, check whether that app uses the system proxy before reinstalling the client.
User guide: import a config and connect for the first time → Rule, Global, and Direct modes →
Check architecture, permissions, and config sources before troubleshooting the connection. For more runtime issues, see the FAQ.
Most desktop and mobile users should start with a GUI client. Clients provide interfaces for importing configs, choosing policies, setting the system proxy, and viewing logs. The standalone mihomo core is for server and router users who manage config files, processes, and services themselves; it is not a GUI installer.
AMD64 and x64 usually refer to the same 64-bit x86 architecture; ARM64 is for 64-bit ARM processors. Check your system information, then verify the package name. If you’re unsure of your Android device’s architecture, consider the universal package. Some macOS download links currently serve x64 builds; Apple Silicon users should check Rosetta compatibility first.
The installer provides the client application, but it does not include a working proxy connection. Import a subscription or local config you’re authorized to use, make sure it loads successfully, then choose a policy and proxy mode. Subscription URLs may contain access credentials, so don’t share the full URL publicly.
Back up your local YAML files, rule overrides, and any settings you need. After importing the config into the new client, recheck policy group names, rule targets, DNS, and TUN settings. Don’t enable system proxy or TUN interception in two clients at once. Remove the old app only after confirming the new one works.
First make sure the download is complete and the package format and processor architecture match your system. Check the specific warning from your OS. On Linux, also check package dependencies and the graphical environment. If the app starts but the core reports an error, inspect config syntax, port conflicts, and permissions. Don’t disable all security protections.
Clash for Windows and ClashX Meta are listed for legacy compatibility and migration reference, and are clearly marked as archived. Archived clients are not actively maintained. For a first-time install, choose one of the current clients above; archived clients may also fail to recognize newer fields in old configs.