Choose a client by operating system, processor architecture, and installation method. For a first installation, start with a GUI version; consider the standalone Mihomo core for servers, routers, and automated environments.
Platform tabs switch to the corresponding installers. Within each platform, clients are listed in recommended order for first-time installation, while discontinued software is retained with archive notes.
Choose the x64 installer for a typical desktop environment. After installation, import your subscription and enable system proxy; if you need to route more application traffic, configure TUN mode using the guide.
A desktop GUI client suited to first-time installations. Configuration is centralized, with support for subscription imports, system proxy, rule mode, and TUN settings.
A Mihomo-based GUI for desktop users. It suits workflows that require inspecting proxy groups, managing configuration overrides, and fine-tuning system proxy behavior.
A cross-platform GUI client offering both an installer and an archive on desktop. Choose the installer for regular use or the ZIP file when managing the folder yourself.
A desktop GUI client for configuration management, policy switching, and system proxy control. A useful alternative for users already familiar with configuration file structure.
An archived client retained mainly for migrating older configurations, checking interface locations, and supporting existing setups. For new installations, choose a maintained client above.
Choose Apple Silicon for Macs with M-series chips and Intel for Macs with Intel processors. The first time you open the downloaded app, follow macOS security prompts to confirm its source and network extension permissions.
A macOS GUI client suited to first-time installations. Confirm your chip type before downloading, then move the app to Applications before launching it.
A Mihomo-based desktop GUI for macOS users who need configuration overrides, proxy group management, and finer control over proxy settings.
A cross-platform GUI with interaction patterns similar to its mobile version, suited to users who switch between desktop and mobile devices and want consistent configuration workflows.
An archived macOS menu bar client retained for migrating older setups and maintaining existing configurations. On new devices, choose a maintained GUI client.
Most recent devices use arm64. If you cannot identify the architecture, choose a client with a universal package. After installation, allow the client to establish a VPN connection; the system status bar will show the connection state.
For standard arm64 Android devices. After installation, import a subscription, select rule mode, and authorize the VPN connection.
An Android client built on Mihomo capabilities, offering arm64, ARM, and universal packages. When the architecture is known, use the matching version first.
A cross-platform GUI client with a mobile interface structured similarly to its desktop version. Provides arm64 and ARM installers.
An Android rule-based proxy client for users with compatible configurations who understand proxy groups and rule behavior. A universal installer is available.
On iOS, install Clash Plus through the App Store. After installation, import a configuration in the app and follow the system prompt to allow adding a VPN configuration.
A GUI client for iPhone and iPad. Import configurations, switch policies, and authorize the VPN connection within the app.
Official site: clashplus.io
Choose DEB for Debian, Ubuntu, and derivative distributions. Choose RPM for Fedora and RHEL-based distributions. This page lists only the amd64 desktop packages currently available.
A Mihomo GUI client for amd64 Linux desktops. Choose DEB or RPM according to your distribution's package management system.
A cross-platform Linux GUI client. The main download here is an amd64 DEB package for Debian, Ubuntu, and derivative distributions.
The Mihomo core has no graphical settings interface and is intended mainly for servers, OpenWrt routers, secondary routers, containers, and environments where users maintain service processes themselves. Most desktop and mobile users should prefer the GUI clients above.
| System | Architecture | File format | Use case | Download |
|---|---|---|---|---|
| Windows | amd64 |
ZIP | Common Intel and AMD 64-bit devices | Download |
| Windows | arm64 |
ZIP | Windows on ARM devices | Download |
| macOS | amd64 |
GZ | Intel processor Macs | Download |
| macOS | arm64 |
GZ | Apple Silicon Mac | Download |
| Linux | amd64 |
DEB | Debian and Ubuntu server environments | Download |
| Linux | amd64 |
GZ | Generic 64-bit Linux environments | Download |
| Linux | arm64 |
GZ | 64-bit ARM servers and router devices | Download |
| Linux | armv7 |
GZ | 32-bit ARMv7 router devices | Download |
| Linux | mips-softfloat |
GZ | MIPS devices using the soft-float ABI | Download |
The core must match the processor architecture. Even when devices all run Linux, amd64, arm64, armv7, and MIPS are not interchangeable. Run uname -m to see the architecture reported by a Linux device, then choose the matching file.
Keep the core binary, configuration files, rule sets, and runtime logs in clearly separated directories. When upgrading the core, replace only the program file to avoid overwriting local configuration, subscription conversion output, or service startup scripts.
A single client may offer multiple files. Choose based on the operating system, processor architecture, and package format; there is no need to download every version.
Windows commonly uses .exe, macOS uses .dmg, Android uses .apk, and Linux desktops commonly use .deb and .rpm. The extension indicates the installation method, and files are not interchangeable across operating systems.
x64, amd64, and x86_64 usually refer to the common 64-bit desktop architecture. arm64 refers to 64-bit ARM devices. Macs with M-series chips use Apple Silicon, so choose an arm64 build.
Installers suit everyday desktop use and create the required application entries. Archives suit manual folder management or portable deployment. Linux users should generally choose native distribution packages so the system package manager can install and remove them.
GUI clients and the Mihomo core read configurations, apply rules, and create a local proxy endpoint. After installation, import a usable subscription URL or local YAML configuration. After a successful import, the client usually shows the profile name and its defined proxy groups; if the list is empty, check the subscription content and network access instead of repeatedly reinstalling the client.
For the first setup, use rule mode. It determines how connections are handled according to domains, IPs, processes, or rule sets in the configuration, making it easier to preserve LAN and direct connections. Global mode sends everything through the current policy and is better for short-term troubleshooting; avoid using it long term until you understand its scope. After choosing a mode, enable system proxy and test the connection in a browser.
System proxy mainly affects applications that follow the operating system's proxy settings, such as most browsers and some desktop software. Some command-line tools, games, store apps, or software with its own network stack may ignore system proxy. TUN mode captures a broader range of traffic through a virtual network interface, but usually requires extra permissions and may conflict with other VPNs, virtual adapters, or security software.
For this reason, start with system proxy during the initial setup. Once the subscription, policies, and DNS behavior are working, decide whether to enable TUN based on the applications you need to cover. Do not change ports, DNS, routes, and overrides at the same time; changing one variable at a time makes the source of a problem easier to identify.
These questions cover client selection, architecture checks, archived versions, and the configuration required after installation.
Start with Clash Plus from the list for your platform. It covers routine tasks such as importing subscriptions, choosing a mode, enabling system proxy, and configuring TUN. If you need a different desktop interface or override workflow, compare Clash Verge Rev and FlClash. Most desktop and mobile users do not need to download the Mihomo core separately.
The installer uses a wizard to place files in the application directory and create launch entries, making it suitable for regular use. A ZIP archive requires manual extraction and folder management, so it suits users who want to control the program location. Both formats use the same configuration logic; there is no need to install both.
Choose Apple Silicon for Macs with M1, M2, M3, and later M-series chips; choose Intel for older Macs with Intel processors. Open About This Mac in the system menu and check the chip or processor field before downloading.
This client is no longer actively maintained. The archived download is intended for migrating older configurations, checking interface locations, and supporting existing setups. For a new installation, choose the maintained Clash Plus, Clash Verge Rev, or FlClash rather than building a new setup around archived software.
The standalone Mihomo core is mainly intended for servers, routers, secondary routers, containers, and environments where users orchestrate services themselves. You must prepare the YAML configuration, startup arguments, directory permissions, and startup service. On desktop and mobile, a GUI client makes everyday switching and troubleshooting easier.
After installation, import a valid profile or subscription, choose rule mode, and enable system proxy or TUN mode according to the applications you need to cover. The client installer does not include a subscription service. If the import fails, check that the subscription URL is complete, the network is reachable, and the system time is accurate.