Clash Plus
A good choice for importing a subscription on Windows for the first time. Test the connection with the system proxy first; use TUN only if you need to route apps that don't read the system proxy settings.
Client Installers / Standalone Core
Choose your operating system, then check the CPU architecture. Use a GUI client on desktop or mobile; deploy Mihomo separately on servers and routers.
Desktop installers are for x64 systems. Open Settings → System → About and check System type before downloading.
A good choice for importing a subscription on Windows for the first time. Test the connection with the system proxy first; use TUN only if you need to route apps that don't read the system proxy settings.
For users who manage multiple configurations and want to inspect connection destinations and matched rules. After adding a subscription, select it and check that the connections panel shows the expected policy.
The installer is recommended for everyday use. If you choose the ZIP, extract all files to a permanent folder before running the app. Launching it from the archive preview may prevent it from finding files in the same folder.
Manage configurations and policy groups in a GUI. When migrating from another client, import a configuration and test the connection first, then migrate overrides to make incompatible fields easier to identify.
Use the archive to inspect a legacy setup or migrate configurations. For everyday use, choose a maintained client. Keep the original YAML during migration; don't import the old client's UI preferences as core settings.
When switching clients, quit the old app and turn off its system proxy before launching the new one. This prevents both clients from changing system proxy settings or listening on the same local port.
| Check | Selection criteria |
|---|---|
| OS version | Use a supported version of Windows 11 where possible. For Windows 10 compatibility, check the selected client's release notes. |
| System type | The desktop installers in this section are for x64, not native ARM64. |
| Permissions | The system proxy and TUN are different traffic-routing methods. If you enable the TUN service, grant permissions as prompted by the client. |
Check Chip or Processor under About This Mac. Choose ARM64 for Apple M-series Macs and x64 for Intel models.
Separate builds are available for ARM64 and x64. Open the disk image and follow the instructions in its window, then launch the client from Applications.
For users who want to inspect active connections and rule matches. The Apple Silicon download is a fallback link to the Intel build; x64 builds require a system that supports Rosetta.
A good fit for users who manage configurations on both desktop and mobile. The Apple Silicon download is a fallback link to the Intel build; check the architecture in the filename before installing.
Kept for migrating legacy menu bar client settings. Both download options link to the archived Intel build. For new deployments, use a maintained client and verify your configuration before removing the old app.
DMG is a disk image format, not a CPU architecture. If macOS reports a compatibility issue, check the OS version and chip type first. For a native ARM64 build, choose an installer explicitly labeled ARM64.
| Check | Selection criteria |
|---|---|
| Apple Silicon | Choose ARM64 when available. Running an Intel build requires Rosetta support. |
| Intel | Choose a disk image labeled x64, AMD64 or x86_64. |
| OS version | Minimum OS versions vary by release. Check the compatibility notes for the specific client version. |
Choose an APK that matches an ABI supported by your system. If unsure, select a universal APK when the client offers one.
For phones and tablets that support arm64-v8a. On first connection, check the app name in the system VPN permission prompt before granting access.
For configuration- and policy group-based workflows. A universal build reduces the chance of choosing the wrong ABI, but still requires a compatible minimum Android version for that release.
Choose between ARM64, 32-bit ARM and x86_64. For emulators, match the APK to the ABI supported by the emulator's system image, not the host computer's processor.
For users with an existing Surfboard-compatible configuration. Its configuration format differs from mihomo's; check your subscription format before migrating, and don't assume Clash YAML fields are supported.
When opening an APK from a browser or file manager, Android may ask you to allow installs from that source. You can revoke the permission after installation, then import a configuration in the app and connect.
| Check | Selection criteria |
|---|---|
| App architecture | Choose an ABI supported by your system: arm64-v8a, armeabi-v7a or x86_64. |
| OS version | Check the selected client's release notes for its minimum Android version. |
| VPN permission | Grant permission when prompted before connecting. If another VPN is already running, resolve the connection conflict first. |
Install from the App Store. Check the product page for compatibility and the required OS version.
Import a compatible subscription after installation. On the first connection, follow the system prompt to add a VPN configuration, then check the connection status and selected policy in the app.
On a device managed by an organization, installing apps or adding a VPN configuration may require administrator approval. Check the device's management policy if you run into restrictions.
| Check | Requirements |
|---|---|
| Device and OS version | Check the Compatibility section on the App Store product page. |
| VPN configuration | The system must allow the app to add a VPN configuration, which the user must approve. |
Check the release and architecture first. The GUI client builds are for x86_64 desktops; for headless systems, see the Mihomo Core tab.
Choose DEB for Debian and Ubuntu-based distributions, or RPM for Fedora and other RPM-based distributions. Desktop proxy settings work only with apps that honor them.
Install the local DEB with your distribution's package manager to resolve dependencies. If dependencies are unavailable, check your distribution version and repository configuration; don't bypass dependency checks.
Run uname -m to check the machine architecture, then read /etc/os-release to identify the distribution. Matching CPU architectures don't guarantee matching package formats, so check both.
| Check | Selection criteria |
|---|---|
| Machine architecture | Desktop builds are for x86_64 (AMD64), not AArch64. |
| Distribution | Choose DEB for Debian-based systems; RPM is available for compatible distributions using RPM repositories. |
| Desktop session | GUI clients require a desktop environment. The distribution's package manager will report any missing dependencies. |
The Mihomo core is intended for servers, routers and command-line environments. For everyday desktop or mobile use, choose a GUI client above; no separate core installation is needed.
Extract ZIP and GZ archives before use; install DEB packages with your system package manager. The standalone core requires a separate config.yaml; you manage its startup options and working directory.
| System | Architecture | Download |
|---|---|---|
| Windows | AMD64 | Download ZIP |
| Windows | ARM64 | Download ZIP |
| macOS | Intel | Download GZ |
| macOS | Apple Silicon | Download GZ |
| Linux | AMD64 | |
| Linux | ARM64 | Download GZ |
| Linux | ARMv7 | Download GZ |
| Linux | MIPS-softfloat | Download GZ |
Configuration Migration / First Connection
Get one configuration working first, then migrate the remaining subscriptions, overrides and startup settings.
Check your processor and OS architecture in system information. x64, x86_64 and AMD64 refer to the same architecture; AArch64 usually corresponds to ARM64. Even if your processor supports 64-bit apps, make sure your installed OS supports the package you choose.
Usually not. GUI clients with an integrated core let you import configurations and manage connections in the app. The standalone Mihomo core is intended for servers, routers and command-line environments deployed with a configuration file and service manager.
Client installers and subscriptions are separate. After installation, import a configuration file you maintain or a compatible subscription from your provider. Subscription URLs may contain credentials, so don't share them in public logs or screenshots.
Archived builds are useful for checking an older interface, migrating local settings or reproducing a legacy setup. For everyday use, choose a maintained client. After migration, verify that subscriptions and policy groups work before removing the old app and its proxy settings.
Quit the old client and check whether the system proxy or VPN still points to its configuration. Then verify the new client's local port, traffic-routing mode and policy selection. Change one setting at a time to identify whether the issue is the proxy entry point or a routing rule.