Selection Guide / Client Comparison

Compare and choose a Clash client

Start by filtering for your operating system, then check whether your configuration will carry over. For a first install, consider Clash Plus. If you use Linux, already have rule files, or are migrating from an older client, use the table below to narrow your options.

Clash Client Comparison Table

Platforms listed reflect the downloads available on this site, not every platform supported by the upstream projects. Ease of setup is based on importing an existing configuration and making the first connection; it is not a performance rating. Scroll horizontally on narrow screens to view all columns.

Platforms, cores, maintenance, and use cases
Client Platforms on this site Core or configuration system Maintenance status Ease of setup Key features Best for
Clash Plus Windows、macOS、Android、iOS Varies by platform release; desktop core details do not necessarily apply to mobile Actively maintained Easy Subscription import and proxy group switching First-time users who need desktop and mobile options
Clash Verge Rev Windows、macOS、Linux mihomo Actively maintained Moderate Configuration management, connection inspection, and rule troubleshooting Desktop users who need to diagnose routing
FlClash Windows、macOS、Linux、Android mihomo Actively maintained Easy Similar configuration and proxy group controls on desktop and Android Users who switch between a computer and an Android device
Clash Nyanpasu Windows Supports mihomo; check the core settings in use Actively maintained Moderate Configuration management and core selection Users who want to compare desktop core options
Clash for Windows Windows Original Clash family Discontinued Easy for existing users; check compatibility before a fresh install Legacy Profiles and proxy group interface Users organizing legacy configurations or preparing to migrate
Clash Meta for Android Android Clash.Meta family (mihomo lineage) Actively maintained Moderate Configuration switching, proxy group selection, and Android VPN integration Android users with existing Meta configurations
Surfboard Android Proprietary configuration system; not a Clash core Actively maintained Easy with a compatible configuration; moderate when migrating Surge-style configuration and rule-based routing Users who already have a Surfboard-compatible configuration
ClashX Meta macOS Clash.Meta family Discontinued Easy for existing users; check compatibility before a fresh install Menu bar mode switching and system proxy controls Mac users checking a legacy setup

mihomo continues the Clash.Meta project lineage. Seeing Meta or mihomo in the interface can help indicate configuration compatibility, but it does not replace testing an import. Even clients in the same core family may differ in subscription updates, rule resource paths, and system permission controls.

Client Reviews

Expand each review to see what to check before getting started and what can be overlooked when migrating from an older setup.

Clash Plus: A first install or use across multiple devices

Clash Plus is our default recommendation. It has download options for Windows, macOS, Android, and iOS, so start by choosing your platform. For a first setup, confirm that your subscription is imported, a proxy group is selected, and the system connection is enabled. If your configuration depends on specific protocol support, rule resources, or DNS fields, import a sample on the target device first to check whether it will work. Check permissions and settings separately on each platform; a successful connection on one device does not verify another.

Clash Verge Rev: Desktop rules and connection troubleshooting

Clash Verge Rev suits users who regularly edit configurations or need to see which rule a connection matched. After importing a configuration, check which one is active, then inspect the connection details to see how traffic is routed. If the configuration parses but behaves unexpectedly, check rule order, policy group names, and whether rule resources are available before switching clients. If you plan to use TUN, check system permissions and routing separately so a permissions issue is not mistaken for a broken configuration.

FlClash: A consistent workflow on desktop and Android

FlClash offers similar configuration and proxy group controls on desktop and Android, making it a good fit for users who want to minimize the learning curve. Enabling the system proxy on desktop is different from granting Android VPN access. Before reusing the same YAML, check for desktop file paths; paths to local rule resources cannot simply be carried over to a phone. Once the configuration opens on both devices, check automatic updates and connection behavior separately.

Clash Nyanpasu: Checking desktop cores and configurations

Clash Nyanpasu suits users who want to inspect core settings while managing configurations through a graphical interface. Before choosing it, identify the protocol fields and rule types your existing configuration relies on, then check which core the client is using. During migration, keep the original configuration separate from any test copies. If an import fails after changing cores, start with the field named in the first parsing error; avoid changing nodes, DNS, and traffic routing all at once. This makes it easier to distinguish configuration issues from network problems.

Clash for Windows: Legacy use and migration options

The archived Clash for Windows release is useful for comparing the old interface and migrating existing configurations. Before moving to a maintained client, save your local YAML, note where the configuration came from, and preserve any manually edited rules. System proxy settings and services enabled in the old client are not carried over with the configuration file. When switching clients, make sure the old process has exited and its proxy settings are disabled. After the new client reads the file, check the default proxy group selection again; different policy choices can otherwise look like rule changes.

Clash Meta for Android: For Android users with existing Meta configurations

Clash Meta for Android suits users who already have a Meta-format subscription or local configuration. After importing, select the configuration and check the current proxy group selection. First-time setup also requires Android VPN authorization. If another VPN app is installed, check which app currently controls the connection. If the connection works but becomes unstable when switching networks, check Android's network switching and background activity restrictions before reviewing configuration logs. Do not assume the rules are wrong based on a single connection test.

Surfboard: Choose based on your configuration source

Surfboard uses its own supported configuration format, so confirm that your provider offers a Surfboard-compatible configuration before choosing it. Proxy groups, rule fields, and DNS settings in Clash YAML cannot be transferred just by changing the file extension. If you only have a Clash configuration, choose an Android client that can read it directly. If you already have a Surfboard configuration, import it and check the policy groups and rules, then verify traffic routing through Android's VPN status and the client's connection logs.

ClashX Meta: Migrating a legacy Mac setup

The ClashX Meta menu bar controls make it easy to check mode selection and system proxy status in a legacy setup. Since the project is no longer maintained, consider actively maintained Mac clients first for a fresh install. Before migrating, save the original configuration and distinguish local files from remote subscriptions. Also note any proxy mode enabled manually from the menu bar. After switching, check the proxy settings in macOS Network settings and recheck rules and global mode in the new client to prevent both clients from changing system settings at once.

Choose by use case

First install: Make one connection you can verify

Start with Clash Plus. Download the version for your operating system, import your existing subscription, keep the configuration's default rule mode, and select a proxy group. After connecting, check that the client shows a corresponding connection record. For the first test, leave DNS, rules, and traffic routing unchanged so you can troubleshoot import, authorization, and routing one step at a time.

Advanced setup: Track which rules match

For desktop, start by comparing Clash Verge Rev. On Windows, you can also check Clash Nyanpasu if you need to review core options. Compare them using the same configuration and traffic routing. Check which rule a connection matches before deciding whether to edit the configuration or switch clients.

Multiple devices: Check platform overlap first

If your devices include an iPhone, Clash Plus is the option listed for it on our downloads page. If your mix includes Linux and Android, compare FlClash, which has options for both. The same app name does not mean configurations sync automatically; handle subscription updates, system permissions, and connection checks separately on each device.

Older computers: Check the OS and architecture before assessing performance

First check the operating system, processor architecture, and installer requirements, then try a compatible version that is still maintained. Use the same configuration and connection method to see whether the device runs reliably under everyday workloads. Archived clients can help with migration comparisons, but an older release date does not make one a better fit for an older computer or prove that it uses fewer resources.

Our recommendation: Start with Clash Plus

For a first install, or when choosing an option for Windows, macOS, Android, or iOS, start with Clash Plus. On Linux, compare Clash Verge Rev and FlClash. If you have a configuration in a specialized format, prioritize import compatibility over interface preferences. Check your operating system and architecture before downloading, and save legacy configurations and manual rules before migrating.