Top pick
Clash Plus
For Windows users who want centralized management of subscriptions, rule modes and the system proxy. The package targets common 64-bit desktop systems.
Platform packages
Clash Download
Client and
Core Packages
Choose a package by operating system, processor architecture and intended use. Use graphical clients on desktop and mobile devices; servers, routers and automated environments can use the Mihomo core directly.
Five operating systems
mihomo core
Graphical clients
Client packages
Choose a client by platform
The same configuration can usually move between mihomo-based clients, but interfaces, system integration and maintenance status vary. For a first installation, start with the recommended option for your platform and adjust based on how you manage configurations.
Windows clients
For 64-bit Windows 10 and Windows 11 desktop environments. After installation, import a subscription or local configuration and enable the system proxy. On managed devices where installers are restricted, obtain device-management approval before choosing a portable format.
Recommended
Clash Verge Rev
A desktop client built on the mihomo core for viewing proxy groups, rule matches, connection logs and configuration files. This is the Windows x64 installer.
FlClash
A cross-platform graphical client with a largely consistent interface across desktop and mobile. On Windows, choose either the installer or the archive.
Clash Nyanpasu
Offers subscription management, proxy groups, system proxy controls and configuration editing for users familiar with the Clash configuration format who want an alternative desktop interface.
Discontinued
Clash for Windows
An archived installer is retained for restoring older devices, migrating existing configurations and supporting legacy environments. For new installations, choose a maintained client.
Windows system requirements
| Item | Recommendation | Why it matters |
|---|---|---|
| Operating system | Windows 10 or Windows 11 | Provides broader compatibility with newer system proxy features, network components and desktop runtimes. |
| Processor | x86-64 / AMD64 | The Windows graphical client packages on this page target common 64-bit computers. |
| Permissions | Permission to install apps and change network settings | System approval may be required to install drivers, modify the system proxy or enable TUN. |
macOS clients
Before downloading, open About This Mac or System Information to identify the chip. Choose ARM64 for Apple M-series chips and x64 for Intel processors. On first launch, macOS may ask you to approve network extensions, proxy settings or app permissions.
Top pick
Clash Plus
Disk images are available for Apple Silicon and Intel. Select the package matching your Mac's chip to avoid relying on translation for an incompatible build.
Recommended
Clash Verge Rev
For macOS users who need mihomo rule pages, proxy-group switching and subscription management. The list keeps separate download keys for each chip type.
FlClash
A cross-platform client for users who want similar workflows across macOS, Android and other devices. Choose the entry matching your chip.
Discontinued
ClashX Meta
Retained for existing ClashX Meta workflows and legacy configurations. On a new Mac, compare currently maintained macOS clients first.
macOS system requirements
| Device type | Package | How to confirm |
|---|---|---|
| Apple M-series chip | ARM64 / Apple Silicon | The Chip field in About This Mac shows Apple M1, M2, M3, M4 or a later model. |
| Intel Mac | x64 / Intel | The Processor field in About This Mac shows Intel. |
| System authorization | Allow network configuration | When enabling the system proxy or a network extension, follow the macOS prompts to grant permission. |
Android clients
Most Android phones and tablets released in recent years use ARM64. If you cannot confirm the architecture, Clash Meta for Android offers a universal package; older 32-bit ARM devices should use the armeabi-v7a build.
Top pick
Clash Plus
For common ARM64 Android devices, with support for importing subscriptions, switching proxy groups and routing selected connections through the system VPN interface.
Recommended
Clash Meta for Android
An Android client based on the Meta family of cores, offering ARM64, 32-bit ARM and universal packages. Choose the universal build when the architecture is unknown.
FlClash
For users who want a similar workflow on mobile and desktop. Offers Android builds for ARM64, 32-bit ARM and x86_64.
Surfboard
An Android proxy client that imports compatible configurations and supports rules and proxy groups. This page provides a broadly compatible universal package.
Choose an Android architecture
| Architecture | Common devices | Recommendation |
|---|---|---|
| arm64-v8a | Recent mainstream phones and tablets | If the architecture is unknown but the device is recent, try ARM64 first. |
| armeabi-v7a | Older 32-bit ARM devices | Choose this only when the device does not support 64-bit apps. |
| x86_64 | Some emulators and specialized devices | Physical phones typically do not use this architecture. |
| Universal | Unknown architecture | The file is usually larger, but it reduces the need to identify the architecture manually. |
iOS client
Install Clash Plus through the App Store. After installation, import a subscription or configuration file in the app, allow it to add a VPN configuration, then choose the rule mode and proxy group you need.
Top pick
Clash Plus
A proxy tool for iPhone and iPad with subscription imports, proxy-group selection and rule-based routing. App details and installation are provided through the App Store listing.
Official site: clashplus.io
iOS requirements
| Item | Details |
|---|---|
| Supported devices | iPhones and iPads that can access the app listing in the App Store. |
| Network permission | When connecting for the first time, follow the system prompt to allow the VPN configuration to be added. |
| Configuration source | Prepare a working subscription URL or compatible configuration file and import it in the app. |
Linux clients
The graphical client suits standard desktop distributions. Debian, Ubuntu and derivatives generally use DEB; Fedora, RHEL, openSUSE and other RPM-based distributions use RPM. For headless servers, see the Mihomo core section below.
Recommended
Clash Verge Rev
For subscription management, proxy-group switching and rule inspection on Linux desktops. The current packages target AMD64; choose the format used by your distribution.
FlClash
A cross-platform Linux graphical client. Alongside DEB, it offers RPM and AppImage packages for different distributions and portable use.
Choose a Linux package
| Format | Common distributions | Details |
|---|---|---|
| DEB | Debian、Ubuntu、Linux Mint | Install with dpkg or the distribution's package manager. |
| RPM | Fedora、RHEL、Rocky Linux、openSUSE | Manage with tools such as rpm, dnf or zypper. |
| AppImage | Most common desktop distributions | Grant execute permission and run it; suitable when you do not want to add files to the system package database. |
| Architecture | AMD64 / x86_64 | The graphical packages in this section target common 64-bit Intel or AMD computers. |
Mihomo core
Mihomo core downloads
Mihomo handles protocol connections, DNS processing, rule matching and proxy-group scheduling, but does not provide a complete desktop management interface. This section is for servers, software routers, container orchestration and command-line users.
| System | Architecture and format | Download |
|---|---|---|
| Windows | AMD64 · ZIP | Download AMD64 |
| Windows | ARM64 · ZIP | Download ARM64 |
| macOS | Intel AMD64 · GZ | Download Intel |
| macOS | Apple Silicon ARM64 · GZ | Download Apple Silicon |
| Linux | AMD64 · DEB | Download DEB |
| Linux | AMD64 · GZ | Download AMD64 |
| Linux | ARM64 · GZ | Download ARM64 |
| Linux | ARMv7 · GZ | Download ARMv7 |
| Linux | MIPS softfloat · GZ | Download MIPS |
Router firmware may impose additional requirements for libc, instruction sets and floating-point support. A device brand alone does not identify the architecture; check the processor type reported by system commands or the firmware information page.
Before installation
Selection order before installation
Whether a package starts depends mainly on the system type, processor architecture and package format. Use the sequence below to avoid downloading the wrong file and having to start over.
Identify the platform first
Desktop and mobile systems use different installation methods. Windows uses EXE or ZIP, macOS uses DMG, Android uses app packages, and Linux uses DEB, RPM or AppImage depending on the distribution.
Then check the architecture
x64, AMD64 and x86_64 generally refer to the same 64-bit desktop architecture. ARM64 is common on Apple Silicon, mobile devices and some routers. An architecture mismatch may prevent the installer from opening.
Finally check maintenance status
For a new installation, prefer maintained clients. Archived clients are intended for restoring or migrating older configurations, not as the default for a new long-term setup. Back up subscription URLs, overrides and local rules before migrating.
Configuration after installation
Installing the client does not mean that rules are active. Import usable content from the subscription or configuration page, wait for proxy groups and rules to load, then choose rule, global or direct mode. Once the system proxy is enabled, apps that follow it enter the rule-matching flow. For additional connection types, evaluate TUN mode based on your operating system's support.
After the first configuration import, check that proxy groups contain selectable options, then open the connection or log page to confirm requests match the expected rules. If a subscription update fails, check the URL, system time, network permissions and client logs in that order instead of repeatedly reinstalling the client.
Download FAQ
Common download and installation questions
These questions cover package selection, maintenance status, processor architecture and next-step configuration. For connection rules and subscription issues, see the complete FAQ.
Which Clash client should I download first on Windows?
For a first installation, start with Clash Plus. If you need more complete mihomo rule management, proxy-group switching and a desktop configuration interface, choose Clash Verge Rev. Both suit common 64-bit Windows 10 and Windows 11 systems.
Clash for Windows is retained here as an archive for restoring legacy environments and migrating configurations. For a new device intended for long-term use, choose a maintained client instead.
How do I choose between Apple Silicon and Intel packages on macOS?
Open the Apple menu in the top-left corner and select About This Mac. If the Chip field shows Apple M1, M2, M3, M4 or a later model, choose Apple Silicon or ARM64. If the Processor field shows Intel, choose Intel or x64.
Matching the architecture reduces reliance on translation layers and helps native system network components run as intended. On organization-managed devices, follow the device-management policy to authorize app and network permissions.
Which Android file should I choose if I am unsure about the CPU architecture?
Most recent Android phones use ARM64, so start with arm64-v8a. Older 32-bit devices may need armeabi-v7a, while x86_64 is more common in emulators. Clash Meta for Android provides a universal package for unknown architectures.
Check the architecture in the device's system information, a processor information tool or the manufacturer's specifications. The Android version, vendor security policy and permission for the installation source can also affect installation.
Why are Clash for Windows and ClashX Meta marked as discontinued?
Discontinued means the client no longer receives feature and compatibility updates at the current pace. The archived downloads remain available so existing users can restore legacy environments, read historical configurations or migrate; they are not recommended for new installations.
Before migrating, record the subscription URL, proxy-group preferences, overrides, DNS settings and system proxy state, then restore them item by item in the new client. Support for private fields may differ, so keep a copy of the original configuration.
What is the difference between the Mihomo core and a graphical client?
Mihomo is the core program that handles protocol connections, DNS queries, rule matching and traffic forwarding. Graphical clients add subscription management, proxy-group selection, system-tray controls, configuration editing and system proxy controls on top of the core.
A graphical client is the more direct choice for everyday desktop and mobile use. Download the core directly for servers, routers or automated deployments that require you to manage configuration files, runtime parameters and the service lifecycle yourself.
How do I import a Clash configuration after downloading?
After installing and opening the client, go to the Subscription, Configuration or Profiles page. Paste the subscription URL from your provider or import a local YAML configuration. After updating, confirm that proxy groups appear, then choose the appropriate node or policy.
Enable the system proxy and use the connection log or rules page to confirm the traffic path. If the configuration will not load, first inspect the fields, indentation and references indicated by the error, then decide whether to fetch the subscription again. For the full workflow, see the Clash Verge Rev guide.
For further help with subscription updates, system proxy settings, DNS, rule order or connection problems, open the central issue library.
View all frequently asked questions