Choose your operating system, then your processor architecture.
Import your subscription and configure the proxy after installation.
Run only one Clash client on a device at a time. Before switching clients, quit the old app and turn off its system proxy and TUN to avoid port conflicts or routing issues. Packages below are grouped by platform, with archived releases clearly marked.
This section offers x64 installers. Open Settings → System → About and check System type. Windows on ARM devices require x64 app compatibility; an x64 installer is not a native ARM64 build.
A good place to start if this is your first time using Clash. Run the installer, open configuration management and import your subscription. Then choose a rule mode and proxy group. Test the browser with the system proxy first; enable TUN later if needed, so you can tell configuration issues apart from routing issues.
A desktop option for managing configurations in a GUI and using local overrides. After importing a subscription, make sure the configuration is active. Follow the app’s prompts to grant permissions before using service mode or TUN. When migrating an old configuration, review DNS and overrides one by one.
A good fit if you want a similar experience on desktop and mobile. After installation, check the Configuration, Proxy and Settings pages. Don’t copy another client’s settings directory directly. Startup behavior is a local setting and won’t move with your subscription.
Another desktop GUI option. You can re-import an existing subscription; add local rules using a method supported by the new client. If startup reports a port conflict, quit other proxy apps first. Changing several ports at once can make the cause harder to find.
This archived release is available for recreating old setups and reference during migration. For a new installation, choose one of the clients above. Older cores may support newer protocols and rule fields differently. Keep backups of your original subscription and overrides; don’t copy the entire old app directory over the new client.
| Check | What to do |
|---|---|
| Operating system & architecture | Windows 10 or 11 is recommended; desktop installers here are x64. Check the installer for the minimum supported Windows version. |
| Permissions | System proxy and TUN have different permission requirements. Review system authorization prompts when installing a service or virtual network component. |
| After installation | Import a subscription, enable the configuration and select a proxy group. Once everything works, configure startup behavior to avoid launching with a broken setup. |
Check your chip under Apple menu → About This Mac. Apple Silicon-native packages differ from Intel x64 packages. Some clients below currently offer x64 files only; even on an Apple Silicon Mac, check Rosetta compatibility first.
Choose the DMG for your chip, open it and move the app to Applications. Approve any permissions on first launch, then import your subscription. Configure the system proxy and TUN separately. If you only need proxy access in a browser, start by testing the system proxy.
Manage subscriptions, rules and proxy settings in a GUI. Both links currently point to the same x64 file. On Apple Silicon, it may require Rosetta and is not a native ARM64 build. Check system compatibility before installing, and grant permission when prompted to enable the service.
A good choice if you already use FlClash. AMD64 in the filename means x64; it doesn’t mean the package only works on AMD processors. On Apple Silicon, check Rosetta compatibility first. After importing, review your proxy group selections and DNS settings.
Kept for migrating older setups and referencing legacy configurations; not recommended as the default for a new device. The current download is x86_64. When moving to a new client, quit the old menu bar app and turn off its system proxy before importing your subscription, so old proxy settings don’t linger.
| Check | What to do |
|---|---|
| Chip type | If About This Mac shows an Apple M-series chip, you have Apple Silicon. If it lists an Intel processor, choose x64. Check each app’s requirements for its minimum macOS version. |
| Architecture compatibility | Only files explicitly labeled ARM64 are native builds for that architecture. An x64 file may require Rosetta on Apple Silicon; don’t rely on the download link’s label alone. |
| First launch | Check the specific prompt under System Settings → Privacy & Security. Don’t disable system-wide security just to launch one app. |
Most recent phones use ARM64. Older devices may use ARMv7; choose the universal build if you’re unsure. When installing an APK, grant permission only to the file manager or browser you’re using. On first connection, approve Android’s VPN connection request.
For Android devices compatible with ARM64 packages. Import your subscription and select its configuration before connecting. Check the app name in Android’s VPN prompt. If the connection drops when the screen locks, review battery optimization and background permissions for this app instead of disabling every power-saving setting.
Choose a package for your processor architecture if you know it; try the universal build if you don’t. After importing a subscription, set its configuration as active and check your proxy group selection. If parsing fails, save the relevant log instead of repeatedly reinstalling the app.
A good fit if you want a similar interface on mobile and desktop. On your phone, import the configuration and set background permissions separately. The desktop system proxy toggle is not the same as Android’s VPN setting. If you use another VPN app, disconnect it before starting FlClash.
Listed as another Android configuration tool. Before using it, check that your subscription uses a supported format. Surfboard’s configuration syntax differs from Clash YAML, so the same configuration may not import directly. Prepare a compatible configuration and follow the app’s prompts to connect.
| Check | What to do |
|---|---|
| Operating system & ABI | Check that your Android version meets the app’s minimum requirements. ARM64 uses arm64-v8a; ARMv7 uses armeabi-v7a. |
| Install permissions | Allow installation from this source. If Android says the package can’t be parsed, check the architecture, OS version and whether the download completed. |
| Background connections | VPN apps generally can’t run alongside another VPN app. If the connection drops when the screen locks, check this client’s background restrictions and battery optimization settings. |
Install Clash Plus from the App Store. Check the store listing for device and iOS compatibility. Before opening the app, have a subscription ready; then follow its prompts to add a configuration and approve VPN access.
Check the App Store listing for system requirements and app details. After installation, add a subscription or compatible configuration. On first connection, approve the VPN configuration prompt, then return to the app to check its status. Subscription updates and app updates are separate: manage them on the Configuration page and in the App Store, respectively.
| Check | What to do |
|---|---|
| System compatibility | Check the Compatibility section on the App Store listing for supported devices and iOS versions. |
| Connection permissions | iOS requires system authorization when you first add a VPN configuration. Disconnect any other active VPN first to avoid conflicts. |
| Configuration setup | Get a compatible subscription URL from your provider and select a proxy group after importing it. Don’t share the full subscription URL publicly if it contains access credentials. |
The desktop clients below provide AMD64 packages. Debian- and Ubuntu-based distributions usually use DEB; Fedora and similar distributions typically use RPM. Check your distribution, processor and desktop environment first. For ARM routers or headless servers, see the core downloads section.
For Linux devices with a desktop environment where you want to manage subscriptions in a GUI. Use your distribution’s package installer to handle dependencies. The system proxy affects only apps that honor proxy settings; check permissions separately before enabling TUN or service mode.
This DEB package is for Debian-based desktop distributions compatible with its dependencies. Check your architecture with uname -m before downloading; choose the AMD64 package if the output is x86_64. After installation, you’ll still need to import a subscription—the app won’t automatically use another client’s data directory.
| Check | What to do |
|---|---|
| Architecture | uname -m typically reports x86_64 for AMD64 packages and aarch64 for ARM64. The AMD64 GUI package here won’t work on aarch64. |
| Dependencies & desktop environment | GUI clients require a compatible desktop environment and libraries. If the installer reports missing dependencies, resolve them with your package manager rather than unpacking and running the app directly. |
| Network routing | Command-line tools may not follow the desktop system proxy. Check the tool’s own proxy settings first; consider TUN only after that, so you don’t mistake routing scope for a node issue. |
For servers, routers and command-line deployments. Most desktop users should choose one of the GUI clients above. With a standalone Mihomo core, you’ll need to prepare the YAML configuration, runtime directory, permissions and service management yourself. There is no graphical configuration window.
| System | Architecture | Format | Download |
|---|---|---|---|
| Windows | AMD64 / x64 | 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 |
Extract ZIP and GZ files before use. GZ files usually contain a single executable, not a graphical installer. On Linux and macOS, check the executable permission after extraction, then specify a configuration directory. Install DEB packages with a package manager, and check separately whether the service is enabled afterward.
For your first deployment, start the core in the foreground and check the logs. Once the configuration parses correctly, set it up as a system service. If using external-controller, bind it to localhost and enable authentication. Configure controlled access only if remote management is necessary; don’t expose the control port directly to the public internet.
Downloading the file is just the first step. Check configuration, routing mode and connectivity in order to avoid bouncing between the client and system settings.
Paste your existing subscription URL into the configuration import field, wait for it to download, then set it as the active configuration. A webpage URL isn’t necessarily a subscription URL. If the logs show a YAML parsing error, check whether the response is a login or error page.
For everyday use, start with rule mode and make sure a usable proxy is selected in the relevant group. The system proxy covers only apps that honor it. TUN routes more traffic and involves system permissions, routing and DNS; avoid repeatedly switching it alongside another VPN.
Open a webpage in the app you’re troubleshooting, then check its requests in the Connections or Logs view. If the browser works but another app doesn’t, check the routing scope first. If all requests fail, check the subscription, proxy selection and DNS before reinstalling the client.
Check the package name and architecture first, then review the specific error. These answers focus on choosing an installer; see the usage guides for rules, DNS and overrides.
For Windows, macOS, Android and iOS, start with the first Clash Plus card for your platform. For Linux, start with Clash Verge Rev. If your current setup works, back up your subscription URL, local overrides and proxy group selections before installing a new client. Installers do not include a working subscription, so you’ll still need to import your existing configuration.
Check your processor architecture in system settings first. Most Intel and AMD desktop computers use x64; Apple Silicon Macs and many Android phones use ARM64. Don’t infer architecture from the operating system name alone. If you’re unsure on Android, try the universal build of Clash Meta for Android. On macOS, check both the package label and the actual filename: an x64 package on Apple Silicon may require Rosetta.
Installing a client only puts the app on your device. Open its configuration or subscription page, import your subscription and make sure the configuration is enabled. Then check the proxy mode and selected proxy group. On desktop, start with the system proxy and test in a browser. Enable TUN mode by following the guide if you need to route more apps. On Android and iOS, approve the system VPN permission the first time you connect.
Save your subscription URL, local YAML files, override rules, scripts and any useful screenshots of your settings. Don’t back up only the subscription cache—a later update may overwrite your manual changes. When switching clients, turn off the old client’s system proxy and TUN before launching the new one. Check that listening ports, DNS, startup settings and proxy group names are configured as expected.
Both projects are discontinued. Their downloads remain available for recreating old setups and migration reference, but choose a maintained client for a new device. Older cores may not support newer protocols or YAML fields. If an import fails, don’t just change the file extension: back up the original configuration and check compatibility in the new client.
Usually not. GUI clients generally include a core or provide a way to manage one. Standalone Mihomo builds are mainly for servers, routers and command-line deployments, where you’ll need to prepare the configuration, runtime directory and service management yourself. Check the CPU architecture, operating system and archive format before downloading. A core download is not a GUI client.