Download entry points for Clash clients organized by operating system, covering Windows, macOS, Android, iOS, and Linux, plus the standalone mihomo core. Clients for each platform are ordered by recommendation, with system requirements listed below each card; download buttons automatically point to the current latest release, and the bottom of the page collects common download and installation questions.
Windows has the widest selection of clients in the Clash ecosystem. All of the clients below bundle the mihomo core and support subscription import, rule-based routing, and one-click system proxy toggling; the main differences are in interface layout and release cadence. New users can just start from the first one in order.
A Clash GUI client maintained across every platform, built on the mihomo core. Paste a subscription and it just works, with system proxy and TUN mode toggled from the main window and latency shown right on the node list. If this is your first time using Clash, start here -- the same habits carry over when you move to a phone or a Mac.
One of the most active open-source clients around, built on Tauri, so it's small and light on resources. Supports config overrides, merge scripts, and an external control panel, which suits advanced users managing multiple subscriptions and custom rule sets. Updates ship quickly and stay current with the mihomo core.
A cross-platform client built with Flutter, following Material Design, with consistent interaction between desktop and mobile. Ready to use out of the box with built-in rule templates, and also ships as a portable zip for anyone who'd rather run it straight from a USB drive or a chosen folder without installing.
Another open-source client built on Tauri, with a younger interface style and polished animations. Supports switching between multiple cores and script extensions, with configuration management close to what the Verge family offers. A good fit if you like experimenting with different UI styles and care about how the client looks.
Once the signature Windows client for the ecosystem, this project shipped its final release before development stopped, and it's kept here purely as an archive for long-time users who want the familiar interface back or need to reference it while migrating their config. New protocols and core updates won't arrive, so new users should pick one of the maintained clients above instead.
| Client | Minimum OS | Architecture | Notes |
|---|---|---|---|
| Clash Plus | Windows 10 | x64 | Windows 10 1809 or later recommended |
| Clash Verge Rev | Windows 10 | x64 | Requires the WebView2 runtime, which is usually pre-installed |
| FlClash | Windows 10 | amd64 | Portable build runs straight from the extracted folder, no install needed |
| Clash Nyanpasu | Windows 10 | x64 | Requires the WebView2 runtime |
| Clash for Windows | Windows 7 | x64 | Archived build, not adapted for newer OS features |
TUN mode requires running the client as administrator; when the firewall prompt appears the first time you enable it, choose Allow.
macOS users should first confirm their chip type: Apple menu → About This Mac. If the Chip field shows an Apple M-series chip, pick the Apple Silicon build; if it shows an Intel processor, pick the Intel build. Open the downloaded .dmg and drag the app into the Applications folder to finish installing.
The macOS build shares the same interface and workflow as the Windows version, with a menu bar icon for quickly switching nodes and proxy modes, and native system proxy handling. If you use multiple devices, your configuration habits carry over without friction.
The macOS build matches the Windows version feature for feature, with config overrides and external control, plus a menu bar icon with quick proxy toggles. A solid choice if you need fine-grained rule management on your Mac.
The macOS build ships as a universal image that runs on both Apple Silicon and Intel machines. The interface matches the mobile app, with common actions grouped on the home screen -- a good fit if you want something simple without heavy override features.
The Meta-core fork of the classic macOS menu bar client ClashX, known for being lightweight -- there's no main window, and everything runs through the menu bar. The project is no longer maintained, but the final release still works fine on current systems, and it's kept here as an archive for long-time users.
| Client | Minimum OS | Chip support | Notes |
|---|---|---|---|
| Clash Plus | macOS 11 | Apple Silicon / Intel | Separate images per architecture -- pick by chip |
| Clash Verge Rev | macOS 10.15 | Apple Silicon / Intel | Needs to be allowed in System Settings the first time it's opened |
| FlClash | macOS 10.15 | Universal | Single image compatible with both chips |
| ClashX Meta | macOS 11 | Apple Silicon / Intel | Archived build, menu bar app |
If the first launch warns about an unidentified developer, go to System Settings → Privacy & Security and click Open Anyway.
Android clients all handle traffic through the VPN service framework, so no root is required. APKs are split by CPU architecture: mainstream phones from 2017 onward should pick arm64-v8a, older 32-bit devices should pick armeabi-v7a, and if you're unsure, go with the universal build. You'll need to allow app installs from this source in system settings.
The Android build carries over the same layout as desktop, with subscriptions, nodes, and rules laid out clearly, plus per-app proxy and automatic reconnection. When paired with the desktop client, you can paste the same subscription link on both sides.
The official Android client from the Meta core family, with a plain but solid interface: config file management, override settings, per-app proxy, and log viewing are all covered. It ships in three architecture variants, so owners of older devices can find a build that works.
The mobile interface exactly matches desktop, with a Material Design look, node speed tests, and policy switching grouped on home screen cards. The x86_64 build works on Android emulators and ChromeOS devices.
An Android client compatible with the Surge config format, while also supporting common subscription imports. The interface follows native Android design guidelines, which suits anyone already holding a Surge-format config or needing to switch between the two config ecosystems.
| Client | Minimum OS | Architecture options | Notes |
|---|---|---|---|
| Clash Plus | Android 8.0 | arm64-v8a | Install directly on mainstream 64-bit devices |
| Clash Meta for Android | Android 7.0 | arm64 / armv7 / universal | Older devices should pick armv7 or the universal build |
| FlClash | Android 8.0 | arm64 / armv7 / x86_64 | x86_64 works with emulators |
| Surfboard | Android 7.0 | Universal | Single universal package |
The system will ask for VPN connection authorization the first time you connect -- tap Allow so the client can take over device traffic.
Apps on iOS and iPadOS are distributed through the App Store -- tap the button below to jump to the store listing and install. After installing, paste your subscription link inside the app, and when you turn on the proxy for the first time, follow the prompt to allow the VPN configuration.
The iOS build is implemented with the Network Extension framework, offering the same core capabilities as desktop: subscription management, policy switching, rule-based routing, and node latency testing all happen inside the app, on both iPhone and iPad. Feature notes and release history are available on the official site at clashplus.io.
| Client | Minimum OS | Device | How to get it |
|---|---|---|---|
| Clash Plus | iOS 15 / iPadOS 15 | iPhone, iPad | App Store listing |
The first time you turn on the proxy, the system shows a confirmation dialog to add a VPN configuration -- allow it once, and you won't be asked again for later toggles.
Linux desktop users can run the GUI clients below directly; deb packages target Debian, Ubuntu, and their derivatives, while rpm packages target Fedora, openSUSE, and similar distros. For servers and routers, switch to the "Core: mihomo" tab and download the standalone binary instead.
The most feature-complete Clash GUI client on Linux desktops, supporting both system proxy and TUN mode, and shipping in both deb and rpm formats. Install the deb package with sudo apt install ./filename.deb, or the rpm package with sudo dnf install ./filename.rpm -- dependencies are resolved automatically.
This Flutter-based cross-platform client is also available on Linux, with an interface matching the other platforms, and basic subscription management and rule-based routing that work out of the box. A good fit for desktop users who just need a GUI for everyday proxy switching without deep customization.
| Client | Package format | Architecture | Notes |
|---|---|---|---|
| Clash Verge Rev | deb / rpm | x86_64 | Requires WebKitGTK, handled automatically by the package manager |
| FlClash | deb | x86_64 | Runs on both GNOME and KDE desktop environments |
Enabling TUN mode requires granting the program the relevant network permissions or running it with elevated privileges; ARM devices and headless servers should use the mihomo core instead.
mihomo is the actively maintained core of the Clash ecosystem, handling protocol connections, rule matching, and traffic forwarding. This section offers standalone binaries for various architectures, aimed at servers, routers, NAS devices, and Docker setups without a graphical interface, where you write your own config file and run it via command line or a system service. Regular desktop and mobile users don't need to download the core separately -- the GUI clients above already include it.
| OS | Architecture | Format | Download |
|---|---|---|---|
| Windows | amd64 | .zip | Download |
| Windows | arm64 | .zip | Download |
| macOS | Intel (amd64) | .gz | Download |
| macOS | Apple Silicon (arm64) | .gz | Download |
| Linux | amd64 | .deb | Download |
| Linux | amd64 | .gz | Download |
| Linux | arm64 | .gz | Download |
| Linux | armv7 | .gz | Download |
| Linux | mips-softfloat | .gz | Download |
Typical usage: extract the archive, make the binary executable, then start it with ./mihomo -d config-dir; for long-running setups, register it as a systemd service. Router devices should pick arm64, armv7, or mips-softfloat depending on CPU architecture. See this site's advanced handbook for configuration examples.
Picking a build, installing on your OS, migrating an old config -- here are answers to the questions that come up most during download. For more usage and troubleshooting questions, see the FAQ page.
For everyday use, Clash Plus is the simplest pick: it bundles the mihomo core, has a clean interface, and gets you from subscription import to a working system proxy in the fewest steps. If you prefer the pace of open-source community development, Clash Verge Rev or FlClash offer equally complete feature sets. The original Clash for Windows is no longer maintained and is kept only as an archived build, so new users should avoid it.
These clients change system proxy settings and may create a virtual network adapter, which is behavior that commonly triggers generic warnings from Windows SmartScreen or third-party security tools. Once you've confirmed the installer came from this site's download page, click "More info" in the SmartScreen prompt and choose "Run anyway"; if security software quarantines it, add the install folder to your trusted list. This is a routine false positive for proxy-type software.
Click the Apple menu at the top left and choose "About This Mac": if the Chip field shows an Apple M-series chip, download the Apple Silicon build; if it shows an Intel processor, download the Intel build. If you pick the wrong architecture, the system will either run it through Rosetta translation or simply refuse to open it -- just download the matching build and reinstall. Your configuration won't be lost.
Most mainstream phones released after 2017 run 64-bit processors, so arm64-v8a is the first choice; older 32-bit devices should use armeabi-v7a. If you're unsure of your architecture, the universal package is slightly larger but works on all of them. The x86_64 build targets emulators and ChromeOS devices.
mihomo is the core engine that handles proxy forwarding and rule matching. Every GUI client listed on this page already bundles it, so regular users can just install the client without downloading the core separately. The standalone binaries in the core section target servers, routers, and Docker setups, where you write your own config file and run it via command line or as a system service.
The final release still installs and runs normally, and existing configurations from long-time users continue to work. However, the project no longer receives updates, so new protocol support and bug fixes won't arrive, which means it will fall further behind over time. We recommend migrating to Clash Plus or Clash Verge Rev -- just re-import your subscription link, since the migration cost is minimal.
Once installation is done, the first step is importing a subscription and finishing basic setup -- the setup guide walks through import, node selection, and connectivity checks step by step; for advanced topics like policy groups, rule sets, and DNS tuning, see the advanced handbook.