Top pick
Clash Plus
A GUI client for everyday desktop use, with configuration imports, proxy-group switching, system proxy controls, and runtime logs. The Windows x64 installer suits most Intel and AMD PCs.
Setup guide / platform selection
Clash download and installer selection
Confirm the operating system first, then check the CPU architecture and package format. The page groups downloads for Windows, macOS, Android, iOS, and Linux; GUI clients suit everyday use, while the Mihomo core is intended for servers and routers.
PLATFORM.EXE
Choose a Clash client by platform
Switching tabs shows only clients for the selected operating system. The order reflects setup difficulty, GUI completeness, and common use cases; version details load from the download list, and a blank version does not affect installer links.
WIN32 / WIN64
Windows clients
Most Windows 10 and Windows 11 desktop PCs use an x64 installer. Import your configuration inside the client after installation; no separate Mihomo core download is required.
Recommended
Clash Verge Rev
For Windows users who need configuration management, rule inspection, and desktop proxy controls. The current download provides an x64 installer; a native Windows ARM64 package is not listed separately.
Cross-platform
FlClash
A consistent interface across desktop and mobile platforms for users who want a similar workflow on multiple devices. On Windows, choose either the installer or a ZIP archive to extract and run manually.
Desktop client
Clash Nyanpasu
Desktop features include subscription configuration, proxy modes, proxy selection, and logs. Download the x64 installer, follow the setup wizard, then add a subscription URL from the configuration page.
No longer maintained
Clash for Windows
This client is no longer maintained. The archived installer remains available for legacy configurations and existing environments. For new installations, compare the actively maintained clients above first.
Windows system requirements
| Check | Recommended condition | How to check |
|---|---|---|
| System | Windows 10 or Windows 11 | Open “Settings → System → About” to check the version. |
| Processor | x64 | Choose x64 when the system type says “64-bit operating system, x64-based processor.” |
| Installation permissions | The current account can install desktop applications | Approve permissions when prompted during installation. |
| Configuration preparation | A valid subscription URL or local YAML file | Import it from the client’s configuration page after installation. |
DARWIN / DMG
macOS clients
Open “Apple menu → About This Mac” to identify the chip. Choose ARM64 for M1, M2, M3, M4, and other Apple chips; choose x64 for Intel processors.
Top pick
Clash Plus
DMG installers are available for Apple Silicon and Intel Macs. Open the disk image, move the app to Applications, launch it, and import your configuration.
Recommended
Clash Verge Rev
The desktop interface includes configuration, proxy, connection, and log sections. Choose the button matching your Mac chip; download URLs are updated from the version list at runtime.
Cross-platform
FlClash
The interface is similar across Windows and Android, making it easier to switch devices. The two buttons correspond to the Apple Silicon and Intel list keys.
No longer maintained
ClashX Meta
This client is no longer maintained. These downloads support older devices, legacy configuration migration, and existing environments. For a first installation, choose one of the clients above.
macOS system requirements
| Check | Selection method | Installation notes |
|---|---|---|
| Chip | Apple M-series: choose Apple Silicon; Intel processor: choose x64 | Find chip information in “About This Mac.” |
| File format | DMG disk image | Open it and drag the app into Applications. |
| Network permissions | Approve the prompt the first time you enable the proxy | macOS may ask you to authorize a network extension or proxy changes. |
| Existing configuration | Export or keep the original configuration file first | Import the subscription again after switching clients instead of overwriting the old directory. |
ANDROID / APK
Android clients
Recent Android phones typically use ARM64. Choose an ARM package only for a confirmed 32-bit ARM device; Clash Meta for Android also offers a universal package.
Top pick
Clash Plus
For ARM64 Android phones and tablets, with subscription imports, proxy-group switching, and connection controls. Open the APK with the system installer, then add a subscription URL on first launch.
Recommended
Clash Meta for Android
A Clash Meta client for Android with ARM64, 32-bit ARM, and universal packages. Choose the matching package when you know the device architecture; otherwise use the universal package.
Cross-platform
FlClash
For users who want a similar interface on Android and desktop devices. ARM64 covers most newer devices; armeabi-v7a covers some older 32-bit devices.
Rule-based proxy
Surfboard
An Android GUI proxy client for mobile use with compatible configurations and rule groups. A universal package is provided locally; import the configuration through the client after installation.
Android system requirements
| Processor type | Package identifier | Compatible devices |
|---|---|---|
| 64-bit ARM | arm64-v8a / ARM64 | Most Android phones and tablets released in recent years. |
| 32-bit ARM | armeabi-v7a / ARM | Some older devices or systems that support only 32-bit apps. |
| x86_64 | x86_64 | Some emulators, development environments, and specialized devices. |
| Unknown | Universal | Prefer the universal package when the client explicitly provides one. |
IOS / APP STORE
iOS clients
Install Clash Plus on iPhone and iPad through the App Store. Open the app listing to check device compatibility, then import your subscription after installation.
App Store · Top pick
Clash Plus
A GUI client for iPhone and iPad. After installation, add a subscription URL on the configuration page, update it, choose a proxy group, and follow the system prompts to establish the network connection.
Official website: clashplus.io
iOS system requirements
| Check | Where to check | Details |
|---|---|---|
| Device compatibility | App Store app listing | Check that the current system and device meet the app requirements before installing. |
| Installation method | App Store | Tap Get and complete the installation through the system workflow. |
| Network connection | When the client is enabled for the first time | Follow the system prompt to approve adding the network configuration. |
| Subscription configuration | Client configuration or subscription page | Paste the subscription URL, update it, and choose an available proxy group. |
LINUX / AMD64
Linux clients
Desktop Linux users can choose Clash Verge Rev or FlClash. Debian, Ubuntu, and derivatives typically use DEB; Fedora, RHEL, and related distributions typically use RPM.
Recommended
Clash Verge Rev
AMD64 DEB and RPM installers are available for Linux desktops. After installation, launch the client from the app menu, import a subscription, and configure the system proxy.
Cross-platform
FlClash
Linux AMD64 supports DEB, RPM, and AppImage. DEB and RPM work well with system package managers; AppImage suits desktop users who want to run a standalone application file.
Linux system requirements
| Distribution type | Recommended format | How to use |
|---|---|---|
| Debian / Ubuntu family | AMD64 DEB | Install through the system software installer or package manager. |
| Fedora / RHEL family | x86_64 RPM | Install with the distribution’s software management tool. |
| Other desktop distributions | AppImage | Grant execute permission, run the file, and configure the system proxy for your desktop environment. |
| Server or router | Mihomo core | Go to the core section below and choose the command-line program for your architecture. |
CORE / MIHOMO
Mihomo core downloads
Mihomo is a proxy core for configuration-file and command-line environments. Choose a build by operating system and CPU architecture for servers, software routers, container hosts, and automated deployments; desktop and mobile users should prefer the GUI clients above.
| Operating system | Processor architecture | File format | Use case | Download |
|---|---|---|---|---|
| Windows | AMD64 | ZIP | For common Intel and AMD 64-bit Windows hosts. | Download AMD64 |
| Windows | ARM64 | ZIP | For devices explicitly running ARM64 Windows. | Download ARM64 |
| macOS | Intel AMD64 | GZ | For command-line environments on Intel Macs. | Download Intel |
| macOS | Apple Silicon ARM64 | GZ | For command-line environments on Apple M-series chips. | Download Apple Silicon |
| Linux | AMD64 | DEB | For Debian, Ubuntu, and derivative systems. | Download DEB |
| Linux | AMD64 | GZ | For general 64-bit Linux server deployments. | Download AMD64 |
| Linux | ARM64 | GZ | For 64-bit ARM servers, development boards, and routers. | Download ARM64 |
| Linux | ARMv7 | GZ | For some embedded devices using 32-bit ARMv7. | Download ARMv7 |
| Linux | MIPS Softfloat | GZ | For routers explicitly identified as using MIPS soft-float architecture. | Download MIPS |
Target: servers / routers / automation
Configuration entry: config.yaml
On Linux, run uname -m in a terminal. Common results include x86_64 for AMD64, aarch64 for ARM64, and armv7l for ARMv7. For routers, also check the firmware page or device documentation to confirm whether MIPS uses soft-float.
After extracting the core, verify the executable and configuration paths separately. Start it in the foreground and read the logs first, checking YAML syntax, listening ports, and DNS initialization; once stable, hand the process to the system service manager.
README.TXT
Choosing an installer and launching for the first time
Downloading is only the first step. The correct system architecture, configuration import order, and proxy activation method directly affect whether the client can establish a connection.
Confirm the system and architecture
On desktop computers, read the system information first; on mobile devices, confirm the processor type. Do not choose between x64 and ARM64 packages based only on similar filenames. Apple M-series Macs use ARM64, common Intel and AMD Windows PCs use x64, and most recent Android phones use arm64-v8a.
Complete the system installation
Run the EXE installer on Windows, open the DMG and move the app to Applications on macOS, open the APK with the Android system installer, and handle DEB, RPM, or AppImage according to the Linux distribution. When permissions are requested, verify the app name and download source before continuing through the system workflow.
Import a subscription or YAML configuration
Open the client’s configuration, subscription, or Profiles page, paste the subscription URL from your provider, and update it. For a local YAML file, use the file import option. After importing, confirm the configuration is valid, then choose a node in the proxy group.
Enable the proxy and verify the connection
For everyday desktop use, start by enabling the system proxy; in rule mode, the configuration determines whether traffic connects directly or through the proxy. If a specific app ignores the system proxy, consider TUN mode if supported. During verification, check both the client’s connection page and logs rather than judging the configuration only by whether a webpage opens.
HELP / DOWNLOAD
Clash download common questions
These questions cover installer selection, processor architecture, configuration imports, and connection checks. Complete the relevant steps first, then use the logs page to locate specific errors.
Which Clash installer should I choose for Windows?
Most Windows 10 and Windows 11 PCs should start with the Clash Plus x64 installer. For a different interface or configuration workflow, compare Clash Verge Rev, FlClash, and Clash Nyanpasu.
If System Information shows an x64-based processor, use a file labeled x64 or AMD64. Clash for Windows is no longer maintained; its archive is better suited to restoring an old configuration than setting up a new environment.
How do I tell Apple Silicon and Intel macOS installers apart?
Open “About This Mac” from the Apple menu to check the chip. Choose Apple Silicon or ARM64 for an Apple M-series chip, and x64 or Intel for an Intel Mac.
When migrating from an older Intel Mac to an Apple Silicon Mac, download the client for the new architecture and restore the configuration through its subscription URL instead of copying the old application files directly.
Should I download arm64, arm, or universal for Android?
Most recent Android phones use arm64-v8a. Choose armeabi-v7a for older 32-bit devices; if you cannot confirm the architecture, choose the universal package for Clash Meta for Android.
x86_64 packages are mainly for some emulators and specialized devices. Before installing, use a device information tool or the manufacturer’s specifications to check the CPU ABI and avoid downloading a package that does not match the system architecture.
What is the difference between a GUI client and the Mihomo core?
GUI clients handle subscription imports, proxy selection, logs, and the system proxy switch for desktops and mobile devices. The Mihomo core runs mainly through configuration files and the command line, making it better suited to servers, routers, and automation.
Most users do not need to download an additional core for a GUI client. Open the Mihomo section only when you plan to manage a process from the command line, write a service configuration, or deploy it on a router, then choose the build for your architecture.
How do I import a Clash proxy subscription after downloading?
After installing and launching the client, open its configuration or subscription page, paste the subscription URL from your provider, download or update it, choose a proxy node, and enable the system proxy.
If no nodes appear after updating, check that the subscription URL is complete, the configuration has no errors, and the client log does not show a failed request. The provider maintains the subscription content; the client only reads and runs the configuration.
What should I do if the internet still does not work after enabling the proxy?
Check that the configuration updated successfully, the proxy group has a working node selected, the system proxy is enabled, and your browser or app is not using an old connection. Then review the client log for DNS errors, port conflicts, or connection timeouts.
Before switching clients, disable the old client’s system proxy and background process to prevent both programs from using the same port. If only a few apps cannot connect, check whether they use their own proxy settings or ignore the system proxy.