Recommended
Clash Plus
A Windows x64 GUI client for a standard desktop installation.
x64
EXE
Installer
Cross-platform packages and architecture choices
Clash Downloads and System Versions
Choose GUI clients such as Clash Plus, Clash Verge Rev, or FlClash for your operating system. For servers and routers, find the standalone Mihomo core farther down the page.
Five platforms
GUI clients
Mihomo core
Architecture details
Platform selector
Choose a client by platform
The same client may use different file formats on different systems. After switching platforms, choose the appropriate download based on the device processor and system version.
WINDOWS · X64
View system requirements
Windows client packages
Most Windows 10 and Windows 11 PCs should use the x64 installer. Windows ARM64 files for Clash Verge Rev are not listed separately here; on ARM devices, first check Clash Plus compatibility.
Desktop client
Clash Verge Rev
A desktop client built on the mihomo core, with pages for configurations, rules, system proxy settings, and logs.
x64
SETUP.EXE
Windows installer
Cross-platform
FlClash
The desktop and mobile interfaces are closely aligned, with both installer and portable archive options.
AMD64
EXE / ZIP
Installer or portable package
Alternative client
Clash Nyanpasu
A Windows GUI client with configuration management for x64 devices.
x64
SETUP.EXE
Desktop installer
No longer maintained
Clash for Windows
An archived client for users who need to reproduce an existing setup. For new installations, choose a currently maintained client instead.
x64
EXE
Archived installer
Windows system requirements
| Check | Recommended choice | Before installation |
|---|---|---|
| System version | Windows 10 / 11 | Older systems may lack the runtime environment or WebView components required by the client. |
| Processor | x86_64 / AMD64 | Open “Settings → System → About” to view the system type. |
| Installation permissions | Apps installable by the current user | Installing as a service or changing system-wide settings may require administrator confirmation. |
MACOS · ARM64 / X64
View system requirements
macOS client packages
For Apple M-series chips, choose Apple Silicon or ARM64; for Intel processors, choose x64. After downloading, open the DMG and drag the app into the “Applications” folder.
Recommended
Clash Plus
Separate packages are provided for Apple Silicon and Intel. Check your Mac’s chip before downloading.
ARM64 / X64
DMG
Desktop client
Desktop client
Clash Verge Rev
Desktop features include configuration management, rule modes, system proxy settings, and connection logs.
ARM64 / X64
DMG
macOS disk image
Cross-platform
FlClash
Its interface is similar to the Windows and Android versions, making familiar workflows easier to use across devices.
ARM64 / X64
DMG
Desktop disk image
No longer maintained
ClashX Meta
An archived macOS menu bar client for maintaining existing configurations and familiar menu bar workflows.
ARM64 / X64
DMG
Archived disk image
macOS system requirements
| Check | Matching package | How to check |
|---|---|---|
| Apple M-series chip | ARM64 / Apple Silicon | Open “About This Mac” and check whether the chip name shows an Apple M-series processor. |
| Intel processor | x64 / Intel | The processor name in “About This Mac” includes Intel. |
| First launch | Applications folder | After opening the DMG, drag the app into “Applications,” then launch it from that folder. |
ANDROID · ARM64 / ARM
View architecture details
Android client packages
Recent phones and tablets usually use ARM64. Choose ARM for older 32-bit devices. If you cannot identify the architecture, use the Universal package for Clash Meta for Android.
Recommended
Clash Plus
A client package for 64-bit ARM Android devices.
ARM64-V8A
APK
Android package
Complete architecture coverage
Clash Meta for Android
Provides ARM64, 32-bit ARM, and Universal packages so you can choose by device processor.
ARM64 / ARM / UNIVERSAL
APK
Mobile client
Cross-platform
FlClash
Provides ARM64, 32-bit ARM, and x86_64 packages for phones, tablets, and some Android desktop environments.
ARM64 / ARM / X86_64
APK
Choose by processor
Universal package
Surfboard
An Android proxy client using a Universal package, suitable for devices that need compatibility across multiple processor architectures.
UNIVERSAL
APK
Local installation file
Android architecture and installation requirements
| Architecture | Common devices | Recommendation |
|---|---|---|
| arm64-v8a | Recent phones and tablets | The standard choice; download this architecture first in most cases. |
| armeabi-v7a | Older 32-bit ARM devices | Use only when the device does not support 64-bit apps. |
| x86_64 | Some emulators and specialized devices | Typical ARM phones should not use this package. |
| universal | Devices with an unknown architecture | Broad compatibility, but the installation file is usually larger. |
IOS · APP STORE
View installation instructions
iPhone and iPad client
Clash Plus provides an iOS client available through the App Store. After installation, add a configuration through the client interface and grant network access when prompted by iOS.
Recommended · App Store
Clash Plus
A proxy tool for iPhone and iPad, installed through the App Store and updated through the store.
iOS installation and usage requirements
| Check | Details | Next step |
|---|---|---|
| Device type | iPhone or iPad | Open the app’s App Store listing and complete the installation. |
| Configuration source | A subscription URL or another configuration method supported by the client | After importing, update the configuration and confirm that the proxy groups appear correctly. |
| System permissions | Permission to configure network connections | Confirm the prompt when connecting for the first time. |
LINUX · AMD64
View format details
Linux GUI clients
Debian and Ubuntu-based systems generally use DEB, while Fedora and RHEL-based systems generally use RPM. The GUI packages listed here primarily target AMD64 desktop environments.
Recommended
Clash Verge Rev
A Linux desktop GUI with DEB and RPM options for different distribution package systems.
AMD64
DEB / RPM
Desktop package
Multiple formats
FlClash
Provides DEB, RPM, and AppImage packages for different distributions and package management preferences.
AMD64
DEB / RPM / APPIMAGE
Desktop client
Linux package selection
| File format | Common distributions | Installation method |
|---|---|---|
| .deb | Debian、Ubuntu、Linux Mint | Use the system software installer or apt / dpkg. |
| .rpm | Fedora、RHEL、Rocky Linux | Use the system software installer or dnf / rpm. |
| .AppImage | Various desktop distributions | Grant execute permission, then run it. It usually does not write to the system package database. |
Core packages
Standalone Mihomo core
The standalone core is mainly for servers, routers, containers, and environments where you maintain configuration files yourself. Most desktop and mobile users should choose a GUI client above.
| System | Architecture | Format | Download |
|---|---|---|---|
| Windows | AMD64 | ZIP | Download file |
| Windows | ARM64 | ZIP | Download file |
| macOS | Intel AMD64 | GZ | Download file |
| macOS | Apple Silicon ARM64 | GZ | Download file |
| Linux | AMD64 | DEB | Download file |
| Linux | AMD64 | GZ | Download file |
| Linux | ARM64 | GZ | Download file |
| Linux | ARMv7 | GZ | Download file |
| Linux | MIPS softfloat | GZ | Download file |
Router firmware may impose additional requirements for architecture, floating-point support, and the C library. If the device is marked MIPS, also confirm endianness and floating-point type; do not choose solely by processor family.
Package reference
How to choose a package format and architecture
The same system name does not mean packages are interchangeable. The processor architecture determines whether the program can run, while the file format determines how the system installs and manages the client.
Check the system first, not the device brand
Windows PCs use EXE or ZIP, macOS uses DMG, and Android uses APK. On Linux, also confirm the distribution’s package system. Device appearance, brand, and purchase year are only clues; rely on the operating system and processor shown in system information.
Then check x64, ARM64, or ARM
x64 is also written as x86_64 or AMD64 and is mainly used by Intel and AMD desktop processors. ARM64 is common on Apple M-series chips, newer Android devices, and some Windows ARM PCs. ARMv7 or 32-bit ARM is found mainly on older mobile and embedded devices.
Finally choose an installer or standalone file
Installers integrate with the system’s application management workflow and suit everyday desktop use. ZIP, GZ, and AppImage files are better for manual management, leaving you to choose the storage directory, permissions, and launch method. The standalone Mihomo core also requires separate configuration and service management.
EXE
Windows installer
DMG
macOS disk image
APK
Android app package
DEB
Debian package
RPM
RPM package
GZ / ZIP
Compressed standalone program file
Download FAQ
Common download and installation questions
These questions cover package formats, processor architectures, and first-time configuration. For more complete connection and log troubleshooting, continue to the FAQ page.
Should Windows users download an installer or an archive?
Most users should choose the installer ending in setup.exe. It creates the application directory, uninstall entry, and shortcuts through the standard process, making later management easier. A ZIP archive suits users who want to choose the program directory, keep a portable file structure, or avoid an installation wizard. The core features depend on the client itself, not on whether an installer was used.
How do I choose between Apple Silicon and Intel on macOS?
Open the system menu in the upper-left corner of the screen and select “About This Mac.” If the chip name shows Apple M1, M2, M3, or a later M-series processor, choose Apple Silicon or ARM64. If the processor name includes Intel, choose Intel or x64. Using the wrong architecture may prevent the app from opening or require an additional compatibility layer.
What is the difference between ARM64, ARM, and Universal Android packages?
ARM64 is for modern 64-bit ARM devices and is the common choice for recent phones and tablets. ARM or armeabi-v7a targets older 32-bit devices. Universal covers more architectures in one installer and is useful when the processor type is unknown, but the file is usually larger. x86_64 is mainly for some emulators and specialized devices.
Should Linux users choose DEB, RPM, or AppImage?
Ubuntu, Debian, Linux Mint, and similar systems generally use DEB; Fedora, RHEL, Rocky Linux, and similar systems generally use RPM. AppImage is a relatively self-contained executable for users who prefer manual management without registering the app in the system package database. You usually need to grant execute permission before running it.
Do regular users need to download the Mihomo core separately?
Usually not. GUI clients such as Clash Plus, Clash Verge Rev, and FlClash provide configuration import, policy switching, system proxy controls, and log viewing for desktop and mobile use. The standalone Mihomo core is mainly for servers, routers, containers, automation services, or environments where you directly maintain YAML configurations and startup parameters.
What should I check if no proxies appear after importing a subscription?
On the configuration page, first confirm that the subscription updated successfully and that the newly imported configuration is enabled. If the configuration is empty or cannot be parsed, check the logs for format and network errors. Once it loads correctly, verify the proxy mode, policy group selection, and system proxy status. Avoid repeatedly switching the system proxy before the subscription has loaded successfully, as this can obscure the source of the problem.
Configuration order after installation
Import and update the subscription first, then choose the rule mode and policy group. Finally enable the system proxy and confirm the connection status in the logs.