Choose your operating system, then check the processor architecture. Use a GUI client for everyday use; choose the core for servers, routers, and self-managed services.
Choose a package Import a subscription Enable the proxy
Clash Plus is the recommended choice on supported platforms. On Linux, start with Clash Verge Rev.
All GUI client packages below are x64. Check your system type under “Settings → System → About.” Windows on ARM users should separately confirm compatibility with the app and its service components.
For users who want to manage desktop and mobile configurations from one product. After installation, import a subscription and check the proxy groups before enabling the system proxy. Set up launch at startup and traffic routing only if needed; you don’t have to enable everything on first launch.
Windows x64 · EXE installer
For desktop users who need to manage subscriptions, rules, and overrides. For features such as TUN, install or enable the service component when prompted. The system proxy and TUN work differently; verify one traffic-routing method before enabling additional options.
Windows x64 · EXE installer
For users who want a similar workflow across multiple devices. After importing a configuration, check its name, proxy groups, and mode, then review the connection logs. When migrating from another client, transfer the YAML configuration and subscription first; don’t overwrite the entire app data directory.
Windows AMD64 · EXE installer
Another Windows GUI client for users who prefer to adjust configuration and proxy policies in an app. Before switching, quit the previous proxy client to avoid multiple apps managing the same ports, system proxy settings, or virtual network adapters.
Windows x64 · EXE installer
Archived download for reproducing legacy environments and migrating configurations—not recommended for new installs. Older cores have limited support for newer protocols and configuration fields. During migration, keep your subscriptions, custom rules, and overrides. Get the base configuration working in a maintained client before restoring extra features.
Windows · Legacy installer
| Check | What to know |
|---|---|
| Windows version | Use a supported version of Windows 10 or 11. Check the installer for each package’s minimum version and runtime requirements. |
| Processor | Packages in this section are mainly x64 / AMD64 and won’t run on 32-bit Windows. On ARM devices, check emulation and driver compatibility. |
| Permissions and ports | Service components and TUN may require administrator permission. If startup fails, check whether another program is using the configured ports. |
Check your chip under “About This Mac.” Clash Plus offers separate packages for each architecture. Some products below still return x64 files from their Apple Silicon links; these are labeled. Before installing, check Rosetta and macOS version compatibility.
Choose the native build for your Mac where available: ARM64 for M-series chips and x64 for Intel processors. Open the DMG and follow the prompts. Grant any required network permissions on first launch, then import a subscription. Product details are available at clashplus.io.
macOS · ARM64 / x64 · DMG
For Mac users who need to manage rules, subscriptions, and overrides. Both architecture links currently provide x64 DMGs, so Apple Silicon users should check Rosetta compatibility. When enabling a service or TUN for the first time, follow macOS permission prompts. If the system blocks the app, check its source and the prompt; don’t disable system protections globally.
Currently available: x64 · DMG
Offers a similar configuration workflow across desktop and mobile. The current Mac build is labeled AMD64, and both links download the same file. Apple Silicon users should check Rosetta compatibility before installing. After migration, check proxy group names and DNS settings one by one.
Currently available: AMD64 · DMG
Archived build for legacy menu bar workflows and configuration migration. The current archive is x86_64, and both architecture links point to the same file. Permissions, network extensions, and newer configuration fields may not work on current macOS versions. Consider migrating your subscriptions to a maintained client.
Archived · currently available: x86_64
| Check | What to know |
|---|---|
| Windows version | Minimum macOS versions vary by client. Check the app’s release notes and system installer prompts; confirm compatibility before using older versions of macOS. |
| Chip architecture | Apple Silicon uses ARM64; Intel uses x64. If the available package is x64, check Rosetta compatibility before installing. |
| Network permissions | System proxy, helper services, and TUN require different permissions. Follow the prompts for your client, and don’t run multiple traffic-routing apps at the same time. |
ARM64 is the usual choice for newer devices; choose ARMv7 for older ARM devices. If Android reports that a package is incompatible, check the architecture and OS version instead of repeatedly installing the same file.
ARM64 package for compatible Android devices. On the first connection, Android will ask to set up a VPN connection. Grant permission, then check the connection status. Installing the app doesn’t include a working configuration; import your own subscription and select a proxy group.
Android ARM64 · APK
Offers ARM64, ARMv7, and universal packages for users who want to choose a specific device architecture. Universal packages are usually larger, but remove the guesswork. After importing a configuration, check that rules and proxy groups have loaded. If the connection drops, check Android’s background activity restrictions.
Android · APK · Choose by device architecture
For users who want a similar workflow on desktop and mobile. Install the ARM64 or ARMv7 package, then configure per-app proxying if needed. If another VPN service is active, disconnect it first; Android typically allows only one standard VPN service to route traffic at a time.
Android ARM64 / ARMv7 · APK
For Android users whose configuration format and protocols are supported by Surfboard. It isn’t a drop-in replacement for importing Clash YAML. Before downloading, confirm that your configuration source supports Surfboard, and check rules and policy names against its syntax. Renaming a file extension alone won’t migrate a configuration.
Android universal build · APK
| Check | What to know |
|---|---|
| OS and architecture | Check your Android version and ABI. Choose ARM64 or ARMv7 based on the device architecture, not the phone brand. Check the installer for the minimum OS version. |
| Install permissions | Grant install permission only to a trusted browser or file manager for this installation. Review or revoke it in system settings afterward. |
| VPN and background activity | A VPN connection requires permission. If it disconnects in the background, check battery optimization and background activity permissions; adjust only what’s needed rather than disabling all restrictions. |
Install Clash Plus from the App Store. Check the store listing for compatible iOS versions, supported devices, and current product details.
Install from the App Store listing, then open the client and import a compatible subscription or configuration. When connecting for the first time, follow the iOS prompt to add a VPN configuration. Return to the client to check the active policy and connection status. Available subscriptions and services depend on your configuration.
Official site: clashplus.io. Before switching phones or migrating a configuration, save your subscription URL and custom rules instead of relying only on app data stored on the old device.
iOS · App Store
| Check | What to know |
|---|---|
| OS and device | Check the App Store’s compatibility section for the minimum iOS version and supported device types before installing. |
| Network permissions | On first connection, follow the system prompt to add a VPN configuration. If another app is already routing network traffic, check which configuration is active. |
| First-time setup | Import a compatible subscription and confirm the proxy policy. After turning on the connection, verify that apps access the network as expected. |
Packages in this section are AMD64 GUI desktop builds. Check your distribution’s package format and desktop dependencies. For headless servers and ARM routers, see the Mihomo core downloads.
Offers deb and rpm packages for desktop users who manage subscriptions and rules through a GUI. Install with your distribution’s package manager when possible to handle dependencies. Check service permissions before enabling TUN; opening the app successfully doesn’t mean traffic routing is working.
Linux AMD64 / x86_64 · deb / rpm
AMD64 deb package for desktop environments using a compatible package format. After importing a configuration, check whether apps follow the system proxy settings. Command-line tools may need separate environment variables; browser access alone doesn’t mean all processes are routed through the proxy.
Linux AMD64 · deb
| Check | What to know |
|---|---|
| Distribution | Choose deb for Debian- and Ubuntu-based distributions, or rpm for Fedora- and RHEL-based distributions. Check dependencies and compatibility for derivative distributions. |
| Processor | Run uname -m to check the architecture: x86_64 corresponds to AMD64; aarch64 corresponds to ARM64. The AMD64 packages in this section won’t run on ARM64. |
| Desktop and permissions | GUI clients require a desktop environment and the relevant runtime libraries. Core traffic routing, routing table changes, and service management require separate permissions and configuration. |
For users managing services on servers and routers. The core doesn’t include a desktop settings interface; you’ll need to provide a YAML configuration, working directory, and service management setup. Most users should choose a GUI client above.
Windows builds come as zip files. macOS and most Linux builds are gz archives containing an executable, not a desktop installer. Linux AMD64 also has a deb package for managing installation through a package manager.
| System | Architecture and format | Download |
|---|---|---|
| Windows | AMD64 · zip | Download AMD64 zip |
| Windows | ARM64 · zip | Download ARM64 zip |
| macOS | Intel AMD64 · gz | Download Intel gz |
| macOS | Apple Silicon ARM64 · gz | Download ARM64 gz |
| Linux | AMD64 · deb | Download AMD64 deb |
| Linux | AMD64 · gz | Download AMD64 gz |
| Linux | ARM64 · gz | Download ARM64 gz |
| Linux | ARMv7 · gz | Download ARMv7 gz |
| Linux | MIPS softfloat · gz | Download MIPS softfloat gz |
| Check | Deployment notes |
|---|---|
| Configuration file | Prepare a valid YAML file, rule references, and a writable data directory. Test the base configuration before adding it to a background service. |
| Network permissions | Proxy ports and the permissions required for TUN or routing differ. Grant permissions as needed for each feature; don’t run everything with elevated privileges by default. |
| Service management | Set the launch arguments, log location, restart policy, and shutdown procedure to prevent old services and new processes from competing for the same ports. |
The installer only installs the program. A working connection also depends on your configuration, proxy policy, and traffic-routing method.
Import an existing subscription or local YAML file, then check which configuration is active. If you see a syntax error, missing proxy group, or failed rule reference, fix that before enabling the system proxy. Subscription URLs often contain access credentials; store them securely and hide sensitive parts before sharing log screenshots.
A desktop system proxy mainly affects apps that follow system settings. Command-line tools, games, and apps with their own network stack may need separate configuration. TUN routes traffic through a virtual network interface and also affects routing and DNS settings. For your first setup, verify a simple connection path. Once rules and proxy groups work, enable TUN, per-app proxying, or launch at startup as needed.
Quit the old client and export custom rules, overrides, and key settings before installing the new version. Don’t copy one product’s entire data directory over another’s. Import the base subscription first, confirm it works, then restore additional settings one by one. If the system proxy still points to an old port, apps may fail to connect even when the new client is running.
For setup steps, see the first-time setup guide. For details on rules, DNS, TUN, and maintenance, read the user guide. If you’re unfamiliar with architecture or configuration terms, start with the glossary.
Start with file format, architecture, and migration method to avoid mistaking a configuration issue for an installation problem.
For desktop and mobile devices, start with a GUI client. It provides subscription import, proxy group selection, and settings. The Mihomo core is mainly for servers, routers, and self-managed services; you’ll need to provide a configuration file and decide how to launch it. You’ll still need to import a working configuration after installation.
Check your processor type in system information, then choose the package architecture shown on the download button. x64 and AMD64 refer to the same desktop architecture; ARM64 is common on newer Android devices and Apple Silicon Macs. If you can’t confirm your Android device’s architecture, choose a client that offers a universal build. Some Mac links still point to x64 files; Apple Silicon users should check Rosetta compatibility rather than relying on the link label.
The installer provides the client app, not a working subscription or proxy service. Import your own subscription or configuration, make sure it’s enabled, and select a proxy group. Then enable the system proxy or VPN routing as needed. When troubleshooting, check configuration loading errors first, then review the connection logs. Avoid changing several network settings at once.
Before upgrading, export your subscriptions, custom rules, overrides, and important settings, and store the backup somewhere secure. When migrating, import the base configuration first and confirm the new client can parse it before restoring overrides one by one. Settings and data directories aren’t interchangeable between clients, and subscription URLs shouldn’t be shared publicly.
Clash for Windows and ClashX Meta are listed here as archived downloads, mainly for recreating legacy environments and migrating configurations. For a fresh install, choose a client that’s still maintained. Older cores may not support newer protocols, rule fields, or DNS options. If a configuration fails, check compatibility before reinstalling the same archived build.
Debian- and Ubuntu-based distributions typically use deb packages; Fedora- and RHEL-based distributions typically use rpm. Check that the package is for AMD64 and that desktop dependencies are met. For headless servers and routers, choose the matching Mihomo core build. After extracting an archive, you’ll need to set executable permissions, configure the file path, and manage the service yourself; it isn’t a desktop installer.
Installed, but still having connection issues? Visit FAQ to troubleshoot configuration loading, traffic routing, and DNS.