Clash Plus
A graphical client for everyday Windows use. The installer guides you through deployment and suits users who want to manage subscriptions, proxy groups, rule modes, and the system proxy in one place.
Client packages
Choose your operating system first, then download the client matching your CPU architecture. Desktop and mobile users should prefer graphical apps; servers, software routers, and command-line environments can use the Mihomo core directly.
Platforms
The tabs switch between installers for each platform. Download links update automatically from the release list; if the list is temporarily unavailable, the page retains the complete file URLs currently available.
Windows packages
Designed for everyday desktop use. On 64-bit Windows 10 and Windows 11 PCs, choose an x64 installer. Quit any older client before installation, then import your configuration afterward to prevent two programs from changing the system proxy at once.
A graphical client for everyday Windows use. The installer guides you through deployment and suits users who want to manage subscriptions, proxy groups, rule modes, and the system proxy in one place.
A Mihomo-based desktop client with subscription management, rule switching, system proxy controls, and configuration editing. The current download is a Windows x64 installer.
A cross-platform graphical client. Use the installer for a fixed setup; use the ZIP package from a custom directory. Both use the same configuration logic, so do not run them at the same time.
Provides interfaces for subscriptions, configurations, proxy groups, and logs. Suited to users familiar with Clash configuration who want to manage multiple files from one desktop app.
An archived client for restoring an existing environment or migrating legacy configurations. For new installations, choose Clash Plus, Clash Verge Rev, or FlClash, which are still maintained.
| Item | Recommended requirement | Selection guidance |
|---|---|---|
| System | Windows 10 or Windows 11 | Keep security updates current and allow the app to modify system proxy settings. |
| Processor | 64-bit x86 | The Windows graphical installers on this page target common x64 PCs. |
| Permissions | Administrator confirmation may be required during installation | Service mode, virtual adapters, and firewall rules may trigger system authorization prompts. |
macOS packages
Check the chip information in About This Mac before downloading. Apple M series chips use Apple Silicon, so choose an ARM64 package; Intel Macs need the x64 package. On first launch, macOS may ask you to approve network extensions, VPN configuration, or background-item permissions.
Ideal for managing subscriptions, proxy groups, and the system proxy on a Mac. Apple Silicon and Intel packages are provided separately; choose the one matching your chip.
A Mihomo-based desktop client for editing configurations, switching rule modes, and reviewing connection logs. The two architecture downloads are managed separately in the release list.
The interface and workflow are similar across platforms, making it convenient for users who switch between a Mac and mobile devices. After installation, move the app to Applications and approve the requested network permissions.
An archived menu bar client for migrating legacy configurations or restoring an existing setup. New users should choose a maintained graphical client.
| Item | Recommended requirement | Selection guidance |
|---|---|---|
| System | A macOS version still receiving security updates | Newer network extensions generally require newer system components. |
| Chip | Apple Silicon or Intel | Choose Apple Silicon for M1, M2, M3, and M4 Macs; choose x64 for Intel models. |
| Permissions | VPN and background permissions | When connecting for the first time, follow the system prompt to let the client add a network configuration. |
Android packages
Recent phones and tablets typically use arm64-v8a. Only older 32-bit devices need armeabi-v7a. After installation, import a subscription, choose a proxy group, and authorize the VPN connection; if battery optimization is aggressive, allow the client to run in the background.
For 64-bit Android phones and tablets, with subscription import, proxy-group switching, and VPN connection management. The current download targets arm64-v8a.
A Mihomo graphical client for Android. Download the package matching your phone's architecture when known; otherwise choose the universal package for broader compatibility.
Provides arm64, 32-bit ARM, and x86_64 packages. Phones usually need arm64; older devices use ARM; Android emulators and certain x86 devices can use x86_64.
For Android users who need basic proxying, rule matching, and configuration-file management. The current download is a universal installer for devices with unknown architectures.
| Architecture | Common devices | Recommendation |
|---|---|---|
| arm64-v8a | Recent Android phones and tablets | The preferred choice for most users; the file is usually smaller than the universal package. |
| armeabi-v7a | Older 32-bit ARM devices | Use only when the arm64 package cannot be installed and the device is confirmed to be 32-bit. |
| universal | Devices with an unknown architecture | Offers broader compatibility when processor information is unavailable. |
iPhone and iPad
iPhone and iPad users can install Clash Plus from the App Store. After the first launch, import a subscription or configuration file, then allow the app to add a VPN configuration. The connection is managed by the iOS network extension and may continue handling requests after the screen locks, subject to system rules.
For iPhone and iPad. The client supports subscription imports, proxy-group selection, rule-hit inspection, DNS management, and on-demand configuration connections. After installation, continue with the usage documentation for first-time setup.
Official website: clashplus.io
| Item | Requirement | Details |
|---|---|---|
| System | iOS 15 or later | Install the latest update available for your device to keep network extensions reliable. |
| Devices | iPhone and iPad | The same configuration can be imported and adjusted separately for each device. |
| Permissions | Allow VPN configuration | The system displays a confirmation prompt on the first connection; afterward, check the status in Settings. |
Linux packages
Desktop Linux users can choose the graphical Clash Verge Rev or FlClash. First check the distribution's package format: Debian, Ubuntu, and derivatives generally use DEB, while Fedora and RHEL-based distributions generally use RPM.
A Mihomo graphical client for Linux desktops, with AMD64 DEB and RPM installers. After installation, launch it from the desktop menu and configure the system proxy.
For AMD64 desktop systems running Debian, Ubuntu, or another distribution using the DEB package format. After installation, import your configuration and allow background operation as required by the desktop environment.
| Package format | Common distributions | Pre-installation check |
|---|---|---|
| DEB | Debian、Ubuntu、Linux Mint | Confirm that the system is AMD64 and that you have permission to install local DEB packages. |
| RPM | Fedora and RHEL-based distributions | Confirm that the system is x86_64 and use the package tool provided by your distribution. |
| Desktop environment | Common graphical desktops | If you need a tray icon, notifications, and system proxy support, check that the desktop components are installed. |
Mihomo core
Core packages target servers, routers, containers, automation scripts, and command-line users. They do not include a desktop GUI, so you must provide configuration files, launch arguments, and a service-management method. Regular computer and phone users should prefer the GUI clients above.
Use the ZIP archive for the Windows core; macOS and most Linux general-purpose packages use GZ archives; Debian-based servers can choose the AMD64 DEB directly. Router and embedded-device users must verify the CPU architecture: ARM64, ARMv7, and MIPS softfloat are not interchangeable.
| System | Architecture and format | Suitable environment | Download |
|---|---|---|---|
| Windows | AMD64 · ZIP | Common 64-bit Windows servers and command-line environments | Download AMD64 |
| Windows | ARM64 · ZIP | Windows on ARM devices and ARM64 servers | Download ARM64 |
| macOS | Intel · GZ | Command-line environments on Intel Macs | Download Intel |
| macOS | Apple Silicon · GZ | Macs with Apple M series chips | Download Apple Silicon |
| Linux | AMD64 · DEB | Debian, Ubuntu, and their server derivatives | Download DEB |
| Linux | AMD64 · GZ | Common x86_64 servers, containers, and custom deployments | Download AMD64 |
| Linux | ARM64 · GZ | 64-bit ARM servers, development boards, and routers | Download ARM64 |
| Linux | ARMv7 · GZ | Older embedded devices using 32-bit ARMv7 | Download ARMv7 |
| Linux | MIPS softfloat · GZ | Routers using the MIPS soft-float ABI | Download MIPS |
Package selection
The order is simple: identify the system, check the processor, then choose an installer, portable package, or core-only download. Similar filenames are not necessarily intended for the same device.
Windows, macOS, Android, iOS, and Linux use different installer formats. Windows commonly uses EXE or ZIP, macOS uses DMG, Android uses APK, and Linux desktops commonly use DEB or RPM. Do not download based only on the client name; open the tab for your platform first.
Common desktop options include x64, AMD64, ARM64, and Apple Silicon; Android commonly uses arm64-v8a and armeabi-v7a. Architecture determines whether the program can run and is separate from the operating system version. If an Android architecture is unknown, prefer a package explicitly labeled universal.
Regular users should choose a graphical installer for managing subscriptions, rule modes, proxy groups, and the system proxy. Portable ZIP packages suit fixed-directory use. The Mihomo core is intended for servers or routers with service scripts and configuration-management experience.
Before installation
Installers only deploy the client. Your own configuration still determines subscriptions, rules, and proxy-group choices. A quick cleanup before updating can prevent issues caused by old services, duplicate proxies, or overwritten configurations.
Record the current subscription name, proxy-group selection, rule mode, and DNS settings. If the client supports configuration export, save local overrides and custom rules separately. Then fully quit the old version, including its tray or menu bar process and background services, before running the new installer.
After updating, verify that the configuration list is complete before enabling the system proxy or VPN. Do not run two clients that modify system network settings at the same time; this can cause occupied proxy ports, repeated proxy switching, or virtual-adapter conflicts.
Subscription URLs can usually be imported again, but local overrides, scripts, external-controller settings, and on-demand connection rules may not migrate automatically. In the old client, identify what comes from the subscription and what exists only locally, then restore each item according to the new client's configuration structure.
Do not remove the old client immediately after migration. First use rule mode to visit several familiar websites and verify proxy-group selection and DNS resolution. Once the new client starts reliably, updates subscriptions, and controls the system proxy, clean up the old program.
After installation, import a valid subscription or local YAML configuration. Open the proxy groups, select an actually usable proxy, and enable rule mode. Mobile devices will request a VPN configuration; desktop systems may request permission for the system proxy, virtual adapter, or background service.
A successful connection only means that the network extension or proxy port has started; it does not confirm that every rule is correct. If a webpage will not open, check the subscription status, proxy-group selection, rule matching, DNS configuration, and system time in that order. Continue with the usage documentation for the complete procedure.
View the complete setup guideFor servers, routers, and always-on devices, save the original executable, configuration, and service definition before updating the core. Run the new core in the foreground first and review its startup output. Confirm that ports, rule files, and external resources load correctly before handing it over to the system service.
If a desktop client will not start after an update, stop its background service and restart the system first; do not repeatedly install multiple clients over one another. Determine whether the cause is the app version, configuration syntax, or system permissions before restoring the old version or importing the configuration again.
Download FAQ
These questions focus on platform selection, architecture checks, and first launch. For configuration fields and rule syntax, continue to the configuration reference.
On the iOS tab, go to the App Store and install Clash Plus. After installation, import a valid subscription or local configuration file, check the proxy groups, and allow the system to add a VPN configuration. The basic steps are the same on iPad and iPhone; split-screen and landscape mode do not change how the network extension connects.
For common 64-bit Windows 10 and Windows 11 PCs, choose the x64 installer for Clash Plus or Clash Verge Rev. If you want to run it from a custom directory, choose the FlClash portable ZIP package. After extraction, keep the complete directory structure intact; do not move only the executable.
Open the Apple menu in the top-left corner and select About This Mac. If the chip is an Apple M series, choose the Apple Silicon or ARM64 package; if it lists an Intel processor, choose the Intel or x64 package. With the wrong architecture, the app may fail to open or require an additional translation environment.
arm64-v8a is for recent 64-bit ARM phones and tablets, armeabi-v7a is for older 32-bit ARM devices, and universal packages offer broader compatibility. Most current devices should use arm64; use the universal package only when the architecture cannot be confirmed.
The Mihomo core has no desktop GUI and must be managed through the command line, configuration files, and system services. It is better suited to servers, routers, containers, and automated deployments. Regular desktop users can manage subscriptions, proxy groups, logs, and the system proxy more easily with the GUI clients above.
The client installer does not include subscriptions or proxy nodes. After installation, import a valid subscription or local configuration, choose a proxy group and operating mode, and allow the system to create a VPN, network extension, or proxy connection. If the internet still does not work, start by checking the subscription status, rule matching, DNS, and system permissions.