Choose your operating system, then check your CPU architecture. Use a GUI client on desktop and mobile; see the standalone core for servers, routers, and self-managed environments.
The GUI installers below are primarily x64. For a new setup, start with Clash Plus. For more detailed rule and desktop settings management, compare Clash Verge Rev, FlClash, and Clash Nyanpasu. Archived clients are listed last for reference when migrating older setups.
A good starting point for a first-time installation. After installing, import your subscription, make sure the configuration is enabled, then choose a rule mode. When moving to another PC, migrate your subscription and local changes separately instead of copying only the program folder. See the official site for product details and supported platforms.
clashplus.io
A desktop client built on mihomo, with a GUI for managing subscriptions, rules, and system settings. System proxy mode works with apps that follow the OS proxy settings. To use TUN, install the service and grant permission when prompted. Before enabling it, disable system-level control by other proxy apps to avoid competing changes to your network settings.
A cross-platform client built with Flutter, suited to users who want a consistent interface across devices. For a standard installation, use the EXE. For the ZIP, extract it to a permanent folder and follow the app's instructions. A portable archive doesn't necessarily eliminate the need for runtime components or system services.
Provides a desktop GUI for managing configurations. When choosing a client, consider not only the interface but also the core it currently uses and its configuration compatibility. When migrating from another client, check subscriptions and rule overrides separately. Settings with the same name may be stored differently or take effect in a different order.
Kept for reproducing or migrating older setups, not recommended for new installations. Archived software won't be updated for changes in newer operating systems, and its older core may not recognize newer protocol fields in subscriptions. Before migrating, note your subscription URL, mixed port, rule overrides, and shortcuts, then recreate them in a maintained client.
See migration steps for discontinued clients →| Check | Details |
|---|---|
| Supported versions | For new installations, use a Windows 10 or 11 version that is still supported. Check the client's installer and release notes for its exact minimum requirements. |
| Processor | Packages in this section are x64 / AMD64. On ARM devices, check the system's emulation support; an x64 package is not a native ARM64 build. |
| Runtime components | If the app reports that WebView2 or a runtime is missing, install the component as described by the client, then restart the app. |
| Permissions and migration | TUN or background services may require administrator permission. Back up your configuration before upgrading, and let only one client manage the system proxy at a time. |
Check your chip in Apple menu > About This Mac: choose ARM64 for an Apple M-series chip and x64 for an Intel processor. Link labels distinguish devices; use the button text and downloaded filename to confirm the actual package architecture.
Separate ARM64 and x64 downloads are available. Open the DMG and follow the window instructions to install the app in a permanent location. After importing your configuration, check the rule mode and permissions. When moving to another Mac, check its chip architecture rather than reusing the package type from your previous device.
clashplus.io
For users who need desktop subscription management, rule settings, and mihomo configuration support. Both links currently point to the same x64 file. On first launch, grant any permissions required by macOS. For service mode or TUN, follow the app's instructions rather than applying another client's background service settings.
A desktop option for users who want a consistent experience across platforms. AMD64 and x64 refer to the same architecture; the name doesn't mean you need an AMD processor. On Apple Silicon, check the translation environment first. After importing the same subscription, you'll still need to set up local ports, system proxy, and startup behavior.
For users who need an archived release for an existing ClashX Meta setup. Both links currently point to an x86_64 file; check system compatibility before installing. Before migrating, save your subscription and custom rules, quit the old app, and restore its proxy settings. Then start the new client to avoid two menu bar apps managing the network at once.
| Check | Details |
|---|---|
| OS version | Check the app's release notes for its minimum macOS version. Confirm compatibility with newer macOS releases separately for archived apps. |
| Chip architecture | For Apple M-series chips, choose a package explicitly labeled ARM64. For Intel, choose x64 / AMD64 / x86_64. |
| Installation location | Follow the DMG window instructions to install the app. Don't run it long-term directly from a mounted disk image. |
| System permissions | Only respond to macOS security prompts after confirming the app's source. Grant background service and network extension permissions as described by the client. |
Most newer phones use ARM64, but the processor hardware and application architectures supported by the OS don't always match. Check your device specifications first. If you're unsure about an older device's architecture, consider a client with a universal package. On first launch, you'll usually need to approve a local VPN connection request.
This package is for Android devices that support ARM64 apps. After installing, import your subscription and approve the VPN connection when prompted. If the system stops the connection in the background, check battery optimization and background activity limits. Settings vary by manufacturer, so avoid disabling system management features across the board.
clashplus.ioAn Android client for the Clash Meta configuration ecosystem, with architecture-specific and universal packages. The universal package simplifies architecture selection but doesn't guarantee support for every Android version. Check that your subscription format is supported when importing it. If loading fails, check the parsing error rather than repeatedly switching packages.
Packages are available for ARM64, ARM, and x86_64, each for a different environment. For phones, check ARM64 first; x86_64 is mainly for emulators and specific devices. You may be able to reuse a compatible subscription across platforms, but Android app-level proxy settings, VPN permissions, and background behavior still need to be configured separately.
An alternative Android configuration client. Surfboard is not interchangeable with Clash YAML clients; check its configuration format and supported fields separately. Ask your configuration provider for a compatible subscription format before use. Changing a file extension won't convert its format or add support for missing protocols.
| Check | Details |
|---|---|
| OS version | Check the minimum Android version specified by the client's current package. If the installer reports incompatibility, verify your OS version and device architecture first. |
| App architecture | arm64-v8a is 64-bit ARM, armeabi-v7a is 32-bit ARM, and x86_64 is mainly for specific devices and emulators. |
| Install permissions | If prompted, allow installation only for the browser or file manager you're using. You can restore its previous permission settings after installation. |
| Connection permissions | Approve the local VPN request. Typically, only one VPN app can be active in a user profile, so end any existing VPN session before connecting. |
Install Clash Plus from the App Store. Check the store listing for device compatibility, iOS requirements, and app updates. After installation, prepare your own subscription, then follow the app's instructions to import it and grant VPN permission.
Open the store listing to install the app. Once installed, add a subscription or supported configuration file. Approve the system VPN prompt when connecting for the first time. If importing fails, check that the link is complete, the subscription is still valid, and the app supports the configuration format.
clashplus.io| Check | Details |
|---|---|
| Compatible devices | Check the Compatibility section of the App Store listing to confirm your device and OS version are supported. |
| Installation and updates | Install from the App Store link above; the App Store manages app updates. |
| Configuration | Provide your own subscription or configuration. Shared links may contain private subscription credentials. |
| VPN permission | Allow the app to add a VPN configuration when prompted. Before troubleshooting connection issues, check whether another VPN app is still connected. |
For desktop environments, choose the package format for your distribution: Debian and Ubuntu-based systems usually use deb, while Fedora and similar distributions usually use rpm. GUI packages in this section are AMD64. For servers and routers, see the Mihomo core section instead of trying to install a desktop app.
For Linux devices with a graphical desktop. Install through your distribution's package manager to handle dependencies and make future removal easier. System proxy behavior varies across desktop environments. To use TUN, also check permissions, service status, and network settings—not just the toggle in the app.
This page provides a deb installer for Debian-based desktop environments. Check distribution dependencies and desktop session support before installing; deb files aren't compatible with rpm-based package managers. If the app starts but traffic isn't proxied, check the desktop system proxy and the app's network settings before considering TUN.
| Check | Details |
|---|---|
| Desktop environment | GUI clients require a supported desktop and runtime dependencies. On headless systems, use the standalone core instead. |
| Processor | This section provides AMD64 / x86_64 files. Use uname -m to help identify your system architecture. |
| Package manager | deb and rpm packages are for different distribution families. Install with your system package manager and check any dependency errors. |
| Network permissions | TUN uses a virtual network interface and routing permissions. Read the client's service installation instructions; don't loosen permissions across the entire program directory. |
For users running servers, routers, or self-managed environments. The core handles proxying and rule processing, but doesn't include a full desktop settings interface; most users should choose a GUI client above. After downloading, prepare your own configuration, specify a working directory, and manage permissions, services, and logs.
| Platform | Architecture | File and download | Usage notes |
|---|---|---|---|
| Windows | AMD64 | Download ZIP64-bit x86 command-line environment. | |
| Windows | ARM64 | Download ZIP | Native ARM64 command-line environment. |
| macOS | Intel / AMD64 | Download GZ | After extracting, run it with the permissions required on your system. |
| macOS | Apple Silicon / ARM64 | Download GZ | For Apple M-series processors. |
| Linux | AMD64 | Download DEB | For compatible Debian-based package management systems. |
| Linux | AMD64 | Download GZ | Set executable permissions and configure service startup yourself. |
| Linux | ARM64 | Download GZ | For 64-bit ARM servers or compatible devices. |
| Linux | ARMv7 | Download GZ | Check the device instruction set and system ABI. |
| Linux | MIPS soft-float | Download GZ | Check the byte order and soft-float environment. |
| Check | Deployment |
|---|---|
| Configuration and paths | Specify the configuration file, rules file, and working directory. Review the configuration parsing results on first launch. |
| Services and permissions | Configure startup through your system's service manager. Standard proxy listeners and TUN require different permissions; grant only what's needed for each feature. |
| Listening interfaces | Check the listen address and access controls. Never expose the management interface directly to an untrusted network. |
| Upgrade and rollback | Back up your configuration and current binary before upgrading. Check field compatibility before replacing the service binary. |
For core families, protocol differences, and configuration compatibility, see the Protocol Guide. If you only need to import a subscription and connect, a GUI client is usually easier to set up.
Downloading is only the first step. Follow the sequence of installation, configuration, and verification to distinguish client issues from subscription issues and avoid changing multiple settings at once.
For a new installation, check the package architecture and system requirements, then install using the system installer. Before upgrading an existing setup, save your subscription URL, local rules, overrides, and port settings. App configuration and installation directories may be separate; copying only the program files won't preserve your complete setup.
If you plan to try two clients, quit the current one and disable its system proxy or VPN session before launching the other. Don't let both apps change the system proxy, create virtual network routes, or listen on the same ports. If a conflict occurs, restore a single-client setup before troubleshooting.
After importing a valid subscription or local configuration, make sure it's enabled. Start with rule mode and check whether the apps you need follow the system proxy. For apps that don't, consider TUN based on your needs. On mobile, approve the system VPN request rather than looking for a desktop setting with the same name.
During testing, check separately that the configuration loaded, which rule matched the target request, and whether the connection log shows errors. Rule mode doesn't mean all traffic takes the same route. To investigate further, note the steps that trigger the error and follow the guide to check DNS, ports, and permissions one by one.
Read the complete user guide →These answers cover package selection, configuration imports, and migration from discontinued clients. For protocol support, DNS, and other advanced topics, see the Protocol Guide.
For Windows, macOS, Android, and iOS, start with Clash Plus. For desktop rule management and TUN settings, compare Clash Verge Rev. On Linux, start with Clash Verge Rev and choose the deb or rpm package for your distribution. After installing a client, import your own subscription or configuration file.
On Windows, check System type in Settings > System > About. On a Mac, check the chip or processor under About This Mac. On Android, check your device specifications. x64 and AMD64 usually refer to the same 64-bit architecture; ARM64 is a different architecture. Linux deb and rpm packages use different package management systems, so don't choose between them based on the processor name alone.
In the current listings, both Mac links for Clash Verge Rev, FlClash, and ClashX Meta point to each client's x64 file, so the links are retained and the actual package architecture is noted. These packages typically require Rosetta 2 on Apple Silicon; check each app's release notes for compatibility. For a clearly labeled ARM64 package, see Clash Plus.
Archived releases can help reproduce an old setup or support a temporary migration, but aren't recommended for new installations. Since the client is no longer maintained, it won't receive updates for future OS compatibility or protocol changes. Before migrating, save your subscription URL, rule overrides, and port settings, then import them into a maintained client and check each setting.
The installer provides the client, not a ready-to-use service configuration. First import a valid subscription or local configuration and make sure it's enabled. Then choose a rule mode and check system proxy settings or VPN permissions. If an error occurs, review the logs to determine whether the issue is subscription retrieval, configuration parsing, or the connection. Change one setting at a time.
Usually not. GUI clients generally include or manage a compatible core. Before replacing it manually, check which versions and interfaces the client supports. Standalone core files are mainly for servers, routers, and users who manage their own configuration; you'll also need to handle configuration paths, permissions, service startup, and logs.