Clash Plus
A GUI client for everyday desktop use. Configuration import, proxy-group switching, system-proxy controls, and connection logs are available in one interface, making it suitable for new installations and migrations from older clients.
PACKAGE ROUTER
Clash Download: Choose a Client by Platform
Identify your operating system first, then its architecture. Windows users should start with Clash Plus; switch platforms with the tabs below. Installers, app-store links, and the Mihomo core are listed separately so the command-line core is not confused with a desktop client.
GUI clients first
Five platform hubs
Archived projects clearly marked
- 01Choose an operating systemPLATFORM
- 02Confirm CPU architectureARCH
- 03Download a GUI clientGUI
- 04Import a subscription or YAMLPROFILE
CLIENT PACKAGES
Platform installers
Tabs sync with the address-bar hash, so you can share a specific platform directly. The first solid button on each card is the recommended option; architecture-specific packages follow it, and you do not need to download every file.
WINDOWS
Windows GUI clients
For a standard x64 PC, choose the first card. Import your subscription and enable the system proxy after installation. The older Clash for Windows entry is kept at the end for legacy configurations and migration only.
System requirements
- System
- Windows 10 / 11
- Architecture
- x64
- Package type
- Installer preferred
Clash Verge Rev
A mihomo-based desktop client for users who need rule editing, configuration switching, and connection details. A Windows x64 installer is provided here.
FlClash
Desktop and mobile interfaces follow similar interaction patterns, making it easy to keep a consistent workflow across systems. The installer handles standard setup, while the ZIP package is useful for manually managing the application directory.
Clash Nyanpasu
Provides configuration management, proxy-group controls, and log views for users familiar with Clash configuration and looking for extensive desktop controls.
Clash for Windows
Archived download. Useful for reading legacy configurations, checking historical settings, or completing a migration. Not recommended as a long-term client for new devices. Preserve the existing configuration file and subscription URL before migrating.
MACOS
macOS GUI clients
Open About This Mac to identify the chip. Choose ARM64 for Apple M-series processors and x64 for Intel processors. On first launch, macOS may ask you to approve network-extension, proxy, or background-service permissions.
System requirements
- System
- Recent macOS
- Chip
- Apple Silicon / Intel
- Package type
- DMG
Clash Plus
A complete GUI workflow from installation and subscription import to system-proxy controls. The two DMG files correspond to Apple Silicon and Intel; download the one matching your chip.
Clash Verge Rev
A mihomo desktop frontend with configuration switching, rule and connection details, and proxy-group selection. After downloading, drag the app into Applications and follow the system prompts to grant permissions.
FlClash
Suitable for users who work across macOS, Windows, and Android. The cross-platform layout is similar, making subscriptions, proxy groups, and connection settings easy to manage consistently.
ClashX Meta
An archived macOS menu-bar client. Existing configurations can help verify a migration; for new installations, prefer Clash Plus, Clash Verge Rev, or FlClash, which are still updated.
ANDROID
Android clients
Most recent phones and tablets use ARM64. Older devices may need ARMv7; when the architecture is unknown, prefer a package marked Universal. The app requires permission to establish a VPN connection.
System requirements
- System
- Android
- Common architectures
- arm64-v8a
- Package type
- APK
Clash Plus
Designed for mainstream 64-bit Android devices. After importing a subscription, choose a proxy group, start the VPN connection, and view its status directly in the client.
Clash Meta for Android
A commonly used Clash Meta client for Android. ARM64 covers most newer devices, ARM supports some older devices, and the Universal package is intended when the processor architecture is unknown.
FlClash
For users who want a similar workflow on mobile and desktop. ARM64 is for most modern phones, while ARMv7 targets older 32-bit devices.
Surfboard
An alternative Android proxy client for users with compatible configurations. Before downloading, confirm that your subscription or configuration format is supported.
IOS
iPhone and iPad
On iOS, install Clash Plus through the App Store. After installation, import a subscription or configuration and follow the system prompts to add a VPN configuration. The official website link is also included on the card.
Installation method
- Devices
- iPhone / iPad
- Source
- App Store
- Official website
- clashplus.io
Clash Plus
The GUI client entry for iPhone and iPad. Install through the App Store, then import a subscription, choose a proxy group, and create a system VPN connection in the client.
OFFICIAL SITE
clashplus.io
LINUX
Linux GUI clients
Choose DEB for Debian, Ubuntu, and derivatives; choose RPM for Fedora and RHEL-based distributions. Only GUI clients are listed here. For servers and routers, continue to the Mihomo core section.
System requirements
- DEB
- Debian / Ubuntu
- RPM
- Fedora / RHEL-based
- Architecture
- AMD64 / x86_64
Clash Verge Rev
The preferred choice for Linux desktops. DEB and RPM cover two common package-management systems; after installation, import configurations and control the system proxy through the GUI.
FlClash
A cross-platform GUI alternative. This entry provides a Linux AMD64 DEB for Debian, Ubuntu, and compatible dpkg-based desktop distributions.
MIHOMO CORE
Mihomo core packages
These files target servers, routers, gateway devices, and users who write their own service configurations. Mihomo is a command-line core and does not include a desktop GUI. Windows, macOS, Android, and Linux desktop users should generally choose a GUI client above.
| System | Architecture | Package format | Use case | Download |
|---|---|---|---|---|
| Windows | amd64 |
ZIP | Typical 64-bit Intel / AMD PCs and servers | Download |
| Windows | arm64 |
ZIP | Windows on ARM devices | Download |
| macOS | amd64 |
GZ | Intel-based Mac | Download |
| macOS | arm64 |
GZ | Apple Silicon Mac | Download |
| Linux | amd64 |
DEB | AMD64 servers or hosts using dpkg | Download |
| Linux | amd64 |
GZ | Generic archive for manual deployment | Download |
| Linux | arm64 |
GZ | 64-bit ARM servers, development boards, and routers | Download |
| Linux | armv7 |
GZ | 32-bit ARMv7 routers and embedded devices | Download |
| Linux | mips-softfloat |
GZ | MIPS routers using software floating point | Download |
Configuration compatibility: Mihomo supports Clash-style configurations and extends them with additional protocol, rule, and DNS capabilities. When deploying a legacy configuration, still check its fields, rule-set paths, listen addresses, and permissions; do not assume every historical field behaves the same way.
BEFORE INSTALL
Four checks after downloading
The installer only provides the client itself. Reliable operation depends on the configuration source, proxy mode, system permissions, and DNS settings. Follow these checks in order instead of repeatedly switching installers.
Prepare a subscription or configuration
The client does not generate nodes automatically. Import a working subscription URL or choose a local YAML file. After importing, confirm that proxy groups and rule lists appear before enabling the connection.
Start with rule mode
Rule mode uses rules in the configuration to decide between DIRECT, PROXY, and REJECT. Global mode sends most connections through one proxy group and is useful for troubleshooting, but not as the default for every situation.
Confirm system permissions
Desktop clients may need to create a system service or change proxy settings; mobile clients need to create a VPN connection. If permission is denied, the client may appear to be running while system traffic never reaches the core.
Check DNS and browser settings
When connections fail, first check the logs for resolution errors, then confirm that the system proxy, TUN, and DNS modes match the configuration. The browser's secure DNS may bypass the system resolution path and should be checked as well.
Need the complete workflow: import a subscription, choose a node, enable the system proxy, and check the connection.
View Getting Started
DOWNLOAD FAQ
Common download and installation questions
Handle the platform and architecture first, then the configuration. A wrong installer usually fails at launch; configuration problems appear in subscription updates, proxy groups, or DNS logs.
Which Clash client should I download first for Windows?
For a new installation, start with the Clash Plus Windows x64 installer. It covers common workflows including subscription import, proxy-group switching, system-proxy controls, and log viewing. If you need a different interface or configuration workflow, compare Clash Verge Rev, FlClash, and Clash Nyanpasu.
Clash for Windows is no longer maintained. Its download entry remains for reading legacy configurations and completing migrations. Before migrating, save the subscription URL, local YAML, and custom rules rather than relying only on the client's temporary state.
How do I choose between Apple Silicon and Intel installers on macOS?
Open About This Mac or System Information from the Apple menu. If the Chip field shows an Apple M-series processor, choose ARM64 or Apple Silicon; if the Processor field shows Intel, choose x64 or Intel. The wrong architecture may prevent startup or require translation-layer support.
After opening the DMG, drag the app into Applications. When enabling the system proxy, network extension, or background service for the first time, follow the system prompts to grant access. If permission was previously denied, review the related Privacy, Security, and Login Items settings.
Which Android package should I download if I do not know my processor architecture?
Most recent Android phones use arm64-v8a, so start with ARM64. Older 32-bit devices may require armeabi-v7a. If a device-information tool cannot identify the architecture, the Universal package for Clash Meta for Android provides broader coverage.
Android will ask to create a VPN connection after installation; this is the standard way to pass traffic to the client. If the connection switch immediately turns off, check VPN permission, background-execution limits, and battery settings first.
Why are there still no nodes after downloading?
The installer contains only the client, not subscriptions or nodes. Import a valid URL from the Profiles, configuration, or subscription page, or load a local YAML file. If the proxy group is empty afterward, check the update notice and logs to confirm that the URL returns a Clash configuration the client can read.
An incomplete subscription URL, expired authorization parameters, an HTML page instead of YAML, or fields lost during conversion can all cause import failures. Do not keep switching the system proxy while the node list is empty; there is no usable configuration to execute yet.
What is the difference between the Mihomo core and a GUI client?
Mihomo is the core that parses configurations, matches rules, handles DNS, and forwards connections, usually running through a command line, service manager, or router script. It does not provide a desktop tray, subscription button, or proxy-group selection interface.
GUI clients such as Clash Plus, Clash Verge Rev, and FlClash turn core capabilities into an interactive interface and handle system proxies, configuration updates, and log display. Use a GUI on ordinary computers and phones; choose the standalone core for servers, gateway routers, and automated deployments.
Can I still use the older Clash for Windows?
An existing installation can still read legacy configurations or verify previous proxy groups, but the project is no longer maintained. New systems, protocols, and configuration extensions will not be prioritized for compatibility, so new devices should use a client that is still being updated.
During migration, record the current mode, system-proxy status, subscription URL, custom rules, and DNS settings. Import the same configuration into the new client, then verify proxy groups, rules, and logs one by one. Do not run two clients that compete for the same ports.