Check your operating system and processor architecture first, then choose an installer.
Use a client on desktop or mobile; see the core section for servers and routers.
After installation, follow the setup guide to import a subscription or local YAML configuration.
Use the platform tabs to switch sections. Platform links in the URL can also be bookmarked or shared.
The graphical client installers in this section are x64. For your first install, start with Clash Plus; compare the other clients if you need to keep an existing workflow.
A good starting point for a first Windows install. After installation, import your configuration and check the proxy group and mode. Traffic from relevant apps only goes through the client after you enable the system proxy or another traffic-routing method. Back up local overrides and rules before updating.
Official site: clashplus.io
For users who manage subscriptions, overrides, and rules on desktop. Import an existing configuration separately, check that the current core supports all its fields, then enable the system proxy. TUN components may require elevated permissions. Quit other apps that are routing traffic before installing a service.
Choose the installer or ZIP archive. Extract the entire archive before running the app; don’t launch a single executable from inside the archive. Quit the client before moving its folder. Different installation methods don’t necessarily use the same configuration directory, so check where your data is stored before migrating.
An alternative for managing desktop configurations. When migrating, check subscriptions, core options, and global overrides separately. Don’t assume settings specific to an older client map directly to standard YAML fields. If a configuration fails to load, find the error line in the logs before addressing syntax or unsupported fields.
The archive is provided for migrating existing setups and checking compatibility; it’s not recommended as the default for new devices. Since Clash for Windows was discontinued, its older core may not support newer protocols or configuration fields. Export your subscription URL, local rules, and overrides, then import them into a maintained client and verify each item.
| Check | Before installing |
|---|---|
| Windows version | Use a supported Windows 10 or 11 system. Check the installer for each client to confirm its minimum version requirements. |
| Processor | This section provides x64 installers. Check Settings → System → About for your system type. On ARM devices, confirm compatibility with emulation separately. |
| Permissions and ports | System proxy and TUN have different permission requirements. If startup fails, check service status and listening ports; make sure multiple cores aren’t competing for port 7890. |
Start with rule mode to test the client. If an older client is still running in the background, disable its system proxy and quit the process before enabling the new client. Otherwise, quitting the old app may restore its previous proxy settings over the new ones.
Check your chip under Apple menu → About This Mac. The links follow the current download listings for Apple Silicon and Intel; some projects currently point both to the same x64 build. See each card for details.
Choose the DMG for your chip. Open the disk image and follow the prompts to move the app into Applications, then launch it from there. After importing your configuration, check the system proxy. If you need TUN, grant the requested network permissions when prompted; avoid changing multiple network settings at once.
Official site: clashplus.io
For managing desktop subscriptions and rules. Both chip links in the current listing point to an x64 file. Apple Silicon Macs typically need Rosetta to run it; the Apple Silicon link does not mean this is a native ARM build. Confirm the app launches successfully before importing an older configuration.
A good fit if you want a similar cross-platform interface. The current listing points both Apple Silicon and Intel links to an AMD64 file, which uses the x64 architecture. Before installing, check that your system and any required translation environment are supported. When switching clients, recheck the system proxy; importing a subscription alone isn’t enough.
Kept for reference with existing configurations and older setups. Both links currently point to an x86_64 archive. Apple Silicon users should check translation compatibility. As this client is discontinued, future macOS changes and compatibility issues with new fields may go unfixed. For a new install, consider one of the clients above.
| Check | Before installing |
|---|---|
| Windows version | Check that your macOS version meets the selected app’s minimum requirements; these vary by project. |
| Chip architecture | On Apple Silicon, choose a build explicitly labeled ARM64 when available. x64 apps typically require Rosetta. |
| Network permissions | Grant network component permissions when prompted by macOS. If the app won’t open, read the specific system warning rather than disabling system security features globally. |
Quit the old menu bar process before updating. If macOS says the app is still in use when you replace it, make sure its background services have stopped. After restarting, check whether your subscription, mode, and system proxy are still configured.
Most recent phones use ARM64, but check your device information to be sure. Before installing an APK, confirm the architecture and Android requirements. When connecting, approve the VPN permission prompt.
This link provides an ARM64 APK. After installing, import a subscription or local configuration, select a proxy group, then connect and approve the system VPN prompt. If the connection drops when the app moves to the background, check whether battery settings restrict background activity; there’s no need to keep reinstalling the app.
Official site: clashplus.io
Choose ARM64, ARM, or universal based on your device. The universal APK supports multiple architectures and is usually larger. After importing a configuration, select it manually and confirm the update succeeded. Saving a subscription URL doesn’t automatically activate that configuration.
Choose between ARM64 and ARM 32-bit builds. If the installer can’t parse the file or says it’s incompatible, check your Android version, CPU architecture, and whether the download completed. Stop any other active VPN connection before testing FlClash.
Available as an alternative configuration tool for Android. Surfboard uses a different configuration format from Clash YAML, so don’t assume the same file can be imported directly. Confirm that your configuration source provides a compatible format and check protocol support. After converting a configuration, review the meaning of its rules and proxy groups.
| Check | Before installing |
|---|---|
| System and architecture | Check your Android version and ABI in device information. A 64-bit processor doesn’t necessarily mean the system has a full 64-bit runtime. |
| Install permission | Allow the file manager or browser you’re using to open the APK to install apps, as required by Android. You can restore the original permission setting afterward. |
| Connection and background activity | Approve the system VPN request. Other VPN apps, Always-on VPN settings, and battery restrictions can affect connectivity. |
If an update fails because of a signature conflict, don’t delete the existing app right away. Back up your subscriptions and local configuration first, then check whether the installers came from different distribution channels or use different app IDs.
Install Clash Plus from the App Store. Check its listing for device compatibility, minimum iOS requirements, and current availability.
After installation, import a subscription or configuration you’re authorized to use, then follow the app’s prompts to add a VPN configuration and connect. Your device passcode or other system authentication may be required the first time. After importing, check the selected proxy group, connection status, and logs; a successful download doesn’t mean traffic is being routed yet.
Official site: clashplus.io
| Check | Before installing |
|---|---|
| System compatibility | Check the Compatibility section on the App Store listing to confirm that your iOS version meets the app’s current requirements. |
| Network permission | When connecting for the first time, allow the app to add a VPN configuration. Device management policies may restrict this permission. |
| Existing connections | Disconnect other VPNs before testing to prevent automatic connection rules from taking over network traffic. |
When switching from another client, reimport your subscription and check the proxy group names. App preferences, network extension settings, and local overrides may not transfer with a subscription.
This section provides AMD64 graphical clients. Check your distribution’s package format and desktop environment. For servers and routers, see the Mihomo core section below.
DEB packages are for distributions that use the DEB package system; RPM packages are for RPM-based distributions. Let your package manager handle dependencies. If desktop runtime components are missing, install the dependencies named in the error instead of running the entire app as root.
This link provides an AMD64 DEB package. After installation, launch the app from your desktop menu and import a configuration. The Linux desktop system proxy only affects apps that honor it. Command-line tools may need proxy environment variables set separately; the tray icon alone doesn’t confirm that all traffic is routed.
| Check | Before installing |
|---|---|
| Device architecture | Run uname -m; these packages target x86_64 and won’t run directly on aarch64 routers. |
| Package format and dependencies | Use a DEB or RPM package supported by your distribution and review the package manager’s dependency prompts. Compatibility varies by distribution. |
| Traffic routing permissions | TUN may require service permissions and changes to system routes. Test the configuration with a regular proxy first, then enable traffic routing as described by the client. |
A successfully launched graphical app doesn’t mean proxying is active in the terminal. Test your browser and command-line apps separately, checking app-level proxy settings, environment variables, and rule matches before deciding whether you need TUN.
For server, router, and self-managed service deployments. Most desktop and mobile users should use a graphical client above.
Mihomo is a proxy core, not a complete subscription management interface. Before running it, prepare a configuration file, data directory, and startup method. You’ll also need to manage the configuration’s listening addresses, DNS, and routing settings. Graphical clients usually bundle a core, so you don’t need to install one separately for your first connection.
Identify your operating system first, then check your CPU architecture and ABI. amd64 and x86_64 usually refer to the same architecture; on Linux, aarch64 typically means ARM64. ARMv7 and MIPS devices also depend on floating-point ABI, endianness, and system compatibility. Don’t choose a file based only on your router model or chip brand.
| System | Architecture | Format and use | Download |
|---|---|---|---|
| Windows | AMD64 | ZIP, x64 command-line core | Download AMD64 ZIP |
| Windows | ARM64 | ZIP, 64-bit ARM core | Download ARM64 ZIP |
| macOS | Intel AMD64 | GZ, Intel Mac command-line core | Download Intel GZ |
| macOS | Apple Silicon ARM64 | GZ, Apple Silicon command-line core | Download ARM64 GZ |
| Linux | AMD64 | DEB, install with a package manager | Download AMD64 DEB |
| Linux | AMD64 | GZ, standalone binary for manual deployment | Download AMD64 GZ |
| Linux | ARM64 | GZ, 64-bit ARM devices | Download ARM64 GZ |
| Linux | ARMv7 | GZ, compatible 32-bit ARM devices | Download ARMv7 GZ |
| Linux | MIPS softfloat | GZ, check endianness and floating-point ABI | Download MIPS GZ |
Before downloading, distinguish three things: the installer determines whether the app runs on your device, the core determines which protocols and fields it can parse, and the configuration controls how connections and routing work. You still need a valid configuration after installation. Switching clients won’t fix an expired subscription or an unreachable server.
Save your subscription URL, local configuration, rule overrides, and any proxy group selections you want to keep. Subscription URLs may contain access credentials; store them somewhere private and don’t include them in public screenshots or support posts. When switching clients, reimport the configuration instead of copying the entire app data directory. Each client may use different databases, service settings, and path formats.
After importing for the first time, confirm the configuration is selected and the logs show no parsing errors, then check rule mode and proxy groups. On desktop, start by testing the system proxy; enable TUN only if you need it. On mobile, approve the system VPN prompt. If you can’t connect, troubleshoot in this order: configuration loading, node connection, rule matching, then DNS resolution. Avoid changing several settings at once so you can compare results.
If port 7890 is in use, identify the process using it, then change mixed-port and update the system proxy or the port set in the app. See How to find and fix a port 7890 conflict for details, or follow the full Clash setup guide.
Most desktop and mobile users should start with a graphical client. Clash Plus is our top pick for Windows, macOS, Android, and iOS; Linux users can start with Clash Verge Rev. The Mihomo core is mainly for server and router users who manage their own configuration, startup options, and system services.
ARM64 is for 64-bit ARM devices. AMD64 and x64 usually refer to the same x86-64 architecture, not just AMD processors. Android universal APKs include multiple architectures and are usually larger. Check your system or device information before downloading; don’t choose based on the device brand alone.
Some clients’ current download listings point both the Apple Silicon and Intel links to the same x64 file. This page reflects those listings and notes the details on each card. Apple Silicon Macs typically need Rosetta to run x64 apps. If installation fails, check the file’s actual architecture and the client’s compatibility requirements.
Archived downloads for both are still available here and marked as discontinued. Older versions may not recognize newer protocols or configuration fields. For a new device, choose a maintained client instead. Before migrating, back up your configuration, overrides, selected proxy groups, and local rules.
The installer only provides the client; it doesn’t include a usable subscription or proxy service. Import a subscription you’re authorized to use or a local configuration, select a proxy group, then enable the system proxy or TUN if needed. If you still can’t connect, check the logs, port conflicts, and DNS settings.
Whether you can install over an existing version depends on the installer and the project’s release notes. Back up your configuration and local overrides, then quit the old process before updating. When switching clients, don’t copy the entire data directory. Import the configuration separately and recheck the system proxy, TUN permissions, and listening ports.
For other configuration and connection issues, see the FAQ.