Top pick
Windows
Clash Plus
A clear interface covers subscriptions, proxy modes, rules, connections, and logs, making it suitable for first-time setup and long-term desktop use.
CLIENT PACKAGES
Choose a Clash Client by Platform
Choose a package by operating system, processor architecture, and usage. Prefer graphical clients for desktops and mobile devices; choose the Mihomo core below for servers, routers, and automated environments.
- Packages for every platform
- Graphical clients first
- Match your architecture
PLATFORM SELECTOR
Choose a Clash package by platform
Platform tabs switch to the matching client list. Each card shows the primary package first, followed by alternatives with different architectures or packaging formats. Version labels come from the release manifest; if the manifest is temporarily unavailable, download buttons retain the current file links.
WINDOWS
Windows clients
For everyday desktop proxying, subscription updates, rule switching, and TUN configuration. The current manifest provides an x64 installer; on Windows on ARM, confirm x64 app compatibility before running it.
Desktop client
Clash Verge Rev
A Mihomo graphical frontend for desktop environments, suited to users who need rule editing, configuration management, system proxy controls, and TUN access.
Multi-platform
FlClash
The same interface covers desktop and Android, making it suitable for users who want a similar workflow across multiple devices. Windows offers installer and portable archive versions.
Alternative interface
Clash Nyanpasu
Provides a separate interface for configuration and policy management as a desktop alternative to Clash Verge Rev and FlClash.
Discontinued
Archived
Clash for Windows
A classic Windows graphical client retained for migrating legacy configurations and restoring older environments. For new installations, choose a maintained client instead.
Windows system requirements
| Check | Recommendation | Before installation |
|---|---|---|
| System version | Windows 10 or Windows 11 | Keep Windows updated and ensure WebView, networking components, and certificate services work normally. |
| Processor architecture | x64 | Windows clients on this page mainly use x64 packages; no separate native Verge ARM64 package is listed. |
| Installation permissions | Allow installation for the current user | TUN drivers, service registration, or firewall changes may require administrator approval. |
| Configuration migration | Back up the configuration directory first | When migrating from an older client, re-import the subscription first, then migrate custom rules as needed. |
MACOS
macOS clients
Check the chip type in About This Mac. Choose Apple Silicon or ARM64 for M-series Macs, and Intel or x64 for Intel Macs. When opening an app downloaded from the internet for the first time, follow the system prompts to approve it.
Top pick
macOS
Clash Plus
Provides packages for M-series and Intel processors. Suitable for macOS users who want unified management of subscriptions, proxy modes, and system network routing.
Desktop client
Clash Verge Rev
Provides access to policy groups, connection lists, rules, and core settings. The two architecture entries in the current manifest use the same DMG file; install the file supplied by the release manifest.
Multi-platform
FlClash
Suitable for users who work across macOS, Windows, and Android. The current macOS architecture entries point to the same DMG file in the release manifest.
Discontinued
Archived
ClashX Meta
Retained for macOS environments that still rely on the original menu-bar workflow and legacy configurations. On new devices, prefer a maintained graphical client.
macOS system requirements
| Device type | Version to choose | How to check |
|---|---|---|
| M1, M2, M3, or M4 Mac | Apple Silicon / ARM64 | Open the Apple menu and choose About This Mac; the Chip field shows the Apple silicon model. |
| Intel Mac | Intel / x64 | The Processor field in About This Mac shows an Intel model. |
| First launch | Complete the security approval | If macOS blocks the app, review its entry under Privacy & Security settings. |
| Network permissions | Allow proxy or VPN configuration | When enabling the system proxy or TUN, macOS may ask for the current user’s credentials. |
ANDROID
Android clients
Recent phones and tablets usually use ARM64. Older 32-bit devices can use the ARM package; when the architecture is unknown, use the universal package. After installation, allow the client to establish a system VPN connection and adjust background activity settings as needed.
Top pick
ARM64
Clash Plus
For common 64-bit Android phones and tablets, with subscription, policy group, runtime log, and system VPN controls.
Mihomo
Clash Meta for Android
An Android-focused Meta client offering ARM64, ARM, and universal packages. If you cannot identify the device ABI, the universal package is the simplest choice, though it is usually larger.
Multiple architectures
FlClash
The mobile interface follows a similar information structure to the desktop version. Use ARM64 on mainstream devices and armeabi-v7a on older 32-bit ARM devices.
Universal package
Surfboard
A rule-based proxy client for Android and an alternative for different configuration workflows. Install it through the system installer, then import a compatible configuration.
Android system requirements
| Package identifier | Supported devices | Recommendation |
|---|---|---|
| arm64-v8a | Most recent Android phones and tablets | If the device is newer but uncertain, start with ARM64. |
| armeabi-v7a | Older 32-bit ARM devices | Choose this only when ARM64 will not install and the device is confirmed to be 32-bit. |
| x86_64 | Some emulators and special-purpose devices | Physical phones usually do not use this architecture. |
| universal | Devices with an unknown architecture | It supports a wider range of architectures, but the installation file is usually larger. |
IOS
iPhone and iPad clients
Clash Plus is used on iOS. Get and update it through the App Store; after installation, import a subscription and allow the app to add a VPN configuration. Product information and access options are also available on the official website.
Top pick
App Store
Clash Plus
A client for iPhone and iPad with subscription import, policy switching, rule modes, and system VPN connection management. Updates are handled through the App Store.
Official website: clashplus.io
iOS and iPadOS requirements
| Check | Requirement | Details |
|---|---|---|
| Device | iPhone or iPad | Get the client through the App Store page on the device. |
| Network permissions | Allow VPN configuration | The system displays a VPN configuration approval prompt when the first connection is established. |
| Subscription import | Prepare a working subscription URL | The client does not create subscription content; update the policy list after importing it. |
| Background connection | Keep the VPN active | If the connection drops after switching networks, return to the client and check the current policy. |
LINUX
Linux graphical clients
Linux desktop users can choose Clash Verge Rev or FlClash. Debian, Ubuntu, and derivatives usually use DEB; Fedora, RHEL, openSUSE, and similar systems should use RPM according to their package management system.
Recommended
Linux desktop
Clash Verge Rev
A Mihomo graphical frontend for Linux desktops. Provides DEB and RPM packages; the current manifest targets AMD64 desktop systems.
Multiple formats
FlClash
Provides DEB, RPM, and AppImage packages. DEB and RPM integrate with system package management; AppImage suits desktop environments where program files should remain self-contained.
Linux system requirements
| Distribution environment | Package format | Details |
|---|---|---|
| Debian, Ubuntu, and derivatives | DEB | Install with the system package manager, which can handle desktop entries and dependencies. |
| Fedora, RHEL, openSUSE, and similar systems | RPM | Choose the RPM file matching the package management system of the current distribution. |
| General desktop environments | AppImage | Grant execute permission before launching; the client still manages configuration and data directories. |
| Processor architecture | AMD64 / x86_64 | This section does not provide an additional native Linux ARM64 graphical package. |
MIHOMO CORE
Mihomo core downloads
Mihomo is a commonly used command-line core in the Clash Meta ecosystem. This section targets servers, software routers, embedded devices, containers, and users who maintain configuration files themselves. Regular Windows, macOS, Android, iOS, and Linux desktop users should prefer the graphical clients above.
core mihomo
config config.yaml
mode rule
control external-controller
Choose by system and processor architecture
The core has no complete desktop settings interface, so you must prepare configuration files, runtime parameters, service management, and log collection yourself. Routers also require checks for firmware architecture, storage, and startup scripts. A mismatched architecture usually prevents the program from running, so verify it through system information or commands before downloading.
| System | Architecture and format | Suitable environment | Download |
|---|---|---|---|
| Windows | AMD64 ZIP | 64-bit Windows servers and command-line environments | Download AMD64 |
| Windows | ARM64 ZIP | Windows on ARM command-line environments | Download ARM64 |
| macOS | Intel AMD64 GZ | Intel Macs and automated runtime environments | Download Intel |
| macOS | Apple Silicon ARM64 GZ | Command-line environments on M-series Macs | Download Apple Silicon |
| Linux | AMD64 DEB | Debian, Ubuntu, and compatible server systems | Download DEB |
| Linux | AMD64 GZ | Generic x86_64 Linux and container environments | Download AMD64 |
| Linux | ARM64 GZ | 64-bit ARM servers, development boards, and routers | Download ARM64 |
| Linux | ARMv7 GZ | 32-bit ARMv7 embedded systems | Download ARMv7 |
| Linux | MIPS softfloat GZ | MIPS routers using the soft-float ABI | Download MIPS softfloat |
INSTALLATION NOTES
Key checks before and after installation
Downloading the correct package is only the first step. Whether it runs correctly also depends on system architecture, configuration source, proxy interception method, and local network status. These checks can prevent missing entry points, stale subscriptions, and ineffective system proxy settings after installation.
Confirm the system and architecture
Windows and most Linux desktops usually use x64 or AMD64; M-series Macs use ARM64; recent Android phones usually use arm64-v8a. The architecture in the filename must match the device. Do not rely only on the brand or appearance; confirm the processor type in system information.
Keep a backup of the old configuration
Before changing clients, record the subscription URL, custom rules, DNS settings, ports, and policy group choices. Configuration directories and field names can differ between clients, and overwriting the old directory may carry stale state into the new environment. A safer approach is to re-import the subscription first, then restore only the settings you need.
Check proxy access after installation
Starting the client does not mean system traffic is already being routed through it. On desktop, check that the system proxy or TUN is enabled as needed; on Android and iOS, confirm the system VPN status. Then open the connections or logs page to see whether requests reach the core before adjusting subscriptions, DNS, or nodes.
Recommended order from installation to a working setup
After installation, import the subscription and run an update, then confirm that policy groups appear. Keep rule mode enabled, choose a policy, and turn on the system proxy. Consider TUN only when the regular system proxy cannot cover the target app. Finally, test with both a browser and the actual app, using logs to identify DNS issues, connection timeouts, or port conflicts.
CLIENT SELECTION
How to choose a client
Multiple clients on one platform cover different interface preferences, package formats, and device architectures; you do not need to install them all. Usually keep one client responsible for system proxy or VPN routing to prevent multiple programs from changing proxy settings or listening on the same port.
| Need | Best choice | Why | Watch out for |
|---|---|---|---|
| First-time use with clear settings as a priority | Clash Plus | Common features are centralized across several major platforms. | Choose the package matching the device architecture. |
| Windows, macOS, or Linux desktop | Clash Verge Rev | Provides a complete desktop control interface around Mihomo. | Linux users must distinguish between DEB and RPM. |
| Want a similar interface on desktop and Android | FlClash | Broad cross-platform coverage with multiple package formats. | Android requires choosing among ARM64, ARM, and x86_64. |
| Need a universal Android architecture package | Clash Meta for Android | Offers ARM64, ARM, and universal entry points. | The universal package is usually larger than a single-architecture package. |
| Migrate an old Windows or macOS configuration | Archived client | Useful for reading a legacy environment and completing the transition. | After migration, consider a maintained replacement client. |
| Server, router, or container | Mihomo core | Suited to command-line, service-based, and automated deployments. | You must maintain configuration, permissions, logs, and processes yourself. |
DOWNLOAD FAQ
Common download and installation questions
These questions cover client selection, package formats, processor architectures, and basic post-installation checks. For more complete configuration and troubleshooting, continue to the setup guide and Troubleshooting page.
Which Clash client should you download first?
For regular desktop and mobile devices, start with Clash Plus. Choose Clash Verge Rev, FlClash, or Clash Meta for Android when you need a different interface or package format. Download the Mihomo core separately only for servers and routers. One primary client per device is usually enough; avoid multiple programs changing system proxy settings at once.
What is the difference between the Windows installer and ZIP archive?
The installer creates an application directory and shortcuts for standard use. A ZIP archive runs after extraction and suits users who manage the program directory themselves. Both formats need permission to let the client write configuration and runtime data. TUN or system services may still require administrator approval.
Should you choose Apple Silicon or Intel for macOS?
Choose Apple Silicon or ARM64 for Macs with an M-series chip, and Intel or x64 for older Macs with an Intel processor. Open About This Mac from the Apple menu to check the chip or processor. If both architecture entries for a client point to the same release file, use the file listed on the current page.
How do you choose among Android package architectures?
Recent Android phones and tablets usually use ARM64, so start with arm64-v8a. Older 32-bit devices use armeabi-v7a. x86_64 is more common on emulators and a small number of specialized devices. If you cannot identify the architecture, choose the universal Clash Meta for Android package.
What is the difference between a graphical client and the Mihomo core?
Graphical clients provide subscription import, policy switching, system proxy controls, and logs for personal computers and phones. Mihomo is a command-line core intended mainly for servers, routers, containers, or environments where configuration files are managed manually. Downloading the core does not replace a complete desktop setup workflow.
What should you check if importing a subscription still does not connect?
Confirm that the subscription has updated and an available policy is selected. Then check whether the system proxy is enabled, the proxy mode is correct, and mixed-port matches the system proxy port. On mobile, also check the system VPN status. If problems persist, review DNS, connection timeouts, refused connections, and port-usage details in the logs.