Choose your operating system first, then verify the processor architecture. For desktop use, select a graphical client such as Clash Plus, Clash Verge Rev, or FlClash. For servers and routers, use the Mihomo core directly.
Platform labels are reflected in the address bar. Copy a link with its platform anchor to return directly to that system later. Each card lists the common installer first, with other architectures available as secondary options.
For a typical desktop, choose the x64 installer. The setup version adds a Start menu entry and guides you through deployment; the portable ZIP keeps everything in a separate folder, but updates and startup behavior usually require manual management.
Windows graphical clients
A good fit for Windows users who want to complete installation, import a subscription, and switch modes quickly. Download the x64 installer, follow the setup wizard, then add your configuration from the client’s subscription section.
mihomo desktop client
Provides convenient controls for rules, subscriptions, the system proxy, and TUN, making it suitable for desktop users who need to inspect configuration details and adjust mihomo options.
Cross-platform Clash client
The interface and workflow are broadly consistent across systems. Choose the installer for a fixed desktop setup, or the ZIP archive when you need to keep the client in a separate folder.
Windows desktop client
A good choice for users who prefer a dedicated desktop interface, configuration switching, and subscription management. Close similar clients before installation to prevent multiple programs from changing the system proxy at the same time.
Archived desktop client
This link is retained for legacy configuration migration and compatibility. For long-term use, move to a maintained client and record the existing subscription URL, port settings, and local override rules first.
First check the chip type in “About This Mac.” Macs with Apple M-series chips should use Apple Silicon or ARM64; Intel Macs should use x64. On first launch, macOS may ask you to approve app startup and network extension permissions.
macOS graphical clients
Provides separate builds for Apple Silicon and Intel. Open the DMG after downloading, move the app to Applications, then launch it and complete any permissions requested by macOS.
mihomo desktop client
Useful for managing subscriptions, rule modes, the system proxy, and TUN settings. The list keeps separate architecture links; still verify your Mac’s chip information before downloading.
Cross-platform desktop client
Suitable for users who want a similar workflow on desktop and mobile. After installation, import your subscription and choose the system proxy or TUN mode based on which apps need proxy access.
Archived macOS client
This link is intended for legacy compatibility and configuration migration. Before migrating, record the subscription URL, proxy mode, bypass list, and DNS overrides, then restore them individually in the new client.
Most recent Android phones use ARM64. Only older 32-bit devices need the ARM package; if you are unsure of the processor type, choose the universal build. After installation, allow the client to establish a local VPN connection.
Android graphical clients
Designed for mainstream 64-bit Android devices. Import your subscription after installation, approve the system VPN request on first connection, and configure per-app proxying and background permissions as needed.
mihomo Android client
Offers ARM64, ARM, and universal packages. Choose ARM64 for most current phones, ARM for older devices, and universal when the architecture is unknown or broader compatibility is needed.
Cross-platform Android client
A good fit for users who manage configurations on both desktop and Android. Physical phones usually use ARM64; older devices may use ARM, while a small number of x86_64 Android environments use the x64 package.
Android rule-based proxy client
Suitable for users with compatible configurations who want to manage rules and connections on Android. Before importing, confirm that the subscription or configuration format is supported by the client.
Clash Plus is available from the App Store. Open the app after installation, follow the system prompt to allow a VPN configuration, then import your subscription and choose the required proxy mode. Visit the domain link on the card for official website information.
iPhone and iPad client
Install through the App Store, add your subscription in the app, and approve the system VPN configuration request. For product details and platform information, visit clashplus.io.
Debian, Ubuntu, and related distributions typically use DEB; distributions using RPM package management should choose RPM. The graphical clients here target x86_64 desktops. For servers and routers, see the Mihomo core section below.
Linux desktop client
Suitable for standard Linux desktop environments. Choose DEB for Ubuntu, Debian, and Linux Mint; Fedora and RHEL-based distributions can use RPM.
Linux cross-platform client
Suitable for Debian- and Ubuntu-based desktop environments. Launch it from the application menu after installation, import your subscription, then configure the system proxy or enable the required traffic-capture mode for your desktop environment.
The standalone Mihomo core is intended for servers, routers, containers, bypass gateways, and users who maintain configuration files themselves. Desktop and mobile users should generally use the graphical clients above, which provide subscription, rule, log, start, and stop controls.
| System | Processor architecture | File format | Suitable environment | Download |
|---|---|---|---|---|
| Windows | amd64 |
ZIP | 64-bit Intel / AMD hosts | Download amd64 |
| Windows | arm64 |
ZIP | Windows on ARM devices | Download arm64 |
| macOS | amd64 |
GZ | Intel Mac | Download Intel |
| macOS | arm64 |
GZ | Apple Silicon Mac | Download Apple Silicon |
| Linux | amd64 |
DEB | Debian / Ubuntu servers | Download DEB |
| Linux | amd64 |
GZ | General x86_64 environments | Download amd64 |
| Linux | arm64 |
GZ | 64-bit ARM servers and router devices | Download arm64 |
| Linux | armv7 |
GZ | 32-bit ARMv7 devices | Download armv7 |
| Linux | mips-softfloat |
GZ | MIPS soft-float router devices | Download MIPS |
Extract the archive to obtain the executable. Linux and macOS usually also require execute permission; pass the configuration file path through the command line, service manager, or router plugin.
Suitable for environments using the Debian package-management system. After the package deploys its files, prepare the configuration directory, service permissions, and startup arguments for the actual runtime setup.
amd64, arm64, armv7, and MIPS target different instruction sets. An incorrect download usually will not start and may produce a format error or an unsupported executable message.
Windows desktop PCs typically use x64; Apple M-series Macs use ARM64; Intel Macs use x64. Android architecture names are easier to confuse: most recent phones are ARM64, older devices may still be 32-bit ARM, and emulators or a small number of specialized devices may use x86_64. If installation fails, recheck the architecture first rather than immediately changing subscription or network settings.
Running multiple clients can cause them to modify the system proxy repeatedly, compete for the same port, or create separate traffic-capture interfaces. Before moving to a new client, exit the old one and disable its system proxy and TUN mode. If it starts at boot, disable that as well so both programs do not run again after a restart.
A subscription can usually be fetched again in the new client, but local overrides, bypass domains, custom DNS, ports, and scripts may not migrate with it. Before switching clients, record the subscription URL and key settings; if you use a local YAML file, keep a copy of the original. After migration, test basic connectivity first, then restore advanced rules one by one to identify the setting causing the problem.
Rule mode determines where connections go according to rule sets. Global mode sends more traffic through the current proxy policy, while direct mode is mainly useful for temporary troubleshooting. The system proxy affects only apps that read the operating system proxy settings; TUN mode can capture more apps that do not. For everyday use, start with rule mode and the system proxy. After confirming that the browser works, decide whether games, command-line tools, or other apps require TUN.
These questions address the most common choices during downloading. For deeper guidance on subscriptions, rules, and troubleshooting, continue to the usage guides and FAQ pages.
For a conventional installation and a quick start, choose Clash Plus. If you need mihomo configuration features and a desktop management interface, Clash Verge Rev or FlClash are also options. Clash for Windows is no longer maintained and is suitable only for legacy configuration compatibility; it is not recommended as a long-term choice for a new setup.
Open “About This Mac” from the Apple menu to view the chip or processor information. If it shows an Apple M-series chip, choose Apple Silicon or ARM64; if it shows an Intel processor, choose Intel or x64. The wrong architecture usually prevents the app from launching—download the correct build instead.
Most recent Android phones use ARM64. Older 32-bit devices may use ARM, while the universal build is the safer choice when the architecture is unknown. Universal packages support more devices and are usually larger; if the device is confirmed to be ARM64, choose the matching build directly.
Usually not. Graphical clients such as Clash Plus, Clash Verge Rev, and FlClash already bundle the required components and provide interfaces for subscriptions, rules, logs, and start/stop controls. The standalone Mihomo core is mainly for servers, routers, containers, or environments where you maintain the startup configuration yourself.
Install and open the client, then paste the subscription URL from your service provider into the “Subscription,” “Configuration,” or “Profiles” page. Import or update it. Once the configuration loads, choose rule mode and the required policy, then enable the system proxy or client connection. Menu names vary slightly, but the workflow is broadly the same.
Being able to launch does not make a client suitable for long-term use. Unmaintained clients will not receive ongoing feature compatibility updates or bug fixes. During migration, export or record the subscription URL, local rules, ports, DNS, and bypass settings, then re-import them into a maintained client and verify each item.