Client downloads / platforms and architectures
Clash Plus, Clash Verge Rev, and FlClash. Choose your device platform, then the right installer; you can import an existing subscription after installation.
Clients and proxy configurations are managed separately. After downloading the software, you’ll still need a valid subscription or configuration file that you’re authorized to use.
01 / GUI clients
Multiple clients are available for some platforms, so you can choose based on your workflow and configuration compatibility. Each download button includes a brief description; version details appear only when valid data is available.
For everyday desktop use. Most installers below are x64. Before downloading, check your system type in Settings > System > About. Don’t choose a package for an ARM device based on the Windows name alone; check system emulation and client driver compatibility too.
A good place to start if you’re new to Clash. After installation, import your configuration, then choose a proxy mode and policy group. Compatible configuration content can be reused across devices, but system proxy, startup, and permissions must be configured separately on each one.
Package: EXE. Official site: clashplus.io.
A good fit if you need to manage subscriptions, rule overrides, and desktop proxy status. It’s also an option when migrating from Clash for Windows. Before migrating, note your existing ports and rule changes. After importing, check the active configuration instead of copying the old client’s data directory.
Package: EXE. Before enabling TUN, follow the client’s instructions to configure its service and permissions.
A good fit if you want a similar workflow on desktop and mobile. After importing your subscription, check the policy group names and rule mode before enabling the system proxy. Whether a configuration works across devices depends on supported core fields and local paths, not on how similar the interfaces look.
Package: EXE. Back up local overrides and app settings before updating.
Another desktop GUI option for managing configurations and connection status your way. Before installing a new client, quit other proxy apps to prevent them from competing to change system proxy settings. Conflicting mixed ports can also prevent startup, so configure them separately.
Package: EXE. Test the connection as a standard user before changing advanced network settings.
This archived download is for restoring older setups or reproducing compatibility issues, not as the default choice for new devices. Older cores may not recognize newer protocols or configuration fields. If you encounter parsing errors, consider moving to a maintained client instead of repeatedly editing the same subscription.
Migration tip: export your configuration and note your ports and policy group selections. Disable the old setup only after verifying the new client.
| Check | What to look for | After installation |
|---|---|---|
| System and architecture | Use a supported Windows 10 or 11 x64 system where possible, and verify the system type. | Make sure the app starts before importing your configuration. |
| Network permissions | System proxy and TUN have different permission requirements. TUN may require a service component and administrator approval. | Grant permissions as prompted. Don’t let multiple clients route traffic at the same time. |
| Ports and migration | Note the old client’s ports and check whether another process is using them. | Test the connection in a browser, then restore advanced settings one at a time. |
Check your chip under About This Mac in the Apple menu. Apple Silicon and Intel require different package choices. A download listed for your device doesn’t necessarily contain a native build; some current links provide x64 files. Check the filename, app details, and macOS compatibility prompts.
Choose a DMG that matches your chip. Open the disk image, move the app to Applications, and launch it from there. Follow macOS prompts to grant network permissions. Running the app from the disk image can cause problems with updates and path detection.
Official site: clashplus.io. After importing your configuration, check the mode and policy group before connecting.
For managing desktop subscriptions, rule overrides, and network modes. Both links currently fall back to an x64 DMG. Apple Silicon users should check Rosetta compatibility; the Apple Silicon link does not guarantee a native ARM build.
When first enabling a service or TUN, respond to the actual system prompts. Don’t change security settings without a clear reason.
A good fit if you prefer an interface similar to the mobile app. The current fallback is an amd64 DMG, so Apple Silicon users should check Intel app compatibility. After installation, review your system proxy and DNS settings rather than relying on settings left behind by an old client.
Quit your current client before switching to avoid conflicts between proxy ports and network services.
Kept only for compatibility with older setups. The current fallback is an x86_64 file; Apple Silicon users should check compatibility separately. If an old network component stops working after a macOS upgrade, migrate to another client rather than relying on an archived build for ongoing support.
Back up your configuration and rule changes before migrating. Recheck system permissions.
| Check | What to look for | After installation |
|---|---|---|
| Chip | Check About This Mac to distinguish Apple Silicon from Intel. Use the architecture of the actual download. | Check Rosetta compatibility before running an x64 app on Apple Silicon. |
| macOS version | Check the app’s current release notes and macOS installation prompts for its minimum version. | Move the app to Applications before launching it for the first time. |
| Network permissions | The client determines how to authorize TUN, background services, and network extensions. | Verify the app’s source, then grant the required permissions in System Settings. |
Most recent phones use ARM64, but check your device specs and OS support. ARMv7 is for compatible older devices; if you’re unsure, try the universal package. On first connection, Android usually asks for VPN permission, which allows the app to route device traffic.
A good option for getting started with subscriptions and everyday connections. Install the app, import your configuration, choose a policy group, and approve Android’s VPN prompt. If the connection stops when the screen locks, check battery management and background activity settings instead of repeatedly importing the subscription.
Package: APK. Official site: clashplus.io.
For users who want to use Clash Meta ecosystem configurations on Android. Choosing the right architecture can reduce download size; the universal build is convenient if you’re unsure. After importing, check that the configuration updates successfully, then choose a policy group on the proxy screen.
If an app with the same name is already installed, a signing key mismatch may prevent an update. Export your data before uninstalling.
A good fit if you want a similar configuration workflow on desktop and mobile. Subscription URLs are sensitive; don’t post them in public forums. If the connection fails after switching networks, check network access and your proxy selection first, then check DNS and app routing rules.
Package: APK. Don’t infer supported app architecture from the processor’s marketing name alone.
An alternative workflow for managing proxy settings on mobile. Surfboard uses a different configuration syntax from Clash YAML; changing a file extension won’t make it importable. Before choosing it, check whether your subscription provider offers a compatible format and whether the required protocols are supported.
Local APK download. When migrating, use only configuration content supported by the target client.
| Check | What to look for | After installation |
|---|---|---|
| App architecture | Choose ARM64 or ARMv7 according to your device and OS support. If unsure, try the universal build. | If Android reports that the app is incompatible, first check the architecture and minimum Android version. |
| Install source | Follow Android’s prompts and allow installation only for the browser or file manager you’re using. | You can review the install-source permission again after installation. |
| Connection permissions | A VPN permission prompt is usually required on first connection. Other VPN apps may conflict. | Disable other VPN apps, then test the connection with the screen on and locked. |
Install Clash Plus on iPhone or iPad through the App Store. The store listing shows current system requirements and release information. Check it before installing. If you already have a configuration, import it in the app and make sure it parses successfully.
After installing, import a subscription or configuration, choose a policy group, and follow the system prompts to add a VPN configuration. If another VPN is already set up on your device, check its connection status so you don’t mistake its traffic for this client’s.
Official site: clashplus.io. Check the App Store listing for updates and system compatibility.
| Check | What to look for | After installation |
|---|---|---|
| Device and OS | Check the App Store compatibility section for supported iPhone and iPad models and iOS versions. | Make sure the app is installed before importing your configuration. |
| Network permissions | When connecting, follow the system prompt to add a VPN configuration and check the name of the app making the request. | Check the system connection status, then test in a browser. |
| Configuration compatibility | Different clients may support different fields in the same subscription. | Check the import result, proxy mode, and policy group—not just the connection button. |
For desktop use, start with a GUI client. The packages below are primarily for AMD64 desktops. Choose DEB or RPM to match your distribution’s package manager. For servers, routers, or other CPU architectures, see the Mihomo core downloads below.
A good fit if you need desktop subscription management and rule-based routing. DEB packages are commonly used on Debian- and Ubuntu-based distributions; RPM packages are common on Fedora and related distributions. Check your distribution’s current dependencies, and use its software installer or package manager where possible.
If the desktop app won’t start, check the error in a terminal to distinguish missing GUI dependencies from a core startup failure.
A good fit for Linux desktop users who prefer a similar interface across devices. Before installing, make sure your distribution supports DEB packages and meets the app’s dependencies. The system proxy affects only apps that honor proxy settings; command-line tools may need proxy environment variables or another suitable traffic-routing method.
Before enabling TUN, check permissions and routing. If you’re managing the device remotely, keep a way to restore network access.
| Check | What to look for | After installation |
|---|---|---|
| Processor | Run uname -m to check your system architecture. The desktop packages here are for AMD64 / x86_64. | ARM devices can’t run AMD64 desktop packages directly. |
| Distribution and dependencies | Choose DEB or RPM to match your package manager. Check current release notes for minimum system library requirements. | Install through your package manager and resolve dependencies; don’t force past dependency errors. |
| Desktop and permissions | GUI clients require a working desktop environment. Use the core in command-line-only environments. | Test traffic routing separately in your browser, terminal apps, and TUN mode. |
02 / Command line and server deployment
For servers, routers, and self-hosted setups. The core does not include the GUI used by the clients above; most desktop and mobile users should choose a GUI client.
You’ll need to provide your own configuration, startup method, and permissions to deploy the core. Before downloading, check the operating system, CPU architecture, and runtime environment. For routers, verify the instruction set and floating-point ABI; don’t choose a package based only on the device brand. Extract compressed files first. Linux and macOS binaries also need execute permission; service management depends on your system.
Keep the management interface on a trusted network and configure appropriate access controls. For the first run, start the core in the foreground and check configuration parsing and logs before setting it up as a background service. Before changing routes or DNS on a remote server, prepare a rollback path to avoid disrupting your management connection.
| System | Architecture | Format | Package |
|---|---|---|---|
| Windows | AMD64 / x64 | ZIP | Download AMD64 |
| Windows | ARM64 | ZIP | Download ARM64 |
| macOS | Intel / AMD64 | GZ | Download Intel |
| macOS | Apple Silicon / ARM64 | GZ | Download Apple Silicon |
| Linux | AMD64 | DEB | Download DEB |
| Linux | AMD64 | GZ | Download AMD64 |
| Linux | ARM64 | GZ | Download ARM64 |
| Linux | ARMv7 | GZ | Download ARMv7 |
| Linux | MIPS softfloat | GZ | Download MIPS softfloat |
03 / Setup and migration
Installing the client doesn’t mean it’s routing your traffic yet. Start the client and import a subscription or local configuration. Check for parsing errors, then choose a rule mode and policy group. Rule mode follows your configuration to decide what connects directly or through the proxy. Global mode can help with temporary troubleshooting, but it doesn’t guarantee that every app is routed; traffic handling still depends on system proxy or TUN settings.
On desktop, start by enabling the system proxy. Visit a known working site in your browser and check the connection log for the request. If the browser works but another app doesn’t, first check whether that app honors system proxy settings, then consider TUN. On mobile, check VPN permission and connection status first. Avoid changing DNS, rules, ports, and modes all at once; otherwise, it’s difficult to pinpoint the cause of a problem.
Before switching clients, export your configuration and overrides, and note your proxy ports, policy group selections, and any local rules you want to keep. Subscription updates may overwrite direct edits, so use the target client’s override feature for changes you want to retain. Once you’ve verified the new setup, disable startup and system proxy settings in the old client to prevent both from running after a reboot.
Handle client, core, and subscription updates separately. They serve different purposes: the client manages the interface and OS integration, the core handles protocols and network behavior, and the subscription provides server information. When something goes wrong, note the specific error and when it occurred instead of blaming the installer for every issue.
For the full setup process, see the Clash setup guide. To learn how modes, rules, TUN, and DNS work together, continue with the Clash system guide.
04 / Download questions