Client downloads · Platforms and architectures
Choose your operating system, then check the CPU architecture. Desktop and mobile users should choose a GUI client; server and router users can browse the standalone core packages.
First time using it? You’ll need to import a valid configuration after installing the client. Downloading the app alone won’t establish a connection. For the right order of operations—subscription, policy groups, and system proxy—see the subscription import guide.
Compare Clash clients →Desktop clients
The desktop installers below are for x64 systems. Check your system type under Settings → System → About. On ARM devices, don’t assume that “64-bit” in the processor name means x64.
A good fit for Windows users who want to start by importing a subscription. After installation, enable the configuration you need, then check the rule mode and system proxy. Follow the guide to enable TUN if you need to route more apps.
For desktop users who need configuration management, rule overrides, and service mode. Before installing the service or changing TUN settings, make sure you have administrator access. When migrating, keep your original subscription and override files—copying only the app’s settings isn’t enough.
A good fit if you want a similar setup experience across desktop and mobile. After importing a configuration, make sure a policy group is selected, then enable the system proxy. When switching clients, check the ports, DNS, and local overrides separately.
For users who want a dedicated desktop interface for managing configurations. After switching cores or importing an existing configuration, check the parsing results in the logs, then test rule matching. Not all configuration fields are supported by every core.
Archived for reproducing legacy environments and migrating configurations. For new installations, choose one of the clients above. Older cores may not support newer protocols or configuration fields, so don’t assume they’ll work with every feature in your current subscription.
| Check | How to choose | Before you install |
|---|---|---|
| Operating system | Use a supported version of Windows 10 or 11 where possible. Check the client’s release notes for its minimum version. | Install any required system updates first, and make sure the installer runs normally. |
| Processor | This section provides x64 / AMD64 packages, generally for 64-bit Intel and AMD PCs. | On Windows ARM devices, check app emulation compatibility first. No native ARM installer is listed here. |
| Proxy and permissions | The system proxy and virtual network adapter takeover are separate settings. | Quit other proxy clients first. Follow the prompts to grant permissions when installing a service or driver, or enabling TUN. |
After installation, keep rule mode enabled, check the local listening port, and then turn on the system proxy. If your browser works but Store apps can’t connect, see the Windows UWP loopback exemption guide instead of repeatedly reinstalling the client.
Desktop clients
Check your chip under Apple menu → About This Mac. M-series Macs use Apple Silicon; choose x64 for Intel Macs. Some links currently share the same x64 file; the download buttons identify the actual package architecture.
Separate installers are available for Apple Silicon and Intel. Open the disk image and follow the installer window to move the app to Applications. Launch it from there, import your configuration, and check the system proxy status.
For users who need desktop configuration management and rule overrides. Both architecture links currently point to an x64 file. Apple Silicon may require Rosetta to run it; this is not a native ARM64 build.
For users who want a similar configuration workflow across devices. Both the Apple Silicon and Intel links currently serve an AMD64 package. Confirm your system can run this architecture before installing, and follow system prompts for TUN permissions.
An archived option for legacy setups that rely on an existing menu bar workflow. Both links currently provide an x86_64 file. Users on newer systems should consider one of the clients above and back up their configuration before migrating.
| Check | Requirements and notes |
|---|---|
| macOS version | The minimum macOS version for GUI clients varies by release. Check the installer and client release notes; the DMG file extension alone doesn’t indicate compatibility. |
| Chip architecture | For M-series Macs, choose a package explicitly labeled ARM64; for Intel Macs, choose x64 / AMD64. Whether an x64 app runs on Apple Silicon depends on Rosetta and app compatibility. |
| System permissions | When launching the app for the first time, verify its source and read the system prompts. Network extensions, services, and TUN may require additional permissions. Avoid disabling macOS security features globally just to install an app. |
Quit the old menu bar client before updating so its process doesn’t keep the port in use. If the system proxy points to the old port, turn off the old proxy setting before enabling it in the new client.
Mobile clients
Most recent phones use ARM64. Choose armeabi-v7a for older 32-bit ARM systems. If you’re unsure, check your device architecture or choose a client that offers a universal package.
ARM64 installer available. After installing, import a subscription or local configuration and approve Android’s VPN prompt when connecting for the first time. For a persistent background connection, check the system’s battery and background activity settings.
ARM64, 32-bit ARM, and universal packages are available for users who need to match the installer to their device architecture. After importing a configuration, enable it before connecting. Connection notifications and logs can help confirm that the app is running in the background.
ARM64 and armeabi-v7a installers are available. If you’re importing a desktop configuration, check that its fields are supported first. App-level routing, background activity, and Android VPN settings need to be checked separately on your phone.
For Android users whose configuration format and rules are supported by Surfboard. Surfboard is not a drop-in replacement for a Clash YAML client. Before downloading, check that your subscription provider offers a compatible format to avoid import errors.
| Check | Requirements and notes |
|---|---|
| System and architecture | Check the installer prompt for the minimum Android version. A 64-bit-capable processor doesn’t necessarily mean the device is currently running a 64-bit system. |
| Installation permissions | When opening an APK from a browser or file manager, follow the system prompt to allow installs from that source. You can revoke the permission afterward if you prefer. |
| Connection permissions | Approve the VPN request when connecting for the first time. Other VPNs in the same user profile, some firewalls, and ad blockers may conflict with proxy routing. |
A dropped background connection doesn’t necessarily mean your subscription has expired. Check persistent notifications, background activity restrictions, and battery settings first, then review the logs. See the Android background and battery settings guide for details.
Mobile clients
Install Clash Plus from the App Store. Check the listing for current system compatibility, app updates, and availability. After installing, follow the in-app instructions to add a configuration.
Check device compatibility on the App Store listing and install the app. Open it, import a valid subscription, make sure the configuration is enabled, and then allow it to add a VPN configuration. To switch policies, use the app rather than repeatedly deleting the system configuration.
| Check | Requirements and notes |
|---|---|
| Device and system | Check the App Store listing for compatible devices and the minimum iOS version. Current store information takes precedence. |
| Configuration | Prepare a valid subscription or configuration supported by the app. Installing the app and getting proxy service are separate steps. |
| Network permissions | Follow the system prompt to add a VPN configuration the first time you connect. On managed devices, follow your organization’s device management policies. |
If you can’t connect after updating a configuration, check the app logs and confirm the subscription is valid, then review your policy selection. Avoid changing DNS, mode, and all your rules at once while troubleshooting, or it’ll be hard to tell what made the difference.
Desktop clients
Check your distribution’s package format, then confirm the architecture. The GUI client packages here are for AMD64 / x86_64. For headless servers, see the Mihomo core packages below.
DEB and RPM packages are available. Debian- and Ubuntu-based distributions generally use DEB; Fedora and other RPM-based distributions use RPM. Required desktop components and dependencies depend on both your distribution and the client.
An AMD64 DEB package is available for systems that support this package format and its desktop dependencies. Use your package manager to handle dependencies, then configure the source and local proxy settings after launch.
| Check | Requirements and notes |
|---|---|
| Distribution | You can’t convert a DEB to RPM, or vice versa, just by changing the file extension. Check your distribution, desktop dependencies, and package manager support before installing. |
| CPU architecture | Run uname -m to check your architecture. x86_64 matches the AMD64 packages here; aarch64 systems can’t run these x86_64 installers natively. |
| Network permissions | TUN may require a supporting service, specific capabilities, or administrator privileges. Whether the system proxy works also depends on your desktop environment and whether the target app reads that setting. |
Don’t let a GUI client and standalone core listen on the same port. If a background service is already running, check its status and listening address before stopping it or changing ports. This helps distinguish a port conflict from a configuration error.
Standalone runtime
For servers, routers, and users who manage their own configurations. Most desktop users should choose a GUI client above. A standalone core doesn’t provide the same graphical setup workflow; you’ll need to manage the configuration file, services, and permissions yourself.
| System | CPU architecture | Package format | Download |
|---|---|---|---|
| Windows | AMD64 | ZIP | Download Windows AMD64 |
| Windows | ARM64 | ZIP | Download Windows ARM64 |
| macOS | Intel / AMD64 | GZ | Download macOS Intel |
| macOS | Apple Silicon / ARM64 | GZ | Download macOS ARM64 |
| Linux | AMD64 | DEB | Download Linux AMD64 DEB |
| Linux | AMD64 | GZ | Download Linux AMD64 GZ |
| Linux | ARM64 | GZ | Download Linux ARM64 |
| Linux | ARMv7 | GZ | Download Linux ARMv7 |
| Linux | MIPS softfloat | GZ | Download Linux MIPS softfloat |
ZIP and GZ archives must be extracted, and the executable placed according to your system’s requirements. On Linux and macOS, check its execute permissions too. Install DEB packages with a package manager, then verify the configuration directory, startup method, and service status. A successful installation doesn’t mean the proxy is enabled.
First check that the YAML parses, then verify the listening address, port, and logs. The common mixed port is 7890, but check your actual configuration. Before enabling TUN, read TUN and Fake-IP; for DNS changes, see DNS configuration.
Keep your original configuration, then verify the new environment one step at a time. Check installation, configuration parsing, and traffic routing separately to narrow down issues faster.
Back up your subscription URL, local YAML, custom rules, and override files. Subscription links may contain private access credentials; don’t include them in public screenshots or logs. Settings exported by one client may not import cleanly into another, so keep the original configuration files.
Turn off the old client’s system proxy and TUN before quitting its background process. If the old service is still running, the new client may fail to start because a port is already in use. Don’t run two traffic-routing setups at once; they can cause routing loops, DNS issues, or conflicting proxy settings.
Import and enable your configuration first, then check the logs for parsing errors. Select a policy group, enable the system proxy, and visit your destination site. Consider TUN only if some apps still bypass the proxy. See the system proxy setup guide for details.
These answers cover choosing a package and installing it. For connection, rules, or DNS issues, see the Troubleshooting FAQ.
For Windows, macOS, Android, and iOS, start with Clash Plus. For Linux, consider Clash Verge Rev. Check your operating system and CPU architecture before choosing an installer. If you already have a configuration, back it up first and make sure the new client supports its fields.
x64 generally means a 64-bit Intel or AMD processor; ARM64 is for 64-bit ARM processors. Android’s armeabi-v7a build is for 32-bit ARM devices. The universal build includes multiple architectures and is usually larger. Check your system information and the installer’s actual contents to confirm compatibility.
For some clients, the Apple Silicon and Intel links currently point to the same x64 installer, as noted on the download cards. Running an x64 app on Apple Silicon may require Rosetta; check the app and macOS prompts for compatibility. For a native ARM64 build, choose an installer explicitly labeled ARM64.
The client installer does not include a proxy service. Import a valid subscription or local configuration, enable it, select a policy group, and then turn on the system proxy. For apps that ignore the system proxy, configure TUN if needed and check permissions, DNS, and routing.
Back up your subscription URL, local configuration, custom rules, override files, and any essential settings. Quit the old client before installing the new version. On first launch, check the ports and proxy mode. Don’t enable system proxy or TUN takeover in two clients at the same time.
Most users can use the core bundled with or managed by their GUI client; a separate core is usually unnecessary. Standalone Mihomo packages are mainly for servers, routers, and self-managed environments. You’ll need to provide the configuration, startup options, service management, and access controls yourself.