Top pick
Clash Plus
A graphical client for everyday desktop use, with config imports, policy switching, system proxy controls, and subscription management. The Windows x64 installer suits most PCs.
CLIENT PACKAGE INDEX
Clash Downloads and Platform Installers
Choose a client based on your operating system, processor architecture, and workflow. This page brings together download links for FlClash, Clash Plus, Clash Verge Rev, Clash Meta, and Mihomo.
Free forever
Open source
Multi-platform installers
114
Dl
Client download index
GUI · CORE · ARCH
SELECT PLATFORM
Choose an operating system
Choose a platform first, then select the primary installer for your processor architecture. After loading, the page reads the latest release list; if the network request is temporarily unavailable, each button keeps its complete fallback path.
WINDOWS
Windows clients
For Windows 10 and Windows 11. The x64 installer is the usual choice; administrator permissions may be required on enterprise or managed devices when enabling system proxy or service mode.
Clash Verge Rev
A mihomo-based desktop client for users who need rule management, config overrides, TUN mode, and granular policy controls.
FlClash
Combines a Flutter interface with the mihomo core, using a similar interaction model across desktop and mobile. Available as both an installer and a portable archive.
Clash Nyanpasu
Offers desktop config management, rule inspection, and proxy mode switching for users who prefer a dedicated desktop interface and organized multi-config workflows.
Discontinued
Clash for Windows
Archived installers remain available for reading legacy configs or completing client migrations. For new installations, choose a maintained client listed above.
Windows system requirements
| Item | Recommendation | Details |
|---|---|---|
| System | Windows 10 / 11 | Use a 64-bit system that is still within its support lifecycle. |
| Architecture | x64 | The Windows GUI clients listed here primarily use x64 installers. |
| Permissions | Standard or administrator permissions | Authorization may be required to enable service mode, TUN, or modify system network settings. |
MACOS
macOS clients
Before downloading, check the chip type in About This Mac or System Information. Choose ARM64 for Apple M-series chips and x64 for Intel processors.
Top pick
Clash Plus
Provides separate Apple Silicon and Intel disk images for macOS users who want clear configuration access, policy selection, and system proxy controls.
Clash Verge Rev
A desktop mihomo client supporting subscriptions, config overrides, rule inspection, and TUN. Both architecture links in the current list are maintained by the same release service.
FlClash
A cross-platform Flutter client for users who want a similar workflow on computers and Android devices. On first launch, follow the system prompts to authorize network access.
Discontinued
ClashX Meta
Kept for legacy macOS config migration and archival use. The installer is still resolved through the release manifest; new deployments should use a maintained client listed above.
macOS system requirements
| Device type | Package | How to identify |
|---|---|---|
| Apple Silicon | ARM64 | The Chip field shows an Apple M-series chip. |
| Intel Mac | x64 | The Processor field shows Intel. |
| Network permissions | Authorize as prompted | Confirmation is required the first time system proxy or a network extension is enabled. |
ANDROID
Android clients
Most recent devices use ARM64. Choose ARM for older 32-bit devices, or download the universal package when the processor architecture is unknown.
Top pick
Clash Plus
For modern 64-bit Android phones and tablets, with subscription imports, policy selection, and a system VPN connection entry point.
Clash Meta for Android
A mihomo-based Android client offering ARM64, ARM, and universal packages. Select the matching package when the architecture is known to reduce download size.
FlClash
Uses the same Flutter design system on mobile and desktop, supporting ARM64, 32-bit ARM, and x86_64 Android devices.
Surfboard
An Android graphical client for mobile devices using compatible configs and rules. This site provides a universal package for broader processor compatibility.
Android architecture guide
| Package | Compatible devices | Recommendation |
|---|---|---|
| arm64-v8a | Most recent phones and tablets | Preferred for modern Android devices. |
| armeabi-v7a | Older 32-bit ARM devices | Use only when the device is confirmed to be 32-bit. |
| Universal | Devices with unknown architecture | Broader compatibility, usually with a larger file size. |
IOS
iPhone and iPad
On iOS, get Clash Plus through the App Store. After installation, import a compatible subscription from the configuration page and follow the system prompts to allow the network configuration.
Top pick · App Store
Clash Plus
A networking tool for iPhone and iPad with config management, policy switching, and system network access. App details and platform information are also available on the official site.
Official site: clashplus.io
iOS system requirements
| Item | Requirement | Details |
|---|---|---|
| Device | iPhone / iPad | Check the App Store page for the currently supported iOS versions. |
| Installation source | App Store | Use the store button above to open the app details page. |
| Network configuration | System authorization | When connecting for the first time, confirm the network configuration prompt from the system. |
LINUX
Linux desktop clients
Choose DEB for Debian, Ubuntu, and derivatives; use RPM for Fedora and RHEL-based distributions. These GUI packages target AMD64 desktop environments.
Recommended
Clash Verge Rev
A mihomo graphical client for Linux desktops, offering AMD64 DEB and RPM packages. After installation, launch it from the applications menu and import a subscription.
FlClash
Provides Linux AMD64 DEB, RPM, and AppImage packages. DEB suits Debian-based distributions; AppImage suits desktop environments that prefer fewer system installation steps.
Linux package formats
| Format | Common distributions | Installation notes |
|---|---|---|
| DEB | Debian、Ubuntu、Linux Mint | Install with the system software installer or dpkg. |
| RPM | Fedora and RHEL-based distributions | Install using the distribution's package manager. |
| AppImage | Most AMD64 desktop distributions | Grant execute permission, then run directly. |
MIHOMO CORE
Standalone Mihomo core
The standalone Mihomo binary is intended for servers, software routers, edge gateways, and command-line deployments. Regular desktop and mobile users should prefer the GUI clients above, which handle core startup, config paths, and system proxy controls.
| System | Architecture and format | Use case | Download |
|---|---|---|---|
| Windows | AMD64 · ZIP | 64-bit Intel / AMD computers and servers | Download AMD64 |
| Windows | ARM64 · ZIP | Windows on ARM devices | Download ARM64 |
| macOS | Intel · GZ | Intel processor Macs | Download Intel |
| macOS | Apple Silicon · GZ | Apple M-series chips | Download ARM64 |
| Linux | AMD64 · DEB | Debian-based servers and desktop systems | Download DEB |
| Linux | AMD64 · GZ | Generic 64-bit Linux environments | Download AMD64 |
| Linux | ARM64 · GZ | 64-bit ARM servers and router devices | Download ARM64 |
| Linux | ARMv7 · GZ | 32-bit ARMv7 router devices | Download ARMv7 |
| Linux | MIPS softfloat · GZ | MIPS router devices using the soft-float ABI | Download MIPS |
Configuration file
Before running independently, prepare config.yaml and confirm that the ports, DNS, proxy nodes, policy groups, and rules are recognized by the current core.
Process management
On servers, use systemd or an existing service manager to keep the process running. On router systems, configure startup order through the firmware's service mechanism.
Processor architecture
The architecture must match the operating system. AMD64, ARM64, ARMv7, and MIPS files are not interchangeable; check the device information before downloading.
BEFORE INSTALL
Post-download installation order
Installers only deploy the client. Completing the connection also requires a config source, policy selection, and system network authorization; following the order below reduces repeated troubleshooting.
-
Confirm the system and architecture
Windows and Linux GUI packages primarily target AMD64; macOS requires choosing between Apple Silicon and Intel; on Android, confirm ARM64, ARM, or universal support first. The wrong architecture usually results in installation or startup failure.
-
Install the client
On desktop systems, use the installer wizard to write the application files. On first launch, macOS requires confirmation of network permissions; Linux AppImage files need execute permission first. Launch Android clients from the app list after installation.
-
Import a subscription or YAML file
Open the configuration page and add a subscription from a URL, or import an existing local configuration file. Clients do not include proxy nodes; prepare the subscription URL and config content yourself.
-
Choose a policy and connect
After updating the configuration, open the proxy or policy page, choose the policy group to use, then enable the system proxy or VPN connection. If more application traffic needs to be captured, evaluate TUN mode according to the platform documentation.
DOWNLOAD FAQ
Common download and installation questions
These questions cover platform selection, processor architecture, configuration preparation, and the differences between archived clients.
Which Clash client should I download for Windows?
For a first installation, start with Clash Plus. If you need more detailed config overrides, rule browsing, and desktop management, compare Clash Verge Rev with FlClash. Clash for Windows is discontinued; its archive is mainly for migrating legacy configs, not for new environments.
How do I choose between Apple Silicon and Intel packages on macOS?
Open About This Mac from the Apple menu. If the Chip field shows an Apple chip such as M1, M2, M3, or M4, choose Apple Silicon or ARM64. If the Processor field shows Intel, choose Intel or x64. A mismatched architecture may prevent the app from launching.
What is the difference between arm64, arm, and universal Android packages?
arm64-v8a is used by most modern 64-bit phones and tablets, while armeabi-v7a is for older 32-bit ARM devices. The universal package supports more architectures and is useful when the device type is unknown, but it is usually larger. Emulators may require an x86_64 build.
What else do I need after downloading a client?
Prepare a Clash- or mihomo-compatible subscription link, or a ready-to-use YAML configuration file. After importing it, update the config, choose a policy group and node, then enable the system proxy, VPN, or TUN as needed. Installing the client alone does not create a working connection.
Why are Clash for Windows and ClashX Meta marked as discontinued?
Both remain available as archived downloads so older devices can read existing configurations and migrations can be checked for policy groups and rules. New environments should use a maintained client, then verify that the subscription URL, rule mode, DNS, and system proxy settings match.
Do regular users need the standalone Mihomo core?
Usually not. Graphical clients such as Clash Plus, FlClash, and Clash Verge Rev manage the core and configuration directory. Standalone Mihomo is better suited to servers, software routers, containers, and command-line deployments, where users manage the config, startup command, permissions, and process supervision themselves.