An installer index grouped by operating system. Each card notes the current version, supported architecture, and maintenance status; version numbers are parsed live from the version API on page load, always pointing to the currently distributed release. Server and router users can switch to the "Core" tab to get Mihomo files for every architecture.
Windows has the widest choice of clients. First-time users should start with the first card; if you need TUN mode, config overrides, or other advanced features, check out Clash Verge Rev. Clash for Windows at the end has stopped updating and is kept only as an archive.
Clash Plus
Top Pick
v—
A multi-platform client built on the Meta core. Subscription import, node switching, and rule management all happen inside the GUI, with a consistent experience across all five operating systems — a solid starting point for anyone new to Clash.
Clash Verge Rev
Recommended
v—
A Tauri-based desktop client with an actively maintained community. Supports TUN mode, config overrides, and Merge/Script enhancements — a common pick for advanced desktop users.
FlClash
v—
A multi-platform client written in Flutter, with a minimal interface that works right away with the default configuration. Desktop and mobile share the same interaction logic, keeping the switching cost low for multi-device users.
Clash Nyanpasu
v—
A snappy desktop client with a built-in config editor and script extension entry point, supporting multiple config profiles. This site hosts its Windows installer.
Once the most widely used Windows client, updates stopped at the end of 2023. The archived installer is kept here to help with migrating old configs; for everyday use, pick an active project from the list above.
| Client | Minimum OS | Architecture | Maintenance Status |
|---|---|---|---|
| Clash Plus | Windows 10 64-bit | x64 | Active |
| Clash Verge Rev | Windows 10 / Windows 11 on ARM | x64 / ARM64 | Active |
| FlClash | Windows 10 64-bit | amd64 | Active |
| Clash Nyanpasu | Windows 10 64-bit | x64 | Active |
| Clash for Windows | Windows 7 64-bit | x64 | No longer maintained |
macOS installers come in two builds by chip: Apple Silicon (M-series) and Intel. Check your chip type under "About This Mac" before downloading. Installing the wrong architecture will still run, but performance and battery life will take a hit.
Clash Plus
Top Pick
v—
The macOS build of the Meta-core multi-platform client. Lives in the menu bar, with subscription and rule management identical to other platforms — pairs smoothly with the iPhone version.
Clash Verge Rev
Recommended
v—
One of the most feature-complete active desktop clients. TUN mode, system proxy guarding, and config overrides all work on macOS — suited to users who want fine-grained control.
FlClash
v—
A consistent, minimal interface across platforms — import a subscription and it just works. Minimal configuration overhead for users who only need basic proxying and routing.
ClashX Meta
No Longer Maintained
v—
A Meta-core fork of the classic ClashX, with a minimalist menu bar style. The project is no longer maintained; existing versions still run and stay here to help longtime users transition.
| Client | Minimum OS | Chip | Maintenance Status |
|---|---|---|---|
| Clash Plus | macOS 11 | Apple Silicon / Intel | Active |
| Clash Verge Rev | macOS 10.15 | Apple Silicon / Intel | Active |
| FlClash | macOS 10.15 | Apple Silicon / Intel | Active |
| ClashX Meta | macOS 10.15 | Apple Silicon / Intel | No longer maintained |
Android installers are split by processor architecture. Mainstream devices released after 2016 should use arm64-v8a; if you're unsure, choose the universal build. You'll need to allow app installs from this source in system settings.
Clash Plus
Top Pick
v—
The Android build of the Meta-core multi-platform client. Subscription management, node speed testing, and rule-based routing are all handled through the GUI, matching the desktop client's logic.
The official Meta-core Android client, with an interface close to native Android style. Supports multiple config profiles and automatic subscription updates — a long-standing, stable choice on Android.
FlClash
v—
The mobile interface matches the desktop version and supports per-app routing. Default settings cover everyday use without excess configuration.
Surfboard
An Android client compatible with the Clash config format. The universal APK covers every architecture, including older devices — a solid fallback option.
| Client | Minimum OS | Available Architectures | Maintenance Status |
|---|---|---|---|
| Clash Plus | Android 7.0 | arm64-v8a | Active |
| Clash Meta for Android | Android 7.0 | arm64-v8a / armeabi-v7a / universal | Active |
| FlClash | Android 7.0 | arm64-v8a / armeabi-v7a | Active |
| Surfboard | Android 7.0 | universal | Slow maintenance |
iOS is distributed through the App Store. After installing, allow the system prompt to add a VPN configuration, then import a subscription — the workflow matches Clash Plus on other platforms.
Clash Plus
Top Pick
The iOS build of the Meta-core multi-platform client, available on the App Store. Subscription import, proxy group switching, and rule routing all happen inside the app; updates are pushed automatically through the App Store. The official site clashplus.io has feature details and links for every platform.
| Client | Minimum OS | Device | Distribution Channel |
|---|---|---|---|
| Clash Plus | iOS 15.0 | iPhone / iPad | App Store |
Linux desktop users should pick a format based on their distro's package manager: deb for the Debian/Ubuntu family, rpm for the Fedora/openSUSE family. Headless servers should switch to the "Core" tab and use Mihomo directly.
Clash Verge Rev
Recommended
v—
The most feature-complete active client on Linux desktop. TUN mode, system proxy, and config overrides all work; deb and rpm packages cover the mainstream distros.
FlClash
v—
A consistent, lightweight interface across platforms — install the deb package and it's ready to go. Suited to Linux desktop users who only need basic proxying.
| Client | Package Format | Architecture | Reference Distros |
|---|---|---|---|
| Clash Verge Rev | deb / rpm | x64 / ARM64 | Ubuntu 20.04+, Debian 11+, Fedora 36+ |
| FlClash | deb | amd64 | Ubuntu 20.04+, Debian 11+ |
Mihomo is the continuation core of the Clash Meta project — a single executable with no GUI. Built for servers, routers, and command-line environments: prepare a config.yaml and run it directly, or manage it with a third-party panel. Desktop and mobile users don't need to download the core separately — it's already bundled into the GUI clients above.
| System | Architecture | Format | Download |
|---|---|---|---|
| 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 |
After extracting the gz file you get a single executable — remember to grant execute permission with chmod +x; install the deb package with dpkg -i and it runs as a systemd service. The armv7 and mips-softfloat builds are mainly aimed at router firmware environments.
The download buttons on this page parse each client's latest version from the version API on page load, and the version numbers on the cards update in sync with the button links — no need to hunt for new releases manually. If the API is temporarily unavailable, buttons fall back to the most recently indexed installer, so downloads still work.
Surfboard, the archived Clash for Windows build, the ARM64 package for Clash Verge Rev, and all Mihomo core files are distributed directly by this site and stay fixed — they aren't part of the dynamic version parsing. Clients marked as no longer maintained are kept only for archival purposes; new users should pick an active project near the top of each platform's list. If you're not sure which one to choose, check the setup guide for the basic workflow first, then come back and download what you need.
Only entries directly related to downloading and installing are listed here. For configuration and usage questions, see the FAQ page and YAML handbook.
On page load, the version number for each client is read from a version API, and the download button points to the currently distributed release — the version shown on the card matches what you actually get. If the API is temporarily unavailable, the button falls back to the most recently indexed installer, so downloads still work. Archived clients and the Mihomo core are fixed files and are not part of the dynamic update process.
Some open-source clients haven't purchased a code-signing certificate, so the installer triggers a SmartScreen block on first run. Click "More info," then "Run anyway" to continue installing. You can also right-click the installer file, open Properties, and check "Unblock" before running it.
This is Gatekeeper's default block on unsigned apps — it doesn't mean the file is actually damaged. Option one: open System Settings → Privacy & Security, and choose "Open Anyway" in the blocked-item log. Option two: open Terminal and run the command below to remove the quarantine attribute, then relaunch the app.
xattr -cr /Applications/AppName.appAny mainstream device released after 2016 should use arm64-v8a — it's smaller and performs better. If you're unsure of your device's architecture, choose the universal build; it's larger but works on every architecture. armeabi-v7a is only for older 32-bit devices — don't pick it on a new phone.
Yes, they can be downloaded — these are archived builds, and existing configs generally still run on them. No longer maintained means bugs won't be fixed and new protocols or config fields won't be supported. They're best used only as a bridge for migrating old configs; for everyday use, pick an active project near the top of each platform's card list.
GUI clients handle the interface, subscription management, and system proxy settings, while actual traffic is processed by a bundled core. Mihomo is the continuation core of the Clash Meta project. Downloading the core on its own makes sense for servers, routers, and other command-line environments, run alongside a config file or a third-party panel; desktop and mobile users can simply install the GUI client without installing the core separately.