Platforms / Core / Migration Effort

Clash ClientComparison and Selection

For a first install, start with Clash Plus. For desktop rule overrides or connection troubleshooting, consider Clash Verge Rev; for one client across Linux and Android, consider FlClash.

Client Platform and Feature Comparison

Platforms listed are limited to downloads available on this site and may not reflect the upstream project's full support. Ease-of-use ratings are based on the steps needed to import a configuration, route traffic, and inspect rules—not performance. Scroll horizontally on smaller screens to view the full table.

Platform, core, maintenance, ease of use, key features, and ideal users for eight clients
Client Platforms available here Core or rule engine Maintenance Ease of use Key features Best for
Clash Plus Windows、macOS、Android、iOS Clash-compatible; core implementation varies by platform version Actively maintained Easy Subscription imports, proxy group switching First-time setup and use across desktop and mobile
Clash Verge Rev Windows、macOS、Linux mihomo Actively maintained Moderate Desktop configuration overrides, connection monitoring, TUN Users who need custom traffic routing on desktop
FlClash Windows、macOS、Android、Linux mihomo Actively maintained Easy to moderate Cross-platform configuration management, proxy group switching Users who want a consistent workflow on desktop and Android
Clash Nyanpasu Windows Supports mihomo; check the core you select Actively maintained Moderate Configuration management, connection logs, core settings Windows users who want to manage the core and configuration separately
Clash for Windows Windows Original Clash core lineage Discontinued Basic use is easy; migration and troubleshooting can be more involved Legacy Profiles, system proxy Users reviewing old configurations or reproducing past behavior
Clash Meta for Android Android Clash.Meta / mihomo lineage Actively maintained Moderate VPN traffic routing, configuration management, proxy group selection Android users familiar with Clash configuration structure
Surfboard Android Independent rule engine; uses Surge-style configuration Actively maintained Easy with compatible configs; more involved when migrating from other formats Sectioned configuration, rule-based routing Android users who already have a compatible configuration
ClashX Meta macOS Clash.Meta Discontinued Basic use is easy; long-term migration can be more involved Menu bar controls for proxy and policy switching Users maintaining legacy macOS configurations

What each client offers—and what to consider

Clash Plus Top pick

A good fit if you already have a subscription and want to get connected with minimal setup. After importing it, confirm the active configuration, choose a proxy in the relevant group, then enable the system proxy or VPN. Downloads are available for desktop and mobile, and the same check sequence works when switching devices—but similar interfaces do not mean settings sync between them. If your configuration uses custom rule providers, DNS, or sniffing fields, verify each feature on the target device instead of assuming mobile support matches desktop.

Clash Verge Rev

A good fit for users who want to inspect connections, check rule matches, or manage subscription overrides on desktop. Subscriptions are usually updated upstream, so put local rules in the override layer to avoid losing them on refresh. Start with the system proxy and check whether browser traffic reaches the client; consider TUN only for apps that ignore system proxy settings. Change one setting at a time when troubleshooting to distinguish permission, traffic-routing, and rule issues.

FlClash

A good fit for sharing a mihomo-oriented configuration between Linux and Android, or for users who want a similar interface on desktop and phone. Subscriptions and compatible rule fields can be reused, but system proxy settings, VPN permission, local paths, and startup behavior must be configured per device. On Linux, check the package format for your distribution; on Android, check the device architecture. After importing, test the same domain against the expected policy on each device, then compare any differences.

Clash Nyanpasu

A good fit for Windows users who want to manage subscription contents, GUI options, and the runtime core separately. On first import, confirm which core is selected and whether the configuration loads fully. Switching cores and refreshing subscriptions can both change behavior, so avoid doing both at once. If an older configuration reports an error, check the field and indentation named in the logs. If it loads but cannot connect, check whether another client is using the proxy port.

Clash for Windows Archived

Use the archived version to review old Profiles or reproduce past routing behavior—not for a new installation. Before migrating, note the configuration source, selected proxy groups, and local rules; move any rules you still need into an override layer the new client supports. Turn off the old app's system proxy before quitting to avoid leaving the system pointed at an inactive local port. If behavior differs between clients, compare the active core configuration rather than relying on modes with the same name in their interfaces.

Clash Meta for Android

A good fit for Android users who want to keep a Meta-based configuration and are comfortable checking proxy groups individually. After importing, grant VPN permission and confirm the intended configuration is active. If startup fails, check whether another app is using the system VPN; if the connection drops when the screen locks, review battery optimization and background restrictions. An unavailable node, a configuration load failure, and a background process being killed are different issues—don't start by changing both the subscription and background permissions.

Surfboard

A good fit if you already have a compatible Surge-style configuration. Surfboard uses an independent engine, so mihomo's configuration field list is not a reliable compatibility guide. Before migrating, check proxy protocols, proxy groups, and rule syntax, then test a small set of rules for expected direct and proxy matches. If your configuration relies on mihomo rule providers or Fake-IP behavior, choose a client from the same core lineage to avoid troubleshooting format and network differences at the same time.

ClashX Meta Archived

The menu bar controls make it easy to review system proxy and mode settings on older macOS setups, but this is not a good long-term option for a new system. Before migrating, save the subscription source and local rules, and note whether the app launches at login. Disable the old app before enabling a new client to keep both from changing system proxy settings. Choose an installer for Intel or Apple Silicon; verify that the app runs and that your configuration is compatible as separate checks.

Choose by device and use case

Checklist before switching clients

Test configuration loading, traffic reaching the client, and rule matching separately. A webpage loading does not tell you which policy the connection actually used.

  1. Back up your configuration sources first. Save the subscription URL, local YAML, and override rules; note the current selections in key proxy groups. Subscription URLs may contain account credentials, so don't paste them into public support tickets or screenshots.
  2. Enable only one traffic-routing method at a time. Turn off the old client's system proxy, TUN, or VPN before enabling the equivalent option in the new client. Test desktop and mobile separately to avoid mistaking a system permission conflict for an invalid subscription.
  3. Test direct and proxied connections separately. Choose a known destination for each and check the matched rule and outbound policy. If only some domains fail, review DNS settings or domain sniffing settings—not both at once.

If you're reinstalling the same client, first check the installer architecture and the location of the existing configuration. If you're also switching cores, start with a minimal configuration to confirm it runs, then add DNS, rule sets, and proxy groups back one at a time.

Which Clash client should you choose? Start with Clash Plus

For a first install, choose Clash Plus; for desktop overrides and connection troubleshooting, choose Clash Verge Rev; for Linux and Android, consider FlClash. Select your OS on the download page, then check the processor architecture or package format.

Download Clash
Clash Download