Clash Plus
Top pickA desktop client installed through a setup wizard. If you're new to the app, import a subscription first, then check the active configuration and proxy mode. clashplus.io
Choose your operating system, then check the CPU architecture and installer format. Archived clients are marked separately.
A desktop client installed through a setup wizard. If you're new to the app, import a subscription first, then check the active configuration and proxy mode. clashplus.io
Configurations, proxy groups, and connection logs are shown separately. When troubleshooting routing, use the connection log to check which rule matched and which policy was used.
The installer and ZIP target the same AMD64 architecture; they differ in how they're deployed. If you choose the ZIP, extract it to a writable folder before launching the app.
Switch configurations and proxy groups in the GUI. When moving from another client, import the original subscription or local YAML instead of copying the app's internal database.
This archived download is for reference and migrating old configurations. Support for newer syntax may differ from current clients. For a fresh install, choose a client that's still maintained.
| Check | What to look for |
|---|---|
| System type | Open Settings → System → About and check System type. Choose an x64 installer based on the processor architecture; don't rely on the words “64-bit” alone. |
| Windows version | Note the Windows version and OS build on the About page, then check the selected client's release requirements. Minimum supported versions vary by project. |
| Proxy permissions | A successful install doesn't guarantee that TUN will work. First test connectivity with the system proxy, then check the client's requirements for a virtual network adapter, services, and elevated permissions. |
Each processor type has its own disk image. Mount the image and follow the included installation instructions. clashplus.io
Both links currently fall back to an x64 file. If you use Apple Silicon, check the downloaded filename and don't treat an x64 file as a native ARM64 build.
The fallback filename is marked AMD64. If your Mac has an Apple chip, check the architecture in the download filename and the client's compatibility notes.
The fallback file for this archived link is x86_64. Before migrating, export or back up your configuration and quit the old client to prevent both apps from changing the system proxy.
| Check | What to look for |
|---|---|
| Chip type | Check About This Mac for the chip or processor. Apple chips use ARM64; Intel processors use x64, AMD64, or x86_64. |
| Windows version | Compare the macOS version shown in About This Mac with the selected client's release requirements. Being able to mount an older disk image doesn't mean its app will launch. |
| Compatibility mode | If only an Intel package is available, check whether the app and its helper components support running on Apple Silicon through Rosetta. Compatibility does not mean native support. |
This build is for devices that support arm64-v8a apps. When you connect for the first time, approve the VPN request when prompted. clashplus.io
Architecture-specific and universal packages are available. A universal package avoids choosing the wrong architecture, but is still limited by the Android version and the architectures it includes.
The x86_64 package is for Android environments using that architecture, not for Windows. For an emulator, choose a package that matches the virtual device's reported ABI.
Surfboard uses its own configuration format. If you have Clash YAML, check whether your subscription provider offers a Surfboard-compatible version before migrating.
| Check | What to look for |
|---|---|
| App architecture | Check the app ABIs supported by the system. A device with a 64-bit processor may still run an operating system that supports only 32-bit apps. |
| Android version | Find your Android version under About phone and compare it with the client's release notes. The version shown in your device's interface may not be the Android version. |
| Installing over an existing app | Packages with the same app name may come from different release channels. If Android reports a signature conflict, back up your configuration before deciding whether to replace the existing app. |
Install from the App Store listing. Product details: clashplus.io.
| Check | What to look for |
|---|---|
| System compatibility | Check the minimum iOS version under Compatibility on the App Store listing, then confirm your current version under Settings → General → About. |
| First connection | Import a configuration before starting a connection. If iOS asks to add a VPN configuration, make sure the prompt comes from the client you just installed before continuing. |
Choose DEB or RPM based on your distribution's package manager. Both packages target the same processor architecture; they differ in packaging and dependency declarations.
This section offers an AMD64 desktop installer. If installation fails because of missing dependencies, check your distribution version and software sources rather than forcing the install past dependency checks.
| Check | What to look for |
|---|---|
| CPU architecture | Run uname -m to check the machine architecture. The GUI clients above target x86_64; for AArch64 servers, see the standalone core below. |
| Distribution and package format | Debian and Ubuntu typically use DEB; Fedora typically uses RPM. Even with the right package format, your distribution and software sources must meet the dependencies. |
| Desktop session | GUI clients need a working desktop session. Servers managed only over SSH are usually better suited to the standalone core, with the administrator configuring how it starts. |
The standalone core is for servers, routers, and users who want to manage the process themselves. Most desktop and mobile users should choose a GUI client above. The standalone package has no GUI; configure its paths, startup options, and background process separately.
Don't choose a package based only on the device's product name. A product line may use different processors, and a device may run an OS whose bitness differs from its processor. On Windows, check System type; on macOS, check the chip; on Android, check the app architectures supported by the OS; on Linux, also check the package format and distribution. AMD64 and x86_64 in desktop filenames refer to the same target architecture and don't require an AMD processor. Once the architecture matches, check the client's release notes for the minimum OS version. Compatibility with newer and older systems should be assessed separately.
Before migrating, record your subscription URL, local YAML, custom rules, and any proxy group names you need to keep. Subscription URLs may include account access tokens, so don't post them in public support tickets or screenshots. Remote updates may overwrite direct edits; keep local changes in a separate copy. When switching clients, import one configuration first and confirm that proxy group names and rule references match. If parsing fails, note the line number and check the syntax and core support before considering a different installer.
If the app opens, installation is complete—but you still need to confirm that a configuration is enabled, a proxy group is selected, and app traffic is reaching the client. When migrating, quit the old client first to prevent both apps from competing for the local proxy port or changing system proxy settings. Test with an app that follows the system proxy, then check the destination, matched rule, and active policy on the connection page before deciding whether to enable TUN. If the client can test a connection but the target app has no connection log, first check whether the system proxy is enabled and whether the app uses it; don't rush to reinstall.
Check the processor and system type shown by your device. x64 may be listed as AMD64 or x86_64; ARM64 as AArch64. Android packages commonly use the arm64-v8a label.
Installers typically guide you through setup. For a ZIP, extract all files first, then launch the app as directed in the release notes. Don't run apps from the archive preview.
Keep your subscription URL, local YAML files, and custom rules. After importing them into the new client, check the active configuration, proxy groups, and proxy settings. Don't overwrite the entire old client directory.
The client and its configuration are separate. Import a subscription or local config in a format the client supports, then select a valid configuration and proxy mode. The installer doesn't include a subscription.
Usually not if you're using a GUI client that includes the core. A standalone core is for users who want to manage the configuration, launch process, and update workflow themselves.