Choose your operating system first, then confirm your processor architecture. Use a graphical client for everyday subscription management and the standalone Mihomo core for server deployments.
Clash Plus is the top pick for Windows, macOS, Android, and iOS; for Linux, choose Clash Verge Rev. The client and proxy configuration are managed separately, so have an existing subscription ready before setting up a connection.
The graphical clients in this section are available for x64. In Windows, go to Settings → System → About to check your system type. On ARM devices, confirm that Windows can run x64 apps; the standalone ARM64 core is not a graphical client installer.
A good choice for first-time installs and everyday subscription use. Manage configurations and connections in the graphical interface.
Run the installer and follow the prompts. On first launch, import your subscription, then check the active configuration and proxy connection method. Back up custom rules before updating so local changes aren’t lost if you only keep the subscription URL.
clashplus.io
For desktop users who want to manage subscriptions, rules, and TUN connections. Check the core status in the app after installation.
A system proxy and TUN are different connection methods. Start with the system proxy to confirm your configuration works, then enable TUN if your apps need it. Follow the client’s prompts for service mode, permissions, and network adapter changes.
Connection Setup Guide →
For users who want a similar interface across desktop and mobile. Available as an installer and a ZIP archive.
For a first install, use the EXE. If you choose the ZIP, extract it fully to a writable folder before running the app; don’t launch it from inside the archive. Either package format still requires a separate configuration import and does not replace a subscription.
For users who prefer managing configurations in a desktop interface. Before migrating an existing setup, check that the selected core supports the fields you use.
The interface manages configuration, while the proxy core handles traffic. After switching cores, check the startup logs, especially for compatibility with protocols, rule providers, and DNS settings. A successful import alone doesn’t mean the configuration works.
For migrating existing setups, reviewing older configurations, and checking compatibility. For new installs, choose a maintained client above.
Discontinued clients may not adapt to future system changes or new protocol fields. Back up subscriptions and custom rules before migrating. Afterward, check configuration compatibility with the new client’s core; don’t copy the entire old application folder.
| Check | Requirements and Steps |
|---|---|
| Processor | The graphical installer is x64. Check your device architecture in system information. |
| Windows Version | Check the selected client’s installer for its minimum Windows version. Confirm compatibility before installing on an older system. |
| Installation Permissions | Grant permissions as prompted by the installer. Service and TUN features may also require administrator privileges. |
| Connection | Make sure the system proxy port matches the client. If multiple proxy clients are running, disable the others first. |
Open the Apple menu and select About This Mac to check your chip or processor. Clash Plus has separate ARM64 and x64 downloads. The Apple Silicon compatibility downloads for other clients currently use x64 files; check that Rosetta is available. These are not native ARM64 builds.
Choose the DMG for your processor: ARM64 for Apple Silicon or x64 for Intel.
Open the DMG and follow the prompts to install the app in Applications. Grant any required permissions on first launch, then import your subscription. Before updating, quit the app and back up its configuration; don’t replace application files while it’s running.
clashplus.io
A graphical configuration client for macOS. The Apple Silicon compatibility and Intel downloads currently use the same x64 DMG.
After installation, check that the core starts. Enabling a service or TUN may trigger a system permission prompt; follow the instructions, then test the connection. Check System Settings for details if you see a permission warning; don’t disable system security features altogether.
For users who prefer a cross-platform interface. Both macOS downloads are currently AMD64 builds.
You can reuse a compatible subscription across devices, but desktop system proxy settings and mobile VPN connections must be configured separately. Don’t copy local ports, absolute paths, or permissions unchanged to another device.
Archived reference for existing menu bar setups. Both the Apple Silicon compatibility and Intel downloads are x86_64 files.
Choose a maintained client for new devices. When migrating, note your configuration source and rule changes, then check protocol support in the new core. An archived installer may not work with later macOS versions.
| Check | Requirements and Steps |
|---|---|
| Chip Architecture | On Apple Silicon, use native ARM64 when available; on Intel, choose x64 / AMD64. |
| Compatibility | To run an x64 file on Apple Silicon, check Rosetta availability and app compatibility. |
| Windows Version | Check the minimum system requirements listed for the installer and client release. |
| Installation and Permissions | Install the app in Applications, then follow system prompts for first launch and network permissions. |
Most newer phones use ARM64; older 32-bit systems may need an ARMv7 package. A 64-bit-capable processor doesn’t guarantee a 64-bit operating system. If installation reports an incompatibility, check the system’s supported ABIs and try a matching architecture or universal package.
A good choice for setting up an Android phone. Download the ARM64 package and follow the system prompts to install it.
Android may ask you to allow the browser or file manager that opens the APK to install unknown apps. Starting a connection requires a separate VPN permission. Import your subscription, select the configuration, then start the connection and check the logs.
clashplus.ioOffers architecture-specific and universal packages for users who want to check configuration and core status directly.
Choose the package that matches your device architecture when known; use the universal package if you’re unsure. After importing the configuration, start the VPN service. A successful subscription download and a working connection are separate checks.
Provides architecture-specific packages for phones and some emulators. For a typical ARM64 phone, use the primary download.
The x86_64 package is for compatible devices or emulators, not a universal replacement for phones. If a connection drops in the background, check the app’s battery settings and VPN status before changing your subscription or proxies.
An alternative Android client. Before using it, make sure your subscription supports a format that Surfboard can read.
Clash YAML and Surfboard use different configuration structures; changing the file extension isn’t enough to make a configuration compatible. Use the format specified by your subscription provider. If you convert a configuration, check that protocols, rules, and proxy groups are all preserved.
Check Subscription Compatibility →| Check | Requirements and Steps |
|---|---|
| System Architecture | ARM64, ARMv7, or x86_64 must match the system ABI. Check the universal package’s supported architectures before using it. |
| Windows Version | Check the APK’s minimum Android version. The installer will report compatibility issues. |
| Install Source | Follow the system prompts to allow the app that downloaded or opened the APK to install apps. |
| Connections and Background Use | A VPN permission is required to connect. Avoid running another VPN at the same time, and check your device’s battery settings for background operation. |
Install Clash Plus from the App Store. The store listing shows current system requirements and app details. After installation, import a compatible subscription in the client, then follow the system prompts to add a VPN configuration.
Install and update the app from its App Store listing. The official app website is clashplus.io.
When connecting for the first time, allow iOS to add a VPN configuration, then check your subscription, proxy selection, and connection status. Downloading the app and getting a subscription are separate steps. After switching devices, grant network permissions again on the new device.
Subscription Import Guide →| Check | Requirements and Steps |
|---|---|
| System and Device | Check the App Store’s compatibility section for minimum iOS version and supported devices. |
| Install | Open the Clash Plus App Store listing and follow the store’s instructions to install. |
| Network Permissions | When connecting for the first time, follow the iOS prompt to add a VPN configuration and confirm which app is handling the connection. |
| Configuration Setup | Prepare a subscription or configuration compatible with the client. Check that the core supports any custom rules. |
The graphical packages are for AMD64 / x86_64 systems. Choose DEB for Debian- or Ubuntu-based systems and RPM for distributions that use RPM packages. Check your distribution, desktop environment, and dependencies before installing. For ARM servers, see the standalone core section.
DEB and RPM desktop installers for managing subscriptions, rules, and system connections in a graphical interface.
Use your distribution’s software installer or package manager to handle dependencies. Desktop proxy settings may not apply to command-line tools. When testing, check desktop apps, terminal environment variables, and TUN separately; one app’s results don’t reflect the whole system.
An AMD64 DEB package for Linux desktop distributions that use the DEB package format.
After installation, import a configuration and confirm the core is running before checking the local proxy port. For broader traffic routing, configure permissions and TUN support as required by the client. When troubleshooting dependencies, keep the installer’s exact error message.
View Connection Checks →| Check | Requirements and Steps |
|---|---|
| Processor | GUI packages are for AMD64 / x86_64. Check with system information or uname -m. |
| Package Format | Choose DEB or RPM to match your package manager; don’t install one format across another. |
| Desktop and Dependencies | A graphical environment and its runtime dependencies are required. Check your package manager for minimum library versions. |
| Connection Permissions | Installation and network services may require elevated privileges. Check TUN permissions and desktop proxy settings separately. |
For servers, routers, and users who manage services themselves. The standalone core reads configuration files and provides proxy ports, but has no graphical subscription manager. Desktop users should choose a GUI client above; extracting the core alone isn’t a complete desktop installation.
| System | Architecture | Format and Use | Download |
|---|---|---|---|
| Windows | AMD64 | ZIP · 64-bit x86 host | Download AMD64 · ZIP |
| Windows | ARM64 | ZIP · ARM64 host | Download ARM64 · ZIP |
| macOS | Intel / AMD64 | GZ · Intel Mac | Download Intel · GZ |
| macOS | Apple Silicon / ARM64 | GZ · Apple Silicon Mac | Download ARM64 · GZ |
| Linux | AMD64 | DEB · Compatible package manager | Download AMD64 · DEB |
| Linux | AMD64 | GZ · Standalone binary | Download AMD64 · GZ |
| Linux | ARM64 | GZ · 64-bit ARM device | Download ARM64 · GZ |
| Linux | ARMv7 | GZ · Compatible 32-bit ARM device | Download ARMv7 · GZ |
| Linux | MIPS-softfloat | GZ · Device matching the architecture and floating-point ABI | Download MIPS · GZ |
Prepare a compatible configuration file and confirm the core can read it before setting up startup and log retention. Restrict proxy ports and control interfaces to trusted networks. Before exposing them publicly, configure access controls; don’t expose a local management interface to every network.
After updating the core, check protocol fields, rule loading, and DNS behavior. GUI clients may manage their own core; check the client’s instructions before replacing files manually to avoid a mismatch between the managed version and the binary in use.
Read about core families and configuration compatibility →Choosing an installer determines whether the app can run; subscriptions, modes, and system connections determine how traffic is handled. Check them in order to pinpoint issues instead of reinstalling repeatedly.
EXE is for Windows, DMG for macOS, APK for Android, and DEB and RPM for different Linux package managers. The same file extension can contain builds for different architectures, so check the architecture label before downloading.
AMD64 and x64 usually refer to the same 64-bit x86 architecture, regardless of processor brand. ARM64 is different. If an Apple Silicon compatibility download is labeled x64, check that a compatibility layer is available. Renaming a file cannot change its architecture.
After installing the client, you’ll need a subscription link or configuration file. Check the format provided: Clash clients typically use YAML, while Surfboard requires a compatible format of its own. After the subscription downloads, select or enable the configuration and confirm that proxy groups and rules have loaded.
Subscription URLs may contain credentials. Don’t share them in public forums or screenshots. If an update fails, check the URL, expiration, and network errors before importing it again. Don’t submit a private subscription to an unfamiliar online conversion tool.
Subscription Import Steps →Desktop system proxies, mobile VPNs, and TUN connections affect traffic differently. First confirm the core is running, then make sure the apps you want online are connected through the right method. Rule mode determines traffic policy; it doesn’t enable the system proxy. Check both settings.
Before upgrading or switching clients, save your subscription source, custom rules, and local configuration. After upgrading, check ports, the active configuration, and permissions. When switching platforms, update file paths and grant system permissions again. Visible proxies don’t guarantee that the new core supports every protocol or rule field.
Connection Verification Steps →From choosing an installer to checking version information, identify whether the issue is with downloading, installation, or connection, then find the relevant answer.
Start with Clash Plus on Windows, macOS, Android, or iOS; for Linux, try Clash Verge Rev. After downloading, import your existing subscription, enable the configuration, then follow the setup guide to check your system proxy or VPN connection. The standalone Mihomo core is better suited to server and router users.
AMD64 and x64 usually refer to the same 64-bit x86 architecture; ARM64 is a different processor architecture. Check your processor in system information before choosing a package. If an Apple Silicon compatibility download is labeled x64, it is not a native ARM64 build and requires a compatibility layer.
Version numbers come from a runtime version manifest and appear only when it includes a non-empty version field. A missing version does not mean the installer is unavailable: use the download button and check the installed version in the client’s About screen. Package file versions may also differ from the app version listed in the manifest.
The installer provides the client application; a subscription or configuration file provides proxies, proxy groups, and rules. After importing, select and enable the configuration, make sure the core is running, then set up a system proxy, VPN, or TUN connection. Installing the client alone does not create usable proxies.
Save your subscription source, custom rules, proxy group settings, and any local configuration you need to migrate. Subscription links may contain credentials, so restrict access to backups. After upgrading, check the active configuration, ports, and system connection method. When switching clients, also verify configuration format and core support.
Archived downloads for Clash for Windows and ClashX Meta are intended for migrating existing setups and checking compatibility. For a new installation, choose a maintained client. The standalone Mihomo core is for server and router users who can manage configuration, services, and logs themselves; desktop beginners should use a graphical client.