PLATFORM PACKAGE INDEX
Choose a package by operating system and processor architecture. Use a graphical client for desktops and mobile devices; find the Mihomo core below for servers, routers, and command-line environments.
CLIENT PACKAGES
Platform labels are reflected in the page URL. When you share a link with a platform anchor, reopening it will still show the corresponding client list.
For common 64-bit Windows desktop environments. Before installing a newer version, exit any older client to avoid conflicts with the system proxy port or background processes.
A graphical client for everyday Windows use, with one interface for subscriptions, nodes, policy groups, the system proxy, and runtime status. Suitable for users who prefer a conventional installation and setup process.
A desktop client built around the Mihomo ecosystem, with configuration management, policy switching, system proxy, and TUN controls. Suitable for Windows users who want access to more runtime options.
Available for Windows, macOS, Linux, and Android, with a largely consistent interface and workflow across devices. Windows users can choose a standard installer or extract the portable archive themselves.
Provides a desktop interface for configuration management, subscription updates, policy selection, and system proxy control. A Windows x64 installer is provided here.
An archived client retained for users who need to handle legacy configurations or existing workflows. For new installations, prefer a maintained client and check rules, policy groups, and local ports after migration.
| Item | Recommended condition | Selection notes |
|---|---|---|
| System | Supported 64-bit Windows | Organization-managed devices may restrict network components or installation permissions. |
| Processor | x64 | Windows graphical clients on this page primarily use x64 packages. |
| Permissions | Administrator permission may be required during installation | TUN, service mode, and system proxy settings may trigger system confirmation prompts. |
| Migration | Back up the configuration and exit the old process first | Avoid conflicts involving listening ports, service processes, and the system proxy state. |
Before downloading, check the chip type in About This Mac. Choose Apple Silicon or ARM64 for Apple M-series chips; choose Intel or x64 for Intel processors.
Apple Silicon and Intel installers are available for managing subscriptions, policy groups, the system proxy, and connection status. On first launch, macOS may ask you to approve the app and network-related permissions.
A desktop interface for configuration, the system proxy, and Mihomo runtime options. The list keeps separate Apple Silicon and Intel download links, so select the one matching your Mac before installing.
A cross-platform graphical client for importing subscriptions, selecting policies, and controlling the proxy on macOS. Both architecture links are resolved from the remote manifest; verify that the downloaded package matches your Mac’s chip.
An archived macOS menu bar client for users who still need to work with existing ClashX Meta configurations. For new devices, compare maintained clients first.
| Item | How to choose | Installation notes |
|---|---|---|
| Apple Silicon | About This Mac shows an Apple M-series chip | Choose the ARM64 or Apple Silicon package. |
| Intel | About This Mac shows an Intel processor | Choose the x64 or Intel package. |
| First launch | Follow the system prompts to approve app permissions | Network extensions, the system proxy, or Keychain operations may request separate permissions. |
| Update and migration | Keep copies of subscriptions and local overrides | After switching clients, recheck DNS, TUN, and the system proxy state. |
Most recent phones use ARM64. Older 32-bit devices can use ARM; if the architecture is unknown, choose a client that provides a universal package.
A mobile client for ARM64 Android devices. When connected, it routes traffic through Android’s local VPN interface; the first connection requires confirmation in the system dialog.
An Android client built around the Mihomo ecosystem, offering ARM64, 32-bit ARM, and universal packages. If the device architecture is unclear, the universal version is easier to install, though it is usually larger than a single-architecture build.
A mobile interface with configuration logic similar to its desktop versions. ARM64 and 32-bit ARM packages are available; choose according to the processor architecture of your phone or tablet.
An Android proxy client for users with compatible configurations who understand how local VPN connections work on mobile devices. This package is served from site resources without dynamic version resolution.
| Item | Recommended choice | Notes |
|---|---|---|
| Recent phones and tablets | ARM64 | Most mainstream 64-bit Android devices use this architecture. |
| Older devices | 32-bit ARM | Choose this only when the device is confirmed to use 32-bit ARM. |
| Architecture unknown | Universal package | Choose the universal package for Clash Meta for Android or Surfboard. |
| Background operation | Allow VPN, notification, and necessary background activity permissions | Aggressive battery-saving policies may stop the connection process; add the client to the battery-optimization whitelist. |
Clash Plus is available on the App Store. Open the store page, complete the installation through the system workflow, then import your configuration and approve the VPN connection permission in the client.
A Clash client for iPhone and iPad, installable from the system store. When establishing a connection for the first time, iOS displays a confirmation dialog to add a VPN configuration; approval is required before it can route device traffic.
Client website: clashplus.io
| Item | Action | Notes |
|---|---|---|
| Installation source | App Store | Use the store button on this page to open the Clash Plus product page. |
| Device | iPhone or iPad | Refer to the compatibility information currently shown on the store page. |
| Connection permission | Approve adding a VPN configuration | The client needs this permission to route traffic through the system network interface. |
| Importing configuration | Use a valid subscription or local configuration | After importing, check the policy group selection before starting the connection. |
For graphical desktops, start with Clash Verge Rev or FlClash. Servers, routers, and devices without a desktop environment should use the Mihomo core section below.
For common x86_64 Linux desktop environments, with Debian and RPM packages available. After installation, manage subscription updates, policy selection, and proxy controls from the graphical interface.
Available in DEB, RPM, and AppImage formats for Linux desktops. Debian, Ubuntu, and derivatives usually use DEB; RPM-based distributions use RPM; choose AppImage for portable execution.
| Distribution environment | Package format | Notes |
|---|---|---|
| Debian, Ubuntu, and derivatives | AMD64 DEB | Install with the system package manager. |
| Fedora, RHEL, and compatible environments | x86_64 RPM | Install according to the distribution’s package management method. |
| Other x86_64 desktop distributions | AppImage | Grant execute permission, then run it and manage the desktop entry yourself. |
| Server or router | Mihomo core | When no graphical interface is needed, download the core below for your system and architecture. |
MIHOMO CORE
The Mihomo core is intended for servers, routers, containers, and users who manage configuration files, launch parameters, and service processes themselves. Most desktop and mobile users should use the graphical clients above to manage subscriptions, policy groups, logs, and the system proxy directly.
| System | Architecture | Format | Use case | Download |
|---|---|---|---|---|
| Windows | AMD64 | ZIP | Common 64-bit Intel or AMD desktop and server environments | Download core |
| Windows | ARM64 | ZIP | Devices running Windows on ARM | Download core |
| macOS | Intel AMD64 | GZ | Macs with Intel processors | Download core |
| macOS | Apple Silicon ARM64 | GZ | Macs with Apple M-series chips | Download core |
| Linux | AMD64 | DEB | Debian, Ubuntu, and compatible x86_64 systems | Download core |
| Linux | AMD64 | GZ | x86_64 environments for deploying the binary manually | Download core |
| Linux | ARM64 | GZ | 64-bit ARM servers, development boards, or routers | Download core |
| Linux | ARMv7 | GZ | 32-bit ARMv7 routers and embedded devices | Download core |
| Linux | MIPS softfloat | GZ | Specific router devices using soft-float MIPS environments | Download core |
Graphical clients provide subscription import, policy group selection, the system proxy, connection logs, and update controls. You do not need to write launch commands directly, and it is easier to observe connection status and locate configuration errors.
A standalone core suits users familiar with the command line, service management, file permissions, and YAML configuration. Before deploying to a router, confirm the CPU architecture and floating-point type, and keep a recoverable copy of the original configuration.
INSTALLATION NOTES
Clients can use similar Clash configuration structures, but their configuration directories, supported fields, and system integration methods are not identical. When switching clients, follow the steps in order to prevent the old proxy state from affecting the new program.
Save active subscription URLs, local rules, script overrides, and DNS settings. If the configuration contains personal access credentials, keep them in a controlled location and do not copy them into public documents or screenshots.
Disable the system proxy and TUN first, then fully exit the old client. On Windows, check the system tray and Task Manager; on macOS, check the menu bar and Activity Monitor to ensure that no old process still occupies a listening port.
Check the operating system, processor architecture, and package format. On macOS, distinguish Apple Silicon from Intel; on Android, distinguish ARM64, 32-bit ARM, and universal versions; on Linux, also distinguish DEB, RPM, and AppImage.
After installation, import the configuration first, then check the default policy group, DNS, the system proxy, TUN, and local ports. Do not assume that every override field from the old client will be read the same way by the new one.
DOWNLOAD FAQ
These questions cover package selection, device architecture, legacy configuration migration, and standalone core use. For more detailed configuration and connection checks, continue to the troubleshooting page.
For everyday desktop and mobile use, start with the recommended client for your platform. Clash Plus is the first option to check on Windows, macOS, Android, and iOS; Linux desktop users can choose Clash Verge Rev. Consider the Mihomo core when managing services, routers, or command-line environments yourself.
When migrating from an older client, do not compare the interface alone. Check supported configuration fields, system proxy behavior, TUN permissions, and DNS behavior before deciding whether to keep the new client.
Confirm that you are using a supported 64-bit Windows system and that the installer downloaded completely. If an older client is still running, exit its process before restarting the installer. Computers managed by organizational policies may require administrator assistance.
If the connection fails after installation, do not immediately reinstall repeatedly. Check the client logs first, then verify that the configuration imported successfully, a policy group is selected, the system proxy is enabled, and local security software is not restricting the network process.
Open About This Mac from the Apple menu to check the chip. Choose Apple Silicon or ARM64 for an Apple M-series chip, and Intel or x64 for an Intel processor. An architecture mismatch may prevent startup or require additional translation.
On first launch, macOS may show prompts for opening the app, network extensions, the system proxy, or Keychain access in sequence. Approve only the permissions required by the features you enable; previously denied permissions can be reviewed in System Settings under Privacy & Security or Network.
Most recent Android phones and tablets use ARM64. Older 32-bit devices can use ARM; if you cannot confirm the architecture, choose the universal version of Clash Meta for Android. You must still grant permission for the local VPN connection after installation.
If the client disconnects often after going into the background, check battery-saving policies, background activity restrictions, and notification permissions. Some vendor-customized systems stop long-running network services, so add the client to the battery-optimization whitelist.
The Mihomo core is mainly intended for servers, routers, containers, and users who write their own launch parameters. Most desktop and mobile users should choose a graphical client to manage subscriptions, policy groups, the system proxy, and runtime logs.
Self-managed deployments also require you to handle configuration paths, execute permissions, startup services, log retention, and updates. Router users must identify the processor architecture accurately, especially distinguishing ARM, MIPS, and different floating-point types.
There is no need to delete it immediately. Back up active subscription URLs, override rules, and local configuration first, then exit the old client. Configuration directories and supported fields vary between clients, so recheck policy groups, DNS, the system proxy, and TUN settings after migration.
Once the new client is stable, remove unused legacy programs and configuration directories. If a field is incompatible or subscription import fails, you can still refer to the original configuration and restore what is needed.