A desktop client refined for everyday use: the mihomo core is built in, and subscription import, system proxy toggling, and rule-based routing all happen on one screen. Most new installs go from download to a working connection in under five minutes - a solid pick for first-time Clash users and anyone who'd rather not fuss over configuration details.
PLATFORMS
Choose a Client by Platform
Each platform lists a curated set of clients, with the top recommendation shown first; projects that are no longer maintained keep an archive link and are clearly labeled. Click a tab to switch platforms - the URL updates too, so you can share a direct link.
Windows has the largest lineup of Clash-ecosystem clients. The five options below are ranked by recommendation: the first four are actively maintained and all run on the mihomo core, so config files and subscription formats are interchangeable between them. The last one, Clash for Windows, stopped receiving updates in 2023 and is kept only as an archive - useful for exporting configs before migrating.
A Tauri-based client maintained by the open-source community, continuing the project after Clash Verge itself stopped receiving updates. It offers service mode (no more admin prompts), a TUN virtual adapter, config overrides, and merge scripts - a good fit for advanced users who want fine-grained control over routing rules. Our blog has a full Windows setup walkthrough you can follow along with.
A Flutter-based client available across all five platforms with a consistent interface, so there's almost no learning curve when you switch devices. Features are kept deliberately lean - subscription management, proxy group switching, and log viewing are all there, with less common options tucked away - a good fit if you want a clean, uncluttered interface.
Another open-source client from the Clash Verge lineage, notable for supporting multiple cores side by side with on-the-fly switching, plus JavaScript/Lua script overrides that work well for experimental setups. The interface leans toward personalization, so it's worth a look if you like custom themes.
Once the de facto standard on Windows, this client stopped receiving updates in November 2023 and is still running on an old Premium core, with no support for newer protocols or rule formats. It's kept here as an archive so existing users can open it briefly to export their configs; for new installs, pick any of the actively maintained clients above instead.
Windows System Requirements
| Client | Minimum OS | Architecture | Package Format |
|---|---|---|---|
| Clash Plus | Windows 10 1809 | x64 | setup.exe installer |
| Clash Verge Rev | Windows 10 (requires WebView2 Runtime) | x64 | setup.exe installer |
| FlClash | Windows 10 | amd64 | Installer / Portable ZIP |
| Clash Nyanpasu | Windows 10 (requires WebView2 Runtime) | x64 | setup.exe installer |
| Clash for Windows (archived) | Windows 7 SP1 | x64 | setup.exe installer |
macOS clients come in two chip variants - Apple Silicon (M-series) and Intel - so check your chip type under "About This Mac" before downloading. The first three clients below are actively maintained; ClashX Meta, a well-known lightweight menu bar client, has stopped receiving updates but keeps an archive link for existing users.
Shares the same interface logic as the Windows version, with a menu bar icon for quickly switching proxy groups and modes. Separate dmg images are provided for Apple Silicon and Intel - download the one matching your chip.
Matches the Windows version feature for feature: service mode, TUN adapter, and override scripts are all here, and taking over the system proxy and network interface is just as stable on macOS - a solid fit for advanced configuration needs.
The same clean interface as the mobile version, with a dmg image that's ready to use right out of the box. If all you need is to import a subscription and flip the proxy on, this is one of the most hassle-free open-source options on macOS.
A classic macOS menu bar client known for its minimal resource footprint and no-frills interface, running on a Clash.Meta-branch core. The project has stopped receiving updates - existing versions still run fine, but compatibility with newer config formats isn't guaranteed. Existing users can still grab the archived image here.
macOS System Requirements
| Client | Minimum OS | Chip Support | Package Format |
|---|---|---|---|
| Clash Plus | macOS 11 Big Sur | Apple Silicon / Intel | dmg image |
| Clash Verge Rev | macOS 10.15 Catalina | Apple Silicon / Intel | dmg image |
| FlClash | macOS 10.15 Catalina | Apple Silicon / Intel | dmg image |
| ClashX Meta (archived) | macOS 10.15 Catalina | Apple Silicon / Intel | dmg image |
Android clients all use VpnService to set up a virtual adapter for system-wide routing, and will ask for VPN permission on first launch. Check your device architecture before downloading: most recent phones use arm64-v8a, older 32-bit devices need armeabi-v7a, and if you're unsure, go with the universal package. To keep the app from being killed in the background, disable battery optimization for it after installing - see our Android stability guide for details.
The mobile client keeps the same workflow as the desktop version: import subscriptions, switch proxy groups, and check connections all from the home screen, with a persistent notification card for quickly pausing and resuming the proxy. An arm64-v8a package is currently provided, covering the vast majority of devices in use.
A native Android client maintained by the open-source community, built on the mihomo core, with support for config overrides, per-app routing (Access Control), and switching between multiple config profiles - one of the most fully featured options on Android.
A Flutter client with the same interface as the desktop version, laid out in cards for one-handed use; it supports per-app proxying and automatic subscription updates - a good fit if interface polish matters to you.
An Android client compatible with the Surge config format that also supports importing common subscriptions. If your subscription pushes both Surge and Clash formats, or you need to cross-check between the two rule syntaxes, this is a solid backup option to install.
Android System Requirements
| Client | Minimum OS | Architecture Choice | Permissions Needed |
|---|---|---|---|
| Clash Plus | Android 8.0 | arm64-v8a | VPN permission, notifications |
| Clash Meta for Android | Android 7.0 | arm64-v8a / armeabi-v7a / universal | VPN permission, notifications |
| FlClash | Android 8.0 | arm64-v8a / armeabi-v7a | VPN permission, notifications |
| Surfboard | Android 7.0 | universal | VPN permission, notifications |
iOS and iPadOS network extension apps are distributed exclusively through the App Store. Clash Plus is already live on the App Store - search for it or tap the button below to go straight to its listing. Once installed, it shares the same subscription with the desktop version, keeping proxy group and rule-routing behavior consistent.
Works on both iPhone and iPad, using the Network Extension framework for rule-based routing - once you import a subscription, you can toggle it right from Control Center. Product details and release notes are on the official site at clashplus.io; updates are pushed automatically through the App Store, so there's no installer to maintain manually.
iOS System Requirements
| Item | Requirement |
|---|---|
| OS Version | iOS 15 / iPadOS 15 or later |
| Device | iPhone and iPad |
| Distribution Channel | App Store |
| Update Method | Automatic via App Store |
Two GUI clients are available on Linux desktops: Clash Verge Rev covers both deb and rpm packages and is the current mainstream choice on Linux desktops; FlClash provides a deb package with an interface consistent with other platforms. For servers or headless environments, switch to the "mihomo Core" tab and deploy the core binary directly.
Pick the deb package for Debian/Ubuntu-based distros, or the rpm package for Fedora/openSUSE-based ones. System proxy and TUN mode are both supported, and the tray icon works fine whether you're on GNOME or KDE; TUN mode requires granting the app the appropriate network capabilities or running the service component with elevated privileges.
Shares the same interface as the Windows, macOS, and Android versions, making it easy to keep a consistent workflow across multiple devices. An amd64 deb package is currently available - install it and launch from your app menu.
Linux System Requirements
| Client | Distro Reference | Architecture | Package Format |
|---|---|---|---|
| Clash Verge Rev | Ubuntu 20.04+ / Debian 11+ / Fedora 38+ | amd64 / x86_64 | deb / rpm |
| FlClash | Ubuntu 20.04+ / Debian 11+ | amd64 | deb |
sudo apt install ./package-name.deb to install and resolve dependencies automatically; for rpm packages, use sudo dnf install ./package-name.rpm. Quote the filename if it contains spaces.mihomo is the main core behind the current Clash ecosystem (a continuation of the Clash Meta project), and it's what handles rule matching and traffic forwarding for every GUI client listed above. Here you'll find standalone binaries for each architecture, meant for servers, NAS devices, and router firmware with no GUI: download it, extract it, and run it alongside a config.yaml and a systemd service. Regular desktop and mobile users don't need to download the core separately - just use one of the GUI clients above.
mihomo · MIT License
| Platform | Architecture | Format | Download |
|---|---|---|---|
| Windows | AMD64 | zip | mihomo-windows-amd64.zip |
| Windows | ARM64 | zip | mihomo-windows-arm64.zip |
| macOS | Intel | gz | mihomo-darwin-amd64.gz |
| macOS | Apple Silicon | 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 |
Deployment Notes
After extracting, make it executable with chmod +x mihomo, then start it with ./mihomo -d /etc/mihomo to point it at your config directory. For long-running setups, write a systemd unit with Restart=always so it restarts automatically if it crashes. On routers and MIPS devices, double-check the CPU's floating-point type before picking a build - config fields are identical to the GUI clients, so you can test everything on desktop first and then deploy it to a server. Rule syntax and field details are in our configuration reference.
DOWNLOAD FAQ
Download FAQs
The most common questions about picking an installer, updating versions, and first launch are collected here. For subscription import and routing setup after installation, head over to the getting started guide.
With so many clients available on Windows, which one should I install first?
Do the download buttons on this page always point to the latest version?
macOS says the developer can't be verified when I first open the app - what do I do?
What's the difference between the arm64-v8a and armeabi-v7a Android packages?
When do I need to download the mihomo core on its own?
More on installation and usage: See the getting started guide →