Choose your operating system first, then check the CPU architecture. Use a GUI client on desktops and phones; see the Mihomo core for servers, routers, and command-line environments.
First install: Start with Clash Plus on Windows, macOS, Android, and iOS; start with Clash Verge Rev on Linux.
After installation: Import a valid configuration, select a proxy group, then enable the system proxy. The installer itself does not include a proxy service.
Several clients may be available for the same platform. Install one first and confirm that your configuration and connection work before switching. Avoid running multiple system proxies at the same time.
The installers here are for x64. Check your system type under Settings → System → About. On Windows ARM devices, confirm that x64 app emulation is supported; an x64 installer is not a native ARM64 build.
For your first setup, start by importing a configuration and choosing a rules mode. Make sure the subscription loads successfully and a proxy group has an available outbound before enabling the system proxy. To route apps that ignore system proxy settings, check TUN permissions and routing separately.
clashplus.io
A good fit if you want to manage configurations, rules, and desktop proxy settings. When switching, import your existing configuration and check core compatibility first. Migrate local overrides and client-specific settings separately; copying a subscription link may not restore every interface setting.
An option for users who want a client that works across desktop and mobile. AMD64 refers to the x86-64 instruction set and also works with compatible Intel processors; this installer is not limited to AMD-branded CPUs. Import your own configuration after launch.
A desktop configuration manager with a different interface. Before switching from another client, quit it and turn off its system proxy, then check for port conflicts. If configuration fields aren’t supported, check which core is actually in use.
Kept for reference when migrating older setups or working with existing configurations. Since development has stopped, don’t expect ongoing compatibility or security updates. For new devices, choose one of the clients above. Some core-specific fields in older configurations may need to be converted before migration.
| Check | What to look for |
|---|---|
| System and architecture | Use a 64-bit Windows version that still receives security updates. Check the installer’s requirements for the minimum supported version; compatibility with older systems isn’t guaranteed here. |
| Installation permissions | Standard proxy and TUN setups have different permission requirements. Installing a system service or virtual network adapter may require administrator approval. |
| Runtime requirements | If the installer reports a missing runtime component, install the component specified by the client. On managed devices, follow your administrator’s deployment policy. |
Check About This Mac to see whether your device has Apple Silicon or an Intel processor. Open the downloaded DMG, move the app to Applications, and follow the prompts to grant permissions. Some downloads currently offer x64 builds only; Apple Silicon users should read the compatibility notes below.
Choose the build for your processor; there’s no need to install both versions on one Mac. After importing your configuration, test browser traffic with the system proxy before enabling TUN if needed. Quit the client before replacing the app during an update.
clashplus.io
Both links currently point to the same x64 file; neither is a native ARM64 installer. Apple Silicon may need Rosetta to run it, depending on app and system compatibility. For a clearly labeled native ARM64 build, see Clash Plus.
Both links currently provide AMD64 builds. Apple Silicon users should check Rosetta and app compatibility; the link label doesn’t indicate the package architecture. When migrating a mobile configuration, also check desktop proxy settings and listening ports.
For reference when migrating an existing menu bar client setup. Both links currently provide x86_64 builds; Apple Silicon may need Rosetta. The project is discontinued, so this archived app should not be treated as a guarantee of long-term compatibility with newer systems.
| Check | What to look for |
|---|---|
| Processor | Apple Silicon uses ARM64; Intel Macs use x64 / AMD64. A compatibility option may still provide an x64 file, so check the file details above. |
| System support | Check the app’s stated requirements and any startup prompts. The interface, helper services, and TUN components may have different system requirements. |
| Permissions | System proxy settings, network extensions, or helper services may request permission. Check the app’s source and why it needs access before approving. Don’t run commands from unknown sources to bypass a block. |
Most recent phones use ARM64. Older devices may need ARMv7. If you’re unsure which architecture your device uses, check its specifications or choose a universal build when available. The first connection usually requires approval for a system VPN request.
For devices that support ARM64 apps. After installation, import a subscription or local configuration, then check the proxy group and rules mode. When Android asks for VPN permission, confirm the request comes from the client you just installed. Typically, only one VPN can be active for a user at a time.
clashplus.ioChoose an architecture-specific or universal installer. The universal build can be useful if you’re unsure of your device’s architecture, but it’s usually larger. If an update reports a signature mismatch, back up your configuration and check where the old app came from before removing it.
Choose an APK that matches your device’s instruction set. If the connection drops in the background, check battery management, background activity restrictions, and client logs first. Don’t keep replacing configurations; the cause may be system sleep rather than an invalid subscription.
For users with an existing Surfboard-compatible configuration. This isn’t a way to import arbitrary Clash YAML files as-is, so check the configuration format and supported protocols before installing. If you already have a Clash subscription, ask your provider whether a compatible format is available.
| Check | What to look for |
|---|---|
| Architecture and system | ARM64 and ARMv7 are different builds. Both the device processor and operating system must support the chosen architecture. Check the installer’s prompt for the minimum Android version. |
| Installation source | Android may ask you to allow your current browser or file manager to install apps. Grant permission only as needed for a trusted source. |
| VPN and background activity | Disconnect other VPNs that might conflict before connecting. If Android restricts background activity, adjust the battery settings for this app as needed instead of disabling device-wide protections. |
Get Clash Plus for iPhone and iPad from the App Store. The store listing shows compatibility requirements for your device, version history, and app details before you install.
After installation, import your configuration from a link or file, then check the proxy groups and rules. The first time you connect, iOS may ask to add a VPN configuration and confirm with your device passcode or biometrics. Return to the client afterward to check the connection status.
iOS handles network traffic differently from desktop system proxy settings. To verify that the connection works, check both the app’s connection log and the results of an actual visit; don’t rely on the status bar icon alone. If another VPN configuration is installed, check which one is active.
clashplus.io| Check | What to look for |
|---|---|
| Device compatibility | Check the current iOS / iPadOS requirements on the App Store listing. The store handles installation and updates. |
| Network permissions | Follow the system prompt to add a VPN configuration the first time you connect. Organization policies may restrict managed devices; contact your administrator for help. |
| Configuration source | Prepare a valid subscription or compatible configuration. Check that the link is complete before importing, then confirm a proxy group has an outbound selected. |
The desktop installers here are for AMD64. Debian, Ubuntu, and derivatives usually use DEB; Fedora, openSUSE, and other distributions typically use RPM. A matching package format doesn’t guarantee that all dependencies are compatible.
For Linux systems with a graphical desktop. After installation, check that the interface starts before setting up the system proxy or TUN. Desktop proxy settings don’t automatically cover every command-line app; terminal tools may also need proxy environment variables set explicitly.
For AMD64 desktops that use the DEB package format. If the installer reports missing dependencies, note their names and install them with your distribution’s package manager. Don’t force installation by ignoring dependencies; the issue may be an incompatible system library version.
| Check | What to look for |
|---|---|
| CPU architecture | Check with uname -m; x86_64 usually means AMD64. These GUI client packages aren’t for ARM64 hosts. |
| Desktop and dependencies | Requires a compatible graphical desktop and runtime libraries. On headless servers, use the standalone Mihomo core instead of a GUI package. |
| Network management | TUN, automatic routing, and firewall changes may require additional permissions. On a remote host, keep a way to restore your management connection before changing routes. |
For servers, routers, and command-line users. The core reads configurations, matches rules, and establishes outbound connections, but doesn’t include a graphical subscription manager. A GUI client is usually easier to use on desktops and phones.
| System | Architecture | Format and download |
|---|---|---|
| Windows | AMD64 | Download ZIP |
| Windows | ARM64 | Download ZIP |
| macOS | Intel / AMD64 | Download GZ |
| macOS | Apple Silicon / ARM64 | Download GZ |
| Linux | AMD64 | Download DEB |
| Linux | AMD64 | Download GZ |
| Linux | ARM64 | Download GZ |
| Linux | ARMv7 | Download GZ |
| Linux | MIPS soft-float | Download GZ |
| Check | Deployment notes |
|---|---|
| File format | ZIP files need to be extracted. GZ files are usually compressed single executables, not graphical installers. On Unix-like systems, set execute permissions for the deployment path you use. |
| Configuration directory | Prepare a valid config.yaml and make sure referenced rulesets, certificates, and other files are readable. Don’t use an unchecked configuration that takes over network traffic. |
| Service permissions | Permissions differ for standard listening ports, TUN, and route changes. Restrict the external control interface to a trusted address range; don’t expose it to the public internet. |
For proxy groups, DNS, TUN, and local overrides, see the Advanced configuration guide. Check the configuration syntax before setting it up as a system service.
Handle installation, configuration, and traffic routing as separate issues. Change one thing at a time so you can match logs to what actually happens.
Check the file extension, then the CPU architecture. EXE, DMG, APK, DEB, and RPM packages are for different systems; a successful download doesn’t mean the file can be installed on your device. If you see “This app can’t run on your PC” or “There was a problem parsing the package,” check the architecture, system version, and whether the download was interrupted before changing proxy settings.
Before updating, back up local configurations, override rules, and any settings you need. The client interface version and core version are separate; updating the interface doesn’t guarantee that every configuration field will stay the same. Quit the old process during the update to free its ports, then check ruleset references and configuration parsing.
Subscription links may contain access credentials; don’t share them in public comments, screenshots, or logs. After importing, make sure the configuration is selected, then check that its proxy groups reference available outbounds. Fix YAML indentation, mismatched group names, and unsupported fields before starting the proxy.
On desktops, first test apps that follow system proxy settings. For broader traffic coverage, configure TUN, DNS, and routing as needed. On phones, approve the VPN request from the system prompt. Check both the client’s connection log and real browsing results; an occasional failure on one site doesn’t mean all proxy traffic is broken.
See the full setup steps in the Clash installation and setup guide. If you’re unsure about rules, Fake-IP, or proxy groups, start with the glossary.
Check your operating system, architecture, and configuration source first, then troubleshoot permissions and connection issues.
For Windows, macOS, Android, and iOS, start with Clash Plus; for Linux, start with Clash Verge Rev. Check your operating system and CPU architecture before choosing an installer. See the client comparison guide to compare configuration management and interface features.
ARM64 and x64 use different CPU instruction sets, so choose by processor architecture, not just by operating system. Android universal packages usually include multiple architectures and may be larger. Apple Silicon may need Rosetta to run x64 apps; compatibility depends on the app and macOS version.
The client installer does not include a ready-to-use proxy service. Import a valid subscription or configuration file, select an available outbound in a proxy group, then enable the system proxy or configure TUN if needed. Installing a client alone does not route every app’s traffic.
Back up your configuration, local overrides, ruleset references, and any important interface settings. Note your ports and TUN settings. Subscription links may contain credentials, so store them somewhere secure. After updating, check that the configuration parses, the right proxy group is selected, and the system proxy is working before removing the old install.
Check the download source, package format, CPU architecture, and the exact warning from your system. Don’t disable device-wide security or run unknown commands to bypass a block. On managed devices, follow your organization’s software deployment policy. If you can’t identify the cause, stop the installation.
Mihomo can load a configuration and route proxy traffic on its own, but it doesn’t provide a full graphical installer, subscription manager, or system proxy interface. Server and router users need to manage configuration, startup, permissions, and logs themselves. A GUI client is usually more straightforward on desktops and phones.