Choosing a Client · Platform and Config Compatibility

Clash Client Comparison
Platforms, cores, and use cases

First check that the client runs on your device, then confirm it can import your subscription. Finally, compare rule handling, TUN support, and the interface. Similar client names don’t guarantee the same core capabilities, config formats, or system permissions.

This page covers the eight clients listed in the download center. Platform support describes each project’s scope, not necessarily the installers available here. Check the download center for available builds, CPU architectures, and system requirements.

Download Clash Compare Clients

Start with Clash Plus, then narrow it down by platform

New to proxy clients or need support across several devices? Start with Clash Plus. It covers Windows, macOS, Android, and iOS, making it a practical choice for building a routine around importing subscriptions, choosing an exit, and everyday rule routing. Official site: clashplus.io. Cross-platform support doesn’t mean every advanced feature works the same way on every platform. Check the details for any protocols, background operation, or config extensions you rely on.

For more desktop configuration options, compare Clash Verge Rev and Clash Nyanpasu. If you want a similar interface on desktop and Android, consider FlClash. Android-only users can also look at Clash Meta for Android. Surfboard is a better fit if you already have a config in its format; a shared protocol name alone doesn’t guarantee compatibility.

Clash for Windows and ClashX Meta are discontinued archival options. They’re kept here for reference with legacy setups, not recommended for new devices. A client that still launches may still have a core that can’t handle newer protocol fields.

Eight Clash Clients Compared

Ease of use is a qualitative assessment of common import and connection workflows, not a performance score. Maintenance status is a guide and may change; check release notes before installing. On narrow screens, scroll the table horizontally.

Client Platforms Core and Config Maintenance Ease of Use Key Features and Workflow Best For
Clash Plus Windows、macOS、Android、iOS Check each platform’s release notes for specific core and protocol support Actively maintained Easy; start with a subscription and mode settings Multiple platform downloads for a straightforward daily connection workflow Beginners and multi-device users; top pick on this page
Clash Verge Rev Windows、macOS、Linux mihomo; Clash YAML configs Actively maintained Easy to get started; advanced settings take some learning Subscription and config management, rule inspection, system proxy, and TUN Desktop users who regularly adjust rule routing
FlClash Windows、macOS、Linux、Android mihomo; Clash YAML configs Actively maintained Easy; system-level routing works differently across platforms Cross-platform interface, proxy group controls, and config management Users who switch between desktop and Android
Clash Nyanpasu Windows, macOS, Linux; this site provides a Windows download Primarily mihomo; can manage different cores. Available options vary by release. Actively maintained Intermediate; distinguish client settings from core settings Tauri desktop interface, core management, subscription, and proxy settings Users who want control over core selection and configuration
Clash for Windows Historically supported Windows, macOS, and Linux; this site archives the Windows version Legacy core from the original Clash family; not the same as current mihomo Discontinued Familiar to existing users; not recommended as a first choice for new users Legacy config workflows and reproducing older setups Users maintaining existing setups
Clash Meta for Android Android Meta/mihomo family; Clash YAML configs Actively maintained Intermediate; requires VPN permission and handling background restrictions System VPN routing, per-app coverage, and config switching Android-only users and those routing traffic by app
Surfboard Android Its own implementation; Surge-style config, not a Clash core Actively maintained Depends on the config source; migration requires conversion Organizes rules and policies around compatible config formats Android users with subscriptions in the supported format
ClashX Meta macOS Legacy Meta-family core; capabilities depend on the archived build Discontinued Easy to get started; advanced use depends on config files Menu bar access, config switching, and system proxy Users keeping a legacy macOS workflow

The same core doesn’t mean the same experience. mihomo handles protocol parsing, DNS, and rule matching; the client handles subscriptions, permissions, and the interface. Connection performance also depends on the route, server configuration, and local network—not just the client’s name.

Client Reviews: Workflows and Limitations

Clash Plus: A practical starting point across platforms

Clash Plus is the recommended starting point here because it’s available on popular desktop and mobile platforms, making it easier to get through the essentials: install, import, and connect. If you’re new to proxy clients, choosing the right OS and CPU architecture matters more than comparing a long list of advanced toggles. After importing a config, make sure it’s enabled, then check the proxy mode and which route your traffic is using.

For multiple devices, you can manage configs from the same subscription source, but don’t assume every desktop setting applies to your phone. Mobile operating systems handle background activity, network permissions, and traffic routing differently. If you depend on a specific protocol or rule extension, check support for that platform instead of assuming features work the same everywhere.

Clash Verge Rev: Desktop rule routing and config management

Clash Verge Rev suits desktop users who regularly switch between subscriptions, proxy groups, and settings. Its mihomo core supports a broad range of protocols and rules, but seeing a feature in the interface doesn’t mean your imported subscription has the required settings. If traffic isn’t routed as expected, check the active config and matching rules first.

To route traffic from more apps, look into TUN and service permissions. If everyday apps like browsers work through the system proxy, there’s no need to enable every routing method. Keep personal changes separate from remote subscriptions when using overrides or merging configs, so updates don’t wipe your edits. For the basics, see the User Guide.

FlClash: A similar workflow on desktop and Android

FlClash stands out for offering a consistent workflow across platforms. If you often switch between a computer and an Android device, familiar screens can make the transition easier. Subscription, proxy group, and connection controls follow similar patterns. However, a similar interface doesn’t mean the operating systems behave the same: desktop system proxy and Android’s VPN interface route traffic differently.

Before importing, make sure the config is in Clash YAML format and that the current core supports its protocols. If the connection drops when your phone locks, check battery optimization and background permissions first. If only some desktop apps bypass the proxy, check whether they respect the system proxy. Troubleshoot these separately instead of repeatedly switching clients.

Clash Nyanpasu: Core management and desktop configs

Built with Tauri, Clash Nyanpasu is a desktop client for users who want a clear distinction between the client, config files, and core. Subscription management determines where configs come from; proxy mode determines how rules are used; the core determines which syntax and protocols can run. This site’s download center provides a Windows build. The project’s support for other operating systems is separate from the packages available here.

Switching cores isn’t a speed boost. Before changing cores, check compatibility with your protocols, DNS fields, and rule providers, and back up a working config. Preview cores are best for users with specific testing needs; for everyday use, stick with a combination you’ve verified as stable. For background on the original Clash core, Meta, and mihomo, see the Technical Reference.

Clash for Windows: Reference for archived setups

Often shortened to CFW, Clash for Windows historically supported more than Windows. This site retains a Windows archive download mainly for reproducing legacy workflows and migrating configs. The project is discontinued, so the fact that it still launches doesn’t imply ongoing support for newer systems, protocols, or config fields.

When migrating from CFW, first export the original subscription URL and any personal config changes, then import them into a maintained client. Avoid copying the entire app data directory: caches, service paths, and runtime state may not be compatible. If a legacy config fails in the new client, check its fields one by one instead of staying on an obsolete setup just to keep the old interface.

Clash Meta for Android: Per-app routing and background operation

Often shortened to CMFA, Clash Meta for Android is suited to users who only need Android and want to control which apps are routed. It uses Android’s VPN interface to handle traffic, and the first connection usually requires system permission. Another VPN app may already be using that interface, so check which app is currently managing the connection.

Per-app routing and rule routing are separate settings: the first determines which apps enter the routing process; the second determines which exit they use. If an app never follows your rules, check whether it’s included in the routed apps first, then review the rules and DNS settings. Some systems restrict background activity, so check your device’s battery settings if you need a persistent connection.

Surfboard: Check the config format first

Surfboard is an Android proxy client, but it isn’t Clash with a different interface. It uses Surge-style configuration, so you can’t just change a Clash YAML file’s extension and expect it to work. Similar policies, rules, or server details don’t guarantee compatibility in keywords, group behavior, or protocol settings.

If you already have a Surfboard-compatible subscription, you can keep using it with its supported config format. If you only have a Clash subscription, ask the provider whether it offers a compatible version. Conversion may drop protocol settings, DNS behavior, or rule-set definitions. After importing, verify that rules match as expected. For beginners, a client that directly supports your existing config usually means fewer steps.

ClashX Meta: A legacy macOS menu bar workflow

ClashX Meta is operated mainly from the macOS menu bar and may be useful as a reference for legacy setups. It’s discontinued, and the Meta-family core in an archived build should be assessed on its own. The Meta name doesn’t guarantee full compatibility with current mihomo. New users can compare Clash Plus, Clash Verge Rev, or FlClash instead.

If you keep using an older version, watch for changes to permissions, proxy restoration, and startup behavior after macOS updates. Before migrating, note the current ports, subscription URL, and manual rules. After migration, let only one client manage the system proxy. If multiple apps compete for proxy settings, one may stop connecting when another exits; that’s separate from whether the subscription is valid.

Narrow Down Your Choice by Use Case

New to proxy clients? Start with Clash Plus. Choose your device in the download center, install the app, then import a subscription, enable the config, and select a rule mode. Test a commonly used app before exploring advanced options like TUN or DNS overrides. Switching clients usually won’t fix a subscription, account, or config-format problem.

Advanced configuration: Compare Verge Rev and Nyanpasu. Verge Rev suits a desktop-focused config management workflow; Nyanpasu is a better fit if core management matters to you. List the protocols, rule sets, and traffic routing methods you need, then check each one. If you plan to write your own rules, learn match order and proxy group references before choosing an interface.

Multiple devices: Start with Clash Plus, then consider FlClash. If your devices include iOS, Clash Plus’s broader platform support fits this use case. For desktop and Android, FlClash is also worth comparing. Your subscription may limit the number of devices or simultaneous connections; cross-platform client support doesn’t change those limits.

Older computers: Check the OS and architecture first. Compatibility with your OS and required runtimes matters more than whether an interface looks lightweight. Don’t choose discontinued software just to reduce resource use. When testing, keep the config, traffic routing method, and usage scenario consistent, then check your system’s task manager. This site doesn’t publish memory rankings that ignore device differences.

Linux users can compare Clash Verge Rev and FlClash in the download center, then choose a package for their distribution. Servers and routers are different deployment scenarios: they usually require managing the mihomo core and service configuration directly, so desktop GUI instructions won’t necessarily apply.

Before You Migrate: Check Subscriptions, Permissions, and Rules

Save your config source before moving personal changes

Record the subscription URL, update method, and currently selected config name. If you’ve added manual direct-connection rules, changed DNS settings, or adjusted proxy groups, save those edits separately. Subscription URLs may contain account credentials; don’t post full links, config files, or logs with sensitive information in public forums.

When launching the new client for the first time, import the unmodified config and confirm it parses and connects before gradually adding your personal rules. This helps identify whether a problem comes from the subscription, format compatibility, or a later override. Clients may save proxy group selections differently, so check the active exit for your usual groups again.

Let only one client route traffic at a time

Before switching desktop clients, turn off the old client’s system proxy and TUN, then check whether its services are still running in the background. On Android, stop the old VPN connection before authorizing the new app. If two clients use the same port or routing interface, you may lose connectivity even when the rules are correct.

Start by checking the active proxy mode, then review connection logs or rule matches. A latency test returning a result only confirms that test request succeeded; it doesn’t prove that every app is routed. Still stuck? Visit Troubleshooting to check subscriptions, permissions, DNS, and rules, or see the User Guide for import steps.

Check the download center for available builds

After choosing a client, select an installer for your operating system, CPU architecture, and package format. A project’s supported platforms, the builds available on this site, and the platforms your device can run are three different things. Visit the download center to check system requirements and available installers; don’t assume a package is suitable based on the client’s name.