Compare Clash Plus, Clash Verge Rev, and FlClash by platform. Check your device architecture before downloading the right installer. The standalone Mihomo core is listed separately for users deploying their own services.
How to import a subscription after installation →The installers below are primarily for x64 devices. Check your system type under Settings → System → About. Windows on ARM users should also verify app compatibility; an x64 installer is not a native ARM64 package.
For Windows users who want to get started by importing a subscription. After installation, add a valid configuration and check the proxy mode and system proxy status. If another client is installed, turn off its system proxy and auto-start first to prevent port conflicts and competing proxy settings.
clashplus.ioA Mihomo-based desktop client for users who need subscription management, TUN, and Merge overrides. Put local changes in overrides so subscription updates don’t overwrite them. Before enabling TUN for the first time, check service mode and authorization prompts. For ordinary browser use, start with the system proxy.
An option for users who want a similar workflow across devices. AMD64 and x64 refer to the same general architecture and are not tied to a particular processor brand. When migrating, import your subscription first, then restore rules, DNS, and port settings individually. Don’t replace the entire application data directory.
Another desktop client in the Clash ecosystem. Settings and extension options vary between clients, so check the active configuration after importing the same subscription. If you encounter an unknown field or startup error, find the field name in the logs and check whether the configuration is compatible with the core in use.
Kept for reproducing older setups and migration, but not recommended for new installations. The legacy Parsers workflow is not equivalent to Merge overrides. When migrating to Clash Verge Rev, note your subscription URLs, custom rules, and ports separately, then rebuild the configuration using the new client’s merge behavior.
| Check | Requirement or action |
|---|---|
| System and architecture | These are primarily 64-bit x64 installers. Check the installer and release notes for the minimum supported Windows version; an available download doesn’t guarantee compatibility with older versions of Windows. |
| Desktop runtime | Clash Verge Rev uses the Tauri desktop framework. If startup reports that WebView2 is missing, install the runtime as directed by Windows or the installer. |
| Service permissions | The system proxy and TUN handle traffic differently. TUN may require service installation and administrator approval. In standard mode, first verify that your subscription and rules work correctly. |
Check your chip under About This Mac. Clash Plus offers separate ARM64 and x64 packages. For the other clients listed below, both current architecture links point to the same x64 file. Apple Silicon users should check Rosetta and app compatibility before installing.
Choose the native installer for your chip. Open the disk image, drag the app to Applications, and launch it from there. After importing a subscription, make sure its profile is selected. If you used another network tool before migrating, quit it first, then check the proxy status in system network settings.
clashplus.ioFor managing subscriptions and local overrides. The current Apple Silicon link does not provide a separate ARM64 file, so check translation compatibility before use. After installation, verify the system proxy first, then enable TUN if needed. Check network-routing permissions separately from standard app launch permissions.
For users who prefer a familiar configuration workflow. AMD64 in the current filename means x64, not a native Apple Silicon build. After switching clients, check that the policy groups match your subscription and review DNS settings. Don’t assume local state from the old client was imported.
For maintaining existing setups and migrating configurations. For new devices, choose a client that is still maintained. Back up configuration files and subscription URLs before migrating, and disable the old app’s login item. If both apps write to the system proxy, quit one before testing the connection again.
| Check | Requirement or action |
|---|---|
| Chip architecture | Choose x64 for Intel. For Apple Silicon, use ARM64 when available; x64 apps require Rosetta and app compatibility. |
| System version | Minimum macOS versions vary by app build. Check the installer prompt, store listing, or release notes; a matching architecture doesn’t guarantee support for your macOS version. |
| First launch | Check the specific message under System Settings → Privacy & Security. Follow the system’s authorization steps only for apps from a source you trust; don’t disable all system protections. |
Most recent phones use ARM64, while older devices may need ARMv7. Successfully installing an APK only means the app is installed. To connect, you’ll also need to grant VpnService permission and import a compatible configuration.
For ARM64 Android devices. After downloading in a browser, Android may ask you to allow installs from that browser or file manager. Follow the prompt to authorize that specific source. Once configured, check background restrictions: first confirm the connection works while the app is open, then troubleshoot disconnections after the screen locks.
clashplus.ioFor users who need Clash Meta configuration support and per-app proxying. If you’re unsure which architecture your device uses, choose the universal package, but make sure your Android version meets the app’s requirements. Android typically allows only one app to use the VPN connection at a time, so disconnect other VPN-based network tools first.
A good fit if you prefer a workflow similar to the desktop app. After importing a subscription, remember that updating the configuration and choosing a policy group are separate steps. If the connection drops only after the screen locks, check battery optimization and background restrictions first instead of repeatedly changing DNS or reinstalling the app.
An alternative Android proxy app with a configuration format and feature set that differ from Clash YAML. A reachable subscription URL doesn’t guarantee it can be imported directly. First check which formats your provider supports, then verify how rules and policy groups map to the app.
| Check | Requirement or action |
|---|---|
| Processor | ARM64 corresponds to arm64-v8a, and ARMv7 to armeabi-v7a. For emulators and other architectures, check the app’s actual support. |
| System and permissions | Check the installer prompt for the minimum Android version. Creating a local VPN connection requires system authorization; installing an APK and granting connection permission are separate steps. |
| Background operation | Adjust background activity and battery optimization exceptions as needed. If the app has trouble running for long periods, check system battery usage before changing its check interval or background settings. |
Install Clash Plus from the App Store. Visit its store listing for device compatibility, release notes, and current availability. After installation, import a subscription and authorize the network configuration through the app.
iPhone and iPad users should check the system requirements on the App Store listing. When adding a network configuration for the first time, review the authorization prompt and confirm the source. After importing a subscription, select a profile and policy group before connecting. A connected status in the menu bar doesn’t confirm that traffic is reaching the right destination or matching the intended rules.
clashplus.io| Check | Requirement or action |
|---|---|
| Device compatibility | Check the supported devices and iOS versions on the App Store listing before installing. |
| Network permissions | Follow the system prompts to allow the VPN configuration. If you already have other network configurations, check which app is currently active. |
| Subscriptions and rules | Have a valid subscription ready and check which import formats the app supports. If the connection drops, check the configuration’s validity and logs, then look for issues caused by switching networks. |
The GUI packages here are for AMD64 desktop systems. Choose DEB for Debian- or Ubuntu-based systems, and RPM for distributions that use RPM packages. Your distribution, desktop environment, and system libraries also affect compatibility, so the file extension alone isn’t enough to tell.
For Linux desktop users who need subscriptions, rules, and local overrides. Install the package with your distribution’s package manager so you can review dependency messages. Before enabling TUN, check service permissions and routing settings. Headless servers are usually better suited to a standalone Mihomo core deployment.
For AMD64 desktop environments compatible with this DEB build. If installation fails, keep the complete package manager error so you can tell whether the cause is an architecture mismatch, missing dependency, or desktop runtime issue. Don’t force-install a DEB on an incompatible package system or use elevated permissions as a substitute for checking dependencies.
| Check | Requirement or action |
|---|---|
| Check the architecture | Use uname -m to check the architecture. The AMD64 package here is for x86_64, not ARM routers. |
| Desktop dependencies | A compatible graphical session and runtime libraries are required. Use your package manager to handle dependencies; check the build requirements for support on your distribution. |
| Traffic routing | The desktop system proxy may not cover terminal applications. Configure environment variables or TUN as needed, and keep a way to restore your connection before changing routes. |
For users managing services on servers or routers. Most desktop users can use the GUI clients above and don’t need to download the core separately. The standalone core has no subscription management interface; you’ll need to provide a configuration, permissions, launch arguments, and service management yourself.
| Platform | Architecture | Format | Local download |
|---|---|---|---|
| Windows | AMD64 | ZIP | Download AMD64 ZIP |
| Windows | ARM64 | ZIP | Download ARM64 ZIP |
| macOS | Intel / AMD64 | GZ | Download Intel GZ |
| macOS | Apple Silicon / ARM64 | GZ | Download ARM64 GZ |
| Linux | AMD64 | DEB | Download AMD64 DEB |
| Linux | AMD64 | GZ | Download AMD64 GZ |
| Linux | ARM64 | GZ | Download ARM64 GZ |
| Linux | ARMv7 | GZ | Download ARMv7 GZ |
| Linux | MIPS-softfloat | GZ | Download MIPS-softfloat GZ |
| Check | Requirement or action |
|---|---|
| Prepare a configuration | Provide a valid YAML configuration and confirm that the core supports the fields it uses. Test the configuration before setting up a long-running service. |
| Files and permissions | Extract ZIP and GZ files first. On Unix-like systems, make sure the binary is executable. The data directory must be writable; grant only the permissions required for your setup. |
| Networking and administration | TUN requires system support and the appropriate permissions. Keep the external controller bound to localhost where possible; configure authentication and access restrictions separately if remote access is needed. |
Don’t replace a service configuration after a subscription update without checking it first. Make configuration changes, core upgrades, and routing adjustments separately to make issues easier to diagnose. For details on how rule sets, DNS, Fake-IP, and overrides work together, see Advanced Usage.
Installing the app deploys the software; it doesn’t make a configuration ready to use. Import a subscription or local YAML file, select the profile, and check the policy groups. Start with rule mode and the system proxy in most cases. Enable TUN only if you need to route traffic from more apps, and check its permissions. Change one type of setting at a time so you can use the logs to pinpoint issues.
First identify whether the issue is package selection, app installation, or configuration and connectivity. Each calls for different checks; a connection problem doesn’t necessarily mean you need to download the installer again.
Start by choosing a package for your operating system. For Windows, macOS, Android, and iOS, consider Clash Plus. Choose Clash Verge Rev for desktop subscription management and Merge overrides; it is also the recommended option for Linux. After installation, import a valid subscription or local configuration.
ARM64 and x64 target different processor instruction sets, so the operating system name alone isn’t enough. Most recent Android phones use ARM64, while older devices may need ARMv7. If you’re unsure, choose a universal package when available. Some current macOS download links point to the same x64 file; Apple Silicon users should check Rosetta compatibility before installing.
The client reads your configuration, applies rules, and routes traffic; the installer does not include a proxy service. Import a valid subscription, select a profile and policy group, then enable the system proxy or TUN if needed. If the connection fails, check the logs to distinguish subscription, DNS, and traffic-routing issues.
Check your operating system, processor architecture, and package format, and make sure the download completed. On Windows, review the installer message and system requirements. On macOS, check the specific block message in Privacy & Security settings. On Android, follow the system prompt to allow installs from the current source. On Linux, use your package manager to inspect dependency errors. Don’t disable all security protections to work around an error.
Archived downloads are mainly for reproducing older setups and migrating configurations; neither client is maintained anymore. For a new installation, choose a client that is still maintained. Before migrating, back up subscription URLs, rules, ports, and overrides. Don’t copy the entire old application directory over the new client.
Most desktop users only need to install a GUI client, which manages the core for them. The standalone Mihomo binary is for users managing services on servers or routers and requires a separate configuration, launch method, and permissions. It’s a command-line core, not a desktop app you can open directly.