CLIENTS / PACKAGES
Choose your operating system, then download the installer for your processor architecture. For everyday use, choose a GUI client; for servers and routers, choose the standalone core.
These GUI installers are for x64 systems. Before installing, go to Settings → System → About and check your system type. On ARM devices, confirm x64 app emulation is supported; an x64 package is not a native ARM64 build.
A good choice for managing configurations through a GUI. After installation, import an existing subscription or local configuration, then choose a proxy group and rule mode. Enable TUN only if the app needs it to route traffic; there is no need to change every network setting on first launch.
clashplus.ioA desktop configuration manager built on Mihomo. If you already use Clash Verge Rev, keep your subscription and overrides before installing or updating. TUN services and the system proxy route traffic differently; if prompted for permission, first check which feature triggered the prompt.
Learn about TUN settings →A good fit if you want a similar interface across desktop and mobile. AMD64 means x86-64; it is not limited to AMD processors and also supports compatible Intel CPUs. After installation, make sure a configuration is selected before enabling the system proxy, so app requests are actually routed.
A desktop GUI option for users choosing a configuration manager based on its interface. When migrating, import your configuration rather than overwriting another client's entire data directory. Check core options, overrides, and app settings separately, and confirm the active core recognizes the configuration fields in use.
Kept for reference and migration from existing installations only. Clash for Windows is not equivalent to a current Mihomo client; older cores may not support newer protocols and configuration fields. For a fresh install, choose a maintained client above. After migrating, check ports, rules, DNS, and traffic-routing settings one by one.
| Check | Requirements and steps |
|---|---|
| Processor | These installers are primarily x64; confirm your architecture in System Information. |
| OS compatibility | Use a Windows version supported by the client's current release notes. Check runtime dependencies separately on older systems. |
| Permissions | Installing a service or enabling TUN may require administrator approval. |
| Configuration | Have a subscription URL or YAML file you are authorized to use, and make sure the local listening port is available. |
If your browser still bypasses the proxy after installation, first check that the system proxy is enabled and its port matches the client. Don't reinstall right away. Some apps ignore system proxy settings; in that case, consider whether TUN is needed. During troubleshooting, let only one proxy client route traffic to avoid competing changes to system settings.
Check the chip in Apple menu > About This Mac: choose Apple Silicon for an Apple M-series chip and Intel for an Intel processor. Check both the architecture label on the download link and the actual package architecture; some projects currently use the same x64 package for both links.
Separate installers are available for Apple Silicon and Intel. Open the disk image and follow the installer instructions to place the app, then launch it from Applications. Import a configuration and verify the connection first; grant network permissions only when a feature actually requires them.
clashplus.ioFor desktop users who rely on Mihomo configurations and overrides. Both links in the current listing point to the same x64 package; Apple Silicon devices may need Rosetta. Follow the app's launch prompts. Check system proxy and TUN separately: a running app does not necessarily mean traffic is being routed.
An option for a similar interface across devices. Both links currently provide an AMD64 (x64) package, not a native ARM64 build. On first launch, check that your subscription has loaded completely, then select a proxy group. When migrating from another tool, keep a backup of your configuration and check DNS and rules separately.
Kept for reference with older installations; not recommended for a fresh install. Both architecture links point to an x86_64 package. The older core does not support every configuration feature in current Mihomo. When migrating, check protocol fields and rule behavior; a successful import does not guarantee every setting is active.
| Check | Requirements and steps |
|---|---|
| Processor | Distinguish Apple Silicon from Intel; x64 packages may require Rosetta on Apple Silicon. |
| OS version | Check the app's current release notes; minimum requirements vary by client. |
| System permissions | Grant network permissions only for features you use, and keep macOS security checks enabled. |
| Install location | Follow the installer prompts to move the app to Applications; don't keep launching it from the mounted disk image. |
If a permission prompt appears, check the app name and the action being performed. Don't disable macOS security features just to launch a client. If traffic routing keeps failing, quit other VPN or proxy apps first, then check the current client's system proxy, service status, and logs.
Most recent phones use ARM64. Older devices may require an ARM package; if you can't identify the architecture, choose a universal package where available. Before updating an existing app, confirm the download source and signing are compatible, and back up your configuration.
This is an ARM64 package for compatible phones and tablets. Allow installs from the current download source when Android prompts you. After installation, import your configuration. The first connection usually triggers a VPN connection request; verify the app name before allowing it, then check the connection status in the notification shade.
clashplus.ioAvailable in ARM64, ARM, and universal packages. Choosing the matching architecture avoids an unnecessarily large download; use the universal package if you can't determine the architecture. After importing a subscription, select the right configuration and proxy group. Check per-app proxy inclusion and exclusion settings for your needs.
A good fit if you want to keep a familiar desktop workflow. Package architecture and Android version are separate requirements: matching the architecture does not guarantee your Android version is supported. If the connection drops when the screen locks, check battery optimization and background activity limits instead of repeatedly switching proxy nodes.
An alternative configuration tool for Android. Surfboard is not a Mihomo GUI client, so Mihomo YAML syntax is not necessarily supported. Check the configuration format and protocol support before importing; a Mihomo subscription is not automatically compatible with a different configuration ecosystem.
| Check | Requirements and steps |
|---|---|
| Architecture and OS version | Check whether you need ARM64 or ARM, and make sure your Android version meets the app's current requirements. |
| Install permission | Allow app installs from the current source in system settings; you can revoke this permission after installation. |
| Network access | Traffic routing through VpnService requires your approval of the VPN request. In most user environments, only one VPN can be active at a time. |
| Background activity | For persistent connections, check battery optimization, auto-start, and background activity settings. |
If Android says “App not installed,” check available storage, architecture, OS version, and the signature of any existing app before taking further action. Don't delete your configuration. If you need to uninstall the old app, export and back up your settings first. If some apps still connect directly, check the per-app proxy list and which rules are matching.
Install Clash Plus from the App Store. Check the app's store listing for supported iOS versions, device compatibility, and current availability. After installation, follow the app's prompts to add a configuration and grant the system permissions needed to connect.
After installation, prepare a configuration or subscription you are authorized to use. On the first connection, allow the app to add a VPN configuration when prompted by iOS, then return to the app and check its connection status. Installing the app and having access to a proxy service are separate things; a successful install does not provide server connection details.
When migrating from desktop, check protocol and configuration-field compatibility before importing a subscription. Don't carry desktop settings such as system proxy ports or service modes over to iOS. Update through the App Store, and keep a backup of any configuration you need before updating.
clashplus.io| Check | Requirements and steps |
|---|---|
| OS and device | Check the Compatibility section of the App Store listing to make sure your device meets the requirements. |
| Download source | Use the App Store link above and review the developer information and app listing. |
| Connection permission | Follow the app and iOS prompts to add a VPN configuration, then confirm which connection is active. |
| Configuration | Confirm the app supports your subscription format. Don't share links that contain personal credentials. |
If multiple VPN configurations are saved on your device, first check which one is active. For connection issues, check that the configuration loaded and the right proxy is selected in the app, then check the iOS VPN status. Avoid changing subscriptions, rules, and DNS all at once; otherwise it is hard to identify what caused the change.
These GUI packages target AMD64 desktop systems. Use DEB for Debian, Ubuntu, and other DEB-based distributions; choose RPM on RPM-based distributions. For servers, routers, and other architectures, see the Mihomo core tab.
Manage Mihomo configurations in a desktop environment. Install the local package with your distribution's package manager so it can identify missing dependencies; don't mix DEB and RPM packages. Tray icons, system proxy integration, and TUN permissions may depend on your desktop environment. Check each separately; a missing tray icon doesn't necessarily mean the core isn't running.
An AMD64 DEB package for compatible desktop distributions. Run uname -m before installing to confirm your architecture. After launching the app, import your configuration and check the logs. Browsers, terminals, and background services may use different proxy settings, so one app's behavior doesn't tell you how all system traffic is routed.
| Check | Requirements and steps |
|---|---|
| Processor | These packages are for AMD64 / x86_64; use the matching standalone core for ARM servers. |
| Package manager | Choose a DEB or RPM package supported by your distribution, and let the package manager handle dependencies. |
| Desktop dependencies | GUI clients require a compatible desktop environment and runtime components; check the app's release notes. |
| TUN requirements | TUN needs a supported device and the required network permissions. In a container, confirm that the device and capabilities are available. |
Linux desktop system proxy settings usually don't cover every command-line program. Terminal apps may use environment variables or their own proxy options, while system services may have separate environments. Decide which programs need traffic routed, then choose the system proxy, explicit proxy options, or TUN. Avoid stacking different methods, which makes troubleshooting harder.
For server and router users who manage their own processes. The standalone core has no GUI configuration manager: you need to prepare YAML, choose how it starts, and manage permissions yourself. For everyday desktop and mobile use, choose a GUI client above.
| Platform | Processor architecture | Package format | Download |
|---|---|---|---|
| Windows | AMD64 | ZIP | Download AMD64 ZIP |
| Windows | ARM64 | ZIP | Download ARM64 ZIP |
| macOS | Intel / AMD64 | GZ | Download Intel GZ |
| macOS | Apple Silicon / ARM64 | GZ | Download ARM64 GZ |
| Linux | AMD64 | DEB | Download AMD64 DEB |
| Linux | AMD64 | GZ | Download AMD64 GZ |
| Linux | ARM64 | GZ | Download ARM64 GZ |
| Linux | ARMv7 | GZ | Download ARMv7 GZ |
| Linux | MIPS softfloat | GZ | Download MIPS GZ |
First confirm your operating system and CPU architecture, then check the runtime environment. On Linux, uname -m can identify the architecture, but routers also require checks for instruction set, endianness, and floating-point ABI. MIPS softfloat does not support every MIPS device; a similar processor name alone is not enough to establish compatibility.
| Check | Requirements and steps |
|---|---|
| Runtime environment | Choose a binary for your OS and architecture, and confirm executable permissions and required resource directories. |
| Configuration file | Prepare valid YAML and check listening addresses, ports, proxy groups, and rule references. |
| Traffic routing | TUN requires OS support and the appropriate permissions. Keep a separate management connection for remote devices. |
| Persistent operation | Configure service management, log rotation, and restart behavior yourself. Avoid starting multiple instances. |
ZIP files need to be extracted. GZ files are usually compressed single binaries, not GUI installers. On Linux or macOS, grant execute permission to the extracted file at its actual location. First run it in the foreground to check startup and configuration parsing, then configure it as a system service. This makes the original logs easier to inspect if something goes wrong.
If you already have the executable and configuration, use this command to check the configuration. It assumes the current directory contains an executable named mihomo and a config.yaml file; adjust the paths before running it. A successful test confirms only that the configuration can be parsed; you still need to verify rules, DNS, and actual connection behavior.
./mihomo -t -f ./config.yamlThe client installer provides the software; proxy servers, credentials, proxy groups, and routing rules come from your configuration. Prepare a subscription or local file you are authorized to use, and check that the client supports its protocols and fields. Never paste subscription links into public screenshots, forums, or untrusted conversion services.
For your first launch, keep the configuration's existing rule mode. Check that the configuration loads and the right proxy is selected, then test access. The system proxy affects apps that follow that setting; TUN uses a virtual network interface and routing. Enable extra features only after deciding which traffic needs to be routed.
Before installing over an existing version, back up your subscription URL, local YAML, override snippets, and client settings. Record your ports, proxy mode, TUN, and DNS options. Also check whether the configuration is locally edited or generated by a remote subscription, so a future subscription update doesn't overwrite manual changes.
When switching clients, quit the old app first and confirm it has stopped changing the system proxy or routes. After importing your configuration into the new app, restore settings one by one rather than copying the entire data directory. See the getting started guide for installation steps and the subscriptions and configuration section for configuration fields.
First check package architecture and configuration source, then troubleshoot connection and permission issues.
For everyday desktop and mobile use, choose a GUI client to import configurations, switch modes, and view logs. The standalone Mihomo core is better suited to server and router users who manage their own configuration, processes, and routing. Downloading the software does not include a proxy service.
On Windows, check System type in Settings > System > About. On macOS, check the chip or processor in About This Mac. On Android, check your device's processor architecture. Most recent Android phones use ARM64; older devices may use ARM. On Linux, run uname -m to check the architecture: x86_64 corresponds to AMD64, and aarch64 to ARM64.
The client reads the configuration and handles connections; a subscription or YAML file supplies proxy servers, proxy groups, and routing rules. Import a configuration you are authorized to use, check the selected proxy group and mode, then enable the system proxy or the relevant traffic-routing feature. Subscription links may contain credentials and should not be shared publicly.
Both clients are discontinued. Archived downloads are kept here for migration and reference by existing users. For a fresh install, choose a maintained client. Before migrating, export your configuration and note your ports, proxy mode, and DNS settings. Do not assume an older client supports every configuration field in current Mihomo releases.
In the current download list, both macOS architecture links for Clash Verge Rev, FlClash, and archived ClashX Meta point to the same x64 installer. Apple Silicon devices may need Rosetta to run these packages; check the app's compatibility prompts. For a native ARM64 package, choose Clash Plus, which explicitly offers one on this page.
Back up your subscription URL, local YAML files, overrides, and client settings. Note your system proxy port and TUN and DNS options. Quit the old client before installing the update. After launching the new version, confirm the configuration loads and the right proxy is selected before restoring traffic routing. Avoid running two clients that both enable the system proxy or TUN.