Choose your operating system first, then check your CPU architecture. For everyday use, choose a graphical client; for servers and routers, see the Mihomo kernel.
Desktop clients / EXE
All desktop clients listed here are x64 builds. Check your system type under Settings → System → About. On Windows on ARM, also verify that your system can run x64 apps; these downloads are not native ARM64 builds.
A good place to start if this is your first install. Once installed, import a configuration and check the active policy and system proxy status. To migrate an existing setup, keep your custom rules and port notes, then verify each setting before enabling it.
Official site: clashplus.io
For users who want to manage subscriptions, policy groups and connection logs on desktop. Before enabling TUN, install any required service as prompted by the client. If you only need the system proxy, there’s no need to enable every traffic-capture option for your first connection.
Another graphical client option for use across devices. This page provides the Windows installer. After launching it for the first time, select your imported configuration, make sure its policy groups have loaded, then test whether your target app follows the system proxy.
Another desktop client in the Clash ecosystem. Before switching, quit your current client and turn off its system proxy to prevent both apps from competing for the same ports. When migrating, check whether the new client’s kernel supports the fields in your existing configuration.
An archived download for restoring older setups and migrating configurations. Its older kernel may not recognize newer protocols or configuration fields. For a new device, consider a client listed above; don’t assume an older interface will be compatible just because you’re familiar with it.
| Check | Before you install |
|---|---|
| System | Use a supported 64-bit version of Windows 10 or 11 where possible. Check the installer for the minimum version required. |
| Processor | The desktop builds on this page are x64 / AMD64. They won’t run on 32-bit systems. |
| Permissions & proxy | Installing a service or virtual network adapter may require administrator approval. Note your current proxy settings, then quit your old client before enabling the new one. |
Desktop clients / DMG
Check your chip under About This Mac. Clash Plus has separate Apple Silicon and Intel downloads. For some clients below, both architecture links currently serve x64 files; this is noted on the buttons. The link label does not mean the file is a native ARM build.
Choose the disk image for your chip. Open the DMG and follow the prompts to install the app in Applications, then launch it from there. After importing a subscription, check the active configuration and avoid running another client that uses the same proxy ports.
Official site: clashplus.io
For users who want desktop configuration management and connection logs. The macOS file currently listed is x64; Apple Silicon users should check Rosetta compatibility before installing. For a native ARM64 build, use the download above.
Offers a configuration workflow similar to the versions on other platforms. The current macOS download is an AMD64 build; Apple Silicon users need to meet compatibility requirements. After importing a configuration, check the ports and mode instead of reusing another client’s service settings.
Kept as a reference for migrating older configurations. Both architecture links currently point to an x86_64 file; compatibility with newer systems should be checked separately. Before switching clients, export your configuration and check its kernel fields and proxy ports rather than overwriting the entire settings folder.
| Check | Before you install |
|---|---|
| Chip architecture | Choose ARM64 for Apple M-series Macs and x64 / AMD64 for Intel Macs. A compatibility option is not the same as a native build. |
| macOS version | Requirements vary by client. Check the app details and system installer prompts; for a new installation, choose a maintained client. |
| First launch | Install the app in Applications. If macOS blocks it from opening, read the specific warning and follow the security steps provided by the system. |
Mobile clients / APK
For most recent phones, ARM64 is a good first option to check. A 64-bit-capable processor doesn’t guarantee a 64-bit system environment, though. If installation fails, check the system architecture and minimum Android version, then try ARMv7 or universal if appropriate. Don’t keep retrying the same incompatible package.
The recommended download for ARM64 Android devices. After installing, import a configuration and approve the VPN request when prompted on the first connection. To stay connected with the screen locked, adjust background permissions according to your device’s battery settings; there’s no need to grant every permission upfront.
Official site: clashplus.ioAvailable in ARM64, ARMv7 and universal builds. Choose the matching package when you know your device architecture; if you’re unsure and your system meets the requirements, consider the universal build. Whether older configuration fields work depends on the included kernel. Check the parse results after importing.
Use a similar management workflow on mobile and desktop. ARM64 and ARMv7 builds are available here. Before installing over an older version, confirm the app source and signing match. If there’s a conflict, back up your configuration first rather than uninstalling and then trying to find your subscription URL.
For Android users with configurations in a format supported by Surfboard. Its format is different from Clash YAML; changing a file extension doesn’t convert it. Before importing, make sure your subscription provides content this client can parse.
| Check | Before you install |
|---|---|
| System & architecture | Check your Android version and the app’s runtime architecture. Refer to the installer for each package’s minimum system requirements. |
| Install permissions | Allow installs from only the browser or file manager you’re using. Once installation is complete, you can revoke that permission based on your security preferences. |
| Connection | Android asks you to approve VPN access. Usually, only one app at a time can use the same VPN connection. |
Mobile clients / App Store
Check the app details, compatibility and update history on the App Store. Use the store’s device compatibility information to confirm you can install it. You’ll still need to import your own configuration and approve VPN access through iOS.
Install from the App Store on iPhone or iPad. After opening the app for the first time, import a configuration, choose an available policy and connect. For configurations with extra fields, check what the client supports; don’t assume desktop service settings apply on mobile.
Official site: clashplus.io| Check | Before you install |
|---|---|
| Device compatibility | Check the Compatibility section on the App Store listing for your iPhone or iPad’s current OS version. |
| Configuration source | Use a configuration you’re authorized to access and that the client supports. Don’t share subscription URLs publicly or include them in screenshots. |
| System permissions | On your first connection, follow the system prompts to add a VPN configuration. If your device is managed by an organization, check its policies first. |
Desktop clients / DEB & RPM
The graphical packages on this page are for AMD64 / x86_64 desktops. Choose DEB for Debian- and Ubuntu-based systems, or RPM for distributions such as Fedora. A matching package format doesn’t guarantee all dependencies are met, so check your distribution version and desktop libraries too.
Recommended for Linux desktop users. Install using your distribution’s package manager, and use its tools to resolve dependency errors. Configure service permissions only if you need TUN; don’t run the entire graphical interface as root as a workaround.
This AMD64 package is for Debian-based desktops. After installing, check that the tray icon or app window works, then import your subscription. Terminal apps may need environment variables or their own proxy settings; the desktop system proxy toggle alone may not route their traffic.
| Check | Before you install |
|---|---|
| Architecture & distribution | Check your architecture with uname -m and your distribution with cat /etc/os-release. The GUI packages in this section are not ARM builds. |
| Desktop environment | A supported desktop environment and the client’s dependencies are required. For a headless server, consider the kernel below instead of installing a desktop environment. |
| Proxy coverage | The desktop system proxy, terminal environment variables and TUN are separate ways to route traffic. Decide which apps need proxy access before choosing a method. |
Kernel downloads / manual setup
For server and router users, and anyone who manages processes themselves. The kernel parses configurations and handles connections, but doesn’t include a full graphical interface for managing subscriptions. Desktop and mobile users should start with a GUI client above.
| Platform | Architecture & format | Download |
|---|---|---|
| Windows | AMD64 · ZIP | Download Windows AMD64 |
| Windows | ARM64 · ZIP | Download Windows ARM64 |
| macOS | Intel AMD64 · GZ | Download macOS Intel |
| macOS | Apple Silicon ARM64 · GZ | Download macOS Apple Silicon |
| Linux | AMD64 · DEB | Download Linux AMD64 DEB |
| Linux | AMD64 · GZ | Download Linux AMD64 GZ |
| Linux | ARM64 · GZ | Download Linux ARM64 |
| Linux | ARMv7 · GZ | Download Linux ARMv7 |
| Linux | MIPS softfloat · GZ | Download Linux MIPS softfloat |
From installation to connection
Being able to open the client only means the app is installed. Check settings in this order—configuration, mode, then proxy entry point—to pinpoint problems more easily than by changing several switches at once.
Get a valid subscription URL from your service provider or prepare a local configuration file. After importing, check for parse errors and select the configuration. Rule mode routes traffic according to its rules; Global mode uses the selected global policy. The mode label alone doesn’t mean you’re connected.
On desktop, start by enabling the system proxy. On mobile, establish a VPN connection when prompted. Open a target app, then check the client’s connection log for its requests. If nothing appears, check the app’s proxy entry point. If requests appear but fail, check the policy, DNS and service availability.
Follow the setup steps →Back up subscriptions, custom rules and overrides, and note your existing listening ports. Quit the old client and restore any proxy settings it changed before installing the new one. You can keep both clients installed, but run only one while troubleshooting to prevent port conflicts and proxy settings from overwriting each other.
A subscription file may not include every setting in the client interface. You may need to set up startup behavior, service mode, keyboard shortcuts and the system proxy again. Clients such as Surfboard use different configuration formats and can’t necessarily import arbitrary Clash YAML. After migrating, test your usual apps instead of relying on the import confirmation alone.
Quick reference: kernels, subscriptions & proxy terms →Downloads & installation / FAQ
First identify whether the issue is with installation, configuration or connection. Expand a question below to see the answer; no extra steps are needed.
For everyday use, start with a graphical client. It handles subscriptions, modes and proxy controls. The Mihomo kernel is mainly for server and router users who manage configuration, processes and services themselves. New users can start with Clash Plus for their platform; Linux users can choose Clash Verge Rev.
These labels indicate the CPU architectures supported by each package. x64, AMD64 and x86_64 generally refer to the same 64-bit architecture; ARM64 is another 64-bit architecture, while Android ARMv7 builds support compatible 32-bit ARM devices. Universal builds bundle multiple architectures and are usually larger. Check your device details and the filename rather than choosing by operating system alone.
The installer includes the client app, not a proxy service. Import a subscription or configuration you’re authorized to use, make sure it’s enabled, select an outbound policy, and turn on the system proxy or the relevant VPN or TUN mode. Then check the connection log to confirm that traffic from your target app reaches the client.
Note the current client, CPU architecture and proxy ports. Use the client’s export or backup feature to save your configuration, custom rules and overrides. Subscription URLs may contain credentials, so keep them on your own device. When switching clients, check configuration formats and kernel support instead of copying the entire app folder.
Archived clients may still run on older systems, but their dependencies, kernels and system compatibility are no longer updated for newer environments. Clash for Windows and ClashX Meta are listed here as references for migrating older configurations and checking compatibility. For a new installation, choose a maintained client that supports your protocols.
Check the operating system, CPU architecture, package extension and OS version, then read the specific warning from your system. On managed work devices, follow your administrator’s installation policies; don’t disable device security just to launch an app. On Linux, check the distribution’s package format and dependencies. On macOS, verify whether the download is an Intel build.