Head-to-head reviewPlatforms / cores / maintenance

Clash Client Comparison and Selection Guide

Start by narrowing down the options by operating system, then check configuration compatibility and traffic routing. Clash Plus is a good first choice for new users. Desktop users who regularly edit rules or use TUN should compare Clash Verge Rev and FlClash.

Compare platforms, cores, and maintenance status

Platform availability reflects the download options listed on this site, not every platform supported by the upstream projects. Ease of use is based on the steps needed to import a configuration, switch policies, and connect for the first time—not performance. Scroll horizontally on narrow screens to view the full table.

ClientPlatformsCore or implementationMaintenanceEase of useKey featuresBest for
Clash PlusWindows、macOS、Android、iOSVaries by platform; check the app detailsActively maintainedEasyConfiguration import and policy switchingFirst-time setup and desktop-and-mobile use
Clash Verge RevWindows、macOS、LinuxMihomoActively maintainedEasy to get started; moderate for advanced featuresConfiguration overrides, TUNDesktop power users
FlClashWindows、macOS、Android、LinuxMihomoActively maintainedEasySimilar workflows on desktop and AndroidUsers across multiple devices
Clash NyanpasuWindowsMihomo and others, depending on the selected coreActively maintainedModerateMultiple configurations and core selectionUsers who keep test and everyday configurations separate
Clash for WindowsWindowsOriginal Clash family; archived builds may differDiscontinuedModerateLegacy configurations and policy panelsMigrating or recreating a legacy setup
Clash Meta for AndroidAndroidClash.Meta family (Mihomo)Actively maintainedModeratePer-app proxy controls and configuration managementAndroid users who need per-app traffic control
SurfboardAndroidIndependent implementation using Surfboard configuration syntaxActively maintainedEasy with existing configurations; moderate when migratingSection-based configuration and per-app traffic routingUsers with existing Surfboard-format configurations
ClashX MetamacOSClash.Meta familyDiscontinuedEasy for existing users; moderate when migratingMenu bar policy switching and system proxyUsers migrating from a legacy menu bar client

Mihomo continues the Clash.Meta project. Similar names do not guarantee full compatibility: the original Clash, older Meta builds, and current Mihomo may differ in their support for rule types, DNS options, and tunnel settings. The core name alone also doesn't tell you whether your operating system is supported.

Reviews of eight Clash clients

Clash Plus: Import a configuration and connect

A good fit for first-time users and anyone who uses both a computer and a phone. After importing a configuration, check that the policy groups and rules appear in the interface, then connect using the steps for your platform. Mobile and desktop versions may differ in connection permissions, configuration formats, and supported fields. If you depend on specific DNS options or overrides, import the same test configuration on your target device and check which settings actually take effect after saving.

Clash Verge Rev: Desktop overrides and TUN

A good fit for desktop users with existing Mihomo configurations who need to preserve local rules. Put local changes in overrides to avoid repeatedly editing the original configuration whenever a subscription updates. Test the system proxy first, then try TUN separately to pinpoint whether a problem comes from the configuration, app proxy settings, or system routing and permissions. After applying overrides, check that the merged rules are in the expected order, especially that broad rules don't take precedence over later exceptions.

FlClash: Consistent workflows on desktop and Android

If your main devices are a computer and an Android phone, FlClash offers similar workflows for configuration, policies, and connection settings. When migrating, first confirm that the subscription works on one device, then check that all policy groups appear on the other. A consistent interface doesn't mean the system handles traffic the same way: check the system proxy and port on desktop, and VPN permission on Android. Don't copy local bypass settings across devices without checking them.

Clash Nyanpasu: Multiple configurations and core selection

A good fit for users who keep everyday, test, and backup configurations separate. Switching cores can change how a configuration is parsed, especially when it uses core-specific rules or DNS options. For a fair comparison, keep the configuration fixed and switch only the core. When testing a new configuration, keep the core fixed. If the connection fails, check the load log first to distinguish a configuration parsing error from a network timeout, then decide what to roll back.

Clash for Windows: For archival reference and migration only

If you're still using a legacy setup, note the local mixed-proxy port, active policy groups, and any custom rules before importing the configuration into a maintained client. Some settings saved in the old interface may not be present in the YAML file. Before testing the migration, turn off the old client's system proxy to prevent both apps from competing for the same port or the system from pointing to a process that has already exited. Archived builds are not recommended for new installations.

Clash Meta for Android: Per-app traffic controls

A good fit for users who want to include or exclude specific apps from proxying. Before your first test, confirm that Android has granted VPN permission and that no other VPN service is running on the device. If a browser connects but another app doesn't, check the app's inclusion settings and network settings before replacing the entire configuration. Local paths and interface names from desktop configurations also need to be adapted for the phone.

Surfboard: Use the matching configuration format

Surfboard doesn't use the Clash core and organizes configurations with its own section-based syntax. If you already have a Surfboard configuration, start by testing the import and rule matching. If you only have Clash YAML, check whether the configuration provider offers a Surfboard version. Migration involves more than changing the file extension: check proxy definitions, policy references, rule order, and the final match one by one. Don't assume policies with the same name behave identically.

ClashX Meta: Migration notes for legacy menu bar setups

If you're an existing user, note your policy selections, proxy mode, and system proxy setting in the current interface before switching to a maintained macOS client. Choose the right build for Apple Silicon or Intel. After switching, use the same app to test both a direct connection and a destination that should use the proxy, then check the match log in the new client. A menu bar icon or an enabled connection toggle alone doesn't confirm that all your old rules migrated correctly.

Choose a client by use case

Our pick: Clash Plus

If Clash Plus supports your platform and meets your configuration needs, start there. For Linux desktop, compare Clash Verge Rev and FlClash. If you need specific core fields, overrides, or per-app controls, narrow your options using the table above. Check your system architecture before downloading, then follow the user guide to verify the connection after installation.

Download Clash