clash2027.com / releases
A client download index grouped by platform. Within each platform, the listing order is the recommended order, with Clash Plus as the top pick. Version numbers and download links are filled in from the release manifest at page load and always point to the latest build in that manifest; if an upstream client doesn't publish a version field, the number is left blank but the link still works. For servers and routers, use the Mihomo core binaries at the bottom of the page.
platforms: 5 · core: mihomo · Open-source licenses follow each client's upstream repository
Five clients are available for Windows, all 64-bit installers. For everyday use, the first one, Clash Plus, is enough; pick Clash Verge Rev if you prefer a lighter desktop app; choose FlClash if you want the same workflow across desktop and mobile; Clash Nyanpasu targets users who want to deeply customize their configuration processing chain. Clash for Windows is no longer maintained and is listed last purely as an archive.
One consistent interface and subscription logic across every platform, with a built-in Mihomo core, Rule/Global mode switching, automatic subscription updates and TUN mode. The Windows build is an x64 installer with a toggle for launch-on-startup in settings — a solid default choice if you want the same client on all five platforms.
A Tauri-based desktop client with a small install size and low memory footprint, supporting Merge and Script style subscription enhancements. The Windows build relies on the WebView2 runtime, which is usually already built into Windows 11 and recent Windows 10 systems.
An open-source, Flutter-based cross-platform client with the same interface on desktop and mobile, supporting multiple subscriptions and automatic node latency testing. Available as an installer or a portable zip archive — grab the zip if you want to run it from a USB drive or avoid touching the registry.
A community fork of Clash Verge with Merge and JavaScript chained configuration processing, finer-grained UI customization and alternative proxy group displays. A good fit for users who want to post-process their subscriptions locally in the client; it also relies on the WebView2 runtime.
Once the dominant Windows client, its repository was archived in 2023 and has received no feature updates or security fixes since, so compatibility with new protocols and newer systems will keep degrading. Kept here only as an archive for users migrating an old configuration — new installs should use one of the actively maintained clients above.
| Item | Requirement |
|---|---|
| Operating system | Windows 10 64-bit or later; the archived Clash for Windows build supports older systems, but new installs aren't recommended |
| Architecture | x64 — all Windows installers on this page are 64-bit |
| Runtime dependency | Clash Verge Rev and Clash Nyanpasu need the WebView2 runtime, usually already built into newer systems |
| Permissions | Enabling TUN mode requires authorizing a system service install; follow the client's prompt the first time you turn it on |
macOS builds are split by chip: pick arm64 for Apple Silicon (M-series) and x64 for Intel — check the chip line under "About This Mac" if you're not sure. ClashX Meta is no longer maintained but still works fine for light menu-bar use; new installs should go with Clash Plus or Clash Verge Rev.
The macOS build shares the same interface and subscription logic as every other platform, with a built-in Mihomo core and both system-proxy and TUN takeover modes. Pick the dmg image matching your chip and drag it into the Applications folder to finish installing.
The macOS build of the Tauri desktop client — low footprint, clean interface, and support for Merge/Script configuration enhancements and switching between cores. If macOS warns about an unidentified developer on first launch, allow it under System Settings → Privacy & Security.
The macOS build of the Flutter cross-platform client, keeping the same workflow as the Windows and Android versions — handy if you use multiple devices and want to minimize the learning curve. Supports multiple subscriptions, config overrides and node latency testing.
A classic macOS menu-bar client — sits in the status bar with a minimal interface, good for light use where you just need to import a subscription and switch nodes. The project is no longer maintained and won't track new systems or protocol features, so new installs should prefer one of the actively maintained clients above.
| Item | Requirement |
|---|---|
| Operating system | macOS 10.15 Catalina or later; newer clients recommend macOS 12 or later |
| Architecture | Apple Silicon (M-series) uses arm64; Intel processors use x64 |
| First launch | If macOS warns about an unidentified developer, allow it under System Settings → Privacy & Security |
| TUN mode | Requires authorizing a system extension or helper tool as prompted by the client |
All four Android clients are distributed as direct-install APKs. Any mainstream device released after 2016 should use the arm64-v8a package; older devices or set-top boxes should pick armeabi-v7a based on the device, and the universal package works if you're not sure of the CPU architecture. Before installing, allow your browser or file manager to install unknown apps in system settings.
The Android build takes over traffic through the system VpnService and shares the same subscription and rule logic as the desktop build, so there's nothing new to learn if you switch devices. Supports automatic subscription updates and per-app proxying; mainstream devices should download the arm64-v8a package.
The official Android client for the Mihomo (Clash Meta) core, supporting full VpnService takeover, per-app proxying and config overrides. Its feature set closely mirrors the core's native capabilities, which suits users comfortable with configuration files. Three packages are provided by CPU architecture.
The Android build of the Flutter client, with an interface identical to the desktop version, supporting multiple subscriptions and automatic latency testing. If you're already using FlClash on your computer, picking it on your phone lets you carry over the exact same workflow.
An Android client compatible with the Clash subscription format, following Material Design guidelines with few settings and a straightforward learning curve — good for light use where you just import a subscription and toggle the proxy. This package is the universal build distributed directly from this site.
| Item | Requirement |
|---|---|
| OS version | Android 7.0 or later; some clients support older versions — follow the prompt during installation |
| Architecture | Devices released after 2016 should use arm64-v8a; older devices use armeabi-v7a; use universal if unsure |
| Install permission | System Settings → Install unknown apps, then authorize your browser or file manager |
| VPN permission | The first time traffic takeover starts, you must accept the system's VPN connection prompt |
Clash Plus for iOS is distributed through the App Store, so the store listing always reflects the latest version and automatic system updates keep it current. Feature details and documentation live on the official site at clashplus.io.
The iOS build takes over traffic through the system Network Extension framework, supporting subscription import, rule-based routing and policy group switching. It works on both iPhone and iPad, with purchases shared across devices under the same Apple ID. Install it from the App Store listing; see clashplus.io for more details.
| Item | Requirement |
|---|---|
| OS version | Follow the minimum system version listed on the App Store page |
| Device | Works on both iPhone and iPad, with purchases shared under the same Apple ID |
| Network permission | The first launch requires allowing a VPN configuration to be added — confirm in the system prompt |
| Update method | Updates automatically through the App Store, no manual package download needed |
Linux desktop builds are offered as deb or rpm packages: use deb for Debian, Ubuntu and their derivatives, and rpm for Fedora, openSUSE and other RPM-based distros. Servers and router setups without a desktop environment don't need a GUI client — use the Mihomo core binaries in the section at the bottom of the page instead.
The most feature-complete and actively used GUI client on Linux desktop, supporting system-proxy writes, TUN mode and Merge/Script configuration enhancements. Install the deb package with dpkg -i or apt install ./package-name, and the rpm package with dnf install.
The Linux build of the Flutter client, with an interface identical to the other platforms, few dependencies and ready-to-run out of the box. Debian-based distros should download the deb package, then launch it from the application menu or run flclash in a terminal.
| Item | Requirement |
|---|---|
| Distribution | The deb package targets Debian 11+ / Ubuntu 20.04+ and derivatives; the rpm package targets Fedora and other RPM-based distros |
| Architecture | amd64 (x86_64); ARM devices and routers should use the matching architecture from the Mihomo core section below |
| Desktop environment | Works with mainstream desktops such as GNOME and KDE; the tray icon depends on desktop extension support |
| TUN mode | Requires root privileges, or granting the core binary the cap_net_admin capability |
Mihomo is the core used by most of the clients above. The binaries below are for headless setups such as servers, routers and containers: extract the archive and run it from the command line alongside a config.yaml. Regular desktop and mobile users should just use one of the GUI clients above — there's no need to download the core separately.
gzip -d mihomo-linux-amd64.gz && chmod +x mihomo-linux-amd64 && ./mihomo-linux-amd64 -d /etc/mihomo, where -d points to a directory containing config.yaml. See the full documentation for configuration syntax.chmod +x to make it executable, then start it with the -d flag pointing to a directory that contains config.yaml; Debian-based systems can install the deb package directly. The core itself has no GUI — regular desktop users should just use one of the GUI clients above instead of downloading the core separately.For importing subscriptions and choosing a mode after installing, see the getting started guide; if you run into startup or connection issues, check the FAQ first.