Windows has the widest range of clients to choose from. For everyday use, follow this order: the first card is the most actively maintained option with the widest protocol coverage; the last one, Clash for Windows, is no longer maintained and is kept only as an archive for users still relying on the old interface. All installers are x64, and Windows 10 or later can install by double-clicking directly.
Clash Plus
Top pick v--A desktop client built on the mihomo core with built-in TUN mode and subscription management, supporting SS, VMess, Trojan, VLESS, Hysteria2 and other mainstream protocols. The interface is available in Chinese, and once you import a subscription link, rule-based routing works right away — a good fit for anyone migrating from an older client.
Clash Verge Rev
Recommended v--An actively maintained open-source client built on Tauri, small in size and light on memory. It offers rule editing, Merge/Script configuration enhancements and a system proxy guard, suited to advanced users who want fine-grained control over their config files.
FlClash
Recommended v--A cross-platform client written in Flutter, with a consistent interface across desktop and mobile, so multi-device users face a low learning curve. Sensible defaults work out of the box, and it includes a dashboard-style traffic view. The installer suits everyday use; the portable build runs straight from an extracted folder with no registry writes.
Clash Nyanpasu
v--An open-source client with a light, snappy interface, supporting multi-core switching and chained config processing, plus a node latency testing panel. Its feature set is close to the Verge family, so it suits users who like its particular interface design.
Clash for Windows
No longer maintained Archived v--Once the most widely used Windows client, this project stopped receiving updates in 2023. The archived build still runs existing configurations, but it doesn't support newer protocols like VLESS or Hysteria2, and issues no longer get fixed. Only recommended for users still tied to an old workflow — see the comparison for alternatives.
Windows system requirements
| Operating system | Windows 10 / 11 (64-bit); the Clash for Windows archive is compatible with Windows 7 SP1 and later |
|---|---|
| Processor architecture | x64; ARM devices can run through the built-in emulation layer, with some performance loss |
| Memory | 4 GB or more recommended; the client uses roughly 100-300 MB while running |
| Disk space | 200 MB available |
| Other | Enabling TUN mode requires administrator rights to install the virtual network adapter driver — just confirm the prompt the first time you turn it on |
macOS clients are split by chip architecture: download the Apple Silicon (arm64) build for Apple M-series chips, or the x64 build for Intel processors. Check which one you have via the Apple menu → About This Mac → Chip field. If the first launch warns that the app is from an unidentified developer, go to System Settings → Privacy & Security and click "Open Anyway".
Clash Plus
Top pick v--The macOS build matches the Windows build feature for feature: mihomo core, TUN mode, subscription management and rule-based routing are all included, with a menu bar icon for quickly switching proxy modes and node groups. It's natively optimized for Apple Silicon, with good energy efficiency.
Clash Verge Rev
Recommended v--The macOS build keeps the same configuration-enhancement power as the other desktop platforms, supporting both system proxy and TUN modes, with quick tray toggles. A good fit for users who want the same configuration workflow across Windows and macOS.
FlClash
Recommended v--The consistent cross-platform interface holds up on macOS too, with identical configuration logic when paired with the Android build. Defaults are sensible out of the box, so users who don't want to fiddle with settings can just import a subscription and go.
ClashX Meta
No longer maintained v--A classic macOS menu bar client, known for its minimal footprint and low resource use, built on the Meta family core. The project is no longer maintained; existing features still work, but new users should prefer one of the actively updated clients above.
macOS system requirements
| Operating system | macOS 11 Big Sur or later; macOS 12 or later recommended for full TUN support |
|---|---|
| Processor architecture | Apple Silicon (M series) and Intel x64 each have their own installer — check "About This Mac" for your chip |
| Memory | 4 GB or more recommended; menu bar clients use roughly 60-200 MB while running |
| Disk space | 150 MB available |
| Other | TUN mode requires authorizing a system network extension; if the first launch is blocked, allow it under Privacy & Security |
Android clients ship as APKs for direct installation; after downloading, allow installs from unknown sources in system settings. Most phones released in recent years use the arm64-v8a architecture, so download the arm64 package first; older 32-bit devices should use armeabi-v7a; if unsure, choose the universal package. On first connection, the client will request VPN permission — this is a normal part of the authorization flow.
Clash Plus
Top pick v--The Android build shares the same mihomo core and subscription system as the desktop build; import the same subscription link to keep configuration in sync across devices. It supports per-app proxying and a battery-friendly background policy, keeping power drain under control during long idle connections.
Clash Meta for Android
Recommended v--The official Android client from the Meta family, with an interface close to native Material design and every configuration option fully exposed, along with strong rule-set and override capabilities. A good fit for users comfortable editing configs directly and who need fine-grained control.
FlClash
Recommended v--Shares the same interface and configuration logic as the desktop build, so anyone already using FlClash on their computer faces zero learning curve. It includes a node latency test and a traffic statistics panel, keeping the workflow short.
Surfboard
An Android client compatible with the Surge configuration format, suited to users who already have Surge-style configs and want to reuse them on an Android device. Regular Clash subscription users should prefer one of the clients above.
Android system requirements
| Operating system | Android 7.0 or later; Android 9 or later recommended for stable VPN service persistence |
|---|---|
| Processor architecture | arm64-v8a (mainstream 64-bit devices) / armeabi-v7a (older 32-bit devices) / universal (all architectures) |
| Storage | 100 MB available |
| Permissions | VPN permission is required on first connection; adding the client to the battery whitelist in system settings is recommended to prevent the system from killing the connection |
iOS distribution goes through the App Store. Tap the button below on your iPhone or iPad to jump to the store page and install; the system handles subsequent updates automatically. The first time you turn the proxy on, allow the VPN configuration when prompted.
Clash Plus
Top pick v--The iOS build implements system-level proxying via Network Extension, supporting subscription import, rule-based routing and on-demand connections, and shares the same subscription link as the desktop and Android builds. For more product details and release notes, see clashplus.io.
iOS system requirements
| Operating system | iOS 15 or later, on both iPhone and iPad |
|---|---|
| Storage | About 60 MB |
| Permissions | Adding a VPN configuration must be allowed the first time you turn on the proxy; a corresponding VPN entry will appear in system settings, which is expected |
| Updates | Handled automatically by the App Store, no manual installer needed |
Linux desktop users should pick a package format by distribution: Debian / Ubuntu family use .deb, Fedora / openSUSE family use .rpm. If TUN mode is needed after installation, the client will request elevated permissions to configure the virtual network adapter. For servers and headless environments, switch to the "Core (mihomo)" tab to download the command-line core.
Clash Verge Rev
Recommended v--The most complete option on Linux desktop: both system proxy and TUN mode are available, with autostart and a tray icon supported, and deb / rpm packages cover the mainstream distributions. Configuration enhancement is on par with the Windows / macOS builds.
FlClash
v--The same cross-platform interface is also available on Linux, suited to users who want a consistent FlClash experience across devices. A .deb package is provided for Debian-family distributions; launch it from the application menu after installing.
Linux system requirements
| Distribution | Debian 11+ / Ubuntu 20.04+ (.deb); Fedora 38+ / openSUSE Leap 15.4+ (.rpm) |
|---|---|
| Processor architecture | amd64 / x86_64; ARM devices should use the matching architecture archive from the "Core (mihomo)" tab |
| Desktop environment | Mainstream desktops such as GNOME / KDE; the tray icon depends on system tray extension support |
| Permissions | TUN mode requires root or the corresponding capability; the client will guide you through authorization the first time it's enabled |
mihomo is the command-line core of the Clash Meta family, aimed at servers, home routers and Docker setups with no graphical interface: you write a YAML configuration by hand and start it via a command or systemd service. Regular desktop and mobile users don't need to download the core separately — just use the GUI client for your platform above, since the core is already bundled inside it. The archive extracts to a single executable; use gzip -d for .gz files, or extract .zip files directly.
mihomo core downloads by architecture
| Platform / Architecture | Format | Use case | Download |
|---|---|---|---|
| Windows AMD64 | .zip | Windows servers, command-line use | mihomo-windows-amd64.zip |
| Windows ARM64 | .zip | Windows on ARM devices | mihomo-windows-arm64.zip |
| macOS Intel | .gz | Command-line use on Intel Macs | mihomo-darwin-amd64.gz |
| macOS Apple Silicon | .gz | Command-line use on M-series Macs | mihomo-darwin-arm64.gz |
| Linux AMD64 | .deb | Debian / Ubuntu servers, includes a systemd unit | mihomo-linux-amd64.deb |
| Linux AMD64 | .gz | Other x86_64 distributions, Docker image builds | mihomo-linux-amd64.gz |
| Linux ARM64 | .gz | ARM64 servers, Raspberry Pi 4 and up, most ARM home routers | mihomo-linux-arm64.gz |
| Linux ARMv7 | .gz | 32-bit ARM devices, older Raspberry Pi models | mihomo-linux-armv7.gz |
| Linux MIPS-softfloat | .gz | MIPS-based routers (soft float) | mihomo-linux-mips-softfloat.gz |
On router firmware, run uname -m to confirm the architecture before downloading: aarch64 maps to ARM64, armv7l maps to ARMv7, and mips maps to MIPS-softfloat. For how the core relates to each client family and their protocol support differences, see the technical reference.