Clash Plus, FlClash, and clients by platform
Choose your operating system first, then check the build architecture. GUI clients are designed for everyday subscription imports and rule-based routing; a standalone core is better suited to users with deployment experience on servers or routers.
This section offers x64 installers. Find your system type under Settings → System → About. On ARM devices, check that Windows supports x64 apps; an x64 download is not a native ARM64 build.
A good place to start if you’re setting up a client and importing a subscription for everyday use. After installation, select a configuration and check the routing mode and system proxy. Follow the setup guide to configure TUN if you need to route traffic from more apps.
A good fit for users who want a GUI to manage configurations and rule overrides. On first launch, check that the service and core are running. Service mode or TUN may request administrator access; read the prompt before proceeding.
A good fit if you want a similar configuration workflow across multiple devices. After installing the desktop app, import your subscription separately. When migrating from another client, don’t assume rule overrides or local file paths can be reused as-is.
A desktop GUI for managing configurations. If you already use a custom setup, back up your original files first. Test the rules and DNS with a separate configuration before migrating your existing setup.
Archived download for migrating an existing setup or troubleshooting compatibility. Older cores may not recognize newer subscription fields. For new installations, use one of the clients above. Don’t delete unfamiliar options just to get a new configuration to load.
| Check | Before installing |
|---|---|
| System and architecture | These are x64 apps. Check the installer for the minimum Windows version and required runtime components. |
| Permissions | Installation, service registration, and TUN drivers may require administrator access. On a managed computer, get authorization first. |
| Traffic routing | For your first test, let only one client manage the system proxy. This helps avoid port conflicts and duplicate route changes. |
If SmartScreen appears, verify the download source and app name before deciding whether to continue. Don’t treat disabling system security as a routine installation step. If websites work in your browser but not in Store apps, check the system proxy’s coverage and UWP loopback restrictions. See the Windows platform setup section.
Check your chip under About This Mac: choose Apple Silicon for an Apple chip or Intel for an Intel processor. Also verify the actual file provided by the download link—a compatibility build is not necessarily a native ARM build.
Separate downloads are available for Apple Silicon and Intel. Open the disk image and follow the installer, then launch the app from Applications. When setting up network routing for the first time, grant the permissions requested by macOS.
A good choice for managing subscriptions and rules from your desktop. Both downloads currently point to x64 disk images. Before using one on Apple Silicon, check that Rosetta is available and that your system is compatible; these are not native ARM builds.
Offers a workflow similar to the versions for other platforms. The current downloads are AMD64 builds; the Apple Silicon link points to the same file and requires a compatible environment. After importing a configuration, check the logs before enabling the system proxy.
Archived for comparing and migrating older setups. The current download is an x86_64 build; check compatibility before using it on Apple Silicon. Back up your configuration before migrating to avoid conflicts with fields unsupported by the older client.
| Check | Before installing |
|---|---|
| Processor architecture | ARM64 is for Apple Silicon. x64, AMD64, and x86_64 builds are for Intel processors. |
| Compatibility | Running x64 apps on Apple Silicon generally requires Rosetta. Compatibility also depends on your system and the client’s requirements. |
| System permissions | Background services, network extensions, or TUN may require your approval. Follow the prompts and don’t bypass system protections indiscriminately. |
If the app won’t open, make sure the disk image finished downloading and the app was correctly moved to your Applications folder, then check the details under Privacy & Security. If the proxy stops working after an upgrade, check whether the proxy address and port in Network settings are still managed by the current client.
Most recent phones use ARM64, but check which app architectures your device supports. The first time you connect after installing an APK, Android will ask for VPN permission. Usually, only one VPN service can route traffic at a time.
An ARM64 download for setting up a mobile proxy, starting with a subscription import. After installation, update and select your configuration, then choose a proxy group. When connecting, verify the app name in Android’s VPN permission prompt.
Choose an ARM64, ARMv7, or universal build for your device. After updating a remote configuration, make sure it’s selected. If the app disconnects in the background, check battery optimization and background activity restrictions.
ARM64 and ARMv7 builds are available. If installation fails with a parsing error, check the architecture and system compatibility first; changing the file extension won’t fix it. If you use another VPN app, disconnect it before testing.
An Android universal package. It uses a configuration syntax different from Clash YAML, so check that your service provider supports the format. Renaming a file won’t convert a Clash configuration into a working Surfboard configuration.
| Check | Before installing |
|---|---|
| App architecture | ARM64 corresponds to arm64-v8a, and ARMv7 to armeabi-v7a. If you’re unsure, try the universal build. |
| Installation permissions | Allow your browser or file manager to install apps. You can revoke this permission afterward, depending on your security preferences. |
| Background activity and connections | Allow necessary background activity. Other VPNs, work profile policies, and system battery restrictions may affect persistent connections. |
If Android reports a conflict with an existing app, the signatures or package names may differ. Back up your configuration and verify where the existing app came from; don’t uninstall it before locating your subscription. A VPN icon only confirms that a tunnel is active—access to a website also depends on the proxy node, DNS, and matching rules.
Install Clash Plus from the App Store. Check the store listing for device compatibility, minimum iOS requirements, and the currently available version.
Install the app from its App Store listing, then return to the client to import a subscription or configuration. On your first connection, approve the request to add a VPN configuration. Then choose a routing mode and an available proxy group in the client.
| Check | Before installing |
|---|---|
| System compatibility | Check the Compatibility section on the App Store listing to make sure your device meets the installation requirements. |
| Network permissions | When connecting, follow the system prompt to allow the VPN configuration. Managed devices may restrict this permission. |
| Configuration source | Prepare a valid subscription or compatible configuration. After importing it, make sure it’s active—not just saved in the configuration list. |
If you’ve used another VPN client, disconnect it before your first test. This helps prevent another app’s routing status from being mistaken for the current configuration. After connecting, check the client logs and try accessing a website; don’t rely on the status bar icon alone.
Subscription links may contain access credentials. Don’t share them in public chats or shared notes. Before switching devices, check how many devices your subscription allows, then import it again on the new device. Installing the same client won’t automatically sync your configuration or credentials.
This section features AMD64 desktop GUI clients. Check your distribution’s package format, then choose DEB or RPM. For headless servers, see the Mihomo core downloads below.
DEB and RPM packages are available. Install using your distribution’s package manager and review any dependency prompts. Service mode and TUN require additional permissions; don’t run your entire desktop session as an administrator.
An AMD64 package for DEB-based distributions. After installation, launch it in your user session and import a configuration. Terminal apps may need separate proxy environment variables or TUN settings; the desktop system proxy alone may not cover them.
| Check | Before installing |
|---|---|
| Distribution package format | Debian- and Ubuntu-based distributions generally use DEB; Fedora and other RPM-based distributions use RPM. Check your package manager for specific dependencies. |
| Processor and desktop | These builds are for AMD64/x86_64 and require a supported graphical desktop and runtime dependencies. |
| Service permissions | TUN needs network device and routing permissions. Configure it according to your distribution’s service management; don’t loosen file permissions indiscriminately. |
Run uname -m to check your architecture: x86_64 usually indicates AMD64, while aarch64 indicates ARM64. Don’t force an installation if the architecture doesn’t match. If dependencies are missing, use your distribution’s official repositories rather than mixing system libraries from another distribution.
For users managing their own configurations on servers or routers. Most desktop and mobile users should choose a GUI client above; GUI clients typically manage their own core, so you don’t need to install one separately just to get started.
| Operating system | Processor 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 |
The core in the archive is a command-line program, not a GUI client. After extracting it, you’ll also need to prepare a configuration directory and file, and set the required permissions. GZ is a compression format, not an installer; use your distribution’s package manager to install DEB packages.
For routers, check more than ARM or MIPS: confirm the bit width, endianness, and floating-point support. The MIPS softfloat build is for specific target environments and won’t work on every MIPS router. Check the firmware details and device architecture rather than choosing based on the processor brand alone.
When maintaining the core yourself, back up your configuration, stop the old process, replace the binary, test the configuration, start the service, and check the logs. Don’t run two core instances on the same listening port. For complete platform setup instructions, see the all-platform guide. To connect a subscription, go straight to the subscription import steps.
Troubleshoot installation failures, architecture mismatches, and subscription connection issues separately. First make sure the client starts, then check configuration loading and network routing.
Choose your operating system first, then check your processor architecture. Start with Clash Plus for Windows, macOS, Android, or iOS, and Clash Verge Rev for Linux. Most desktop and mobile users can use a GUI client without installing the Mihomo core separately.
Check your device’s system information and the architecture listed for the download. x64 and AMD64 generally refer to the same architecture; ARM64 and ARMv7 are not interchangeable. If you’re unsure which architecture your Android device uses, choose a universal build for broader compatibility. Some macOS compatibility downloads are x64 builds; check Rosetta availability and the client’s system requirements before using one on Apple Silicon.
The installer includes the client, not a proxy service. Import a subscription or configuration from a trusted source, select the configuration and a proxy group, then enable the system proxy or configure TUN if needed. An expired subscription or unavailable node is a separate issue from whether the client installed successfully.
Check your browser’s download history to make sure the file finished downloading, then verify its extension, operating system, and processor architecture. If a link is temporarily unavailable, try again later. If your system blocks the file, verify its source and read the warning before proceeding—don’t disable security protections. On managed devices, follow your organization’s policies.
Back up your current configuration, rule overrides, and any essential local settings. Note the system proxy port and whether TUN is enabled. Data directories and core settings may not be compatible between clients, so reimport your configuration after migrating and check the logs. Backups may contain subscription credentials; don’t upload them publicly.
Clash for Windows and ClashX Meta are listed here as archived downloads for migrating existing setups and troubleshooting compatibility. For a new installation, choose a maintained client that meets your system requirements. Older clients may not recognize newer configuration fields or may have compatibility issues after a system upgrade.
For connection issues after installation, visit the Help Center. For subscription update problems, see subscription update troubleshooting.