Eight clients · Six comparison criteria

Clash Client Comparison & Selection

Start by ruling out options that cannot run on your operating system, then compare the core, maintenance status, and learning curve. For a straightforward recommendation, choose Clash Plus first; for advanced desktop configuration, compare Clash Verge Rev and FlClash.

01
Confirm your platform

First identify whether you use Windows, macOS, Android, iOS, or Linux.

02
Check maintenance status

For new installations, prioritize actively maintained clients.

03
Match your workflow

For basic connections, look for clear controls; for advanced use, compare rule and override support.

The bottom line

Clash Plus is the top choice for most users

Clash Plus supports Windows, macOS, Android, and iOS, with common controls kept in one place and a relatively gentle learning curve for importing subscriptions, switching modes, and configuring the system proxy. For people new to Clash, users who want a similar workflow across computers and phones, or anyone seeking reliable everyday rule-based routing, it is the most straightforward starting point.

If you mainly use Linux or need more granular overrides and desktop integration, consider Clash Verge Rev or FlClash. Users of Clash for Windows or ClashX Meta do not need to delete their old setup immediately, but should export subscription URLs and custom rules before moving to a maintained client.

Side-by-side comparison

Platforms, cores, and learning curve

Platform coverage in this table is based on the installers provided on our download page. “Meta” refers to the Clash.Meta family of cores; mihomo is the current name of that core project.

Client Supported platforms Core Maintenance Ease of use Key features Best for
Clash Plus Windows、macOS、Android、iOS mihomo Actively maintained Low Cross-platform interface, subscription management, rule modes, and centralized system proxy controls First-time users, multi-device setups, everyday connections
Clash Verge Rev Windows、macOS、Linux mihomo Actively maintained Medium Comprehensive overrides, desktop tray controls, system proxy, and TUN settings Advanced desktop users, Linux users
FlClash Windows、macOS、Linux、Android mihomo Actively maintained Medium Broad desktop and Android coverage with a similar workflow across devices Users switching between platforms who value a consistent workflow
Clash Nyanpasu Windows mihomo Actively maintained Medium Rich configuration management, proxy group controls, and desktop settings Windows users familiar with rules and configuration files
Clash for Windows Windows Original Clash family No longer maintained Medium Large ecosystem of legacy interface and configuration guides Existing users reviewing legacy configurations and migrating; not recommended for new installations
Clash Meta for Android Android Clash.Meta Actively maintained Medium Mobile subscriptions, proxy modes, per-app routing, and override settings Android-only users who need detailed mobile routing
Surfboard Android Independent core with support for common Clash configuration concepts Actively maintained Medium to high Independent mobile rule management and configuration import workflow Users who understand rule syntax and are willing to verify configuration compatibility
ClashX Meta macOS Clash.Meta No longer maintained Medium Menu bar controls and a legacy macOS workflow Existing users migrating; not recommended for new installations

Choose by use case

Narrow down the options based on how you actually use the client

The same subscription can work across different clients, but interface controls, configuration compatibility, and platform capabilities are not identical.

Client-by-client review

The trade-offs across eight clients

The reviews below focus on the clients and installers provided on this site. Version numbers, release dates, and subjective ratings are not used as selection criteria.

Actively maintained

Clash Verge Rev

mihomo

Clash Verge Rev is designed for desktop use across Windows, macOS, and Linux. It provides a comprehensive desktop management structure for Profiles, proxy groups, the system proxy, TUN, and configuration overrides, making it suitable for users who inspect runtime settings, switch between multiple configurations, or maintain custom rules.

More settings mean you should distinguish between client settings and configuration-file fields before getting started. For example, mixed-port defines a listening port, mode selects rule, global, or direct operation, and the system proxy routes application traffic through the client. Once these boundaries are clear, management becomes much easier.

Actively maintained

FlClash

mihomo

FlClash supports Windows, macOS, Linux, and Android, making it a good fit for users with a mixed device lineup who still want a similar workflow. It handles subscription management, proxy group selection, and common connection settings, helping establish consistent habits between desktop and Android.

With FlClash, check the processor architecture and installer type for each device. Linux users should also confirm that their distribution supports the selected package format, while Android users should choose a package for the device architecture. After a successful import, test the connection in rule mode before enabling TUN.

Actively maintained

Clash Nyanpasu

mihomo

This site provides a Windows installation entry for Clash Nyanpasu. It is best suited to users who understand the roles of Profiles, proxy groups, rule modes, and core settings. Its rich configuration controls are particularly useful when managing multiple subscriptions, inspecting proxy groups, or adjusting desktop behavior.

First-time users can establish a basic connection, but should not change core parameters, DNS, and override rules all at once. A safer sequence is to import a known-good configuration, confirm that rule mode connects, and then duplicate the configuration for experiments. This keeps the original subscription separate from local changes.

No longer maintained

Clash for Windows

Original Clash family

Clash for Windows was once widely used, so many guides still refer to its legacy interface. The project is no longer maintained and should not be the default choice for a new installation. Labels such as Profiles, Proxies, Rules, and General in older guides can still provide context, but do not necessarily match the menus in current clients.

Before migrating, existing users should record the subscription URL, current proxy groups, and custom rules, then import them again in the new client. Do not copy the entire application directory over the new client: different clients may store settings, caches, and core files in different locations.

Actively maintained

Clash Meta for Android

Clash.Meta

Clash Meta for Android is designed for Android users who want finer control over mobile proxy behavior. It provides subscription, proxy mode, per-app routing, and override settings for users who can distinguish rule, global, and direct modes and are prepared to handle Android background restrictions.

Mobile connection problems are not always caused by configuration. Battery optimization, background restrictions, VPN permissions, and other network tools can all interfere. After importing a configuration, grant the required permissions and check for the VPN indicator in the status bar. If the system stops the app, adjust its background activity policy.

Actively maintained

Surfboard

Independent implementation

Surfboard is an Android client with its own implementation that supports common Clash rules and configuration concepts. It suits users who already understand proxy groups, rule matching, and subscription updates, and offers another configuration management option on Android.

An independent implementation means not every mihomo field should be assumed compatible. Before importing, check whether the configuration relies on specific DNS settings, rule providers, or scripting capabilities. After importing, verify proxy groups, rule counts, and connection results. If a field is not recognized, prefer a compatibility format supported by the subscription provider.

No longer maintained

ClashX Meta

Clash.Meta

ClashX Meta is designed for the macOS menu bar, retaining a relatively simple desktop control style, but the project is no longer maintained. Existing users can still use it to understand their configuration structure and menu actions; new users should choose Clash Plus, Clash Verge Rev, or FlClash instead.

Before migrating, disable the system proxy in the old client and quit its process completely so two clients do not listen on the same port. After importing the subscription into the new client, reauthorize the system proxy or network extension and check that the rule mode is active. The old client's menu state does not prove that the new client has taken over traffic.

Migrating from archived clients

Move from CFW or ClashX Meta to a current client

The key to migration is preserving the configuration source and local rules, not copying the old application itself.

  1. Save the subscription source

    Find the source URL for the current Profile in the old client. If the configuration comes from a local file, back up the YAML file separately and note its purpose.

  2. Document local changes

    Check whether you manually added rules, proxy-groups, DNS, or port fields. Subscription updates may overwrite content written directly into the original configuration, so save local changes separately.

  3. Quit the old client

    Disable the system proxy first, then quit the old program completely. This prevents listening-port conflicts involving mixed-port and stops two menu bar or tray processes from changing the system proxy at the same time.

  4. Import and verify

    Import the subscription again in the new client, select a rule mode and proxy group, and enable the system proxy. Finally, check web access and the exit address to confirm that traffic follows the expected path.

Selection checklist

Four checks before downloading

01

Does the installer match your system?

On macOS, distinguish Intel from Apple Silicon; Android and Linux may also require a specific processor architecture or package format. If you are unsure, check your system information instead of guessing from the filename.

02

Is the client still maintained?

For new installations, choose an actively maintained project. Archived clients are better suited to existing users reviewing configurations and completing migrations; a large number of old tutorials does not make one the default choice.

03

Does the configuration depend on a specific core?

Configurations containing mihomo-specific fields, rule providers, or advanced DNS settings should preferably use a mihomo client. With an independent core, verify field compatibility first.

04

Do you actually need advanced features?

If you only need subscription import, rule-based routing, and a system proxy, clear basic controls matter most. Choose a more fully featured desktop client when you need overrides, multiple configurations, or TUN tuning.

Browse downloadable clients by platform

The download page groups installers and system requirements for Windows, macOS, Android, iOS, and Linux.