Installers organized by platform · version manifest resolved automatically
This page lists client installers for five platforms in recommended order, with the OS version, CPU architecture and package format noted on each card; the Mihomo core files for servers and routers are further down. The same subscription link works on every platform, with identical config syntax.
For a first install, start with the setup guide, which walks through subscription import and mode selection step by step.
Installers · by platform
Windows and macOS offer the widest choice of clients, while Android, iOS and Linux each have their own focus. Switch tabs to see the client list, system requirements and download links for that platform; the first card on each platform is the recommended pick.
Windows has the widest selection of clients, from the top-pick Clash Plus to the archived Clash for Windows. Apart from the entries marked as discontinued, every client here offers its current release; for everyday use, take the first card and treat the rest as comparisons and alternatives.
System requirements
| Operating system | Windows 10 version 1809 or later (64-bit) |
|---|---|
| CPU architecture | x64; ARM64 devices can pick the matching build in the Mihomo core section |
| Package format | .exe installer; FlClash also offers a portable .zip |
| Permissions | TUN mode requires administrator rights; system proxy mode does not |
The top pick across platforms: import a subscription, switch proxy modes and check policy group latency from the graphical interface, with everyday settings gathered in one panel — a good fit if you'd rather not edit YAML by hand.
Official site: clashplus.io
A community-maintained desktop client with multiple profile switching, core version management and a TUN mode toggle; its settings are grouped clearly, which suits users who move back and forth between the GUI and config files.
Profiles and subscription lists are stored in the user data directory, so installing over an existing copy won't clear your configuration.
A Flutter-based cross-platform client whose interface and workflow stay the same on Windows, macOS, Linux and Android; the installers are fairly small, which makes it easy to keep one set of habits across platforms.
The portable build works exactly like the installer — just unzip it and run the main executable.
A desktop client that puts policy groups and rules in the same view on its configuration page, with automatic subscription updates and policy group sorting — a good fit if you like reading the config file directly.
The installer already bundles the core, so there's no separate core file to set up afterwards.
The most widely used Windows client in the early days, and the one later clients took their interface structure and configuration logic from. The project is archived and frozen at its final release, kept here only for historical downloads and migration reference.
No new releases; new users should pick the recommended entry above.
macOS clients mostly live in the menu bar, with the control panel opened from the status bar icon. Clash Plus ships separate installers per chip, while other clients publish a single dmg entry upstream, so both chips download the same file.
System requirements
| Operating system | macOS 11 or later |
|---|---|
| CPU architecture | Apple Silicon（arm64）/ Intel（x64） |
| Package format | .dmg disk image — open it and drag the app into your Applications folder |
| First launch | If macOS reports an unidentified developer, allow the app under System Settings → Privacy & Security |
The top pick across platforms, living in the menu bar: subscription import, mode switching and policy group latency tests all happen in the GUI. Apple silicon and Intel Macs are packaged separately, so just download the build that matches your processor.
The two installers are split by processor; the wrong build reports an incompatible architecture at launch.
A desktop client with multiple profiles, subscription groups and rule set management, plus one-click switching between TUN mode and system proxy; config changes take effect immediately, which suits setups where rules change often.
Upstream ships one dmg for both chips, so Intel and Apple silicon Macs share this download.
A Flutter cross-platform client with separate main window and menu bar entry points; you can edit YAML directly on the configuration page and reload it instantly, which makes it easy to keep one workflow across macOS and Windows.
Open the dmg and drag the app into your Applications folder to finish installing.
A menu bar client built on the mihomo core, with support for newer rule types and TUN mode. The project is no longer maintained and is frozen at its final release; new users should choose a client that is still updated.
No further releases; if you plan to keep using it long term, keep an eye on rule compatibility.
Android installers are split by CPU architecture: arm64-v8a covers mainstream phones released in recent years, armeabi-v7a targets older 32-bit devices, and x86_64 is for emulators and a few tablets. If you're unsure which architecture your device uses, go with arm64-v8a first; Clash Meta for Android also offers a universal APK.
System requirements
| Operating system | Android 8.0 or later |
|---|---|
| CPU architecture | arm64-v8a / armeabi-v7a / x86_64 |
| Package format | .apk — you'll need to allow installs from unknown sources in system settings |
| Permissions | The first connection asks for VPN permission, which lets the client route app traffic |
The top pick across platforms: install it, import a subscription and you're set, with policy group switching, latency tests and connection logs in the interface. The APK is built for arm64, covering mainstream phones released in recent years.
Before installing, make sure your device runs Android 8.0 or later.
A community-maintained Android client with rule-based routing, TUN mode and config import/export, showing policy groups and the connection list on separate tabs; three APKs are provided, so pick the one matching your device's architecture.
If you're unsure which architecture your device uses, pick the universal APK.
A Flutter client that shares one configuration model between Android and desktop, with per-app proxy and in-app updates; the APKs are built per CPU architecture and are functionally identical.
The three APKs differ only in the instruction set they target; features and config format are the same.
A graphical Android client focused on rule-based routing and network diagnostics, where you can inspect connections and traffic flow per app; the universal APK offered here covers the vast majority of devices.
The universal APK isn't tied to a CPU architecture — a single file covers the vast majority of devices.
On iOS, installation goes through the App Store, where Clash Plus offers its current release for iPhone and iPad. Once installed, import your subscription link in the app to get started; the first connection triggers a system prompt to authorize the VPN configuration.
System requirements
| Operating system | iOS 15.0 or later |
|---|---|
| Device type | iPhone / iPad |
| Installation | App Store listing; the system handles installation and updates |
| Permissions | The first connection asks you to allow a VPN configuration, which you can review later in Settings |
The top iOS pick: after importing a subscription you can switch policy groups and review connection logs and traffic statistics. The app is distributed through the App Store, so version updates arrive with store pushes and there's no installer to replace by hand.
Official site: clashplus.io
Linux builds come as .deb and .rpm system packages plus a portable AppImage. Choose .deb for Debian and Ubuntu, .rpm for Fedora and openSUSE; the AppImage writes nothing to system directories, which suits restricted or portable setups.
System requirements
| Distribution | Debian / Ubuntu / Fedora / openSUSE and other mainstream distributions |
|---|---|
| CPU architecture | amd64 |
| Package format | .deb / .rpm / AppImage |
| Permissions | TUN mode needs root, or the matching capability set on the executable |
The recommended desktop client on Linux, available as both .deb and .rpm system packages; launch it from the application menu after installing, manage profiles and subscription lists on a single page, and switch nodes without restarting the app.
The package manager handles dependencies for system packages; launch the app from your application menu once it's installed.
A Flutter client that offers an AppImage single-file build alongside .deb and .rpm, which suits setups without root access or where you want to keep the client on removable storage; all three formats are functionally identical.
Make the AppImage executable before running it.
Mihomo is the core most widely used across the Clash ecosystem today; the binaries here cover various platforms and architectures for servers, soft routers and setups where you arrange startup parameters yourself. Desktop and mobile users can simply use the GUI clients above — there's no need to download the core separately.
| Platform | Architecture | File | Download |
|---|---|---|---|
| Windows | AMD64 | mihomo-windows-amd64.zip |
Download |
| Windows | ARM64 | mihomo-windows-arm64.zip |
Download |
| macOS | Intel（amd64） | mihomo-darwin-amd64.gz |
Download |
| macOS | Apple Silicon（arm64） | mihomo-darwin-arm64.gz |
Download |
| Linux | AMD64 (deb package) | mihomo-linux-amd64.deb |
Download |
| Linux | AMD64 | mihomo-linux-amd64.gz |
Download |
| Linux | ARM64 | mihomo-linux-arm64.gz |
Download |
| Linux | ARMv7 | mihomo-linux-armv7.gz |
Download |
| Linux | MIPS softfloat | mihomo-linux-mips-softfloat.gz |
Download |
Launching
# start with an explicit config directory and config file after extracting
./mihomo -d /etc/mihomo -f config.yamlThe core has no graphical interface: listening ports, DNS and routing rules all come from config.yaml; on a router or server you'll usually add a service script to start it on boot.
After downloading
The installer is only the starting point — whether browsing actually works depends on importing the subscription successfully and choosing the right proxy mode. Work through the three steps below and the client is ready for everyday use.
Open the client's configuration page, paste the subscription link into the field and save, then wait for nodes and rules to finish loading. If policy groups appear in the list and latency tests respond, the subscription is active.
For everyday browsing use rule mode, which sends mainland China domains direct and routes the rest by rule; switch to global mode when all traffic should go through the proxy; use direct mode for LAN debugging or when troubleshooting the client.
Run a latency test in a policy group to confirm nodes respond, then open a web page to confirm it loads. If it doesn't, check the errors in the client log first, then see whether the system proxy or TUN is being held by another application.
Full step-by-step instructions are in the Clash setup guide; for rule syntax, DNS and core parameters, see the zero-to-advanced handbook.
Download FAQ
These six questions cover how versions are resolved, platform choices, architecture picks, and what to do with discontinued clients.