Client downloads · Choose by system and architecture
Choose your device’s operating system, then select a package. For desktop and mobile, start with Clash Plus; for Linux, see Clash Verge Rev. Servers and routers can go straight to the Mihomo core.
You’ll still need to import a valid subscription or configuration after installing the client. To compare features, start with the client comparison guide.
DESKTOP / WINDOWS
For a first install, start with Clash Plus. If you need desktop rule management and core settings, compare Clash Verge Rev, FlClash, and Clash Nyanpasu. The desktop installers listed here are x64 builds. Windows ARM users should first confirm that their system supports running the app through compatibility emulation; an x64 installer is not a native ARM64 build.
A good everyday client for Windows. After installing, add a configuration, then choose a rule mode and proxy policy. Enable system proxy or TUN depending on which apps need access. For your first setup, enable only one connection method so you can verify how traffic is routed.
A desktop client for managing configurations, proxies, connections, and logs in one place. After importing a subscription, make sure the configuration is selected. If you need TUN, check service permissions and the virtual network interface. Quit the previous client before switching to avoid port conflicts.
A good fit if you want a similar interface across devices. The Windows download is an installer; add your subscription from the configuration screen after installation. Compatible configuration content may be reusable when migrating, but check local interface preferences, shortcuts, and service settings separately.
A graphical interface for configuration and proxy management. A good option if you already have a Clash configuration and want to compare desktop workflows. After importing, check rule group names, core selection, and port settings before enabling background services or startup on boot.
Archived download for reproducing legacy environments and reference during migration. For new installations, choose one of the clients above. Older cores have limited support for newer protocols and configuration fields, so importing a newer subscription may cause parsing errors. Keep a copy of the original configuration before migrating; don’t overwrite your only backup.
| Item | Before installing |
|---|---|
| System and architecture | Use a supported version of Windows 10 or 11. This section mainly offers x64 installers; check the installer prompt for the minimum supported Windows version. |
| Permissions | Standard installation, service installation, and TUN have different permission requirements. Grant permissions as prompted by the client when using a service or virtual network adapter. |
| Existing proxies | Quit the old client and turn off its system proxy. If a port is in use, find out what’s using it rather than starting multiple proxy services at once. |
After installation, start by testing the system proxy to narrow down issues. For UWP app access, see Clash UWP loopback settings. For background startup, see Clash startup on boot. These are separate from importing a subscription.
DESKTOP / MACOS
Open About This Mac from the Apple menu to check whether your device has an Apple chip or an Intel processor. Clash Plus has separate ARM64 and x64 builds. Some other clients currently use the same x64 file for both architecture links, as noted below. Compatibility on Apple Silicon depends on macOS support; the link label does not mean the package is a native ARM64 build.
Choose the DMG that matches your chip. Open the disk image, drag the app to Applications, then launch it and import your configuration. Approve network access if macOS prompts you. When switching from another client, turn off its system proxy first.
A desktop-window interface for managing configurations and rules. Both macOS links currently point to the same x64 image; Apple Silicon users should confirm compatibility first. After importing, check the system proxy status. Configure TUN permissions separately if needed.
A good fit if you manage subscriptions across devices. The current image is amd64, also known as x64; both architecture links point to this same package. After installation, check that your configuration’s protocols are supported before enabling a connection mode. Don’t assume permissions work the same way across operating systems.
Archived menu bar client, useful for preserving an older workflow or referencing configuration during migration. The current download is x86_64. Check compatibility with your macOS version, permissions, and configuration. For a new installation, choose a maintained option above.
| Item | Before installing |
|---|---|
| Chip type | Apple M-series chips use ARM64; Intel Macs generally use x64 / x86_64. Choose a native build that matches your processor whenever possible. |
| macOS version | Minimum macOS versions vary by client. Check the app details and installer prompts. On older systems, confirm runtime and compatibility requirements first. |
| Installation and permissions | A DMG is a disk image, not an application folder. Copy the app to Applications before launching it. Grant permissions for network extensions or helper services as prompted. |
If macOS displays a security warning, verify the app name and download source, then check the specific reason in System Settings. Don’t disable system security protections broadly just to run an app. System proxy, menu bar status, and TUN are separate settings; check each one when troubleshooting.
MOBILE / ANDROID
Most recent Android phones can use the ARM64 build. Older 32-bit ARM devices should use ARMv7. If you’re unsure of your architecture, check your system information or choose the universal build of Clash Meta for Android below. The first time you install an APK, Android may ask you to allow this browser or file manager to install apps.
A mobile GUI for importing subscriptions and choosing policies. After installation, load a configuration, start the connection, and approve Android’s VPN prompt. For longer background sessions, check whether Android’s battery settings restrict the app.
Includes architecture-specific packages and a universal build. If you already have a compatible Clash Meta configuration, import it and check that it loads correctly. The universal build is useful when you’re unsure of your device architecture, but the app’s system requirements still apply.
A good choice if you use the same subscription across desktop and mobile and want a similar configuration workflow. Choose ARM64 or ARMv7 to match your device. After importing, check policy groups and DNS settings. Android routes traffic through its VPN interface when the connection starts.
For users with a Surfboard-compatible configuration. Surfboard uses a different configuration format from Clash YAML, so matching node details don’t mean the entire configuration is interchangeable. Before downloading, check that your subscription’s format, rules, and protocols are supported.
| Item | Before installing |
|---|---|
| System and ABI | Check your Android version against the app’s supported range. arm64-v8a is ARM64; armeabi-v7a is 32-bit ARM. |
| Installation permissions | Android manages APK installation permissions by source. Grant permission only to the browser or file manager you use, and follow the system prompts. |
| VPN access | VPN apps generally can’t control connections at the same time within the same user profile. Exit other VPN services before starting this one. |
Updates usually retain app data, but packages from different branches or signed differently may not install over the existing app. If Android reports a signature conflict, export your configuration and verify the app source first. Don’t immediately uninstall the only app that contains your subscription. Subscription links may contain access credentials; don’t include them in public screenshots.
MOBILE / IOS
Find Clash Plus in the App Store for iPhone and iPad. Check the store listing for compatible devices, system requirements, and current availability. After installing, prepare a valid subscription or configuration, then import it and choose your policies in the app.
Install and manage updates through the App Store. The first time you connect, follow the iOS prompt to add a VPN configuration. After approving it, return to the app and check the connection status. Rule mode depends on the configuration that’s loaded; installing the app doesn’t activate a subscription.
| Item | Before installing |
|---|---|
| Device and system | Check the App Store listing for iPhone and iPad compatibility and the minimum iOS version. Use the current store listing as the source of truth. |
| Installation and updates | Install and update through the App Store. For app details and feature information, you can also visit clashplus.io. |
| VPN configuration | Approve the system prompt the first time you connect. If you already have other VPN configurations, check which service is currently active. |
What happens to a connection when the app moves to the background depends on iOS and the client’s settings. If you have connection issues, return to the app to check the configuration and logs, then verify the system VPN status. Don’t rely on the status bar alone to determine whether traffic is being routed as expected.
DESKTOP / LINUX
If your system has a desktop environment, start with a GUI client. Debian, Ubuntu, and compatible distributions typically use DEB packages. For Fedora, openSUSE, and others, check RPM compatibility for your distribution. The GUI packages here are amd64 / x86_64; for ARM servers and routers, see the core downloads instead. Don’t install a desktop package built for a different architecture.
Manage configurations, policies, and connections on a Linux desktop. Choose DEB or RPM for your distribution and let the system package manager handle dependencies. Whether apps use the system proxy depends on the desktop environment and the app itself. TUN requires additional permission and routing checks.
A DEB package for Linux desktops, useful if you manage compatible subscriptions across multiple devices. Launch the app from a regular user session first and check that the graphical dependencies and configuration load correctly. Set up background services or traffic routing only if needed.
| Item | Before installing |
|---|---|
| Processor | Check your architecture in system information or run uname -m. x86_64 matches the amd64 package listed here; aarch64 is ARM64. |
| Distribution and dependencies | Choose a package format that matches your package manager. Check the installer notes for minimum runtime libraries, graphical components, and desktop integration requirements. |
| Permissions and traffic routing | The desktop system proxy does not route every process. Check environment variables, routing, and permissions separately for command-line tools, containers, and TUN. |
On a headless server, you don’t need to install a full desktop environment just to run a proxy. Use the Mihomo core below and manage the process with a service manager. You’ll need to configure the file paths, logs, listen address, and access controls yourself.
CORE / MIHOMO
For servers, routers, and manual deployments. Most desktop users should choose a GUI client above.
Mihomo handles protocol connections, DNS, and rule execution; it does not include a full desktop interface. Before downloading, check your operating system, CPU architecture, and package format. After extracting the archive, you’ll still need to prepare a configuration file and set execution permissions. Copying the binary to a device does not automatically configure transparent proxying, routing, or DNS interception.
| System | Architecture | Format and use | Download |
|---|---|---|---|
| Windows | AMD64 / x64 | ZIP · 64-bit x86 systems | Download AMD64 ZIP |
| Windows | ARM64 | ZIP · ARM systems | Download ARM64 ZIP |
| macOS | Intel / AMD64 | GZ · Compressed executable | Download Intel GZ |
| macOS | Apple Silicon / ARM64 | GZ · Compressed executable | Download Apple Silicon GZ |
| Linux | AMD64 | DEB · Debian-based package managers | Download AMD64 DEB |
| Linux | AMD64 | GZ · Manual installation | Download AMD64 GZ |
| Linux | ARM64 | GZ · 64-bit ARM devices | Download ARM64 GZ |
| Linux | ARMv7 | GZ · 32-bit ARM devices | Download ARMv7 GZ |
| Linux | MIPS soft-float | GZ · Match the device’s instruction set and byte order | Download MIPS GZ |
For routers, also check byte order, system ABI, firmware, and available storage. MIPS and MIPSEL use different packages, and soft-float is not a universal option for all MIPS devices. Don’t try to force an incompatible package by renaming it. Check your device specifications before deployment.
Back up your current configuration and service startup arguments before updating. After launching the new core, check configuration parsing and logs before restoring automatic startup. GUI clients often manage their own core; replacing files in the application directory may conflict with app updates. Learn how protocols relate to the core in Protocol Guide.
Downloading installs the software; connecting also requires a configuration and a system-level way to route traffic.
Identify your operating system first, then your processor, and finally the installation format. EXE, DMG, APK, DEB, and RPM are for different environments; changing a file’s extension won’t convert it. Installer compatibility details are more precise than the broad label “64-bit,” especially when distinguishing x64 from ARM64.
The version shown on a page and the installer filename may come from different release metadata. Use the package details and actual file type to determine the supported architecture. If your system reports an incompatibility, check the OS version and CPU instead of repeatedly opening the same installer.
The client and subscription service are separate. After importing a valid configuration, confirm it’s selected and that its policy groups have usable options. Then enable the system proxy or VPN. Rule mode matches traffic against rules in order; choosing a policy in global mode can’t fix an expired subscription or an unsupported protocol.
Before migrating, back up the original subscription URL, local overrides, and custom rules. Don’t copy entire cache directories between different clients. For the full procedure, see the Clash Setup Guide; for definitions, see the Glossary.
First make sure the installer matches your device, then check the configuration and network connection.
Windows, macOS, Android, and iOS users can start with Clash Plus for their platform; Linux users can start with Clash Verge Rev. If you already have a configuration, make sure the client’s core supports its protocols and fields. Installers include the client only; you’ll need to obtain nodes and a subscription separately.
Check your CPU architecture in your system information first. x64 and amd64 generally refer to the same 64-bit architecture; ARM64 is for compatible ARM devices. If you can’t identify your Android architecture, consider the universal build of Clash Meta for Android. Some macOS download links currently point to the same x64 file; Apple Silicon users should confirm compatibility support in macOS.
The client installer does not include a usable subscription. After installation, import a valid configuration, choose a policy group, then enable system proxy or VPN access as needed for your device. If you still can’t connect, first check that the configuration loaded, then review the client logs and rule matches. Follow the setup guide to verify each step.
Both clients are no longer maintained. Archived downloads are kept here for legacy compatibility and configuration migration. For a new device, choose a maintained client. Older cores may not recognize newer protocols or configuration fields. Back up your configuration before migrating, and don’t run system proxy or TUN mode in two clients at the same time.
GUI clients provide graphical tools for subscriptions, proxies, and logs, and may also manage the core. The Mihomo core handles connections and rule execution; running it directly requires you to manage the configuration, permissions, and service yourself. Most desktop users should choose a GUI client. Server and router users can select a core build for their architecture.
First make sure the download finished and the file type matches your device and operating system. Then check the CPU architecture, available storage, and any system installation prompts. On Linux, also check the distribution’s package format and dependencies. Restart interrupted downloads. If the installer shows an error, save the message and look up the cause by operating system and client name.
Installed the client but still having configuration issues? Check the FAQs, or follow the setup guide to check your subscription, mode, and connection tests.