Choose a package by operating system and CPU architecture. Use a GUI client on desktops and mobile devices; for servers, software routers, and command-line environments, choose the Mihomo core below.
Before installing, confirm your operating system, CPU architecture, and package format. Version details load from the download manifest; if it is temporarily unavailable, the complete package links on this page remain available.
Platform tabs update the URL anchor so you can save or share the download section for a specific system. A client card shows its version only when the remote manifest returns a valid version.
Windows 10 and Windows 11 users should generally choose the x64 installer. After installation, import a subscription or local configuration and enable the system proxy. To route more application traffic, use TUN mode only after confirming the driver and permissions are working.
| Check | Recommendation |
|---|---|
| Operating system | Windows 10 / 11, 64-bit |
| Processor | Choose x64 for common Intel and AMD devices |
| Installation permissions | Administrator privileges may be required to install services or enable TUN |
A GUI client for everyday desktop use, with configuration imports, proxy selection, system proxy controls, connection logs, and common settings. A good fit for Windows users who want a clear first-time setup.
A desktop client built on the Mihomo core for users who need rule mode, proxy group switching, configuration overrides, and TUN controls. This page provides the Windows x64 installer.
A GUI client for multiple desktop and mobile platforms, with a largely consistent interface across systems. On Windows, choose the installer or download the archive and run it after extraction.
Desktop features include subscription management, configuration switching, proxy group controls, and connection status. Suitable for users who understand rule mode and proxy groups and want to try a different desktop workflow.
A legacy Windows GUI client retained mainly for restoring older environments and migrating configurations. For new installations, choose a maintained client; during migration, reimport the subscription and manually verify overrides, DNS, and TUN settings.
First check the chip type in About This Mac. M1, M2, M3, and M4 models use Apple Silicon, so choose the ARM64 package; older Intel Macs need x64. If macOS displays a security prompt on first launch, review the app source under Privacy & Security in System Settings and follow the on-screen instructions.
| Device type | Package |
|---|---|
| Apple chip | ARM64 / Apple Silicon |
| Intel chip | x64 / Intel |
| Install format | Open the DMG and move the app to Applications |
A macOS GUI with standard proxy controls. Choose the package that matches your chip, then use the menu bar or main window to switch proxy groups and system proxy status after importing a configuration.
A desktop Mihomo GUI with controls for rules, proxy groups, system proxy, TUN, and configuration overrides. The two download buttons correspond to the Apple Silicon and Intel entries in the manifest.
A good choice for users who want a similar workflow on desktop and mobile devices. After installation, grant the network permissions requested by macOS, import a configuration, and check that the proxy port is listening.
A legacy macOS menu bar client, retained for older devices and configuration migration. For long-term use, migrate subscriptions and custom rules to a maintained client.
Recent Android phones and tablets generally use arm64-v8a. Choose armeabi-v7a for older 32-bit devices, and use the universal package only when you cannot confirm the architecture. On the first connection, Android will request VPN permission to create the required local virtual network interface.
| Architecture | Compatible devices |
|---|---|
| arm64-v8a | Most modern Android phones and tablets |
| armeabi-v7a | Older 32-bit ARM devices |
| universal | Universal package for unknown architectures |
A client for modern Android ARM64 devices, with configuration imports, proxy group selection, connection controls, and runtime information. Check the device information to confirm a 64-bit ARM processor before downloading.
A popular Mihomo GUI for Android, offering ARM64, 32-bit ARM, and universal packages. Choose the file that precisely matches the device architecture to reduce download size and avoid incompatibility.
Provides ARM64 and 32-bit ARM packages, with a configuration workflow similar to the desktop version. After importing a subscription, confirm that proxy groups have loaded before starting the connection.
A rule-based proxy client for Android, suitable for users with compatible configurations. Import a configuration after installation and approve network access when Android displays the connection permission dialog.
Install Clash Plus on iOS and iPadOS through the App Store. On the store page, verify the app name and developer information, then import a configuration after installation. The first connection will ask you to approve adding a VPN configuration.
| Item | Details |
|---|---|
| Device | iPhone / iPad |
| Installation channel | App Store |
| Configuration method | Import a subscription URL or supported client configuration |
A proxy tool for iPhone and iPad, installed from its App Store listing. After installation, import a usable configuration and choose rule mode, proxy groups, and connection status according to your needs.
Debian, Ubuntu, and derivatives generally use DEB; Fedora and RHEL-based distributions can use RPM. Desktop users should choose a GUI to manage subscriptions, the system proxy, and proxy groups; for servers, see the Mihomo core section below.
| Distribution type | Recommended format |
|---|---|
| Debian / Ubuntu | AMD64 DEB |
| Fedora / RHEL | x86_64 RPM |
| Other desktop distributions | Choose a compatible format based on the package manager and runtime environment |
A common Mihomo GUI for Linux desktops. This page provides AMD64 DEB and RPM packages, with no separate packages for architectures not listed in the download manifest.
Provides Linux AMD64 packages in DEB, RPM, and AppImage formats. Prefer the format that matches your distribution’s package manager; AppImage suits desktop environments that favor a self-contained executable.
The Mihomo core is intended for servers, routers, containers, scripted deployments, and command-line users. It has no full desktop management interface, so prepare a YAML configuration, working directory, startup arguments, and process manager. Most computer and phone users should choose a GUI above.
| System | CPU architecture | Format | Download |
|---|---|---|---|
| Windows | AMD64 | ZIP | Download AMD64 |
| Windows | ARM64 | ZIP | Download ARM64 |
| macOS | Intel AMD64 | GZ | Download Intel |
| macOS | Apple Silicon ARM64 | GZ | Download Apple Silicon |
| Linux | AMD64 | DEB | Download DEB |
| Linux | AMD64 | GZ | Download AMD64 |
| Linux | ARM64 | GZ | Download ARM64 |
| Linux | ARMv7 | GZ | Download ARMv7 |
| Linux | MIPS softfloat | GZ | Download MIPS softfloat |
GUI clients integrate core startup, configuration switching, proxy group selection, system proxy, TUN, and logs. If you only need to import a subscription and switch routes on a personal computer, a GUI is easier to maintain and avoids manually writing service and permission rules.
When running on a server, define the configuration path, working directory, listen address, and log location. Use the operating system’s service manager to keep the process running. After editing YAML, check indentation and field references before reloading to prevent startup failures.
The same client name does not mean every package fits your device. Check the following in order to avoid architecture mismatches, incorrect package formats, and missing configuration steps.
First identify whether the device runs Windows, macOS, Android, iOS, or Linux. On desktops, also confirm that the version is currently supported; older systems may lack required runtimes, system extensions, or network interface capabilities. Linux users should also check whether the distribution uses DEB, RPM, or is better suited to AppImage.
Common Windows devices use x64; Apple Silicon Macs use ARM64 and Intel Macs use x64; most newer Android devices use arm64-v8a. Servers and routers may require distinguishing AMD64, ARM64, ARMv7, and MIPS. Choosing the wrong architecture may prevent the installer from launching or cause the system to report an incompatible file.
Personal computers and mobile devices usually benefit from a GUI, with dedicated controls for subscriptions, proxy groups, the system proxy, and logs. Run the Mihomo core directly only on servers, containers, software routers, or automation scripts. The core is not a stripped-down GUI package; it is a runtime component whose configuration and process must be managed separately.
The package contains only the client program, not a ready-to-use proxy configuration. After starting the client, import a legitimately obtained subscription URL or local YAML file. Once imported, confirm that the proxy list and groups appear, then choose rule, global, or direct mode for your use case.
For ordinary desktop apps, start by enabling the system proxy. Apps that ignore system proxy settings may need a separate proxy address, or TUN after you understand its routing impact. If a browser works but the terminal does not, check terminal environment variables, the local listening port, and the app’s own proxy settings instead of reinstalling repeatedly.
These questions cover client selection, architecture checks, configuration migration, and first launch. For in-depth guidance on routing rules, DNS, and proxy groups, continue to the FAQ.
For a Chinese-language GUI and common configuration controls, start with Clash Plus. Clash Verge Rev suits users who need Mihomo, configuration overrides, and TUN controls; FlClash offers a similar workflow across platforms; Clash Nyanpasu provides another desktop interface.
Clash for Windows is no longer maintained; its download is mainly for restoring older environments and migrating configurations. Do not build a long-term setup around it for a new installation. Before migrating, save the subscription URL, custom rules, DNS settings, and overrides, then restore them item by item in the new client.
Open About This Mac or the System Information page from the Apple menu and check the Chip or Processor field. Choose ARM64 or Apple Silicon when an Apple M-series chip is shown; choose x64 or Intel when it says Intel.
If the package architecture does not match the device, the app may fail to launch or require an additional compatibility layer. The safest approach is to choose the file directly from System Information rather than guessing from the Mac’s appearance or purchase year.
Most Android phones and tablets released in recent years use arm64-v8a, so ARM64 is usually the right choice. Older 32-bit ARM devices use armeabi-v7a. The Universal package supports a wider range of devices and is useful when the architecture is unknown, but it is typically larger.
If Android reports that the app is incompatible with the device, return to the device information page and verify the Android version and CPU architecture. Changing the client configuration will not fix an incorrectly matched package.
A GUI client adds subscription management, proxy group switching, system proxy, TUN, logs, and update controls on top of Mihomo or a related core. It suits desktop and mobile devices; users generally do not need to write startup commands or maintain a background process themselves.
The Mihomo core runs mainly through the command line and YAML configuration, making it suitable for servers, routers, containers, and automation. Operators must manage configuration directories, permissions, startup, log rotation, and process restarts. For everyday personal computer use, choose a GUI client.
The client package provides only the program itself. After the first launch, import a subscription URL or local YAML configuration and wait for the client to parse its proxies and groups. Then choose a suitable policy and enable the system proxy or establish a VPN connection on mobile.
If the list is empty after import, check that the configuration URL is reachable, the YAML is valid, and the client log contains no parsing errors. If nodes appear but an app bypasses the proxy, check the system proxy, TUN, the browser’s independent proxy settings, and terminal environment variables.
In most cases, you can reimport the original subscription URL or YAML file, but the client’s interface settings, override scripts, system service state, and configuration directory will not automatically carry over. Before migrating, record the current mode, proxy group selections, DNS settings, rule overrides, and local ports.
After migrating, do not enable the system proxy or TUN in both clients at once; this can cause port conflicts and routing problems. Exit the old client first, then start the new one and check listening ports, proxy groups, and connection logs before handling the old configuration directory.
For system proxy, subscription updates, DNS, or TUN issues, browse the troubleshooting knowledge base by category.
View the FAQ