Clash Plus
Top pickFor your first setup, import a config in the app, choose a policy group, then enable the system proxy. Check that traffic appears in the client using a browser before deciding whether you need TUN mode.
PACKAGESClients & Core
Choose your operating system first, then match the CPU architecture and package format. Use a desktop or mobile app for everyday use, or run Mihomo directly on a server or router.
Open Settings → System → About to check your system type. Choose the x64 package if it says “64-bit operating system, x64-based processor.” If you have an ARM device, don’t rely on the “64-bit operating system” line alone.
For your first setup, import a config in the app, choose a policy group, then enable the system proxy. Check that traffic appears in the client using a browser before deciding whether you need TUN mode.
A good fit if you want to inspect rules, connections, and core logs in one place. For standard proxy use, start with the current-user settings. Check the client’s service-mode guidance if you later need system-wide traffic handling.
The installer is best for everyday use. Choose the ZIP package if you want to keep the app in its own folder. Extract it fully before launching; don’t run it from your archive utility’s preview.
A good option for managing local configs and subscriptions separately on desktop. If you’re testing it alongside an older client, quit the old process first, then check the system proxy address and port.
Archived packages are for migrating old configs or recreating a legacy setup. For a new installation, choose a maintained client. Before migrating, keep your original YAML and custom rules, then uninstall the old version.
| Check | What to look for |
|---|---|
| Windows version | Use a Windows version that still receives security updates. Minimum version and runtime requirements vary by client release. |
| Processor | Desktop packages in this section are primarily for x64. On Windows on ARM, check separately whether the app UI, core, and service components work under emulation. |
| Installation permissions | Installing a service or virtual network adapter may require administrator approval. If you’re only testing browser proxying, start with the standard system proxy setup. |
Open About This Mac from the Apple menu. Choose ARM64 for a Mac with Apple silicon, or x64 for an Intel Mac. A package labeled Intel is not native to Apple silicon.
Separate builds are available for each processor type. Open the DMG and follow its instructions to move the app to Applications. Eject the disk image, then launch the app from Applications.
A good choice for managing rules and connections in one interface. The fallback DMG listed for Apple silicon is the Intel build; running it on an Apple silicon Mac may require Rosetta.
Choose this graphical client if you prefer a mobile-style workflow. The fallback file listed for Apple silicon is an AMD64 build; check the actual package architecture if you need a native version.
An archived menu bar client, useful for exporting an old config or recreating a previous setup. Both processor links point to the Intel build, so it’s not recommended for a new Mac.
| Check | What to look for |
|---|---|
| Windows version | Minimum macOS versions vary by client. If you see an OS compatibility warning, check the app’s release notes first; it doesn’t necessarily indicate a proxy config problem. |
| Processor and translation | Choose ARM64 for Apple silicon and x64 for Intel. Rosetta can run many Intel apps, but it doesn’t turn an Intel build into a native one. |
| Network permissions | System proxy settings and virtual network adapters use different network features. Confirm a standard connection works first, then enable additional features as prompted by the app and macOS. |
Choose an APK based on the ABI supported by your Android system, not just the processor model. Some older devices have 64-bit chips but run a 32-bit OS; in that case, choose armeabi-v7a, not arm64-v8a.
For ARM64 phones and tablets. On the first connection, Android will ask you to approve the VPN request. Return to the app afterward and confirm the selected config is enabled.
Import a Clash-format subscription or local file from the config screen. If you know your device’s architecture, choose the matching package. If you’re unsure which ABI your system supports, try the universal build.
Choose a package for your phone or emulator’s system architecture. For an emulator, use the Android image’s ABI, not the host computer’s processor; select the matching build only if you’re using an x86_64 image.
This client uses a different config ecosystem and is intended for users with Surfboard-compatible configs. If a rule set or subscription won’t import, check the format instead of simply renaming the file extension.
| Check | What to look for |
|---|---|
| Android version and ABI | Check the app’s minimum Android version, then confirm which ABIs your system supports. Universal packages still require a compatible Android version. |
| Install source | When you open an APK from a browser or file manager, Android may ask you to allow installs from that source. You can revoke this permission in Settings after installation. |
| VPN access | Android usually allows only one active system VPN per user. If you’re told another VPN connection will be replaced, pause the app currently using that system interface. |
Open the app’s App Store page on your iPhone or iPad and check Compatibility before installing. The first time you connect, iOS will separately ask you to approve adding a VPN configuration.
After installation, import a config in the app, choose a policy group, and start the connection. For product details, visit the official site: clashplus.io.
| Check | What to look for |
|---|---|
| Windows version | Refer to the iOS or iPadOS versions currently listed under Compatibility on the App Store page. |
| Device management | Devices managed by a workplace or school may restrict app installation or VPN configuration changes. If you see a management policy warning, check with your device administrator. |
| Connection check | Once iOS approves the VPN configuration, return to the app and check the connection status. The system icon only indicates that the VPN is active; check the app’s logs to see which rules are being applied. |
Run uname -m to check your device architecture, then choose a package for your distribution. x86_64 maps to the AMD64/x64 downloads here. For headless servers, see the Mihomo core.
Choose DEB for Debian and Ubuntu-based systems, or RPM for Fedora and other RPM-based distributions. If your package manager reports missing dependencies, check your distribution’s repositories and package versions rather than forcing the installation.
The AMD64 DEB package is available here; installing through your package manager makes dependency handling easier. If the tray icon doesn’t appear after launch, open the app from the applications menu and check whether your desktop environment supports a system tray.
| Check | What to look for |
|---|---|
| Distribution and dependencies | Choose a package that matches your distribution. Even distributions using the same package format may require different dependency versions; follow your package manager’s guidance. |
| Desktop environment | These clients require a graphical session. For servers, containers, or headless systems accessed only over SSH, choose a standalone core package for your architecture. |
| Proxy scope | Desktop proxy settings may not apply to terminal apps. If your browser works but command-line tools don’t, check those tools’ proxy settings or environment variables. |
The standalone core is for servers, routers, and users who manage their own configs. It reads configs, listens on ports, and applies rules; graphical clients handle subscriptions, system proxy toggles, and tray interfaces. For everyday desktop or mobile use, start with a client above.
| Operating system | Architecture | Package format | Download |
|---|---|---|---|
| Windows | AMD64 | ZIP | Download ZIP |
| Windows | ARM64 | ZIP | Download ZIP |
| macOS | Intel / AMD64 | GZ | Download GZ |
| macOS | Apple Silicon / ARM64 | GZ | Download GZ |
| Linux | AMD64 | DEB / GZ | |
| Linux | ARM64 | GZ | Download GZ |
| Linux | ARMv7 | GZ | Download GZ |
| Linux | MIPS softfloat | GZ | Download GZ |
Place the extracted binary and config in a directory the current user can read and write. Use the config reference to check listening ports, DNS, and rules, then start the core in the foreground and watch for errors. If a port is already in use, identify the process listening on it. If it’s another client, quit that app and try again; don’t expose the listening address to your entire network by changing it blindly.
Once it runs correctly in the foreground, consider setting it to start at boot. When moving it to a service account, check the working directory: a config readable from an interactive terminal may not be accessible to the service account, and relative paths to rule files may resolve differently.
For your first setup, choose one client for your operating system; there’s no need to install several versions at once. If you’re already using an older client, note the active config, routing mode, and selected policy group, then back up any locally edited rule files. A subscription URL is not the same as a config file: the URL fetches updates, while the file contains the result of a particular download or edit. Keeping only one may leave you without the other when you migrate.
To compare clients, check platform support and workflow differences in the Client Picks. You can keep two apps installed, but before testing the new one, disable the old app’s system proxy or VPN and quit its background process. Then launch the new app. This ensures its logs show the connections it actually handled, rather than making old settings look like the new rules are working.
If the installer won’t open the main window, check the architecture, OS version, disk space, and runtime dependencies first. If the app opens but can’t import a config, check whether the subscription URL is reachable and the format is supported. If the config is enabled but the app can’t connect, check the listening port, system proxy, or VPN status. Troubleshoot each stage separately instead of repeatedly blaming the installer.
For a basic check, open a webpage and confirm its domain appears in the client’s connection list. Then inspect the matched rule and outbound policy. If your browser works but one app doesn’t, check whether that app uses the system proxy. For a more thorough walkthrough, follow the Getting Started guide to repeat the import, connection, and verification steps.
No. They are different architectures: x64 is used by most Intel and AMD PCs, while ARM64 is for 64-bit ARM devices. Some apps can run across architectures when the operating system supports translation, but native builds are still the best choice.
For everyday use, check the client’s core options first; you usually don’t need to run Mihomo separately. The standalone core is intended for servers, routers, or setups with manually managed configs. Running both at once may also cause a port conflict.
Back up your working YAML files and local rules, then import your subscription or local config into the new client. UI preferences, service settings, and override scripts from the old client may not carry over, so check them individually.
An in-place update usually keeps the app’s data, but installed and portable versions may use different directories. Back up your subscriptions and local changes before updating, then check the active config, selected policy group, and traffic-handling mode.
Make sure you copied the subscription URL, not the account page, then check the client’s error summary. If the download fails, check your connection and subscription status. If it downloads but won’t parse, check that the config format is supported. Don’t include the full subscription URL when sharing troubleshooting details.