Choose a client for your operating system, then check your CPU architecture. For a first installation, start with a graphical client. For servers, routers, and command-line deployments, see the Mihomo core section.
Several clients may be available for the same platform; you’ll usually only need one. Interfaces and configuration management vary, and subscription compatibility depends on the configuration format and the core bundled with the client.
The graphical clients listed here have x64 installers. Check your system type under Settings → System → About. On ARM devices, also confirm x64 app compatibility—an x64 build is not a native ARM64 app.
For desktop users getting started with a subscription. After installation, add a configuration, then choose a proxy group and operating mode. If you need to route traffic from more apps, check the client’s TUN settings and permission prompts.
Official site: clashplus.io
A desktop client built on the mihomo core, suited to users who manage subscriptions, rules, and overrides. When migrating an existing setup, test the original subscription first, then restore local changes one at a time to avoid legacy scripts overwriting new settings.
A mihomo client with a cross-platform interface. A good fit if you want a similar workflow on desktop and mobile. You can reuse configuration files, but system proxy settings, background operation, and TUN permissions must be set up separately on each device.
A desktop client for managing Clash configurations through a GUI. Before using a specific protocol or advanced fields, check which core the client is currently using; the interface name alone doesn’t guarantee compatibility.
Kept for reproducing legacy setups and migrating configurations. Since Clash for Windows is discontinued, don’t expect ongoing compatibility updates or fixes for newer systems. For a new installation, choose one of the clients above. Existing users should back up their configuration directory first.
| Check | What to do |
|---|---|
| CPU architecture | The downloads in this section are x64 / AMD64. They don’t support 32-bit Windows. On Windows on ARM, check app and driver compatibility. |
| Windows version | Check the installer’s minimum Windows version. Older Windows releases may be missing required runtime components, so CPU bitness alone won’t tell you whether the app will run. |
| Installation and permissions | Run the EXE to install. System proxy access and TUN service permissions are different; install a service if prompted by the client. You don’t need to run the entire interface as an administrator all the time. |
| First-run check | Import a configuration and check the listening port before enabling the system proxy. If Store apps still can’t connect, check for UWP loopback restrictions or use TUN if needed. |
If you see a port conflict on startup, quit any older client and check its background services. Don’t let two clients change the system proxy at once. For help diagnosing the issue, see the Troubleshooting guide.
Check your chip under About This Mac in the Apple menu: choose a native ARM64 build for Apple silicon or x64 for Intel. Some download links here currently provide x64 files, as noted beside the buttons. Before using one on Apple silicon, check Rosetta compatibility.
Installers are available for Apple silicon and Intel. Open the disk image, move the app to Applications, then launch it and import your configuration. Follow macOS prompts for network extensions and system permissions.
Official site: clashplus.io
Manage configurations and rules through a desktop interface. Both architecture links in the current list point to x64 files. Apple silicon users should check Rosetta and client service compatibility; this is not a native ARM64 build.
A good fit if you want a similar experience across devices. Both macOS links currently provide AMD64 files, which require Rosetta on Apple silicon. Install according to the actual file architecture, then test proxy and network permissions.
An archived release for existing ClashX Meta setups. The current download is an x86_64 build, intended for reproducing legacy setups and migrating configurations. For a new installation, choose a maintained client. Back up your configuration and check compatibility before upgrading macOS.
| Check | What to do |
|---|---|
| Chip | Apple M-series chips use ARM64; Intel uses x64 / AMD64 / x86_64. These three x86 names refer to the same architecture here. |
| Windows version | Check the minimum macOS version listed for the app you downloaded. Network extension permissions on newer systems and runtime support on older systems may require separate checks. |
| Where to install | Open the DMG and drag the app into Applications. Don’t keep launching it from the mounted disk image, as this can cause confusion with update paths and permissions. |
| Security prompts | Verify the download source first, then read the specific message under System Settings → Privacy & Security. If macOS says the app is damaged or incompatible, investigate why instead of disabling system protections. |
The system proxy only affects apps that follow the operating system’s proxy settings. Terminal tools may need proxy environment variables set separately. Before enabling TUN, check whether another VPN or network filter is running.
Most recent Android phones use ARM64. Older devices may use ARMv7, and the Android version alone won’t tell you which. If you’re unsure, check the device’s CPU ABI or choose a universal build if the client offers one.
For ARM64 Android devices. After installation, import a subscription, start the proxy, and approve the system VPN connection request. For ongoing background use, adjust the app’s background permissions in your phone’s battery settings.
Official site: clashplus.io
A Clash Meta client for Android with configuration imports and rule-based routing. ARM64 is common on newer devices; ARM suits some older devices, and the universal build is an option when you can’t confirm the architecture.
For users who switch between desktop and mobile. Choose a build that matches your device ABI. You can import the same subscription on both, but app routing, notifications, background permissions, and VPN status must be configured separately on your phone.
An Android proxy app with a different configuration syntax, not a graphical front end for mihomo. Suited to users with Surfboard-compatible configurations. Clash YAML isn’t guaranteed to import as-is, so first check whether your subscription provider offers the right format.
| Check | What to do |
|---|---|
| Device ABI | arm64-v8a is ARM64; armeabi-v7a is 32-bit ARM. Choosing the wrong build may result in an installation or compatibility error. |
| Android version and install permissions | Check the minimum Android version listed by the installer. Grant permission to install unknown apps only to the browser or file manager you’re using to open the APK. |
| Updating the app | An in-place update requires a compatible package name and signing certificate. If signatures conflict, back up your configuration and verify the download source before uninstalling; uninstalling may erase local data. |
| VPN and background use | Approve the system VPN request when enabling the app. Another VPN may already be using the same service. If Android stops the app in the background, check battery optimization, background activity, and notification permissions. |
A successful installation doesn’t mean your subscription works. Update the configuration, then check rules, proxy groups, and logs. If battery use seems high, compare idle and active use instead of repeatedly switching DNS modes to guess at the cause.
Install Clash Plus from the App Store. The store listing shows compatibility requirements and app details for your device. After installation, import a subscription you’re authorized to use and approve the system request to add a VPN configuration.
Manage subscriptions, proxy policies, and rule-based routing on your iPhone. Install and update through the App Store. Before connecting for the first time, check the configuration format, approve the VPN configuration prompt, then start the connection and test access.
Official site: clashplus.io
| Check | What to do |
|---|---|
| Windows version | Check the compatibility details on the current App Store listing. The store determines whether the app can be installed based on your device and system version. |
| Install from the App Store | Open the Clash Plus App Store listing and confirm the app name before installing. Install updates through the App Store as well. |
| Network permissions | Approve the system request to add a VPN configuration before connecting. If you use another VPN, check both connection states to avoid repeatedly switching control between them. |
| Prepare your configuration | Import a compatible subscription or configuration, then choose a proxy group. If the import fails, check that the link is valid, the format is supported, and the network can reach it. |
Start by testing the connection to a specific destination, then adjust rules and DNS. If your configuration includes desktop-only local paths, scripts, or port settings, check mobile support first. Don’t assume you can copy the entire file and start it as-is.
The graphical installers below are for AMD64 desktops. Choose DEB for Debian- or Ubuntu-based distributions and RPM for Fedora and other RPM-based distributions. For headless servers and other architectures, see the Mihomo core section.
For Linux desktop users who want graphical configuration management. Choose DEB or RPM for your distribution and let the package manager handle dependencies. After first launch, check your subscription and listening port, then decide whether to use the desktop system proxy or TUN.
For cross-platform use on Debian-based desktops. Check that the required desktop libraries are installed. Command-line apps may not use desktop proxy settings, so check each tool’s proxy configuration if terminal traffic still fails.
| Check | What to do |
|---|---|
| CPU architecture | Run uname -m. If it returns x86_64, you can use the AMD64 builds in this section. Don’t install these x86 builds on aarch64. |
| Distribution and package format | Check /etc/os-release and use the DEB or RPM package for your distribution. Renaming the file extension won’t make an incompatible package install. |
| Desktop dependencies | Graphical clients require the appropriate desktop components. If installation fails, keep the missing-dependency details from the terminal and resolve them with your distribution’s package manager. |
| TUN permissions | Check /dev/net/tun, routing permissions, and service configuration. Running in a container is also subject to device passthrough and network permissions on the host. |
Desktop proxy settings, environment variables, and app-specific proxy settings are separate layers on Linux. If a browser works but terminal tools don’t, first check whether those tools read proxy environment variables, then consider adjusting your rules. Don’t change system-wide routing to fix a single app.
For server, router, and command-line use. The core has no graphical interface for managing subscriptions, so you’ll need to provide a configuration file, working directory, and startup service. For a typical desktop or phone, choose one of the graphical clients above.
| Platform | Architecture | File type | Download core |
|---|---|---|---|
| Windows | AMD64 / x64 | ZIP archive | Download Windows AMD64 |
| Windows | ARM64 | ZIP archive | Download Windows ARM64 |
| macOS | Intel / AMD64 | GZ archive | Download macOS Intel |
| macOS | Apple Silicon / ARM64 | GZ archive | Download macOS ARM64 |
| Linux | AMD64 | DEB package | Download Linux AMD64 DEB |
| Linux | AMD64 | GZ archive | Download Linux AMD64 GZ |
| Linux | ARM64 | GZ archive | Download Linux ARM64 |
| Linux | ARMv7 | GZ archive | Download Linux ARMv7 |
| Linux | MIPS softfloat | GZ archive | Download Linux MIPS softfloat |
| Check | Deployment notes |
|---|---|
| Prepare the files | Extract ZIP archives. Unpack GZ files to get the executable; on Linux and macOS, also make it executable. Install DEB packages with your package manager. |
| Configuration directory | Prepare config.yaml and a writable working directory. Keep relative paths such as rule-providers aligned with the working directory so the service can find the files at startup. |
| Before starting | Run mihomo -t -f config.yaml to validate the configuration. If the actual filename or path differs, use the correct path in the command. |
| Network and permissions | Check listening ports, firewall rules, and service account permissions. TUN needs additional network permissions. Don’t expose the external controller interface directly to the public internet. |
Start the core in the foreground and watch the logs first. Once the configuration loads successfully, set it up with a service manager. Before enabling startup on boot, also check the working directory, network readiness order, and log retention; a successful manual run doesn’t guarantee the background service will work.
Downloading the file is only the first step. Verify the subscription, proxy groups, and traffic routing separately so configuration issues aren’t mistaken for installer problems.
Add a link through the client’s configuration or subscription manager, update it, and set that configuration as active. If you import a local YAML file, check indentation, file encoding, and paths to external rule files. The client doesn’t provide proxy servers automatically; verify the subscription source, expiration, and access permissions. Keep credentials in subscription links private—don’t include them in public screenshots or support posts.
The configuration’s mixed-port is commonly used for combined HTTP and SOCKS listening, but the actual value depends on the configuration and client overrides. Don’t assume every client uses the same port. In rule mode, connections are matched in rules order; you also need to choose an available policy in the relevant proxy group. Check connection logs to see which rule matched, not just whether the interface says the client is running.
The system proxy works with apps that follow the operating system’s proxy settings; some command-line tools, games, and Store apps may ignore them. TUN handles traffic at the virtual network interface layer and requires additional permissions. It may also conflict with routes from other VPNs, virtual adapters, or security software. Test the basic configuration with the system proxy first, then enable TUN if needed. Avoid changing multiple network layers at once so you can still identify the cause of problems.
Record your current client settings and back up custom rules, overrides, and subscription sources. After updating, first verify that the original subscription loads, then restore local changes. Version labels describe the app release; installer filenames may also include a platform build number, so they don’t always match. When troubleshooting, note the app version, actual filename, and CPU architecture. See the Clash Meta Getting Started guide for the full workflow, or Troubleshooting for connection issues.
How to choose an architecture, migrate an update, and troubleshoot installation failures.
If you’re new to Clash, start with a graphical client. It offers subscription imports, proxy group selection, rule inspection, and logs. The Mihomo core is mainly for command-line, server, and router deployments, where you’ll need to provide your own configuration and startup method.
The graphical client provides the interface and system integration; the core reads the configuration and handles connections. They’re different software layers, so a compressed core download isn’t a complete desktop installer.
x64, x86_64, and AMD64 generally refer to the same 64-bit x86 architecture; they are not limited to AMD processors. ARM64 is 64-bit ARM, while ARMv7 is used by some 32-bit ARM devices. Check System type on Windows, About This Mac on macOS, or run uname -m on Linux. On Android, check your device specifications or system information.
Check the actual filename and package architecture too. If a download link currently provides an x64 file, don’t treat it as a native ARM64 build. Compatibility also depends on the operating system and the client’s service components.
The client reads your configuration and handles connections, but it does not provide proxy servers automatically. Import a subscription or configuration you’re authorized to use, choose a rule mode and proxy group, then enable the system proxy or TUN if needed. Subscription URLs may contain credentials, so don’t share them publicly.
If a subscription link returns a webpage instead of configuration data, check whether it has expired, requires a login, or whether the service offers a format compatible with your client. Reinstalling the client repeatedly won’t fix this.
Back up your subscription sources, custom rules, override files, scripts, and client settings. Configuration directories and override formats vary by client. When migrating, import the original subscription first, then restore custom changes one at a time. Don’t let two clients manage the system proxy or TUN at the same time.
After migrating, check that the old client’s startup entry and background services are disabled if you no longer need them, then remove the old setup. This helps prevent port conflicts and lets you refer back to the original settings if something goes wrong with the new configuration.
Check the OS version, CPU architecture, file extension, and download source first. On Windows, review the security prompt and error details; on macOS, check the specific message under Privacy & Security; on Android, check install-source permissions and signature conflicts; on Linux, review dependency errors from the package manager in a terminal. Don’t disable system security features outright.
If a download is interrupted or the file won’t extract, download the correct file again. If the app launches but can’t connect, troubleshoot the subscription, ports, DNS, and routing instead. Successful installation and a working connection are two different things.
Archived releases are mainly for reproducing existing setups, compatibility testing, and configuration migration. They’re no longer maintained, so don’t expect compatibility with newer systems or ongoing fixes. For a new installation, choose a maintained client and back up your old configuration before migrating.
Older cores and mihomo may support different protocols and configuration fields. Don’t copy the client’s private data directory wholesale. Import the original subscription first, confirm it parses and connects correctly, then migrate custom rules and overrides.
For other configuration issues, see Troubleshooting.