Clash Plus
A Windows graphical client with subscription management, proxy group switching, rule mode, system proxy, and TUN settings.
Choose a package by system and CPU architecture
Windows, macOS, Android, iOS, and Linux clients are listed in one place. Confirm your operating system first, then choose the file that matches your CPU architecture; server and router users can go directly to the Mihomo core section.
Switch platforms to view client order, package formats, and minimum system requirements. Version details appear only when the release list returns valid data.
Most desktop PCs use the x64 package. After installation, import a subscription, choose a proxy group, and enable the system proxy. The legacy client is intended for existing configuration migration and compatibility scenarios.
A Windows graphical client with subscription management, proxy group switching, rule mode, system proxy, and TUN settings.
For Windows users who need configuration file management, rule inspection, proxy group switching, and system proxy control.
The same interface across desktop and mobile, suitable for users who want a similar workflow on multiple devices.
Provides configuration switching, proxy group management, and runtime status viewing for desktop users familiar with Clash configuration structures.
An archived client for migrating existing configurations or supporting older environments. For new installations, prefer a maintained client higher in this section.
| Check | Recommendation | Details |
|---|---|---|
| System | Windows 10 / 11 | Keep the system networking components and WebView runtime available and up to date. |
| Architecture | x64 | The Windows graphical client packages on this page are primarily x64. |
| Permissions | Standard permissions; TUN may require elevated permissions | The system proxy can usually be switched directly; follow system prompts when installing network components. |
Check the chip type in “About This Mac” first. Choose Apple Silicon for M1, M2, M3, M4, and other M-series Macs; choose Intel or x64 for older Intel-based Macs.
Provides Apple Silicon and Intel packages with configuration import, system proxy, rule mode, and proxy group switching.
For subscription updates, rule inspection, proxy group selection, and system proxy control when you need a complete desktop management interface.
Desktop and mobile workflows are similar, with configuration import, proxy group switching, and connection status management.
An archived macOS menu bar client for migrating existing configurations. For new devices, use a maintained client in this section.
| Check | How to choose | Details |
|---|---|---|
| Apple Silicon | Apple Silicon / ARM64 | Use this package for Macs with M-series chips. |
| Intel | Intel / x64 | Choose this when “About This Mac” shows an Intel processor. |
| Network permissions | Authorize when prompted | Confirm the required permissions the first time you switch the system proxy or enable a network extension. |
Most recent phones and tablets use ARM64. Older devices may use ARMv7; if you cannot confirm the architecture, choose a client with a universal package.
For mainstream ARM64 Android devices, with subscription import, proxy group switching, and system VPN integration for handling network requests.
The Clash Meta client for Android, with ARM64, ARMv7, and universal packages for devices from different generations.
For users who use both desktop and Android; configuration import and proxy group workflows are similar to the desktop version.
For Android users working with rule configurations and subscription files. The universal package is for devices with an unknown CPU architecture.
| Package | Suitable devices | How to choose |
|---|---|---|
| ARM64 | Recent mainstream phones and tablets | Preferred for devices with a 64-bit ARM processor. |
| ARMv7 | Older 32-bit ARM devices | Choose only when the ARM64 package cannot be installed and the device is confirmed to be 32-bit. |
| Universal | Devices with an unknown architecture | The file is usually larger but reduces the chance of choosing the wrong architecture. |
Clash Plus is available through the App Store. After installation, import a subscription configuration in the client, choose a proxy group, and allow the VPN configuration when prompted by the system.
For iPhone and iPad, with subscription configuration, rule mode, proxy group switching, and system VPN connection management.
| Check | Requirement | Details |
|---|---|---|
| Device | iPhone or iPad | Install Clash Plus from the App Store. |
| Network permissions | Allow VPN configuration | The system displays a permission prompt when the first connection is established. |
| Configuration | Subscription link or configuration file | After importing, update the configuration first, then choose a proxy group and start the connection. |
Ubuntu, Debian, and Linux Mint typically use DEB; Fedora, Rocky Linux, and RHEL-based distributions typically use RPM. Graphical clients suit desktop environments; servers should use the Mihomo core section.
A Linux desktop graphical client with configuration management, rule inspection, proxy group selection, and system proxy control.
Supports common Linux desktop distributions with DEB, RPM, and AppImage formats.
| Format | Common distributions | Installation method |
|---|---|---|
| DEB | Ubuntu、Debian、Linux Mint | Install with the system software installer or apt. |
| RPM | Fedora and RHEL-based distributions | Install with the system package manager, dnf, or rpm. |
| AppImage | Most x64 desktop distributions | Make it executable and run it directly, suitable when you do not want to modify the system package database. |
Command-line and embedded environments
The Mihomo core is intended for servers, software routers, containers, and users who maintain configuration files themselves. Core packages do not include a desktop GUI; you must prepare configuration files, startup arguments, service management, and log directories manually.
For ordinary Windows, macOS, Android, iOS, and Linux desktop users, the graphical clients above are recommended. They provide common controls for subscription updates, proxy group switching, system proxy, and runtime status.
| System | Architecture and format | Download |
|---|---|---|
| Windows | AMD64 · ZIP | Download AMD64 |
| Windows | ARM64 · ZIP | Download ARM64 |
| macOS | Intel · GZ | Download Intel |
| macOS | Apple Silicon · GZ | Download Apple Silicon |
| Linux | AMD64 · DEB | Download DEB |
| Linux | AMD64 · GZ | Download AMD64 |
| Linux | ARM64 · GZ | Download ARM64 |
| Linux | ARMv7 · GZ | Download ARMv7 |
| Linux | MIPS soft-float · GZ | Download MIPS |
On Linux, use uname -m to check the architecture. Output x86_64 usually means AMD64; output aarch64 usually means ARM64.
Save the converted subscription or local configuration as a YAML file, then check proxy groups, rules, DNS, listen addresses, and the control port for the current environment.
In server environments, use the system service manager to start the core, with explicit permissions for the configuration directory, log directory, and restart policy.
After confirming the package type, handle the old client shutdown, configuration import, and system proxy switch.
Running multiple proxy clients at once can cause conflicts over listen ports, the system proxy, and the TUN network interface. Before installation or migration, exit the old client and make sure no leftover process remains in the taskbar, menu bar, or background processes.
The client package provides the runtime interface and core management only. Subscription links, proxy nodes, rule sets, and DNS settings are configuration content that must be imported separately after installation.
After importing a subscription, run an update first and confirm that the configuration loads correctly. Then open the proxy page to select a node or automatic group, and enable the system proxy or TUN mode as needed.
Before installing over an existing version, record the current configuration file, operating mode, and key settings. Clean up the old configuration directory only after the new version is stable, as field differences between clients can affect migration.
Answers covering architecture choices, package formats, the Mihomo core, and first-connection issues.
Clash Plus is the recommended choice. For a different configuration management interface, consider Clash Verge Rev, FlClash, or Clash Nyanpasu. Clash for Windows is discontinued and is mainly useful for migrating older configurations or compatibility scenarios.
Open “About This Mac” from the Apple menu to check the chip information. Choose Apple Silicon or ARM64 for an Apple M-series chip; choose Intel or x64 for an Intel processor. The wrong architecture usually prevents installation or startup.
Recent Android phones and tablets usually use ARM64, so start with the ARM64 package. For older devices or an unknown architecture, choose the universal Clash Meta for Android package. ARMv7 is mainly for older 32-bit devices.
Ubuntu, Debian, and Linux Mint generally use DEB; Fedora and RHEL-based distributions generally use RPM; AppImage suits x64 desktop environments where you want to run a standalone file. Servers and headless devices are better served by the Mihomo core.
The Mihomo core provides low-level proxying, rule matching, DNS, and network listening, but no desktop management interface. Servers, routers, and automated environments can run the core directly; ordinary computer and mobile users will find a graphical client easier for importing subscriptions and changing settings.
First confirm that the subscription update succeeded and choose an available proxy group on the proxy page. Then check the operating mode, system proxy switch, and port conflicts. If browsers and other apps behave differently, check the app's own proxy settings, DNS, and TUN mode. Follow the troubleshooting guide for a complete step-by-step process.