Clash Download for Every Platform
Clients for all five platforms are listed top to bottom in recommended order, each with its system requirements; version numbers auto-update with official releases once the page loads, so you don't have to track them yourself. Once installed, head to the tutorial page to import your subscription — we've already flagged the key steps for you.
Pick your OS, then choose a client in order
Click the platform tab below that matches your system. If you're not sure which client to pick, go with the first card on each platform's list; server and router users can jump straight to the Mihomo core section further down.
Windows has five clients on offer. For a fresh install, just grab the first card. If you want finer rule control and script extensions, check out Clash Verge Rev and FlClash below. Clash for Windows is archived and kept only for users who haven't migrated yet.
Clash Plus
Top Pick
One consistent workflow across every platform: subscription import, node switching, and rule-based routing all live on a single home screen, so new users barely need to check the docs. It ships with a Meta-family core, works out of the box with all common protocol types, and updates on a steady schedule. We recommend starting with this card on every platform, and it's also the main client used throughout our tutorials.
Windows 10 or later, 64-bit. First launch takes you straight into the subscription import screen.
Clash Verge Rev
Recommended
The go-to pick for power users on desktop: a config editor, Merge and script extensions, a TUN mode toggle, and service mode are all built in, with the most thorough visual editor for policy groups and rules. First launch requires the WebView2 runtime — it's already built into Windows 11, and the installer will guide you through installing it on Windows 10 if it's missing. For the full setup walkthrough, see our blog post on the complete Windows install process.
Windows 10 or later, 64-bit; requires the WebView2 runtime (already present on most systems).
FlClash
A cross-platform client built with Flutter — light on resources with a clean interface, clear policy-group and latency-test displays, and the same interaction patterns on both mobile and desktop. Available as a full installer or a portable ZIP: the portable build runs straight from the archive with no registry writes, handy if you don't want to touch your system or need something you can carry on a USB drive.
Windows 10 or later, 64-bit; the portable build runs straight from the extracted folder — just replace the whole folder to update.
Clash Nyanpasu
Another desktop client built on the Meta-family core, with support for config merging and script chains, a snappy interface, and a core version you can switch in the settings. It's positioned similarly to Clash Verge Rev — which one you pick mostly comes down to interface preference, since config files are interchangeable between the two.
Windows 10 or later, 64-bit; requires the WebView2 runtime.
Once the de facto standard on Windows, development stopped in late 2023, and this is the final archived build — kept only as a bridge for legacy configs that haven't been migrated yet. Don't start here if you're installing fresh: it no longer gets bug fixes and won't support new protocol types, so pick any of the actively maintained clients above instead.
Runs on Windows 7 or later; frozen at the final archived version, no further updates.
WINDOWS · System Requirements at a Glance
| Client | Minimum OS | Architecture | Extra Dependencies |
|---|---|---|---|
| Clash Plus | Windows 10 | x64 | — |
| Clash Verge Rev | Windows 10 | x64 | WebView2 runtime |
| FlClash | Windows 10 | x64 | — (portable, no install) |
| Clash Nyanpasu | Windows 10 | x64 | WebView2 runtime |
| Clash for Windows | Windows 7 | x64 | No longer maintained |
For macOS, check your chip first: machines from 2020 onward are mostly Apple silicon, while older ones run Intel chips. The buttons on each card are split by chip — click "About This Mac" to confirm which one you have. ClashX Meta is no longer maintained and should only be used as a stopgap.
Clash Plus
Top Pick
The macOS client mirrors the Windows version's interface, with a persistent menu bar item and a two-step flow for importing a subscription and switching nodes. Apple silicon and Intel each get their own installer — grab the one matching your chip below, and authorize once when the system proxy first turns on.
macOS 11 or later; download the matching DMG for Apple silicon or Intel.
Clash Verge Rev
Recommended
The macOS build matches the Windows version feature for feature: config editing, script extensions, and TUN mode are all here, making it a solid pick if you need fine control over rules and policy groups. Enabling TUN mode requires authorizing a system extension when prompted; if Gatekeeper blocks the unsigned app on first launch, see question 3 in the FAQ at the bottom of this page.
macOS 10.15 or later; TUN mode requires authorizing a system extension.
FlClash
A lightweight, cross-platform client that's easy on resources on macOS, with fast startup and clear latency-test and policy-group switching. If you're already used to FlClash on mobile, picking it on desktop too keeps the same interaction patterns, with configs and subscriptions carrying over seamlessly.
macOS 10.15 or later.
ClashX Meta
No Longer Maintained
A lightweight menu-bar client that longtime macOS users will recognize, now no longer maintained. The archived build still runs fine, but compatibility with newer macOS releases isn't being tracked and it won't gain support for new protocols — treat it as a stopgap only, and migrate to one of the actively maintained clients above as soon as you can.
macOS 11 or later; no longer maintained, compatibility with newer macOS releases isn't guaranteed.
MACOS · System Requirements at a Glance
| Client | Minimum OS | Chip Support | Notes |
|---|---|---|---|
| Clash Plus | macOS 11 | Apple Silicon & Intel builds | — |
| Clash Verge Rev | macOS 10.15 | Apple / Intel | TUN needs system extension authorization |
| FlClash | macOS 10.15 | Apple / Intel | — |
| ClashX Meta | macOS 11 | Apple / Intel | No longer maintained |
For Android, check your chip architecture first: mainstream devices from 2016 onward are almost all arm64, so grab the arm64-v8a build. If you have an older device or aren't sure, choose the universal build. Picking the wrong architecture typically shows up as an install failure or a crash on launch — just reinstall with the matching build.
Clash Plus
Top Pick
Android follows the same interface logic as desktop, with subscription import, node switching, and traffic-routing rules all handled on a single home screen. It takes over traffic through the system's VPN interface, needing authorization just once on the first connection; it stays stable in the background, and a sensible health-check interval keeps battery drain reasonable. New mobile users should start with this card.
Android 8.0 or later, arm64 architecture; allow installing apps from unknown sources during setup.
The official Android client for the Meta-family core, with configuration options closest to the core itself: overrides, per-app proxying, and multi-config switching are all supported — a good fit if you're already comfortable with Clash config structure and want full control on mobile. The interface is plain but the settings are thorough; pick the build matching your architecture, or go with universal if you're not sure.
Android 7.0 or later; pick one of three architecture builds based on your device, or use universal for any device.
FlClash
One of the cleanest interfaces among Android clients: latency tests are easy to read, policy-group switching takes one tap, and resource usage stays low. It behaves identically to the desktop FlClash build, so users with multiple devices can skip re-learning a new interface. Pick the build matching your architecture; the x86_64 build is for emulators and tablets and similar edge cases.
Android 8.0 or later; use the x86_64 build for emulators.
Surfboard
An Android client compatible with the Surge config format, with support for common subscriptions too, built on Material Design. It's mainly aimed at users who already have Surge-format configs on hand, or who want to cross-test between multiple clients; if you're only working with standard Clash subscriptions, pick one of the three clients above instead.
Android 7.0 or later, universal build.
ANDROID · System Requirements at a Glance
| Client | Minimum OS | Architecture Build | Notes |
|---|---|---|---|
| Clash Plus | Android 8.0 | arm64-v8a | — |
| Clash Meta for Android | Android 7.0 | arm64 / armv7 / universal | Most complete config options |
| FlClash | Android 8.0 | arm64 / armv7 / x86_64 | x86_64 for emulators |
| Surfboard | Android 7.0 | universal | Compatible with Surge config format |
On iOS, everything goes through the official App Store — one card covers it: Clash Plus is already listed there, so search for it or click the button below to jump straight to its store page. Installation and updates are handled entirely by the App Store, no extra setup needed.
Clash Plus
App Store · Top Pick
Works on both iPhone and iPad, taking over traffic through the system's network extension — just add the VPN configuration when prompted on first connection. Subscription import, node switching, and rule-based routing all match the desktop version exactly, and it shares the same subscription with Clash Plus on Mac and Windows, so switching between devices takes zero relearning. Updates are pushed automatically through the App Store. For more platform details, see the official site at clashplus.io.
iOS 15 or later, works on both iPhone and iPad; installation and updates are managed by the App Store.
IOS · System Requirements at a Glance
| Client | Minimum OS | Device | How to Get It |
|---|---|---|---|
| Clash Plus | iOS 15 | iPhone / iPad | Officially listed on the App Store |
Two desktop options for Linux: grab the .deb for Debian-based distros (Ubuntu/Debian/Mint), the .rpm for Red Hat-based ones (Fedora/openSUSE), or the AppImage if you'd rather skip the package manager entirely. For command-line environments and servers, jump straight to the Mihomo bare-core section below.
Clash Verge Rev
Recommended
The most feature-complete option for Linux desktops, with config editing, TUN mode, and system proxy management all included. Both deb and rpm packages cover mainstream distros; TUN mode requires installing the core component as a service, which the app handles with one-click authorization. Works under both Wayland and X11 sessions.
Ubuntu 20.04 / Debian 11 / Fedora 38 or later, x86_64; TUN mode requires installing the service component.
FlClash
Stays true to the lightweight philosophy on Linux too, with deb, rpm, and AppImage builds all available. Give the AppImage executable permissions and double-click to run — no package manager needed, which suits rolling-release distros or anyone who'd rather not touch their system setup. The deb / rpm builds plug into your system's normal update flow instead.
Mainstream distros, x86_64; the AppImage needs chmod +x before it will run.
LINUX · System Requirements at a Glance
| Client | Package Format | Architecture | Notes |
|---|---|---|---|
| Clash Verge Rev | .deb / .rpm | amd64 / x86_64 | TUN needs service component |
| FlClash | .deb / .rpm / AppImage | amd64 | AppImage needs no install |
Mihomo Bare Core: For Servers & Routers
This section is for command-line environments: running the headless core on a VPS, router, or NAS, where you write your own config.yaml and manage the process yourself. Regular desktop and mobile users don't need to download the core directly — the GUI clients above already include it.
| Platform | Architecture | File Format | Download |
|---|---|---|---|
| Windows | AMD64 | .zip | mihomo-windows-amd64.zip |
| ARM64 | .zip | mihomo-windows-arm64.zip | |
| macOS | Intel | .gz | mihomo-darwin-amd64.gz |
| Apple Silicon | .gz | mihomo-darwin-arm64.gz | |
| Linux | AMD64 | .deb / .gz | mihomo-linux-amd64.deb mihomo-linux-amd64.gz |
| ARM64 | .gz | mihomo-linux-arm64.gz | |
| ARMv7 | .gz | mihomo-linux-armv7.gz | |
| MIPS softfloat | .gz | mihomo-linux-mips-softfloat.gz |
Quick rule of thumb for core builds: amd64 for x86 servers, arm64 for Raspberry Pi 4 and later, armv7 for older ARM boxes, and mips-softfloat for legacy MIPS routers. After extracting, grant execute permission and configure config.yaml, then manage the process with systemd or an init script. For how the core and client families relate, and their protocol support differences, see our protocol reference.
Six Common Download & Install Snags
Check here first — most issues get sorted out in under a minute. The full, categorized question set lives on our Troubleshooting page.
The download button isn't responding, or downloads are very slow — what should I do?
Download links resolve automatically to the current latest version when the page loads; if that resolution request gets blocked by your network, the button falls back to the page's built-in direct link, which still works. If it's slow, try switching networks first — and if that doesn't help, grab another client from the same platform's list. Core features are the same, so install whichever one works.
Windows install is blocked by SmartScreen or flagged by security software — what should I do?
Open-source clients rarely purchase a commercial code-signing certificate, so SmartScreen flags unsigned installers by default — this is expected. Once you've confirmed the installer came from this page, click "More info" then "Run anyway" to continue. Some security tools misidentify proxy apps as threats, so you may need to temporarily allow the installer before running it.
macOS says the file is damaged or the developer can't be verified — what should I do?
This is Gatekeeper's quarantine flag for unsigned apps. Go to System Settings → Privacy & Security, find the blocked app under the Security section, and click "Open Anyway"; or run sudo xattr -rd com.apple.quarantine /Applications/YourApp.app in Terminal to clear the quarantine attribute before launching it.
Should I pick arm64-v8a or armeabi-v7a for the Android APK?
Mainstream devices released after 2016 are almost all arm64, so choose arm64-v8a. If you have an older device or aren't sure, pick the universal build — it's slightly larger but installs on any architecture. Picking the wrong architecture typically causes install failures or crashes on launch; just reinstall with the matching build.
Clash for Windows is no longer maintained — can I still download and use it?
The archived build is still available for download, and existing configs will keep working, but there won't be any more feature updates, bug fixes, or support for new protocol types. We recommend migrating to Clash Verge Rev or Clash Plus — config file formats are compatible, and re-importing your subscription link completes the switch.
What should I do right after installing?
Open the client, import the subscription link from your provider, pick a node, and confirm traffic is routing correctly. The full walkthrough is laid out step by step on the tutorial page, with an anchor for each stage from importing your subscription to verifying the connection — just follow along. If you're not sure which protocol type to pick, check out the protocol reference alongside it.