CLIENTS / CHOOSE A PLATFORM
Choose your operating system, then check the processor architecture. For phones, start with Clash Plus. If you already have a configuration, choose a client based on core compatibility and your workflow.
These desktop installers are primarily for x64. Check your system type under Settings → System → About. If you have an ARM device, don't assume an x64 build is native.
A good place to start. After installation, import a subscription, select the configuration and enable the system proxy. The system proxy routes traffic only for apps that follow system settings; it does not cover every program. If needed, learn how to use the TUN virtual network interface.
For users who need subscription management, rule overrides and desktop services. Before enabling TUN, make sure the service component installed correctly. If the service won't start, check system permissions and existing virtual adapters; changing subscription settings won't fix a permissions issue.
For users who want a similar workflow on phone and desktop. AMD64 is the standard x64 architecture and also works with compatible Intel processors. When migrating, check ports, DNS and mode separately—don't just copy the server list.
Another option for managing desktop configurations. After importing for the first time, check which core the client actually uses and review the configuration. Support for advanced rules and protocols depends on the core; similar client names don't guarantee full compatibility between configuration fields.
Kept for restoring older setups and migration reference. For new devices, choose a client above. Before migrating, note your subscription source, rule overrides and policy group selections. Turn off the old client's system proxy and background services before starting the new one to avoid port conflicts.
| Check | Requirement and action |
|---|---|
| System and architecture | Use 64-bit Windows compatible with the installer you choose. Check the installer for the minimum supported version. |
| Permissions | Installing services or virtual adapters, or enabling TUN, may require administrator approval. Editing a subscription normally should not require repeated elevation. |
| Before connecting | Quit other proxy clients and check for port conflicts. Test in rule mode first, then decide whether to enable TUN. |
Check your chip under Apple menu → About This Mac. Apple Silicon refers to M-series chips; Intel Macs use x64. Check both the chip label on the download link and the file's actual architecture.
For M-series Macs, choose the native ARM64 build. Open the disk image and move the app to Applications, then launch it from there. When first setting up the system proxy or network service, follow the system prompts to grant permission. Avoid running a temporary copy directly from Downloads.
For desktop users who need subscription overrides and rule management. Both links currently point to the same x64 file. It may require Rosetta on Apple Silicon, so it is not a native ARM64 build. Check app and OS compatibility before installing.
For users moving from the mobile app who want a familiar workflow. Both the Apple Silicon and Intel links currently serve an AMD64 file; the Apple Silicon version may rely on Rosetta. After importing your configuration, check that the system proxy, DNS and startup settings are correct.
For restoring an existing setup or reference with older configurations only. Both links currently point to an x86_64 file; M-series Macs may need Rosetta. Before switching clients, turn off the old menu bar app's system proxy and back up any custom rules in its local configuration.
| Check | Requirement and action |
|---|---|
| Chip and OS | Check whether your Mac has an Intel or Apple Silicon chip. See the app's requirements for the minimum macOS version, and use a native build for your chip whenever possible. |
| x64 translation | Apple Silicon may need Rosetta to run x64 apps. Translation does not guarantee compatibility with every network service component. |
| Install and authorize | Move the app to Applications. If a security warning appears, verify the source and follow Apple's guidance; don't disable system-wide security protections. |
Most recent phones use ARM64. After installation, grant VPN permission. If the connection drops when the screen locks, check battery optimization and your manufacturer's background app restrictions.
A good choice for getting started on your phone. After downloading, grant temporary install permission only to the browser or file manager you're using; you can revoke it after installation. Import your subscription, choose a rule mode, approve the system VPN prompt when connecting, then test access.
For users who want to keep using Clash-style configurations. This is the Meta branch; don't assume it's identical to an older version based on the app name alone. When migrating, check rule sets, DNS and core-specific fields. If you're unsure which architecture you need, try the universal build.
For users who want a similar workflow across phone and desktop. Background operation requires OS permission. Before enabling Always-on VPN, make sure the configuration connects successfully; a bad setup can block all network access. If troubleshooting, restore a normal connection first.
Included as an alternative for a different configuration format. Surfboard primarily uses Surge-style configurations, so Clash YAML files cannot be imported as-is. Before using it, check whether your subscription provider supports the format and whether the required protocols and rules are available.
| Check | Requirement and action |
|---|---|
| System and architecture | Your OS must meet the selected APK's requirements. ARM64 needs an OS that supports 64-bit apps; for older devices, check the ARM or universal build. |
| VPN permission | Uses VpnService to create a local traffic tunnel and generally doesn't require root. Another VPN may conflict with the current client. |
| Background activity | Allow background activity and exempt the app from battery optimization if needed. Menu names vary by phone manufacturer. |
If the connection drops when the screen locks, check your system settings. See VpnService permissions and battery optimization exemptions for details.
Install Clash Plus from the App Store. Import your subscription after installation, then follow the system prompt to add a VPN configuration the first time you connect.
Check the App Store listing for system compatibility before installing. In the app, add a subscription or local configuration, enable it and choose a policy group. When iOS asks to add a VPN configuration, verify the app name before approving.
Official website: clashplus.io
| Check | Requirement and action |
|---|---|
| Compatible OS | Check the App Store listing for the minimum iOS version and supported devices. |
| Network permissions | The first connection requires adding a VPN configuration. This authorizes an OS-managed network extension; it does not install a root certificate. |
| Configuration setup | Prepare a compatible subscription or configuration file. After importing, confirm the correct configuration is enabled and avoid running another VPN at the same time. |
For desktop use, start with a graphical client. These packages target AMD64: choose DEB for Debian-based distributions and RPM for distributions that use RPM package management.
For desktop users who want a graphical interface to manage subscriptions and policy groups. Install with your distribution's package manager so dependencies are handled. Not all terminal tools follow the desktop system proxy. If you enable TUN, also check service permissions, routing and DNS interception.
For desktop distributions compatible with DEB packages and their dependencies. After installation, import a configuration in the GUI and test rule mode before changing startup settings. Don't run the entire desktop app as root just to make the interface launch.
| Check | Requirement and action |
|---|---|
| Processor | These GUI packages target AMD64. Check with uname -m; the common output x86_64 indicates this architecture. |
| Distribution and dependencies | DEB and RPM are package formats, not a guarantee that every related distribution is compatible. Follow the installer prompts for minimum library requirements. |
| Runtime environment | Requires a compatible graphical desktop and dependencies. For servers or routers, see the Mihomo core section to manage services yourself. |
This is a command-line core, with no subscription management interface. It's intended for users who manage network services on servers, routers or custom setups. Most phone and desktop users should choose a GUI client above; GUI means an app with a visual interface.
| System | Architecture and 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 Apple Silicon 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 softfloat GZ |
A GZ file usually extracts to an executable; it is not an installer that sets up a service for you. Prepare a configuration directory, set execute permissions and manage startup for your platform. Validate the configuration before enabling network interception. Don't expose the configuration's control interface directly to the public internet.
On Linux, TUN also requires the relevant device and network permissions. In containers, check device mappings and capabilities separately. Downloading a file for the right architecture does not configure the host network, DNS or routes for you.
Add a URL under Configuration or Subscription. Once the update succeeds, select and enable it. Seeing server names only confirms that data was imported; also check that every policy group referenced by your rules exists.
On phones, approve the system VPN permission. On desktop, check the system proxy first. TUN routes traffic through a virtual network interface; enable it only if needed, and avoid changing multiple settings at once.
Check for configuration errors first, then test the services you need. A latency test reflects only its specified test endpoint, not the speed of every website. If something fails, check the connection logs.
Start with Clash Plus on Windows, macOS, Android or iOS; Linux users can start with Clash Verge Rev. If you already use a client, back up your subscription URL, custom rules and DNS overrides before deciding whether to switch. The installer does not include a subscription service.
Most recent phones use ARM64; older devices may use 32-bit ARM. A 64-bit processor does not guarantee that the operating system supports 64-bit apps, so check your device's system information. If you're unsure, choose the universal build of Clash Meta for Android. It supports more architectures, but does not improve connection performance.
You'll need a working subscription URL or a local configuration file. In the client's Profile or Subscription page, import from a URL and enable the configuration, then choose a rule mode. Subscription URLs may contain personal credentials, so don't share them publicly. Supported fields vary by client; if an import fails, check the configuration format and core compatibility.
Android clients typically use VpnService to route traffic; iOS clients ask to add a VPN configuration. This is an OS permission step, not proof that you're connected to a remote server. Make sure the request comes from the client you just installed, then return to the app and enable the configuration. Stop any other active VPN first to avoid conflicts.
Choose a native build explicitly labeled arm64 whenever possible. Some macOS download links on this page currently point to the same x64 file, as noted on the cards. These builds may require Rosetta on Apple Silicon, and compatibility depends on the OS and app requirements. Don't assume a package's actual architecture from the chip label on its download button alone.
Archived clients are intended for restoring older setups or reference during migration, and aren't recommended for new devices. Mihomo is a command-line core for server and router users who manage their own configuration, services and routing. Most phone and desktop users should start with a graphical client.
Still can't connect after installation? See the FAQs. For platform-specific system settings, consult the full documentation.