PLATFORM PACKAGE MATRIX
Check your operating system and CPU architecture first, then choose a graphical client. Windows, macOS, Android, iOS, and Linux use different package formats; servers and routers can use the Mihomo core directly.
CLIENT PACKAGES
A single client may offer packages for multiple CPU architectures. Check your system information before installing instead of relying only on the platform name in the filename.
Built for everyday Windows desktop use, with subscription management, policy switching, system proxy controls, and rule configuration. A good choice for first-time installations and users managing multiple configurations from one interface.
A desktop graphical client for configuration editing, rule inspection, proxy mode switching, and Mihomo features. The current release provides a Windows x64 installer.
A cross-platform graphical client with a similar interface across desktop and mobile. On Windows, use the standard installer or deploy it manually from the archive.
For Windows users who prefer a different desktop workflow and configuration layout. Quit other similar clients before installation to avoid competing for the system proxy port.
A legacy desktop client retained for restoring older devices and migrating configurations. For new installations, choose a maintained client and back up existing configuration files before migrating.
| Processor | x86-64; this page does not provide a separate Windows ARM64 entry for Clash Verge Rev. |
| Package formats | .exe is for standard installation; .zip is for manual extraction and deployment. |
| Installation permissions | The system proxy typically does not require ongoing administrator access. Service mode, TUN drivers, or firewall changes may trigger a system authorization prompt. |
| Conflict check | Do not enable the system proxy or TUN in multiple proxy clients at the same time. Quit the old client and restore its proxy settings before switching. |
Provides disk images for Apple Silicon and Intel. Choose ARM64 for M-series chips such as M1, M2, M3, and M4; choose x64 for Intel Macs.
For users who need desktop policy management, configuration overrides, and Mihomo settings. The current download manifest maps both architecture keys to the same disk image.
A cross-platform interface for users who want a similar workflow on macOS and Android. The current manifest maps both macOS architecture keys to the same AMD64 disk image.
Retained for existing menu bar workflows and legacy configuration migration. Both Apple Silicon and Intel keys currently point to the same x86-64 disk image.
| Identify the chip | Open About This Mac and check the chip field. Select ARM64 when it shows an Apple M-series chip, or x64 when it shows Intel. |
| Package formats | .dmg is a disk image. Open it and follow the client’s instructions to copy the app to Applications. |
| System authorization | The first time you enable the system proxy, network extension, or TUN, macOS may request the Mac administrator password. |
| Architecture note | Some release manifests may map multiple architecture keys to the same file. Use the actual filename and the client’s documentation as the source of truth. |
For mainstream 64-bit ARM Android phones and tablets. After installation, grant VPN permission so the system can route relevant traffic through the local VPN interface.
A Mihomo graphical client for Android, with ARM64, ARM, and Universal packages. Most recent phones use ARM64; if unsure, check the device CPU ABI.
For users who use both desktop and Android clients. It provides ARM64, 32-bit ARM, and x86-64 packages; choose based on the device ABI to avoid architecture incompatibility during installation.
An Android rule-based proxy client for users familiar with configuration files, proxy groups, and rule matching. A Universal package is provided locally; confirm that Android allows installations from the current source.
| Common architectures | Recent phones and tablets usually use arm64-v8a; older devices may use armeabi-v7a. |
| Installation format | .apk files are handled by Android’s package installer. The system may temporarily ask you to authorize the current browser or file manager to install apps. |
| Network permissions | Android shows a VPN connection confirmation the first time you start the proxy. This permission creates the local virtual network interface. |
| Background operation | Some systems restrict background processes. If connections drop frequently, check battery optimization, background activity, and auto-start settings. |
Install through the App Store for subscription imports, policy selection, and network connection management on iPhone and iPad. When starting the proxy for the first time, follow the system prompt to allow the VPN configuration.
Official client website: clashplus.io
| How to install | Open the Clash Plus listing in the App Store and complete the installation. |
| Supported devices | For compatible iPhone and iPad models. Check the App Store listing for the exact iOS version requirement. |
| Network authorization | Allow iOS to add a VPN configuration on the first connection. Without this permission, the client cannot establish a local network tunnel. |
| Configuration setup | After installation, import a subscription or configuration file, choose a proxy node, and start the connection. |
For standard Linux desktop environments. Choose DEB for Debian, Ubuntu, and derivatives; choose RPM for Fedora, RHEL, Rocky Linux, and other RPM-based distributions.
Provides AMD64 packages in DEB, RPM, and AppImage formats. Distribution packages work with system package managers; AppImage suits desktop environments that do not want to modify the package database.
| Desktop architecture | The graphical clients in this section primarily target AMD64 or x86-64. For ARM servers and routers, see the Mihomo core section below. |
| Debian-based systems | Use .deb; the distribution software center or apt can handle dependencies during installation. |
| RPM-based systems | Use .rpm for distributions built around RPM package management. |
| AppImage | After downloading, grant execute permission before launching. Desktop menu integration depends on the current desktop environment. |
MIHOMO CORE
For servers, routers, containers, automation scripts, and command-line environments. Most desktop and mobile users should use the graphical clients above, which include configuration management and system proxy controls.
| System | Architecture | Format | Use case | Download |
|---|---|---|---|---|
| Windows | AMD64 | .zip |
64-bit Intel / AMD command-line environments | Download AMD64 |
| Windows | ARM64 | .zip |
Windows on ARM devices | Download ARM64 |
| macOS | Intel AMD64 | .gz |
Intel Mac command-line environments | Download for Intel |
| macOS | Apple Silicon ARM64 | .gz |
M-series Mac command-line environments | Download for Apple Silicon |
| Linux | AMD64 | .deb |
Debian, Ubuntu, and derivative systems | Download DEB |
| Linux | AMD64 | .gz |
General server and container environments | Download AMD64 |
| Linux | ARM64 | .gz |
64-bit ARM servers and routers | Download ARM64 |
| Linux | ARMv7 | .gz |
32-bit ARMv7 routers and single-board devices | Download ARMv7 |
| Linux | MIPS softfloat | .gz |
Routers using the MIPS soft-float ABI | Download MIPS |
Run the executable from a terminal after extracting the Windows ZIP. On macOS and Linux, extract the GZ archive first, then add execute permission to the binary. Set the configuration path, working directory, and service account before startup.
The Mihomo core reads YAML configuration. Server deployments typically also require a log path, DNS settings, TUN permissions, an external control address, and service management. Do not copy local absolute paths directly from a desktop configuration.
INSTALLATION NOTES
A successful installation only confirms that the program was deployed. The client will process connections only after you import a subscription, select a node, and enable the proxy.
Windows and Linux desktops commonly use AMD64; Apple Silicon Macs use ARM64; Android devices require a choice based on the CPU ABI. The wrong architecture typically results in installation failure, failure to launch, or an incompatible-format warning.
Multiple clients modifying the system proxy, listening on the same port, or enabling TUN can cause port conflicts, duplicate routes, and misleading connection states. When migrating, quit the old client before launching the new one and importing the configuration.
The installer does not include proxy nodes. Import a subscription URL or local YAML file, wait for parsing to finish, and check that selectable nodes appear in the proxy groups. If parsing fails, first inspect the line number and field name reported by the client.
Rule mode processes connections in the order defined by the configuration. Global mode typically sends connections through the selected policy, while direct mode temporarily bypasses the proxy. After choosing a node, enable the system proxy or configure TUN for your use case.
Open a regular webpage first to confirm basic connectivity, then test the intended proxy destination. If the system reports a connection but pages do not load, check node status, policy selection, DNS, the system proxy, TUN routes, and the firewall in that order instead of repeatedly reinstalling the client.
DOWNLOAD FAQ
These answers cover installer selection, configuration setup, and core use cases. For a complete connection troubleshooting workflow, open the troubleshooting page.
Most desktop users can start with Clash Plus. If you want a different configuration editor or interface layout, compare Clash Verge Rev, FlClash, and Clash Nyanpasu. Clash for Windows is discontinued; its entry is mainly retained for legacy device recovery and configuration migration, not as a long-term choice for new setups.
Open About This Mac. If the chip field shows an Apple M-series chip, choose Apple Silicon or ARM64; if it shows an Intel processor, choose Intel or x64. Some release manifests may map both architecture keys to the same file, and the page preserves the corresponding entries from the current manifest.
ARM64 covers most recent Android devices, ARM usually covers older 32-bit hardware, and Universal bundles multiple architectures into one installer. Choose the exact architecture when you know the device ABI; otherwise, use Universal when the client provides it.
The installer contains only the client, not subscription or node configuration. After installation, import a valid subscription or local configuration, wait for it to parse, choose a proxy node, and enable the system proxy or TUN. If the proxy group is empty, check the subscription response and parsing details first.
Mihomo is a command-line core for servers, routers, containers, and automated deployments. You must provide the configuration, startup arguments, and service management yourself. Graphical clients add subscription, policy, logging, and system proxy interfaces, so most desktop and mobile users should choose one.
The version field is read from the release manifest when the page loads. If the manifest has no version, the request fails, or the network is interrupted, the version slot remains hidden rather than showing an incomplete label. The button still retains the complete fallback file URL and remains usable.
If nodes time out, subscription parsing fails, the system proxy does not take effect, or TUN cannot start, open the centralized troubleshooting page and check each layer in order.
View Troubleshooting