Installers · Architecture · Configuration setup
Choose your operating system, then select the processor architecture. Start with a graphical client for everyday use; for servers and routers, see the Mihomo core.
CLIENT PACKAGES
In package names, x64, amd64, and arm64 refer to processor architectures, not software tiers. Select a platform to see package formats and system requirements.
Open Settings → System → About to check your system type. The graphical clients here offer x64 installers; on an ARM device, first confirm that your system supports x64 apps. If you already use another proxy client, turn off its system proxy and auto-start settings to prevent conflicts.
Recommended for your first install. Download and run the installer, then add a subscription or local YAML file from the configuration page. Enable the configuration and select a rule mode before turning on the system proxy. If you need to route more app traffic, check the TUN permissions and service setup.
clashplus.io
For users who want granular configuration management, rule overrides, and desktop proxy controls. Save your existing configuration before switching, then check service status and listening ports after installation. The system proxy is usually enough for web browsing; enable TUN only if your apps require it.
For users who want a similar workflow on desktop and mobile. Choose the installer for a first-time setup; the ZIP archive must be extracted and the application folder managed manually. Either way, import a valid configuration first. The portable archive does not grant the system permissions required by TUN.
An alternative desktop interface for managing configurations and connections. Compare its workflow with other clients before choosing. After installation, check that your subscription loads correctly, then review your policy groups and rules. When switching clients, migrate the configuration you need rather than reusing the entire old application folder.
Archived download for compatibility checks and migration from existing setups. This older client differs from current mihomo releases in core capabilities and configuration support, and may not parse newer rule fields. For a first install, choose one of the clients above. Before migrating, export your configuration and verify DNS and rule behavior one item at a time.
| Check | What to choose or do |
|---|---|
| Operating system | We recommend a supported version of Windows 10 or 11. Check the selected client’s installer for its minimum version. |
| Processor | These packages are x64 / amd64 (64-bit x86) and won’t run on 32-bit Windows. |
| Permissions and ports | The system proxy is usually enabled in the client settings. TUN or background services may require administrator approval. If startup fails, check the logs for port conflicts. |
Open About This Mac from the Apple menu. Choose the matching download for Apple silicon or Intel. Open the downloaded DMG, then move the app to Applications before launching it instead of running it from the mounted disk image.
Separate downloads are available for Apple silicon and Intel. For your first install, choose the one matching the processor shown in About This Mac. After launching the app, add a subscription and enable the configuration, then check policy groups and the system proxy. To use TUN, grant the permissions requested by the client before testing the connection.
clashplus.io
For desktop users who need configuration overrides and detailed proxy controls. Both downloads in the current list point to x64 DMGs; check Rosetta compatibility before using them on Apple silicon. After installation, check service permissions. If a configuration change causes problems, review the logs before enabling network routing features one at a time.
For users who want a familiar interface and configuration workflow across desktop and mobile. The current listing provides an amd64 DMG for both processor options; the Apple silicon download is also this compatibility package, so check Rosetta support first. Quit the client before moving the app or updating it to avoid running a process from the old path.
Archived download for users with an existing menu-bar workflow. Both processor options provide an x86_64 DMG; Apple silicon users should check compatibility first. If the older client encounters new configuration fields, check the parsing logs. Before migrating, keep your subscription and custom rules rather than copying only the app.
| Check | What to choose or do |
|---|---|
| macOS version | Check your macOS version in About This Mac. Minimum versions vary by client; follow the compatibility notice in the installer over general recommendations. |
| Processor architecture | For Apple silicon, choose a package explicitly labeled arm64. x64, amd64, and x86_64 are Intel architectures and generally require Rosetta for compatibility. |
| First launch | Verify the app’s source, then follow any authorization prompts under Privacy & Security. If macOS reports that the app is damaged or incompatible, download it again and check the system requirements instead of disabling system security. |
| Network routing | Test your configuration with the system proxy first, then enable TUN if needed. If multiple clients are changing proxy or DNS settings, quit the others before troubleshooting. |
Most recent phones support arm64, but check the app ABIs supported by your system. After downloading the APK, temporarily allow your file manager or browser to install apps when prompted. On the first connection, approve Android’s VPN request and check the client’s connection status.
This arm64 APK is for devices whose systems support 64-bit ARM apps. After installation, import a subscription from the configuration page and enable it before connecting. To keep the connection active while the screen is locked, check your system’s battery management and background app settings. Adjust app routing as needed.
clashplus.ioOffers arm64, ARM, and universal APKs. If you know your device’s architecture, choose the matching package; if not, try the universal version and check compatibility during installation. After importing a local YAML file, make sure any referenced rule sets can be downloaded so routing resources are ready when the configuration is enabled.
For users who want a similar setup on desktop and mobile. Choose an APK for an architecture supported by your phone. When moving between devices, migrate subscriptions and rules, not desktop-specific network adapter names, paths, or permissions. If some apps still use your regular network after connecting, check app routing and the VPN’s coverage.
For Android users who need its supported configuration syntax and protocols. Surfboard uses a different configuration format from Clash YAML. Check the format provided by your subscription before downloading; changing the file extension alone won’t make it importable. If you already have a Clash configuration, prepare it in the required format before switching.
| Check | What to choose or do |
|---|---|
| System compatibility | Minimum Android versions vary by APK. If the installer reports incompatibility, check your Android version and the app ABI supported by your system. |
| Architecture | arm64-v8a is for 64-bit ARM apps; armeabi-v7a is for 32-bit ARM. A 64-bit processor doesn’t necessarily mean the system supports 64-bit apps. |
| VPN and background activity | The first connection requires VPN permission. Usually, only one VPN can be active for a user at a time; if connections conflict, quit other VPN apps first. |
Install Clash Plus from the App Store. Check the store listing for system compatibility before installing. When connecting for the first time, follow the system prompt to add a VPN configuration. Subscription links contain access credentials: use your own link and don’t share the full URL in screenshots or comments.
Install the app from its App Store listing, then add a subscription and enable the configuration. Confirm the VPN permission when prompted. If the configuration won’t parse, first check that the subscription uses a supported format. If the connection drops, check your network, subscription status, and app logs in that order.
clashplus.io| Check | What to choose or do |
|---|---|
| Device compatibility | Check the system version and device compatibility listed on the App Store page. |
| Installation and updates | Install and update through the App Store. Before updating, save any configuration you need to keep. |
| Connection permissions | Follow the system prompt to add a VPN configuration. Before connecting, check whether another VPN is already routing network traffic. |
First check which package format your distribution uses, then confirm your CPU architecture. DEB packages are for Debian, Ubuntu, and compatible distributions; RPM packages are for distributions that use RPM. The graphical installers here are amd64 / x86_64. For servers or other architectures, see the core downloads.
Available in DEB and RPM formats. Use your distribution’s package manager to install dependencies rather than simply extracting the application files. After launch, import a configuration and test the regular proxy. To enable TUN, check service permissions, virtual network interface support, and routing rules.
This amd64 DEB is for desktop users on a compatible package-management system. If startup fails, check dependency and display-environment errors before troubleshooting your configuration. Terminal apps may not use the desktop system proxy automatically; configure a proxy in the app or set up TUN for your deployment.
| Check | What to choose or do |
|---|---|
| Distribution and dependencies | Choose a client package that matches your distribution and let the system package manager handle dependencies. Check installation errors and the client documentation for specific runtime requirements. |
| Processor | uname -m shows your architecture. These packages are for x86_64 and can’t be installed directly on ARM or MIPS systems. |
| Desktop environment and permissions | Graphical clients require a compatible desktop environment. TUN requires system support and appropriate permissions; for command-line deployments, use the core instead. |
For servers, routers, and command-line deployments. Core packages don’t include a graphical interface for managing configurations, so you’ll need to set up the configuration directory, startup options, and service management yourself. For everyday desktop and mobile use, choose one of the graphical clients above; the core isn’t an application installer.
| Operating system | Architecture | Format and use | Download |
|---|---|---|---|
| Windows | AMD64 | ZIP · 64-bit x86 command-line environments | Download ZIP |
| Windows | ARM64 | ZIP · Windows on ARM | Download ZIP |
| macOS | Intel / AMD64 | GZ · Intel Mac command-line environments | Download GZ |
| macOS | Apple silicon / ARM64 | GZ · Apple silicon command-line environments | Download GZ |
| Linux | AMD64 | DEB · Debian-compatible package management | Download DEB |
| Linux | AMD64 | GZ · Manual deployment | Download GZ |
| Linux | ARM64 | GZ · 64-bit ARM environments | Download GZ |
| Linux | ARMv7 | GZ · Compatible 32-bit ARM environments | Download GZ |
| Linux | MIPS softfloat | GZ · Compatible soft-float environments | Download GZ |
| Check | Deployment notes |
|---|---|
| Operating system and ABI | The operating system, CPU architecture, and runtime environment must all match. Router models that look similar may use different architectures; check your firmware’s system information. |
| Prepare the configuration | Prepare config.yaml, check the listening ports, DNS, and rule resource paths, then test the configuration. |
| Services and permissions | Run it in the foreground first to check the logs and confirm it works, then set up a background service. Assess permissions separately before changing TUN or routing settings. |
| Controller API | Restrict the Controller API’s listening address and set access credentials. Never expose it directly to the public internet. |
See advanced mihomo configuration for deployment details. Keep a recoverable copy of your configuration before changing cores. Once tests pass, adjust auto-start and routing policies.
AFTER INSTALLATION
A successful installation only confirms that the program can start. Check the configuration, proxy routing, and rule matching separately; this usually helps pinpoint issues faster than repeatedly switching packages.
01 / PROFILE
Open the configuration page and paste a subscription URL or select a local YAML file. Once it finishes downloading, select that configuration and check for parsing errors. If the subscription returns a web page, login prompt, or another format, resolve the source or format issue before changing network modes.
See the import steps →02 / ROUTING
Start with rule mode and select an available policy in the policy group. On desktop, turn on the system proxy and test in a browser; on mobile, approve the VPN permission. Configure TUN only if an app doesn’t follow the system proxy or you need broader traffic routing. Change one thing at a time.
See Rules & Routing and TUN setup →03 / VERIFY
Visit a site you want to test, then check the destination domain, matched rule, and selected policy on the connections page. A working browser doesn’t mean every app is being routed. If something goes wrong, save the error details and determine whether the issue is configuration parsing, DNS, permissions, or connectivity before making targeted changes.
Visit the Help Center →DOWNLOAD FAQ
For Windows, macOS, Android, and iOS, start with Clash Plus. For Linux, consider Clash Verge Rev. Choose a package for your operating system and processor, then import your existing subscription. If your current client meets your needs, back up its configuration before deciding whether to switch.
Open About This Mac from the Apple menu to check your chip or processor. Clash Plus offers separate downloads for Apple silicon and Intel. The listed Clash Verge Rev, FlClash, and ClashX Meta downloads are x64 packages; check Rosetta compatibility before using them on Apple silicon.
arm64 is for devices that support 64-bit ARM apps; the ARM package is for compatible 32-bit ARM environments. If you’re unsure which app ABI your device supports, choose the universal package for Clash Meta for Android. Some phones have 64-bit processors but only support 32-bit apps, so check your system’s supported ABIs.
The client provides the interface and proxy runtime, but your subscription, proxy details, and routing rules come from a configuration. Open the configuration page to import a subscription URL or local YAML file, enable the configuration, then choose a policy group and rule mode. On desktop, enable the system proxy if needed.
Export your local configuration, rule overrides, and any settings you want to keep. Note the current system proxy, TUN, and port settings. Quit the old client before installing the update. When switching clients, check configuration paths and service permissions, then use the connection logs to confirm that rules and DNS settings are working.
For everyday desktop and mobile use, choose a graphical client to manage configurations, policy groups, and connections. The Mihomo core is intended for servers, routers, and command-line deployments; you’ll need to prepare the configuration, startup method, and permissions yourself. Check the operating system, CPU architecture, and runtime environment before downloading.