Clash Plus
Top pickA good fit for desktop users who prefer a guided installer. If you’re switching from another client, turn off its system proxy and quit it from the system tray before importing your subscription.
Clash for Mac · Downloads
Choose the operating system where you’ll run the client, then download the build for your device’s architecture. On a Mac, use About This Mac to tell Apple silicon and Intel models apart.
macOS is shown by default. Switch platforms to view their downloads, then copy the current URL to share that platform’s download page.
Check Settings → System → About for your system type. The desktop downloads below are for x64. On Windows on Arm, verify compatibility with app emulation and networking features separately.
A good fit for desktop users who prefer a guided installer. If you’re switching from another client, turn off its system proxy and quit it from the system tray before importing your subscription.
Use the desktop interface to check connections and logs, including which rules match. Test with a standard proxy first, then decide whether to configure TUN.
Available as both an installer and a portable ZIP. For the ZIP, extract all files to a local folder before opening the app; don’t run it from the archive preview.
Manage multiple subscriptions from the configuration page. After importing, check which configuration is active and confirm the proxy groups in the sidebar belong to the one you expect.
This archived build is for legacy systems and configuration migration. For a new installation, choose a maintained client. Don’t overwrite the new client’s data directory when migrating.
| Check | What to look for |
|---|---|
| OS and architecture | Use a supported Windows 11 x64 system where possible. Check each client’s requirements to see whether older Windows versions are supported. |
| Runtime | If the interface reports that WebView2 is missing during startup, install the runtime as directed by the client. The runtime needed to display the interface is separate from the permissions needed to configure network services. |
If About This Mac lists an Apple silicon chip, choose arm64. For a Mac with an Intel processor, choose x64 or amd64.
DMG downloads are available for Apple silicon and Intel. Open the disk image, drag the app to Applications, then launch it from that folder.
Check configurations and connections from the desktop dashboard. The fallback file for the Apple silicon link is currently x64; if the downloaded file is still x64, it isn’t a native build.
A similar interface across desktop and mobile. The fallback package currently linked for Apple silicon is labeled amd64; for a native install, choose a file labeled arm64.
Archived build for migrating legacy configurations. Both download links currently point to an x86_64 fallback, not a native Apple silicon build. For a new installation, choose a maintained client.
| Device | What to look for |
|---|---|
| Apple silicon | Choose macOS arm64. Some Intel apps run through Rosetta, but an app launching successfully doesn’t guarantee its helper processes or networking features will work. |
| Intel | Choose macOS x64, amd64, or x86_64. For older Macs, also check the client’s minimum macOS version; matching the processor architecture isn’t enough. |
| Network permissions | Follow the client’s prompts to grant system proxy or helper service permissions. If your organization-managed Mac restricts installation or permissions, contact your device administrator. |
Most recent phones use ARM64. Older devices may support only 32-bit apps, while emulators may use x86_64. Choose a build supported by your device’s operating system.
This download is an arm64-v8a package. When connecting for the first time, check the app name in Android’s VPN permission prompt.
Available for 64-bit ARM, 32-bit ARM, and universal devices. Choose the package for your architecture when known; try the universal build if you can’t identify it.
Available for ARM and x86_64. For an emulator, choose the package supported by the emulated device architecture, not the processor in the computer running the emulator.
Uses its own configuration format. If you already have Clash YAML files, first check whether you can get a compatible configuration, then migrate your rules and proxy groups.
| Check | What to look for |
|---|---|
| OS and architecture | Your Android version must meet the client’s requirements. Also check whether your device supports arm64-v8a, armeabi-v7a, or x86_64. |
| Installation and connection | Android may ask separately whether to allow app installs from this source and whether to allow a VPN connection. If installation succeeds but the connection doesn’t work, check VPN permission and whether another VPN is connected. |
Install Clash Plus from the App Store. Check the Compatibility section on the store listing for the minimum iOS version.
Open the App Store listing on the device you’ll use and install the app. After importing a configuration, allow it to add a VPN configuration when prompted at first connection. See clashplus.io for app details.
| Check | What to look for |
|---|---|
| iOS version | Check your current version in Settings → General → About and compare it with the minimum version listed on the App Store page. |
| Device management | Managed devices may restrict app installation or VPN configurations. If the permission option is unavailable, check your device management policy first. |
amd64/x86_64 GUI clients are available here. Choose a package format for your distribution. For systems without a desktop environment, check the matching architecture in the Mihomo core section.
Choose DEB for Debian and Ubuntu-based distributions, and RPM for Fedora and other RPM-based distributions. Check your desktop environment and package dependencies before installing.
This page provides an amd64 DEB package. If your package manager reports unmet dependencies, check your distribution and version first. Don’t try to resolve them with system libraries from another distribution.
| Check | What to look for |
|---|---|
| Architecture and package format | Run uname -m to check your system architecture. x86_64 corresponds to the amd64/x86_64 packages here; aarch64 is a different architecture. |
| Desktop environment and dependencies | GUI packages need an available desktop session and the dependencies specified by the package. Desktop proxy settings usually apply only to apps that read them; they don’t mean all system traffic is routed through the proxy. |
For servers, routers, or command-line use, where you manage configuration and processes yourself. Most desktop users should choose a GUI client and don’t need to download the core separately.
Card badges show the app version listed in the release directory. If it differs from the version in the package filename, use the downloaded file to confirm the package version and architecture.
Change one setting at a time. First confirm the app launches, then import your configuration and enable the proxy.
x64, amd64, and x86_64 usually refer to the same desktop instruction set; arm64 refers to a different one. Even with a matching architecture, packages for different operating systems aren’t interchangeable: a Mac DMG can’t replace a Windows EXE, and an APK can’t be installed on a Mac as a regular desktop app.
Back up your current local configuration, subscription source, and any rules you added yourself. Subscription URLs may contain account credentials; don’t share them in public logs or screenshots. Import a compatible configuration into the new client. You may need to set up ports, bypass lists, and launch options again.
On first launch, confirm your configuration appears in the list and can be enabled, then choose a rules mode. Test with an app that uses the system proxy and check its requests in the connection log. If you need to route traffic from apps that ignore the system proxy, test TUN separately.
If the app won’t open before you’ve imported a configuration, check the OS version, architecture, and startup message first. If it opens but doesn’t work, distinguish between a failed subscription import, an inactive configuration, and traffic that isn’t being routed. Quit other proxy or VPN apps before reproducing the issue to avoid multiple apps changing network settings at once.
Open About This Mac from the Apple menu. If it lists a Chip with an Apple M-series name, choose arm64. If it lists a Processor with an Intel name, choose x64 or amd64. Even when download links are listed by Mac model, check the downloaded filename: an x64 file is not a native Apple silicon build.
Usually, yes. Each client stores subscriptions and local settings separately, and installing a new client won’t import your old configuration automatically. Back up your configuration and subscription URL first, then import them into the new client and check your proxy groups, rules, and local ports. Quit the old client before testing to prevent both clients from changing system proxy settings at the same time.
First check which app architectures your device supports and the Android version required by the client. If you’re unsure of the architecture and a universal build is available, try that. If an app with the same name is already installed, a different signing key may prevent an in-place update. Back up your configuration before uninstalling.
Choose DEB for Debian and Ubuntu-based distributions, and RPM for Fedora and other RPM-based distributions. Run uname -m to check your system architecture, then make sure your distribution meets the package’s dependencies. A matching package format alone doesn’t guarantee that the architecture or library versions are compatible.
Usually not. GUI clients typically include a core or provide a way to manage it; use the client’s built-in update method where available. The standalone Mihomo package is for users managing configuration and processes themselves on servers, routers, or from the command line.