Choose your operating system first, then check your processor architecture. Graphical clients handle everyday subscription management and rule-based routing; the Mihomo core is for running a proxy service yourself.
Installers don’t include a subscription service. You can import an existing configuration after installation; if you’re new, see the user guide. Downloads are listed by client, and each project has its own release schedule and features.
The graphical clients below offer x64 installers. Check your system type under Settings → System → About and confirm that you have an x64-based processor. Windows on ARM app emulation does not guarantee compatibility with kernel services or virtual network adapters.
A good choice for setting up a day-to-day workflow, from installation to subscription import. After installing, import your configuration, select a routing mode, and verify the system proxy. Check the required permissions before enabling TUN to handle apps that ignore system proxy settings. See the official site for product details: clashplus.io.
For desktop users who want to manage mihomo configurations, rules, and connections. The installer and background service have different roles: opening the interface doesn’t mean the service has the permissions it needs. When enabling TUN for the first time, follow the client’s prompts to install or enable the service. Check that other VPNs or virtual network adapters aren’t also handling your traffic.
A good fit if you want a similar workflow across desktop and mobile. Here, AMD64 means the 64-bit x86 architecture and also works with Intel processors that support the same instruction set—it isn’t limited to AMD-branded devices. When migrating, import your subscription again and check proxy groups and DNS settings one by one instead of overwriting another client’s data directory.
Another desktop interface for managing configurations. Consider the interface separately from the capabilities of the underlying core: whether a subscription works depends on whether the core supports its node types and configuration fields. If you rely on complex overrides, scripts, or rule sets, keep your original configuration and test the import with a separate copy first.
For compatibility testing and reproducing configurations in existing environments only. The project is no longer maintained, so this archived release won’t receive ongoing feature or security updates. For newer protocols, core options, or operating system compatibility, consider one of the actively developed clients above. Before migrating, export your subscription, rules, and local overrides.
| Check | Before you install |
|---|---|
| Operating system | Use a supported version of Windows. Check the selected client’s current installer notes for its minimum version. |
| Processor | This section offers x64 / AMD64 graphical installers, not native Windows ARM64 installers. |
| Permissions and network handling | Running the interface and installing a service require different permissions. TUN or service mode may require administrator approval. |
If the app won’t start after installation, note the error and Windows version, then check the required runtimes. Don’t install multiple clients and enable each one’s system proxy at the same time.
Check your chip in the Apple menu under About This Mac. Choose a native ARM64 package for Apple M-series Macs and an x64 package for Intel Macs. Some links currently point to the same x64 file and are labeled as compatibility packages; they are not native ARM64 installers.
Choose a package for your chip, open the disk image, and move the app to Applications. Follow the system prompts to authorize it on first launch. After importing your subscription, test the system proxy before enabling TUN. Find product and platform details on the official site: clashplus.io.
For users who need desktop rule and configuration management. Both links currently point to the same fallback file: x64. Apple Silicon requires a compatible Rosetta environment; check separately whether the helper service and network extension are supported. For a native ARM64 package, see the Clash Plus download above.
A similar configuration workflow across platforms. The available macOS file is labeled AMD64, or x64, and the Apple Silicon link points to this compatibility package too. Before installing, confirm your system supports the required translation environment. When migrating from another client, recheck your selected subscription, DNS mode, and system proxy settings.
For users accustomed to the old menu bar workflow or reproducing existing configurations. The project is no longer maintained, and both links point to an x86_64 file. On Apple Silicon, check compatibility with Rosetta and any helper programs yourself. For a new setup, choose one of the clients above; support for a field in an old configuration doesn’t guarantee compatibility with newer protocols or operating systems.
| Check | Before you install |
|---|---|
| Chip architecture | Apple M-series chips use ARM64; Intel processors use x64. Check both the button label and the actual package architecture. |
| Operating system and translation | Check the app’s release notes for the minimum macOS version. Running an x64 package on Apple Silicon requires a working Rosetta environment. |
| Network permissions | Follow system prompts to authorize helper services or network handling. Read the reason for any security warning before responding; don’t disable system protections wholesale. |
Before upgrading, quit the old process and then replace the app to avoid leaving an old service using the port. Keep a configuration backup, and remove old installation files only after confirming the new version runs.
Most recent phones use ARM64, but choose a package based on the app ABIs your device actually supports. After downloading the APK, follow system prompts to allow installation from that source. Approve the VPN permission when connecting for the first time, and avoid having another VPN app take over at the same time.
Manage subscriptions, choose proxy groups, and control connections from your phone. This is an arm64-v8a package and won’t work on devices that support only 32-bit apps. Import your configuration before granting VPN permission. If the connection drops when the screen locks, check the system’s background activity restrictions. Official site: clashplus.io.
For Android users with existing Clash Meta configurations. If you’re unsure which architecture to choose, consider the universal package, but note that it’s usually larger and may not support every Android version. Before connecting, make sure the right configuration is active. Per-app routing and domain rules are separate settings, so check the apps being handled and the selected proxy group independently.
Offers a configuration workflow similar to the desktop version. Before choosing the 32-bit ARM package, confirm that your system supports that ABI; some newer devices support only 64-bit apps. If installing over another client results in a signature conflict, don’t uninstall right away. Export your configuration and confirm the backup can be restored before changing the download source or client.
For users whose configuration is supported by Surfboard. It’s not a replacement for a client that can read arbitrary Clash YAML files. Before importing, confirm that your service provider offers a compatible format. Converting a configuration may drop proxy groups, rules, or protocol settings. Check the converted content rather than assuming it’s compatible because the subscription URL opens.
| Check | Before you install |
|---|---|
| App architecture | arm64-v8a is 64-bit ARM; armeabi-v7a is 32-bit ARM. Both the device hardware and the system’s supported ABIs must match. |
| Operating system | Check the installer and client release notes for the minimum Android version. Older systems may not support newer packages. |
| Permissions | Permission to install from a source and VPN permission are separate. Background restrictions may also interrupt an ongoing connection. |
“There was a problem parsing the package” can indicate an incomplete download, an outdated system, or a package architecture mismatch. Check all three before trying another package.
Check the App Store for device compatibility and current availability. After installation, import a subscription or configuration. When connecting for the first time, follow the system prompts to add a VPN configuration, then confirm your proxy group selection in the app.
Manage subscriptions and proxy connections on an iPhone or compatible device. Refer to the App Store listing for current system requirements, supported devices, and availability. Installation methods and features differ between platforms; desktop file paths and service setup steps don’t apply here.
Before connecting for the first time, confirm in the app that your configuration imported successfully. A VPN indicator in the system status means network handling is active, but doesn’t prove a particular site matched the expected rule. Verify the result using the app’s connection details, rule matches, and your actual traffic route.
| Check | Before you install |
|---|---|
| Device and operating system | Check the App Store’s compatibility section to make sure your device and operating system version meet the requirements. |
| Configuration source | Prepare a subscription or configuration the client can read. App installation and subscription services are managed separately. |
| Connection permission | Approve the system VPN configuration prompt the first time you connect. When troubleshooting, quit other apps that are currently handling network traffic. |
If connection behavior changes after an app update, check the active configuration, proxy group, and routing mode first. Don’t delete a subscription that still works.
Choose a graphical client if you use a desktop environment. For server or router deployments, see the Mihomo core section. The graphical installers here are AMD64; first check your distribution’s package format, then verify desktop dependencies and service permissions.
Choose the DEB download for Debian, Ubuntu, and other DEB-based distributions. Choose RPM for Fedora, openSUSE, and other RPM-based systems, then check the dependencies. After installation, launch the app in your desktop session. TUN services need additional permissions; don’t run the entire graphical app as root long-term.
For AMD64 desktop environments that use DEB packages. Whether the system proxy affects a particular app depends on the desktop environment and whether the app reads proxy settings; command-line programs may need separate environment variables. If you need system-wide traffic handling, consider TUN and check for conflicts with DNS, routing, and existing container networks.
| Check | Before you install |
|---|---|
| Processor | This section offers AMD64 / x86_64 graphical installers. For ARM servers, see the matching architecture in the core section. |
| Distribution and dependencies | DEB and RPM packages aren’t interchangeable by changing the file extension. Use your distribution’s package manager to handle dependencies. |
| Graphics and permissions | Graphical clients need a working desktop environment and runtime dependencies. Configure permissions separately for service mode, TUN, and routing changes. |
Use uname -m to check the machine architecture reported by the kernel. Containers and specialized user spaces may require additional checks.
For users running services on servers or routers, or managing their own deployments. The standalone core has no full graphical configuration interface, so you’ll need to provide the configuration file, working directory, startup method, and access permissions yourself. Most users should choose a graphical client above.
| System | Processor architecture | Package format | Download |
|---|---|---|---|
| Windows | AMD64 / x64 | 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 AMD64 · DEB |
| Linux | AMD64 | GZ | Download AMD64 · GZ |
| Linux | ARM64 | GZ | Download ARM64 |
| Linux | ARMv7 | GZ | Download ARMv7 |
| Linux | MIPS · softfloat | GZ | Download MIPS softfloat |
| Check | Before deployment |
|---|---|
| Architecture and ABI | Check the system ABI as well as the instruction set. For MIPS, pay special attention to endianness and soft-float requirements; don’t choose based on the router brand alone. |
| Configuration and directories | Prepare a YAML configuration and specify the working directory, rule data location, and log output path. Test the configuration before adding a startup service. |
| Networking and permissions | Standard proxy ports and TUN traffic handling have different permission requirements. Check virtual network adapters, policy routing, and firewall rules separately. |
Graphical clients may bundle a core and manage its services themselves. Avoid replacing files directly in the app directory with a standalone core. For core families, protocol support, and configuration compatibility, see the technical reference.
Get one connection working before expanding traffic handling or adding complex rules. A completed installer doesn’t mean a subscription has been imported or that every app uses the same proxy settings.
Prepare your subscription URL or a local YAML file, import it from the client’s configuration page, and select it. After confirming the update succeeded, check that the proxy groups contain selectable nodes, then enable the system proxy or mobile VPN. Verify the result with both a real browsing test and the connection panel. A successful latency test only confirms that the test request reached its destination; it doesn’t verify every app’s connection.
View the complete setup guideBefore upgrading, save your subscription URL, custom rules, overrides, and port settings. When switching clients, interface options and configuration storage locations may differ. Test with a separate copy of your configuration before disabling the old client. Let only one program handle the system proxy or VPN at a time to reduce port conflicts, DNS changes, and routing issues.
Check Protocol and Core CompatibilityTroubleshoot in this order: choose a client, confirm the architecture, investigate installation errors, then verify the configuration. This helps keep installation issues separate from subscription problems.