SHELF DL-2026 / PLATFORMS 5 / KERNEL mihomo
This is the unified download hub for the Clash family of clients, organized into five platform tabs: Windows, macOS, Android, iOS, and Linux. Within each platform, entries are listed in recommended order — Clash Plus first as the overall top pick, followed by actively maintained open-source clients, with discontinued clients placed last and clearly labeled as archive-only. Below the platform tabs you'll find the Mihomo core binaries section and a download FAQ. All download buttons automatically resolve to the current latest release once the page loads.
Click a platform tab to switch shelves; shared links jump straight to the matching platform.
Five clients are listed for Windows. The first four are actively maintained and built on the mihomo core, supporting rule-based routing, subscription management, and system proxy settings. The last entry, Clash for Windows, is no longer maintained and is listed only to support legacy config migration and archival purposes.
A unified Clash client maintained across all platforms, built on the mihomo core. Subscription import, rule-based routing, system proxy, and TUN mode are all configured from the same interface. The UI is natively designed and updates ship on a steady cadence, making it our top recommendation for Windows users.
One of the most actively developed open-source desktop clients, built with Tauri for a small footprint and low resource usage. It supports multiple config profiles, Merge and Script enhancements, and a visual rule editor — a good fit for advanced users who want fine-grained control, and a common destination for people migrating away from Clash for Windows.
A Flutter-based cross-platform open-source client sharing the same interaction model across desktop and mobile. The interface is clean with a low learning curve, and it supports automatic subscription updates and a proxy group view. Alongside the standard installer, a portable zip build is available for restricted environments where writing to system directories isn't an option.
Another Tauri-based open-source client with a lighter, snappier interface, letting you switch between multiple core versions and offering chained proxy configs plus script-based extensions. Its feature set is close to Clash Verge Rev, so pick whichever interface you prefer.
Once the most widely used Clash desktop client, its developer stopped updates in 2023 — it no longer receives core updates or security patches. The last publicly released build is kept here strictly for legacy environments and config-export migration; for regular use, choose one of the actively maintained clients above instead.
| Item | Minimum | Recommended |
|---|---|---|
| Operating System | Windows 10 64-bit (CFW archived build supports Windows 7) | Windows 11 64-bit |
| Processor Architecture | x64 (Intel / AMD 64-bit) | x64 |
| Memory | 2 GB | 4 GB or more |
| Disk Space | About 300 MB | 500 MB (including configs and logs) |
| Other | Enabling TUN mode requires running as administrator | — |
macOS installers are split by chip architecture: choose the arm64 build for Apple Silicon (M-series chips), or the x64 build for Intel chips. Check your chip type under Apple menu → About This Mac before downloading.
The same unified client shared with Windows and mobile, combining a persistent menu-bar icon with a full main window. Subscription, proxy group, and rule-routing settings match every other platform, so users on multiple devices don't have to relearn a new interface.
Feature set matches the Windows build, with multi-profile management and enhancement scripts. Both system proxy configuration and TUN mode are fully supported on macOS; the first time you enable TUN, follow the prompt to install and authorize the system extension.
A clean, consistent interface across platforms, ideal for users who just need to import a subscription, pick a node, and turn on the proxy. It has a lighter settings footprint than the Verge-family clients, making it a good starting point for macOS users new to Clash.
A Meta-core fork of the classic menu-bar client ClashX, known for its lightweight footprint and native feel. The repository is no longer updated. The last published build is kept here to help existing users transition; for new installs, choose one of the actively maintained clients above.
| Item | Minimum | Recommended |
|---|---|---|
| Operating System | macOS 10.15 Catalina (Clash Plus / ClashX Meta require macOS 11) | macOS 13 Ventura or later |
| Chip | Intel or Apple Silicon (download the matching build) | Apple M-series |
| Memory | 4 GB | 8 GB or more |
| Other | First-time system proxy / TUN setup requires authorization in System Settings | — |
On Android, apps use VpnService to set up a local virtual network interface and take over traffic — you'll need to grant VPN permission on first launch. Nearly all phones from the past five years use the arm64-v8a architecture. After installing, add the client to your battery-optimization whitelist to avoid background disconnects.
A mobile client sharing the same codebase as the desktop version — subscription management, proxy group switching, and rule-based routing are all handled in-app, with scheduled subscription auto-updates and a quick toggle in the notification bar. The interface matches the desktop build exactly, so there's no learning curve switching devices.
The official Android client maintained by the Meta community, exposing the full configuration power of the mihomo core with support for fine-grained config editing and overrides. Its feature density is higher than graphical clients, making it a good fit for users already comfortable with Clash config structure. If you're unsure of your device's architecture, pick the universal build.
Shares the same interface logic across mobile and desktop, with a short setup path — import a subscription and you're one tap from connected. It's friendly to users who don't want to deal with config details, using the default rules and proxy groups defined in the subscription itself.
An Android client compatible with Surge config syntax that also supports importing standard Clash subscriptions. A good fit if you maintain both Surge and Clash configs and want to manage them from a single app; if you only use Clash subscriptions, choose one of the clients above instead.
| Item | Minimum | Recommended |
|---|---|---|
| Operating System | Android 7.0 (Clash Plus / FlClash require 8.0) | Android 12 or later |
| Processor Architecture | armeabi-v7a | arm64-v8a |
| Permissions | VPN connection permission required on first launch | Add to battery-optimization whitelist, allow auto-start |
| Storage | About 150 MB | 300 MB (including subscriptions and logs) |
iOS and iPadOS are distributed through the App Store. Installing from the store gets you automatic updates for future releases; on first launch, allow the VPN configuration when prompted, then import your subscription.
The iOS version of Clash Plus uses the NetworkExtension framework to handle traffic, with subscription management, proxy groups, and rule-based routing working exactly the same way as on Android and desktop. The app is published officially on the App Store, with its own site at clashplus.io where you can verify version info and read the docs.
| Item | Requirement |
|---|---|
| Operating System | iOS 15 / iPadOS 15 or later |
| Devices | iPhone, iPad (including iPad apps running on Apple Silicon Macs) |
| Permissions | VPN configuration must be allowed on first launch |
| Getting It | Install from the App Store; updates are pushed automatically |
Linux desktop users should pick a package format based on their distro: deb for Debian/Ubuntu-based systems, rpm for Fedora/RHEL-based systems. For servers and routers without a desktop environment, use the Mihomo core binary further down this page and run it from the command line.
The most feature-complete Clash GUI client on Linux desktops, with system proxy support in both GNOME and KDE; TUN mode requires the appropriate permissions to enable. The deb package works on Debian, Ubuntu, and their derivatives; the rpm package works on Fedora, openSUSE, and similar distros.
The same lightweight, cross-platform interface works just as well on Linux — few dependencies and ready to run right after install. A good fit for desktop users who just need basic subscription management and node switching; switch to Clash Verge Rev if you need deeper config customization.
| Item | Minimum | Notes |
|---|---|---|
| Distro | Debian 11 / Ubuntu 20.04 / Fedora 38 or later | Match package format to your distro family |
| Processor Architecture | x86_64 | Other architectures: use the Mihomo core files below |
| Desktop Environment | GNOME / KDE (GUI clients) | Servers should use the core binary directly |
| Permissions | Enabling TUN requires root or the appropriate capability | — |
Core binaries for servers, routers, and command-line environments; regular desktop and mobile users should use the GUI clients above.
Mihomo is the core now built into nearly every client in the Clash ecosystem. Below are standalone binaries for each OS and architecture. The zip and gz files are archives — extract them to get an executable, then run it from the command line alongside a config.yaml; the Linux deb package can be installed directly with dpkg. For routers and embedded devices, choose the ARM or MIPS build that matches your device's processor.
| OS | Architecture | Format | File |
|---|---|---|---|
| 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 |
Core files have no graphical interface — you'll need to write or place a config file yourself and launch it from the command line. For details on protocol types, core family relationships, and config compatibility, see our protocol handbook.
Six questions specifically about getting installers; for installation and usage issues, see the FAQ page.
Windows SmartScreen and some browsers show a generic warning for new installers that haven't yet accumulated a download reputation. This is a default policy for unrecognized publishers, not a verdict on any specific file. Every installer linked on this page comes from the official release channel of its respective client.
On Windows, choose "More info → Run anyway" on the warning screen to continue. On macOS, confirm the app on first launch under System Settings → Privacy & Security. On Android, allow your browser to install apps from this source when prompted.
The order clients appear in on this page is our recommended order. Clash Plus, listed first and marked "Top Pick," covers both desktop and mobile with a consistent interface and active maintenance, making it the right choice for most users. Clash Verge Rev and FlClash are mature open-source alternatives. Entries marked "No Longer Maintained" are kept only as archives for legacy setups or migration.
For a full breakdown of feature differences, resource usage, and who each client is best for, see our client comparison page.
These correspond to different processor architectures: x64 and amd64 refer to 64-bit Intel and AMD processors, while arm64 refers to 64-bit ARM processors, including Apple silicon (M-series chips) and most recent Android phones.
On a Mac, check Apple menu → About This Mac to see your chip type — choose arm64 for M-series, x64 for Intel. On Android, arm64-v8a is the right choice for nearly all modern phones; fall back to armeabi-v7a or the universal build only on older devices. Picking the wrong architecture usually shows up as a failure to launch or an "incompatible" error — just re-download the matching build.
After the page loads, a script fetches a version manifest and points each download button to that client's current latest release; the version numbers shown on each card update from the same manifest.
If the manifest fails to load due to a network issue, buttons fall back to the archived links built into the page — downloads still work, but may not be the newest version. Refreshing the page will retry the update.
A freshly installed client doesn't do anything on its own — you still need to import a subscription, choose a proxy mode, and turn on system proxy or TUN mode. All three steps are required. We recommend following our Getting Started guide in order: first confirm the subscription imported successfully and the node list isn't empty, then check the proxy mode and toggle state, and finally verify your browser or app is actually routing through the system proxy.
If you're still stuck after checking each step, see the Troubleshooting section of our FAQ page.
Pick based on your distro's package manager: Debian, Ubuntu, Linux Mint, and their derivatives use deb packages installed via apt or dpkg; Fedora, RHEL, and openSUSE use rpm packages.
On rolling-release distros like Arch, consider a community package from your distro's repository first, or use the Mihomo core binary further up this page for server setups.