Clash Plus
Top pickA good fit for importing configs and switching proxy groups on a desktop for the first time. Project site: clashplus.io.
127.0.0.1 / Client installers
Choose your operating system, then check the CPU architecture and package format. For everyday use, choose a desktop client. For managing configs yourself on a server or router, choose the standalone core.
ARCH / Platform index
Find the package for your platform. Archived builds are useful for checking older setups; for a first install, start with a client that's still maintained.
Most desktop packages here are x64. Check Settings → System → About to confirm your system type. If a client offers both EXE and ZIP packages, choose based on whether you want a standard install or to manage the program folder yourself.
A good fit for importing configs and switching proxy groups on a desktop for the first time. Project site: clashplus.io.
For users who want to manage config overrides or inspect connection details in the interface. On first use, make sure the config loads before enabling TUN if needed.
Use the EXE for a standard install. Choose ZIP if you want to manage the program folder yourself; extract the files fully before running the app. Don't launch it from the archive preview.
A desktop client with a graphical interface. When migrating, import your existing config first; check the old client's UI preferences, ports, and system proxy settings separately.
Kept for reference with older setups. Newer config fields and protocols may not load. If you run into parse errors, consider switching to a currently maintained client.
| Check | What to look for |
|---|---|
| OS and architecture | Use a supported 64-bit version of Windows where possible; check each client's release notes. The x64 packages listed here are not native ARM64 builds. |
| Installation and services | Check your system's installation policies. TUN may require a separate service or virtual network adapter. |
Opening the app and routing traffic through it are two different things. For a first test, quit any old client, import a config into the new one, and enable system proxy only. Then check the browser and connection logs. If the result changes in a terminal, check whether the terminal reads the system proxy instead of reinstalling the app.
Check About This Mac for your chip. Apple silicon uses arm64; Intel uses x64. Some listings here are Intel builds, labeled according to the architecture of the available fallback package.
Choose the DMG for your chip, open it, and follow the instructions in the disk image. Project site: clashplus.io.
Manage subscriptions and overrides in the desktop interface. This listing is an Intel build; Apple silicon users should check compatibility with translation and helper services before trying it.
This listing is an Intel build. Before switching clients, back up your existing config and local edits, then check the system proxy settings separately after importing them into the new app.
For reference with older menu bar setups. Both links fall back to an Intel build, not a native Apple silicon package.
| Check | What to look for |
|---|---|
| Chip and macOS version | Choose arm64 for Apple silicon and x64 for Intel. Minimum macOS versions vary by release; check the project's release notes if you're running an older version. |
| Translation and permissions | Running an Intel app on Apple silicon may require Rosetta. If your managed device restricts helper components, check with your administrator first. |
To replace an older app, quit its menu bar process before copying the new one. Don't migrate subscriptions by overwriting the app: the program and config folders are separate, and you should check whether the existing config is compatible. If macOS blocks the app, verify its source and compatibility rather than disabling security settings.
Choose an APK that matches an ABI supported by your device. A chip that can run 64-bit code doesn't necessarily mean the device has a 64-bit Android OS. If you're unsure, check the device specs or choose the client's universal package.
For devices that support arm64-v8a. Project site: clashplus.io.
Available in several package types. A universal package saves you from checking the ABI, but you still need a compatible Android version and signing certificate.
Use the x86_64 package only on a device or emulator that reports support for this ABI. The host computer's processor alone isn't enough to determine compatibility.
An alternative for other config formats. Existing Clash YAML files may not import directly. Before migrating, check the formats supported by the client and make sure its proxy groups and rules map correctly.
| Check | What to look for |
|---|---|
| System ABI | Choose a package for an ABI supported by your system: arm64-v8a, armeabi-v7a, or x86_64. Check the app's release notes for the minimum Android version. |
| Installation and connection | Manually installing an APK may require allowing installs from the current source. When connecting for the first time, approve the VPN permission prompt. |
After installation, select the config you just imported in the app, then connect. If another tool is already using the system VPN, disconnect it and try again. If the connection drops only when the screen is locked, check background restrictions first. If it also fails in the foreground, check the logs for config, node, or DNS errors.
Open the app's App Store page and check Compatibility for the system requirements of the current release, then install it using the store button.
Project site: clashplus.io. Install and update the app through the App Store.
| Check | What to look for |
|---|---|
| Compatibility | Check the current App Store listing for supported iOS versions and compatible devices. |
| VPN configuration | Approve the system prompt the first time you connect. If a managed device can't add a VPN configuration, check its management policies first. |
Once the store reports the app is installed, import and select a config in the app. Permission to add a VPN configuration only confirms authorization; it doesn't mean a node can connect. For testing, select a known-working proxy group and check the app's connection log to confirm requests match the expected rules.
These are desktop GUI packages. Check your distribution and package manager: Debian- and Ubuntu-based systems usually use DEB; Fedora-based systems usually start with RPM. Check your CPU architecture too.
Manage configs and connections on a system with a desktop session. DEB and RPM are different package formats for the same client; install only the one that matches your distribution.
Choose DEB or RPM if you want your package manager to manage the app. For AppImage, check the file's execute permission and any runtime requirements for your distribution.
| Check | What to look for |
|---|---|
| Architecture and desktop | When uname -m reports x86_64, check that the AMD64 desktop package and its desktop runtime dependencies are compatible. |
| Distribution and dependencies | Use your package manager to identify missing dependencies. Matching CPU architecture doesn't guarantee compatible graphics library versions. |
If the app works on the desktop but terminal requests don't appear in its logs, check desktop proxy settings and terminal proxy environment variables separately. For headless remote sessions, always-on forwarding, or service-managed startup, switch to the standalone core instead of installing a full desktop environment on the server.
For servers, routers, and users who manage processes themselves. The core handles proxying, rules, and DNS; you manage the config directory, process startup, and logs. For everyday desktop use, a graphical client above is usually easier.
| OS | Architecture | Package and download |
|---|---|---|
| Windows | AMD64 | Download ZIP |
| Windows | ARM64 | Download ZIP |
| macOS | Intel / AMD64 | Download GZ |
| macOS | Apple silicon / ARM64 | Download GZ |
| Linux | AMD64 | |
| Linux | ARM64 | Download GZ |
| Linux | ARMv7 | Download GZ |
| Linux | MIPS softfloat | Download GZ |
Extract the archive before use. For routers, check more than the CPU family: verify the firmware's userspace architecture, endianness, and floating-point convention. For example, a device reporting mipsel can't use the MIPS package here as though it were the same build. On first run, prepare a config directory and check the logs for a successful config load before setting it up as a persistent service.
MIXED-PORT / Setup handoff
Test one layer at a time: first make sure the app starts, then check that the config loads, and finally confirm that app requests are routed through the proxy.
Before switching clients, save the original config, custom rules, and overrides separately. Store subscription URLs somewhere secure; don't include them in screenshots or public logs. Menus, service settings, and subscription refresh behavior vary between clients. Import one config and test it before migrating the rest.
mixed-port is the local proxy listening port, not the subscription service URL. If the port is already in use, quit the old client and check whether its background process has stopped. If you switch ports, update any apps with manually configured proxy settings too. To see whether rules are matching, test in rule mode rather than relying on the connection toggle.
Clash Open Source Hub organizes links and usage notes for these projects; it doesn't publish the clients. Installers, subscriptions, and local client settings are separate: updating the app doesn't update a subscription, and refreshing a subscription may replace remotely synced content. For custom rules you need to keep, use the client's local override feature when available.
DIRECT / Download FAQ
Check Settings → System → About to see your system type. x64 is the package type used by most Windows desktop clients listed here. Some Windows on Arm devices can emulate x64 apps, but virtual network adapter and service driver support must be checked separately. An app opening successfully doesn't mean TUN will work.
Open About This Mac from the Apple menu. Choose arm64 for Apple silicon or x64 for an Intel processor. If a listing only offers an Intel build, Apple silicon devices may need Rosetta. For system extensions or helper services, prefer a client with a native build.
Check whether the phone already has an app with the same name. Updating an existing app usually requires the same application ID and a compatible signing certificate; an older version may also be rejected. Back up your config, then decide whether to update from the original source or migrate. A universal package may solve some architecture mismatches, but it won't fix a signing conflict.
The installer provides the client app. Nodes, proxy groups, and rules come from a separately imported config file or subscription. After importing, make sure the config is selected, then check the proxy groups for available entries. Don't enter an installer URL as a subscription URL.
Usually not if the client includes or can manage the required core. A standalone Mihomo install is better suited to servers, routers, or command-line setups where you manage the config, process, and logs yourself. If two instances run on the same device, check their listening ports and traffic interception scope separately.
Already installed, but having trouble starting the app, using the system proxy, or connecting? See Troubleshooting.