Clash Plus
A good choice for first-time installations and anyone who wants a full GUI. It supports configuration imports, proxy-group switching, system proxy controls, and common network settings through a straightforward setup.
Choose a build by operating system and processor architecture
Clash downloads and client selection
A central collection of Windows, macOS, Android, iOS, and Linux GUI clients, plus the Mihomo command-line core for servers and routers. Choose your platform first, then download the package matching your processor architecture.
GUI clients
mihomo core
GPL-3.0 ecosystem
five platforms
Platform packages
Choose your current device
Platform tabs switch to the corresponding client list. When sharing a page URL with a platform anchor, the selected platform opens directly.
WINDOWS / X64
Windows clients
Most Intel and AMD computers use the x64 package. For everyday use, choose a GUI client that is still actively updated; if you depend on an old Clash for Windows configuration, use the archived build for migration.
Clash Verge Rev
A mihomo-based desktop client for Windows users who need subscription management, configuration overrides, rule inspection, and TUN settings.
FlClash
Its desktop and mobile interfaces remain broadly consistent, making it a good fit for users who work across Windows, macOS, Linux, or Android.
Clash Nyanpasu
Provides configuration management, proxy-group switching, and connection details for users who prefer a standalone desktop workflow.
Clash for Windows
Retained for legacy configuration migration and compatibility cases. This client no longer receives feature updates; new installations should use one of the actively maintained clients above.
Windows system requirements
| Item | Recommendation | Selection notes |
|---|---|---|
| System | Windows 10 / 11 | Newer system versions generally offer better compatibility with system proxy settings, TUN drivers, and the desktop runtime. |
| Architecture | x64 / AMD64 | Most Intel and AMD desktops and laptops should use x64. |
| Permissions | Standard user; TUN may require administrator approval | Grant permission only when enabling a virtual network adapter or installing network components, as requested by the system. |
MACOS / ARM64 + X64
macOS clients
Choose ARM64 for Apple Silicon and x64 for Intel Macs. Open “About This Mac” to check the chip name, then download the matching DMG package.
Clash Plus
For macOS users who need graphical configuration, subscription updates, and system proxy controls. Separate packages are provided for Apple Silicon and Intel Macs.
Clash Verge Rev
For desktop users who need rule management, configuration overrides, and TUN settings. The two architecture buttons are linked to the corresponding files in the release manifest.
FlClash
A good fit for users who work across multiple operating systems and want a consistent workflow, with support for common configuration imports and proxy-group switching.
ClashX Meta
An archived menu-bar client for users preserving an older workflow or migrating existing configurations. New installations should use an actively maintained client.
macOS system requirements
| Device | Package | How to check |
|---|---|---|
| Apple M-series chip | ARM64 / Apple Silicon | The chip name in “About This Mac” begins with Apple M. |
| Intel Mac | x64 / Intel | The processor shown in “About This Mac” is Intel. |
| First launch | Follow the system security prompt | After installation, grant network configuration permission when prompted by macOS. |
ANDROID / APK
Android clients
Recent Android phones and tablets typically use ARM64. If you cannot confirm the architecture, start with the universal Clash Meta for Android package; consider ARMv7 only for older devices.
Clash Plus
For common ARM64 Android devices, with subscription imports, proxy selection, connection controls, and basic network settings for everyday phone use.
Clash Meta for Android
An Android client based on the Meta core, available in ARM64, ARMv7, and universal packages. Choose the universal version first if you are unsure of the device architecture.
FlClash
For users already running FlClash on desktop who want a similar interface and configuration workflow on mobile.
Surfboard
For Android users familiar with rule configuration and profile management. The universal package is useful when the device CPU architecture is unknown.
Android system requirements
| Architecture | Common device | Recommended choice |
|---|---|---|
| ARM64 | Recent phones and tablets | Usually the best balance of performance and compatibility; choose this first for confirmed 64-bit ARM devices. |
| ARMv7 | Some older 32-bit devices | Use only when the device does not support ARM64. |
| Universal | Devices with an unknown architecture | The file is usually larger, but reduces the risk of choosing the wrong architecture. |
IOS / APP STORE
iOS clients
iPhone and iPad users can install Clash Plus from the App Store. Obtain a subscription URL from your provider, then import the configuration in the app.
Clash Plus
A GUI client for iOS and iPadOS with subscription, proxy-group, and connection-status management. Check the store listing for current app details and system compatibility.
iOS system requirements
| Item | Details |
|---|---|
| Supported devices | iPhone and iPad; check the App Store listing for the exact system version requirement. |
| Installation channel | Open the app listing in the App Store and complete the installation. |
| First configuration | Prepare a valid subscription URL, import it in the app, then choose a proxy group and enable the connection. |
LINUX / AMD64
Linux clients
Linux desktop users can choose Clash Verge Rev or FlClash. Debian, Ubuntu, and derivatives typically use DEB; Fedora and RHEL-based distributions typically use RPM.
Clash Verge Rev
For AMD64 Linux desktops, with GUI configuration plus rule and proxy-group management. Choose DEB or RPM according to your distribution’s package system.
FlClash
Provides AMD64 DEB, RPM, and AppImage packages. DEB and RPM integrate with system package managers, while AppImage suits desktops that prefer a self-contained executable.
Linux system requirements
| Package | Supported distributions | Processor architecture |
|---|---|---|
| DEB | Debian, Ubuntu, and related derivatives | AMD64 |
| RPM | Fedora, RHEL-based distributions, and related systems | x86_64 |
| AppImage | Common desktop distributions with AppImage support | AMD64 |
Command-line core
Mihomo core downloads
Mihomo is suited to servers, software routers, containers, and users who manage configuration files themselves. It does not include a full desktop GUI; prepare a YAML configuration and start it through the command line or a service manager. Most desktop and mobile users should choose a GUI client above.
System
Architecture and format
Use case
Download
Configuration files
Prepare a valid YAML configuration before startup. Check listening ports, DNS, proxy groups, rule providers, and the final matched rules. Relative paths in the configuration are based on the actual working directory.
Run in the background
Server environments typically run the process under a system service manager. Set the working directory, configuration path, and log output, then configure automatic startup and restart-on-failure behavior.
Upgrade procedure
Back up the current configuration and service definition before upgrading the core. After replacing the binary, test the configuration in the foreground before restoring the background service to avoid architecture or permission issues.
Client differences
How to choose a package
Client names can look similar, but their focus differs. First decide whether you need a GUI, then confirm the platform, processor architecture, and configuration compatibility.
First installation
Start with Clash Plus. Its GUI covers subscription imports, proxy-group switching, system proxy controls, and common settings without requiring you to write startup commands.
Windows, macOS, and Linux users can also choose Clash Verge Rev. If you use multiple platforms and want a consistent workflow, consider FlClash.
Processor architecture
In this download context, x64, AMD64, and x86_64 generally refer to common 64-bit Intel or AMD processors. ARM64 is mainly used by Apple Silicon, some Windows on ARM devices, and modern Android devices.
ARMv7 and MIPS are more common on older or specialized embedded devices. Do not infer the architecture from the operating system name alone; read the device architecture information before deployment.
Migrate an old configuration
Standard proxies, proxy groups, and rules can usually be migrated, but implementations of DNS, TUN, scripts, rule providers, and overrides may differ between core versions.
After importing, keep rule mode enabled and check the subscription update time, proxy-group contents, and DNS settings before enabling the system proxy. Do not overwrite a configuration directory that is still in use.
Servers and routers
When there is no desktop environment or you need remote maintenance or automated deployment, the Mihomo core is more direct. It provides core proxy functions, but configuration, process supervision, and log checks are your responsibility.
Home computers and phones prioritize ease of interaction. They generally do not need a command-line core; a GUI client makes everyday proxy switching and subscription updates easier.
After downloading
Installation and first-connection sequence
Downloading is only the first step. Follow a fixed installation, import, and verification sequence to reduce cases where a configuration exists but traffic does not pass through the client.
-
01
Install the client for your platform
Confirm the file extension and processor architecture. Run the installer on Windows, open the DMG on macOS and follow the prompts, use the appropriate package method on Linux, open the APK on Android, or install through the App Store on iOS.
-
02
Import a valid subscription or configuration
Open the client’s configuration, subscription, or Profiles page, paste the subscription URL from your provider, and update it. For a direct YAML import, first verify the file source and indentation.
-
03
Choose rule mode and a proxy group
For first-time use, keep rule mode enabled so connections are routed according to the configuration. Then open the proxy group and choose an available node or automatic test strategy; importing a configuration alone is not enough.
-
04
Enable the proxy and verify the connection
After enabling the system proxy, visit a clearly testable site and check whether the client’s connection page shows a new record. Browser extensions, in-app proxies, and system proxies can override one another, so keep only one entry point active while troubleshooting.
View the complete installation and subscription import guide →
Download FAQs
Packages and architecture
These questions cover client selection, architecture checks, legacy configuration migration, and first-time imports. For broader usage questions, visit the FAQ page.
View all FAQsWhich Clash client should I download first?
Clash Plus is a good starting point for everyday desktop and mobile users. Windows, macOS, and Linux users can also choose Clash Verge Rev or FlClash based on their preferred interface. Mihomo core downloads are generally needed only for servers, routers, or automated deployments.
How do I tell whether my device needs AMD64, ARM64, or ARMv7?
Most computers with Intel or AMD processors use AMD64 or x64; Apple Silicon Macs use ARM64, and recent Android devices are usually ARM64 as well. If an Android architecture is unclear, choose the universal package; servers and routers should read the architecture with system commands first.
What is the difference between a GUI client and the Mihomo core?
GUI clients bring subscription management, proxy switching, system proxy controls, TUN settings, and connection details into one interface for everyday use. Mihomo is a command-line core that requires you to prepare configuration files, startup arguments, and background services, making it better suited to servers, routers, and automated environments.
Why is Clash for Windows marked as discontinued?
Clash for Windows no longer receives feature updates. The archived package is retained mainly for legacy configuration compatibility and migration. New installations should prefer actively maintained options such as Clash Plus, Clash Verge Rev, FlClash, or Clash Nyanpasu.
How do I import a subscription after downloading?
After installing the client, open its configuration or subscription page, paste the subscription URL from your provider, and import or update it. Once the profile appears, choose rule mode, a proxy group, and a node, then enable the system proxy and check the connection log.
Can I migrate an old configuration to a new client?
Standard Clash YAML configurations can usually be imported, but support for scripts, overrides, extended rules, DNS, and experimental features varies by client. After migration, check ports, DNS, rule providers, and proxy groups individually; do not directly overwrite the original client’s configuration directory.