DOWNLOAD SHELF · CL-03
This page is organized into six shelves by operating system. Each entry card covers one client, listing its core, catalog date, and installers by architecture. Pick your platform first, then grab the top card in that shelf; once installed, follow the import guide to finish setting up your subscription.
Cards within each shelf are ordered by recommendation; discontinued entries are marked separately and kept for archival use only.
The Windows shelf lists five clients. The first four are actively maintained and bundle the mihomo core; the fifth is an archived entry kept only for migrating old configs. All are x64 installers — installing to a path without spaces or non-English characters helps avoid permission issues.
A cross-platform client. Subscription import, proxy group switching, system proxy, and TUN toggle all live on one main screen, and the defaults work out of the box — no need to understand config file syntax first. The interface is identical across all five platforms, so switching devices doesn't mean relearning anything. This is the card to start with if you're new to Clash.
A community-maintained fork of Verge. Offers two tiers of config enhancement (Merge and Script), a dedicated TUN mode panel, and detailed connection logs, with a dense, information-rich interface. Good for users who need fine-grained control over proxy groups or edit rules often — and the most common landing spot for people migrating off Clash for Windows.
An open-source, cross-platform client built with Flutter, sharing the same UI logic across desktop and mobile. Supports multiple subscriptions at once and per-subscription core parameter overrides, with a clean panel layout. Comes as both an installer and a portable zip — grab the zip for a no-install setup.
A Tauri-based desktop client that's small and fast to launch, with support for script extensions and running multiple cores side by side. The interface is light and breezy, aimed more at everyday use than heavy tweaking. Only the Windows installer is listed in this shelf.
Once the most widely used Windows client, it stopped receiving updates in 2023 and no longer gets core or security patches. The archived installer here is kept for people migrating old configs. For everyday use, pick any of the actively maintained entries above instead — your subscription link will carry over directly.
| Item | Requirement |
|---|---|
| Operating System | Windows 10 64-bit or later; all editions of Windows 11 |
| Processor Architecture | x64 (all installers in this shelf) |
| Disk Space | About 200 MB (including core and logs) |
| Permissions | Run as administrator once to enable TUN mode |
The macOS shelf lists four clients. Check your Mac model before downloading: Apple Silicon Macs (2020 or later) need arm64, older Intel Macs need x64. See the tutorial page for the network extension authorization steps on first launch.
The macOS build matches the Windows version's interface, with a menu bar icon for switching modes and proxy groups on the fly. Comes as two separate dmg files — one for Apple Silicon, one for Intel — pick the one matching your Mac. Just approve the system proxy and enhanced mode prompts when they appear.
The macOS build matches the Windows version feature for feature: config enhancement, a TUN panel, and connection logs are all included. Good for users who want fine-grained proxy group control on a Mac. If the system blocks it after installing, follow the steps under FAQ CL-03.7-03 on this page to allow it.
Shares the same interface and multi-subscription management logic as its counterparts on other desktop platforms. If you bounce between a Mac and your phone, this keeps your workflow consistent across devices. Open the dmg and drag the app into your Applications folder to install.
The Meta-core fork of the classic ClashX menu bar client — lightweight, no main window, everything runs from the menu bar. The project is no longer maintained, though the existing build still works fine; longtime ClashX users can keep using it, but newcomers should pick one of the actively maintained entries above instead.
| Item | Requirement |
|---|---|
| Operating System | macOS 11 Big Sur or later |
| Processor Architecture | Apple Silicon(arm64)/ Intel(x64) |
| Permissions | Must be allowed under Privacy & Security on first launch; enhanced mode requires network extension authorization |
| Disk Space | About 150 MB |
The Android shelf lists four clients, all distributed as APKs — you'll need to allow app installs from this source. On architecture: recent flagship phones should use arm64-v8a; if you're not sure, go with the universal build.
The Android build shares the same account logic as the desktop versions: paste your subscription link to import, connect with one tap from the home screen, and switch proxy groups on the same screen. It takes over traffic through the system's VPN interface — no root required. This is the card to start with for setting up Clash on your phone.
The standard Clash client on Android, with a no-frills interface that exposes every setting and supports per-app proxying and config overrides. Good for users who want to understand exactly what each setting does. Three architecture builds are available — the universal build works on any of them.
The mobile build looks and feels just like the desktop version, with the same experience for managing and switching between multiple subscriptions. It remembers your proxy group choice per subscription, so switching subscriptions won't reset your settings. Same rule for picking an architecture as the client to the left; the x86_64 build is meant for emulators and a handful of tablets.
An Android client compatible with Surge's config syntax — the rule format differs from the Clash family, which suits users who also maintain Surge configs, or whose subscription service offers both formats. Only a universal build is available, hosted directly by this site.
| Item | Requirement |
|---|---|
| Operating System | Android 8.0 or later |
| Processor Architecture | arm64-v8a preferred; armeabi-v7a for older devices; use universal if unsure |
| Permissions | VPN configuration must be authorized on first connection; disabling battery optimization for the app is recommended |
| Install Method | Direct APK install; must allow installs from this source |
The iOS shelf is distributed through the App Store — search there or tap the button below to jump straight to the listing. iPhone and iPad share the same entry.
The iOS build takes over traffic through the system's Network Extension, with subscription import, proxy groups, and rule mode switching working the same as on other platforms — it runs on both iPhone and iPad. The developer's official site is clashplus.io, where release notes and links for every platform are listed. On first connection, just approve adding the VPN configuration when prompted.
| Item | Requirement |
|---|---|
| Operating System | iOS 15 / iPadOS 15 or later |
| Device | Works on iPhone and iPad |
| Install Method | Install directly from the App Store listing |
| Permissions | Must allow adding a VPN configuration on first connection |
The Linux shelf lists two GUI clients, both x86_64 builds. Debian/Ubuntu-based distros should grab the deb; Fedora/openSUSE-based ones should grab the rpm. For command-line or server environments, see the core shelf at CL-03.6 instead.
The most fully-featured Clash client on Linux desktops, with a system tray icon, TUN mode, and config enhancement all supported. Available as either deb or rpm depending on your package manager — once installed, launch it from your app menu. TUN mode requires granting the core binary the relevant capability, as prompted.
The cross-platform interface holds up just as well on Linux, with the same multi-subscription management as its desktop counterparts. Fewer dependencies make it a good fit for lightweight desktop setups. Only a deb build is listed here, for Debian/Ubuntu-based distros.
| Item | Requirement |
|---|---|
| Distribution | Mainstream x86_64 distributions (Debian / Ubuntu / Fedora, etc.) |
| Desktop Environment | Common desktops like GNOME and KDE; tray icon support depends on the relevant extension |
| Permissions | TUN mode requires granting the core binary network management capability |
| Package Format | deb / rpm |
This shelf is for servers, routers, and command-line environments: a bare mihomo core binary that needs its own config file and manual process management. Desktop and mobile users don't need this — the GUI clients in the first five shelves already bundle the core. All files are hosted directly by this site.
| Platform | 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 |
The gz archive extracts to a single executable, which you run from the command line with a config.yaml; the deb package installs directly as a system service on Debian-based distros. arm64 and armv7 target ARM devices like Raspberry Pi, while mips-softfloat targets certain router firmware. For a comparison of core families and config compatibility, see the protocol handbook.
Only questions directly related to downloading and installing are covered here; for subscription import and connection issues, see the tutorial page and technical notes.
The button fetches a version manifest on page load and automatically points to the current listed installer; if the manifest fails to load, it falls back to the installer link recorded when this page was last catalogued. Both come from the same release channel and contain the same build. The version number shown on each card is likewise filled in from the manifest — the button's actual target is what matters.
This is a standard warning for installers with newer signatures, not a sign that anything is wrong with the installer. Click "More info" then "Run anyway" to continue. After installation, it's a good idea to run the app as administrator once on first launch so it can register the system proxy — after that, just double-click to launch normally.
If the app is blocked on first launch, go to "System Settings → Privacy & Security", scroll to the bottom, and choose "Open Anyway" next to the relevant prompt. Pick the right build: Apple Silicon Macs need the arm64 installer, Intel Macs need the x64 installer. Full steps for handling the network extension and keychain prompts are covered in a dedicated technical note.
For phones released after 2019, go with the arm64-v8a build. Older 32-bit devices should use armeabi-v7a. If you're not sure of your processor architecture, pick the universal build — it's larger, but works on every architecture. Installing the wrong architecture build usually means the app won't install, or crashes right after opening — just reinstall with the correct build.
The archived build can still be downloaded and run, but it no longer receives core updates, bug fixes, or support for newer protocol types. For everyday use, we recommend switching to Clash Plus or Clash Verge Rev — your existing subscription links and config files carry over directly, no rework needed. See the client comparison guide for more.
The core archive is meant for servers, routers, and command-line environments — you'll need to write your own config file and run it from the command line, with no graphical interface. Desktop and mobile users should just use the GUI clients on this page, which already bundle the core and update it along with the app.
Once your client is installed, continue with these two guides.
Step-by-step instructions from importing a subscription to verifying your connection, with a checkpoint at every step. Follow this guide once for your first setup.
Go to the GuideCovers the design trade-offs of each proxy protocol, how core families relate to each other, and subscription format compatibility — useful for picking the right protocol type in your client.
Go to the Handbook