Clash Client Comparison and Selection Guide

Narrow down your options by operating system and config format, then decide whether you need TUN, rule editing, or multiple subscriptions. Being available for your platform does not mean a client supports every field in your config.

Clash Client Comparison Table

Platform listings cover only the download options available here, not every build offered by each project. Clash.Meta is now maintained as mihomo, so either name may appear in different client generations. Sharing a core lineage does not guarantee full config compatibility.

Setup difficulty reflects the steps to import a config, choose a policy, and connect—not performance. Maintenance status is a general guide. For projects marked “Check release history,” review the release notes for your platform before installing. Scroll horizontally on smaller screens to see the full table.

Eight graphical clients; standalone Mihomo cores are not included.
Client Platforms Core or implementation Maintenance Setup Key features Best for
Clash Plus Android、iOS、Windows、macOS Check each platform's docs for core and config support Actively maintained Easy Import configs and connect through a graphical interface First-time installs and switching between phone and computer
Clash Verge Rev Windows、macOS、Linux mihomo Actively maintained Moderate System proxy, TUN, and config overrides Users who need to control which desktop traffic is routed
FlClash Windows、macOS、Linux、Android mihomo Check release history Easy to moderate Similar interface on mobile and desktop Users who want a consistent experience across devices
Clash Nyanpasu Windows Supports mihomo; available cores depend on the build Check release history Moderate Manage multiple profiles and switch the active one Users familiar with managing Clash configs
Clash for Windows Windows Original Clash lineage Discontinued Moderate Keeps the legacy config interface and workflows Users checking legacy configs or planning a migration
Clash Meta for Android Android Clash.Meta/mihomo lineage Check release history Moderate VpnService, rule-based routing, and policy groups Android users with existing Meta configs or who need to inspect routing rules
Surfboard Android Independent implementation Check release history Easy with an existing config; harder when migrating Manage rules and policies in its own config format Users with Surfboard-compatible configs
ClashX Meta macOS Clash.Meta lineage Discontinued Easy to moderate Switch policies and system proxy from the menu bar Users reviewing legacy behavior or moving old configs

Choose by Use Case

Client Reviews

An easy-to-use interface and a clean config migration are two different things. Here’s what each client is best suited for and what to check when trying it out.

Clash Plus

A good starting point for a new install, especially if you want to import a config, choose a policy, and connect through a graphical interface. Downloads are available here for Android, Windows, and macOS; on iOS, use the App Store. If you have a heavily customized YAML config, test it on a small scale first: check that policy groups are intact and common rules match. A successful import alone does not mean every field is active.

Clash Verge Rev

A good fit if you need to distinguish between system proxy and TUN on desktop, or add local rules to a subscription. When using config overrides, add one easy-to-check rule first and observe where the request goes. If the browser connects but the terminal does not, check whether the terminal app uses the system proxy before reinstalling the client or replacing the entire subscription. For Linux, choose the download that matches your distribution's package format.

FlClash

The similar interface on Android and desktop makes configs and policy groups easier to find when switching devices. It works well for reusing a subscription between phone and desktop, and is also an option for Android plus Linux. A similar interface does not mean traffic is routed the same way: Android requires system VPN permission, while desktop requires checking system proxy or other routing settings. Test custom rules separately on each platform.

Clash Nyanpasu

A good fit for Windows users with multiple Clash configs who need to switch between profiles for different purposes. To try it, import a familiar config and make sure the intended profile is active. After switching profiles, check whether policy group names and the default outbound have changed. If you also change the core, test with the original config first, then investigate any compatibility issues that may be core-related.

Clash for Windows

No longer maintained. Kept as an archive for checking the old interface and existing configs, not recommended for new installs. When moving to a new client, re-import the subscription or migrate only the rules and policy groups you need instead of copying the entire old settings directory. Note the old proxy port before switching. After closing the old client, check that the system proxy no longer points to that port before starting the new one.

Clash Meta for Android

A good fit for Android users with existing Meta configs who want to keep rule-based routing and switch policy groups manually. Grant VPN permission when prompted on first launch. If it works in the foreground but disconnects when the screen locks, check battery optimization and background activity restrictions first. If only certain apps take the wrong route from the start, review the mode, policy groups, and rule order.

Surfboard

An independent Android option if you have a Surfboard-compatible config. It is not a mihomo client with a different interface, so do not assume Clash YAML or Meta-specific fields will work unchanged. Before migrating, confirm that your config source can provide the right format, then test the protocols, policy groups, and rule types you need. Changing the file extension alone does not convert the config.

ClashX Meta

No longer maintained. Its menu bar controls are useful for checking policy selection and proxy-switching behavior in older configs. For a new macOS install, compare Clash Plus and Clash Verge Rev first. When migrating, choose the installer for Apple Silicon or Intel, then confirm the old client has quit and the system proxy has been restored. Finally, test the same rule's outbound behavior in the new client.

Recommendations and Pre-Install Checks

Best pick for a new install: Clash Plus. Linux users can start with Clash Verge Rev. If you rely on Meta config syntax on Android, check Clash Meta for Android first. If you still use Clash for Windows or ClashX Meta, keep the archived version as a reference when migrating configs.

  1. Check your OS and architecture first. If you're unsure which architecture your Android device uses, check its specifications. Choose a universal package only if the client explicitly offers one. On macOS, select the package for your chip; on Linux, choose one for your distribution and package manager.
  2. Then check the config format. A subscription URL, a single node link, and a local config file are different import types. Find out which one your source provides, then use the matching import option. Keep your original config before switching clients, and never post a subscription URL publicly.
  3. Finally, test what actually happens. After importing, test one destination that should use the proxy and one that should connect directly. Then check desktop TUN or the Android connection after locking the screen, if relevant. Once both routes behave as expected, migrate the rest of your configs.