iOS · macOS · Mihomo core
Choose your system first, then check the architecture. Apple users should start with Clash Plus; desktop and mobile clients are listed by installer, permissions, and configuration compatibility.
Client shelf
Use the tabs to switch platforms; platform anchors in the address bar can be bookmarked or shared. Each card shows the download first, followed by compatibility details. Quit other apps that manage network traffic before installing. After installation, import your own configuration and avoid enabling multiple system proxies at once.
All desktop client installers in this section are x64. Open Settings → System → About to check your system type before downloading. Windows on ARM devices require separate checks for emulation and driver compatibility; an x64 installer is not a native ARM64 app.
A good starting point for setting up a desktop proxy from a subscription. After installing, select a configuration and check that its proxy groups have an available outbound. For the first test, use the system proxy; enable TUN only if needed after confirming your browser connects.
For users who want to manage subscriptions, configuration overrides, and desktop traffic routing. TUN requires the client service and system permissions. If startup fails, check the service status and logs first instead of repeatedly switching configurations to work around a permissions issue.
For users who want a similar configuration workflow on desktop and mobile. You can reuse compatible subscription details when migrating, but window settings, service installation, and system proxy status must still be configured on this PC.
For desktop setups that need a graphical way to manage configurations and policies. Before using an older configuration, check which core is selected. Support for newer protocols and DNS fields depends on the core's capabilities, not just the client name.
Kept for migrating existing setups and referencing the legacy interface. For new installations, choose one of the clients above. Older cores may not parse newer protocols; if an import fails, check the unsupported fields and migrate to a compatible core rather than deleting required configuration.
| Check | Requirements & steps |
|---|---|
| Windows version | Use a version of Windows 10 or 11 that is still supported by Microsoft. Check the installer for its specific minimum requirements. |
| Processor | Installers in this section are x64 / AMD64 and cannot be installed natively on 32-bit Windows. |
| Permissions | Grant administrator permissions when prompted to install a service or virtual network adapter, or to enable TUN. Importing a configuration alone does not route network traffic through the client. |
| First connection test | Check whether another app is using the local proxy port. Test in rule mode before expanding the traffic being routed. |
For connection issues with Store apps, see the Windows installation and setup section. First determine whether the app is ignoring system proxy settings or the proxy node is unavailable; these require different fixes.
Open About This Mac from the Apple menu and check whether your chip is Apple M-series or Intel. Clash Plus offers arm64 and x64 builds. Compatibility builds listed on other cards currently point to x64 files; Apple Silicon devices may need Rosetta to run them.
Drag the app into Applications, then launch it from there. When prompted on the first network connection, approve the required permissions. Importing a subscription without starting the proxy will not automatically route app traffic.
For managing subscriptions and configuration overrides on macOS. Both links currently point to the same x64 file. Apple Silicon users should check compatibility requirements; the link label does not mean the build is native arm64.
For keeping a similar configuration workflow across devices. The current file is AMD64, which is equivalent to x64. System proxy settings, background services, and network permissions do not migrate with your subscription; set them up again on your Mac.
For migrating legacy menu bar workflows and configurations. Both links currently point to x86_64 files. If an OS upgrade causes permission or core compatibility issues, back up your configuration and move to a maintained client.
| Check | Requirements & steps |
|---|---|
| Windows version | Check the installer or app listing for the minimum macOS version. The file extension alone does not tell you whether it will work on an older system. |
| Apple Silicon | Choose a native arm64 build when available. If a compatibility link points to an x64 file, Rosetta and the client's own compatibility requirements apply. |
| Intel | Choose x64, AMD64, or x86_64; all three labels refer to 64-bit Intel architecture here. |
| Network permissions | Approve the service, VPN, or network extension required by the client. Not all clients use the same extension mechanism. |
Most recent phones use ARM64, but check your device's actual ABI. When installing an APK, grant install permission only to the browser or file manager you used to download it; you can turn that permission off afterward. On the first connection, approve the system VPN request. This is separate from importing a configuration.
For importing subscriptions and using rule mode on ARM64 phones. If the connection drops when the screen locks, check battery restrictions and background app settings, then review the logs. Reinstalling usually won't fix the system stopping background activity.
For users who want to use the Meta / Mihomo configuration ecosystem on Android. If you know your device architecture, choose the matching build. The Universal package is an alternative when the architecture is unclear; actual device support depends on installation and system requirements.
For users who want a similar workflow on phone and computer. After importing a subscription, check app-level VPN routing. If an app is excluded from the VPN, its traffic won't pass through the client even when the right proxy group is selected.
Uses a configuration format different from Clash YAML. Before choosing this client, confirm your subscription provider supports its format. Don't import a Clash configuration just by changing its file extension; protocol fields, policies, and rules must use syntax the client understands.
| Check | Requirements & steps |
|---|---|
| Windows version | The minimum Android version depends on the APK. If parsing fails, check your OS version, ABI, and whether the download completed successfully. |
| Install source | When prompted by Android, allow app installation only for the browser or file manager you are using. You don't need to grant this permission to other apps. |
| VPN permission | Approve the system VPN request on the first connection. Usually, only one VPN can route network traffic at a time. |
| Background activity | Check your device manufacturer's settings for battery optimization, background restrictions, and autostart permissions to prevent the service from stopping when the screen locks. |
For more on app routing, DNS, and background disconnects, see the Android configuration section.
Install Clash Plus on iPhone or iPad from the App Store. Check the store listing for device compatibility, system requirements, and current availability. After installing, import a compatible subscription, start the first connection in the app, and approve the system VPN configuration request.
Install and update through the App Store. After opening the app, import your configuration and check that its proxy groups and outbounds are recognized before connecting. The VPN icon confirms that a system tunnel is active, but not that the selected outbound is working; verify with a real connection test and the logs.
On iOS, the app uses a system network extension to create a tunnel. Desktop service installation and system proxy steps do not apply. Supported configuration fields and import methods depend on the app.
| Check | Requirements & steps |
|---|---|
| System & device | Check the App Store listing for the minimum iOS / iPadOS version and supported devices. |
| Install | Use the App Store link on this page to open the Clash Plus listing. Product information is available at clashplus.io. |
| Connection permissions | Approve the system VPN configuration request on the first connection. If another VPN is installed, check which one is currently active. |
| Prepare a configuration | Have a subscription URL you're authorized to use or a compatible configuration ready. Don't paste links containing access credentials into public pages. |
Follow the subscription import guide for step-by-step instructions. For system permissions and platform-specific details, see iOS installation and configuration.
This section covers desktop GUI clients; the installers target AMD64 / x86_64. Run uname -m to check your processor, then choose DEB or RPM for your distribution. For headless servers and routers, use the Mihomo core section instead of installing a desktop app.
DEB packages are for Debian- and Ubuntu-based systems; RPM packages are for distributions that use RPM. Let your package manager handle dependencies where possible. TUN and service mode require extra permissions; an open window alone doesn't mean traffic is being routed.
For managing subscriptions and policies on Debian- or Ubuntu-based desktops. Check distribution dependencies before installing, then test the GUI app and command-line programs separately; terminal tools may not automatically use the desktop system proxy.
| Check | Requirements & steps |
|---|---|
| Distribution | Check the package format and desktop dependencies. Don't install a DEB as an RPM, or vice versa, just by changing the file extension. |
| Processor | If uname -m returns x86_64, use the AMD64 build in this section. For other architectures, see the core section. |
| Permissions | Package installation usually requires administrator permissions. TUN also depends on device nodes, routing permissions, and the client's service implementation. |
| Traffic routing | The desktop system proxy, terminal environment variables, and transparent proxying are different mechanisms. Know which one you're testing. |
For installation commands and service startup, see the Linux installation and configuration section. When troubleshooting, check the process, listening ports, and configuration load status before investigating DNS and routing.
Mihomo is a configuration and network processing core, not a desktop management interface. These files are intended for servers, routers, and users who manage processes themselves; desktop and mobile users should choose a GUI client above. After downloading the binary, you'll still need to prepare a configuration, working directory, and service startup method.
| System | Architecture | 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 |
| Check | Requirements & steps |
|---|---|
| Runtime environment | The filesystem must allow execution, and the architecture must match the system. On Linux, also check runtime dependencies, TUN devices, and permissions. |
| Archive format | ZIP is an archive; GZ usually contains a single compressed binary. Identify the file after extracting it, then set its executable permission. |
| Configuration directory | Set clear locations for configuration files, rule resources, and logs. The service should use the same working directory as your manual tests. |
| Management API | Restrict the control interface to localhost or a trusted network, and configure access controls. Don't expose it directly to the public internet. |
Run the core in the foreground first to catch configuration errors; once it loads successfully, set up a background service. If managing system routes manually, record the original settings to avoid leaving broken routes when the process exits. For field definitions, see the quick reference.
After installation
01 / Import
Paste a subscription URL you're authorized to use into the client's configuration manager, or import a local file. Once parsing finishes, review any errors and confirm the configuration is selected. Subscription URLs may contain access credentials; remove sensitive information before sharing screenshots or backups.
02 / Route
Start in rule mode and choose an available outbound in the proxy groups. On desktop, check the system proxy; on mobile, approve the VPN request. Consider TUN only if you need to route all traffic. Every policy named in a rule must exist in the current configuration, or the configuration may fail to load.
03 / Verify
Test destinations that should connect directly and through the proxy, then check the logs to confirm which rules matched. Turn off the proxy and confirm your normal network connection is restored. If you can't connect afterward, check for leftover system proxy or route settings instead of resetting the entire device before troubleshooting.
For the full walkthrough, see the Clash subscription import and connection guide. For platform permissions, DNS, and port issues, see the cross-platform guide.
Download notes
Start with Clash Plus for Windows, macOS, Android, and iOS; for Linux, start with Clash Verge Rev. Check your device architecture and installation requirements before downloading. If your configuration relies on specific core fields, make sure the client's core supports them.
Open About This Mac from the Apple menu. If it lists an Apple M-series chip, choose the native arm64 build; if it lists an Intel processor, choose the x64 build. Some compatibility links currently point to x64 files, as noted on their cards. Apple Silicon may need Rosetta to run these apps, so don't infer binary architecture from the link label alone.
The client reads configuration, selects policies, and handles network requests; installing it does not provide a proxy service. Import a subscription you're authorized to use or a compatible local configuration. Check that its proxy groups include a working outbound, then enable the system proxy or VPN.
For your first setup, enable the system proxy and test with a browser that follows system proxy settings. If you need to cover apps that ignore those settings, install the required client service or grant administrator permissions, then enable TUN. Avoid running multiple proxy clients or VPNs while troubleshooting.
The Clash for Windows and ClashX Meta downloads are provided for migrating legacy setups and referencing older configurations. Older cores may not recognize newer protocols or fields, and OS upgrades can introduce compatibility issues. For a new device, choose a maintained client. Back up your configuration before migrating, and check proxy group names, ports, and rule references.
Note your subscription source, configuration name, current ports, proxy group selections, and local overrides. Use the client's export or backup feature to save your configuration. Quit the old client before installing the update; afterward, confirm the configuration loads, then check the system proxy, TUN, and DNS. Don't share backups publicly if they contain subscription URLs.