Packages · Installer Archive
Clash download
Installers for every platform
Choose a client by operating system and CPU architecture. For desktops, start with Clash Plus, Clash Verge Rev or FlClash; on Android, choose Clash Plus, Clash Meta for Android, FlClash or Surfboard; for servers and routers, use the standalone Mihomo core.
Platform · Platform Selection
Choose a Clash installer for your device
Platform tabs update the URL anchor, so you can save or share a page for a specific platform. The primary button on each card targets the common architecture; secondary buttons cover other CPU architectures or package formats.
Windows · x64
Windows clients
The current list provides x64 installers. Windows 10 and Windows 11 users should prefer graphical clients that are still maintained. After installation, import a subscription or local configuration and enable the system proxy; for broader traffic interception, configure TUN mode if supported by the client.
Clash Verge Rev
FlClash
Clash Nyanpasu
Clash for Windows
Windows system requirements
| Item | Recommendation | Selection guidance |
|---|---|---|
| Operating system | Windows 10 / 11 | Newer system versions generally offer more reliable compatibility with desktop runtimes, drivers and TUN components. |
| Processor | x64 | The Windows client links on this page target common Intel or AMD 64-bit PCs. |
| Permissions | Allow required system changes during installation | Administrator privileges may be required to enable TUN, install a service or write system proxy settings. |
macOS · Apple Silicon / Intel
macOS clients
Before downloading, open About This Mac from the Apple menu. Choose Apple Silicon when the chip is an Apple M-series chip; choose Intel when the processor is Intel. Select the architecture based on the actual hardware, not just the macOS version.
Clash Plus
Clash Verge Rev
FlClash
ClashX Meta
macOS system requirements
| Hardware or setting | Selection | How to verify |
|---|---|---|
| Apple M-series chip | Apple Silicon / ARM64 | The chip field in About This Mac shows Apple M1, M2, M3 or a later M-series chip. |
| Intel processor | Intel / x64 | The processor field in About This Mac shows Intel. |
| First launch | Confirm the app as prompted by macOS | On first launch, complete the confirmation required by macOS security settings, then allow the client to change proxy-related settings. |
Android · ARM64 / ARM
Android clients
Recent phones and tablets typically use arm64-v8a. Older 32-bit devices may require armeabi-v7a. If you cannot identify the architecture, check the ABI in a system information tool or choose the universal build of Clash Meta for Android.
Clash Plus
Clash Meta for Android
FlClash
Surfboard
Android system requirements
| Device type | Package | Details |
|---|---|---|
| Recent mainstream phones and tablets | ARM64 | Most 64-bit Qualcomm, MediaTek, Samsung and Google devices use this architecture. |
| Older 32-bit devices | ARM | Choose this only when the system ABI explicitly shows armeabi-v7a. |
| Architecture unknown | Universal version | The universal package supports more devices, but is usually larger than a single-architecture package. |
iOS · App Store
iPhone and iPad clients
On iOS, install Clash Plus from the App Store. After installation, add proxy settings through a subscription link, configuration file or another supported import method, then follow the system prompts to establish a VPN connection.
Clash Plus
iOS system requirements
| Item | Requirement | Details |
|---|---|---|
| Device | iPhone or iPad | Install the client from the App Store on the device. |
| Network permission | Allow VPN configuration | iOS displays a system authorization prompt on the first connection; confirm it before the client can route network traffic. |
| Configuration source | Subscription link or local configuration | After installing the client, import a valid configuration, choose a policy and start the connection. |
Linux · AMD64
Linux graphical clients
This section provides graphical clients for common AMD64 desktop distributions. Debian, Ubuntu and derivatives generally use DEB; Fedora, RHEL, openSUSE and other RPM-based systems use RPM. For servers or routers, see the Mihomo core section below.
Clash Verge Rev
FlClash
Linux system requirements
| Distribution type | Package format | Installation guidance |
|---|---|---|
| Debian / Ubuntu and derivatives | DEB | Install through a graphical software manager or the system package manager. |
| Fedora / RHEL / openSUSE and others | RPM | Choose the Clash Verge Rev RPM package and use the package manager for your distribution. |
| Desktop environment | Graphical session | GUI clients require an available desktop environment; use the Mihomo core below for headless server deployments. |
Core · Mihomo
Mihomo core architecture packages
The standalone core is intended for servers, routers, containers, gateway devices and command-line deployments. Regular desktop and mobile users should generally choose a graphical client above, since GUI clients already provide configuration imports, policy switching, log viewing and system proxy controls. Running the core directly requires you to prepare the YAML configuration, working directory, startup arguments and system service yourself.
| Operating system | Architecture | Format | Package |
|---|---|---|---|
| Windows | amd64 |
ZIP | Download Windows AMD64 |
| Windows | arm64 |
ZIP | Download Windows ARM64 |
| macOS | amd64 |
GZ | Download macOS Intel |
| macOS | arm64 |
GZ | Download macOS Apple Silicon |
| Linux | amd64 |
DEB | Download Linux AMD64 DEB |
| Linux | amd64 |
GZ | Download Linux AMD64 GZ |
| Linux | arm64 |
GZ | Download Linux ARM64 GZ |
| Linux | armv7 |
GZ | Download Linux ARMv7 GZ |
| Linux | mips-softfloat |
GZ | Download MIPS Softfloat GZ |
Selection · Selection Guide
How to identify package formats and architectures
A client may offer an installer, an archive and multiple CPU architectures at once. Confirm the operating system first, then the CPU architecture, and finally the package format to reduce startup failures and component incompatibility.
Windows installer
An EXE installer follows the standard desktop setup process, placing application files and creating a usable launch entry. For a personal computer used regularly, this is the more direct option. With a ZIP version, you choose the extraction folder yourself and must replace files manually when updating.
macOS disk image
After opening the DMG, move the app to the Applications folder and launch it from there. Apple Silicon and Intel describe hardware architectures, not operating system versions; two Macs running the same macOS release may still require different installers.
Android architecture packages
ARM64 is common on current Android devices, while 32-bit ARM is mainly found on older hardware. A universal package includes resources for multiple architectures and is useful when the ABI is unknown. After installation, allow the client to establish a VPN connection in system settings.
Linux package formats
DEB targets Debian, Ubuntu and derivatives; RPM is commonly used by Fedora, RHEL, openSUSE and similar systems. The wrong format usually cannot be installed directly by the system package manager, and the CPU architecture must also match the device.
FAQ · Downloads and Installation
Clash download FAQs
These questions cover package formats, CPU architectures, the standalone core and configuration imports. For a complete connection workflow, continue to the usage documentation; for network issues, open the troubleshooting page and work through the checks in order.
Should I install the Windows version or use the portable ZIP?
Most desktop users should choose the installer. It creates a Start menu entry and places application files through the standard setup process. The ZIP version suits users who manage folders themselves, keep separate configuration environments, or lack installation permissions. The main difference is deployment, not a fixed difference in proxy capabilities.
How do I choose between Apple Silicon and Intel on macOS?
Open About This Mac from the Apple menu. Choose Apple Silicon when the chip field shows an Apple M-series chip; choose Intel when the processor field shows Intel. A mismatched package architecture can prevent startup or require additional translation, so rely on the hardware information rather than the purchase year.
What is the difference between arm64, arm and universal Android builds?
Most recent Android phones and tablets use arm64, while older 32-bit devices use arm. If you cannot identify the architecture, choose the universal build; it contains files for multiple architectures and is usually larger. If system information shows arm64-v8a, choose ARM64 directly.
Do regular users need to download the Mihomo core?
Usually not. Graphical clients such as Clash Plus, Clash Verge Rev and FlClash already provide a complete interface and core management. The standalone Mihomo core is mainly for servers, routers, containers and command-line deployments, where you must manage configuration paths, startup arguments, permissions and system services yourself.
Why can’t I connect immediately after installing the client?
The client does not include proxy nodes. After installation, import a working subscription URL or local YAML configuration, wait for it to parse, select a node or proxy group, then enable the system proxy or TUN mode for the traffic you want to route. If the configuration will not update, check the subscription URL, network connectivity and client logs first.
Can a discontinued client still be used?
Archived versions may still run on compatible systems, but they will not keep up with new operating systems, core behavior or configuration formats. For new installations, prefer a maintained client; Clash for Windows and ClashX Meta archives are mainly for configuration migration, preserving specific legacy environments and necessary fallback operations.