Clients and matching installers are grouped by operating system below. Download links are resolved from the version manifest in real time when the page loads, so they always point to each client's current release; version numbers and system requirements are marked in monospace, so check your device architecture before choosing.
Windows has the most client options, and the five below are ordered by maintenance status and ease of use. For everyday use, the installer version (setup.exe) is all you need; the setup wizard handles autostart and the WebView2 dependency. If you need a portable option, FlClash offers a zip archive that requires no installation.
A clean, multi-platform client that keeps subscription import, node speed testing, rule-based routing and system proxy toggling all on one screen, so first-time users rarely need to check the docs. Desktop and mobile share the same interaction logic, so there's no relearning curve across devices, making it the most beginner-friendly option right now.
An actively maintained community Tauri client with the mihomo core built in, supporting TUN mode, multiple config profiles, Merge/Script enhancements and scheduled subscription updates. It goes deeper than Clash Plus, making it a good fit for advanced users who need fine-grained routing control and frequently edit config files.
An open-source client built with Flutter, sharing one UI across desktop and Android, with clean, intuitive light/dark themes and a node latency panel. It also ships a no-install zip archive that just needs unzipping and writes nothing to the registry, making it a good fit for portable drives or restricted environments where installing software isn't an option.
A community fork sharing a codebase with Verge, offering richer UI animations and theme customization along with multi-core switching and chained proxy configs. Its feature set overlaps heavily with Verge Rev, so pick whichever interface you prefer; users already on Verge don't need to install this as well.
Once the de facto standard Windows client, it stopped receiving updates in 2023; the final release is provided here as an archive. The original core doesn't support newer protocols, and its rules and Geo data no longer track the wider ecosystem, so it's only recommended as a short-term bridge for migrating old configs. New users should pick one of the actively maintained clients above.
SYSTEM REQUIREMENTS · WINDOWS
| Item | Requirement |
|---|---|
| Operating system | Windows 10 / 11 (64-bit) |
| Processor architecture | x64 |
| Disk space | ≥ 200 MB |
| Runtime dependency | WebView2 (auto-detected and installed by Verge Rev / Nyanpasu setup) |
| Permissions | TUN mode requires installing the virtual network adapter service as administrator |
On macOS, pick the installer that matches your chip: M-series Macs from 2020 onward should use the Apple Silicon build, while older Macs should use the Intel build. A single click on the menu bar icon handles routine node switching and mode changes.
Keeps the same interaction logic on macOS as other platforms: subscription management, node latency and routing mode are all in the main window, with a menu bar icon for quick toggling. Users migrating from another OS won't need to relearn the interface.
Fully matches the Windows version's feature set: TUN mode, system proxy guard, config-enhancing scripts and scheduled subscription updates are all included. If you need to build complex routing rules or maintain multiple config files on your Mac, this saves more time than a lighter client would.
A cross-platform Flutter build that runs just as smoothly on Mac, with a leaner config surface than Verge while still keeping core capabilities like TUN mode, rule grouping and latency testing. A good fit for users who just want a stable connection without diving deep into configuration.
The Meta core fork of the classic menu bar client ClashX, known for its minimalism: there's no main window, everything is handled from the menu bar, and resource usage is minimal. The project has stopped receiving updates; existing builds still work, but no longer track new protocols or system changes, so long-term users should consider migrating to one of the clients above.
SYSTEM REQUIREMENTS · MACOS
| Item | Requirement |
|---|---|
| Operating system | macOS 11 Big Sur or later |
| Chip | Apple Silicon (M1 and later) / Intel |
| Disk space | ≥ 250 MB |
| Permissions | TUN mode requires authorizing a system extension or helper tool |
Android clients are all distributed directly as APKs. Check your processor architecture before downloading: most recent mainstream devices should use arm64-v8a, older 32-bit devices should use armeabi-v7a, and if you're not sure, pick the universal package. During installation you'll need to allow app installs from your browser or file manager in system settings.
The closest thing to a plug-and-play experience on Android: import a subscription, pick a node, and turn on VPN mode to connect in three steps, with per-app proxying and scheduled subscription updates ready to go from the settings page. The interface matches the desktop version, so multi-device users don't need to relearn anything.
The official Android client built on the Clash Meta core, with the most complete configuration surface: config overrides, an external controller API, per-app routing and custom DNS are all exposed. The interface leans technical, making it a good fit for users already familiar with Clash config syntax who want desktop-level routing control on their phone.
The Android build shares the same interface as the desktop version, with a consistent experience for subscription grouping, latency sorting and theme switching. Its configuration options sit between Clash Plus and Clash Meta for Android, giving newcomers a place to start while still keeping advanced entry points like rule overrides.
An Android client compatible with the Surge config format, aimed at users who already have Surge rules and want to reuse them directly on an Android device. Users on Clash subscriptions should pick one of the three clients above instead, since no config conversion is needed there.
SYSTEM REQUIREMENTS · ANDROID
| Item | Requirement |
|---|---|
| Operating system | Android 8.0 (API 26) or later; Surfboard requires 5.0+ |
| Processor architecture | arm64-v8a preferred / armeabi-v7a / universal |
| Storage space | ≥ 100 MB |
| Permissions | The first connection requires VPN authorization; disabling battery optimization is recommended for background persistence |
iOS is distributed through the App Store, which handles installation and future updates automatically, with no need to manage installer files manually.
Built on the system's Network Extension framework, with subscription import, node switching and rule-based routing working the same way as on Android and desktop, supporting both iPhone and iPad. Updates are pushed automatically through the App Store. For more platform news and documentation, see the official site clashplus.io.
SYSTEM REQUIREMENTS · IOS
| Item | Requirement |
|---|---|
| Operating system | iOS / iPadOS 15.0 or later |
| Device | iPhone / iPad |
| Installation method | Installed via the App Store, with updates pushed automatically |
| Permissions | The first connection requires allowing the VPN configuration in the system prompt |
Linux desktop environments get both deb and rpm packages: Debian, Ubuntu and derivatives should use deb, while Fedora, openSUSE and similar distros should use rpm. Servers and headless setups should switch to the "Core" tab and use the Mihomo command-line build instead.
Currently the most reliably maintained GUI client on Linux desktops, with the system tray, TUN mode and autostart all working correctly on mainstream distributions. Install the deb package with apt or dpkg, and the rpm package with dnf or rpm; dependencies are resolved automatically by the package manager.
The Flutter desktop build also runs on Linux, with an interface identical to the Windows and macOS versions. It covers everyday proxy use cases well, though its deep customization is weaker than Verge Rev's, making it a good fit for desktop users who prefer a simpler interface.
SYSTEM REQUIREMENTS · LINUX
| Item | Requirement |
|---|---|
| Distribution | Debian 11+ / Ubuntu 22.04+ / Fedora 38+ and mainstream derivatives |
| Processor architecture | x86_64 |
| Desktop environment | GNOME / KDE, etc.; enable system tray extension support first if needed |
| Permissions | TUN mode requires root or the corresponding capability grant |
Mihomo is the core program in the Clash Meta lineage, pure command-line with no GUI, aimed at server-based, router firmware and automated deployment scenarios. You'll need to prepare your own config file and run it via the command line or systemd; desktop and mobile users should use the GUI clients above for their platform, which already bundle the core.
Note: both zip and gz are compressed archives that unpack into a single executable; the Linux amd64 build is also offered as a deb package, which the package manager can install and upgrade for you. For router devices, choose the arm64, armv7 or mips-softfloat build according to your firmware's instructions.
| Target system | Architecture | Format | File |
|---|---|---|---|
| Windows | amd64 | zip | mihomo-windows-amd64.zip |
| Windows | arm64 | zip | mihomo-windows-arm64.zip |
| macOS | Intel (amd64) | gz | mihomo-darwin-amd64.gz |
| macOS | Apple Silicon (arm64) | gz | mihomo-darwin-arm64.gz |
| Linux | amd64 | deb | mihomo-linux-amd64.deb |
| Linux | amd64 | gz | mihomo-linux-amd64.gz |
| Linux | arm64 | gz | mihomo-linux-arm64.gz |
| Linux | armv7 | gz | mihomo-linux-armv7.gz |
| Linux | mips-softfloat | gz | mihomo-linux-mips-softfloat.gz |
Frequent questions about getting installers, choosing an architecture and system warning prompts. For configuration and usage questions, see the troubleshooting and tutorials pages.
No, they don't stay stuck on old versions for long. When the page loads, it resolves the latest release files for each client from a version manifest in real time and swaps in the download URLs, and the version numbers shown on each card refresh accordingly. If a network issue prevents that resolution, the buttons fall back to a recent version link built into the page, so downloads still work, and you can update from within the client afterward.
Most devices released after 2019 use 64-bit processors, so arm64-v8a is the right choice for those; older 32-bit devices should pick armeabi-v7a. If you're unsure of your device's architecture, choose the universal package, which is larger but works on all architectures. Installing the wrong architecture simply fails at install time with no other side effects; just reinstall with the matching package.
This is SmartScreen's default block for open-source software that hasn't purchased a commercial signing certificate, not a detected threat. Click "More info" in the prompt, then click "Run anyway" to continue installing. Open-source clients rarely purchase expensive code-signing certificates, so this warning is common and expected.
Right-click the app icon in Finder, choose "Open," and confirm once in the dialog that appears; alternatively, go to System Settings → Privacy & Security, scroll to the bottom, and click "Open Anyway." If macOS says the file is damaged, run xattr -cr /Applications/AppName.app in Terminal to clear the quarantine attribute, then try opening it again.
After the first launch you need to import a subscription to establish a connection: paste your subscription link into the client's config or subscription page, update it, pick a proxy node, then enable the system proxy or TUN mode. The tutorials page walks through the full process, from importing a subscription to verifying connectivity, and if you run into connection issues, work through the troubleshooting checklist.
The core is a command-line program with no graphical interface, built for servers, routers and automated scripts; you need to write your own config file and run it via the command line or systemd. Desktop and mobile users should just use the GUI clients listed on this page for their platform, since those already bundle the core and don't need it downloaded separately; see the side-by-side comparison for how each client's core implementation differs.