Start by checking your platform and subscription format, then compare configuration tools, TUN mode and maintenance status. Clash Plus is the top pick for most users. For a consistent Flutter interface across platforms, consider FlClash; for a desktop override workflow, consider Clash Verge Rev.
Platform coverage reflects project support; package availability reflects what our site lists. Maintenance status is a general guide—check the relevant release notes before installing. Scroll horizontally to view the table.
Compare platforms, cores and ease of use—not version numbers or ratings.
Clash Meta ecosystem; built-in capabilities are limited by the archived package
Discontinued
Basic controls are easy; troubleshooting requires understanding system proxy settings
Menu bar controls for legacy setups; useful as a migration reference, not recommended for new installations.
Narrow down your options by use case
In-depth reviews of all eight clients
These reviews focus on workflows and migration effort. A client provides configuration controls, system integration and an interface; actual connectivity also depends on subscription contents, server protocols, your local network and rules. Switching interfaces alone won't fix network or routing issues.
Clash Plus: best for beginners and multiple devices
Clash Plus is a good starting point for most users. Windows, macOS, Android and iOS users can find platform-specific options in one download center, then check each platform's installation steps. Its strength is coverage across common device combinations—not identical settings on every platform. Check mobile VPN permissions, desktop traffic routing and subscription format support separately.
If you mainly need to import a subscription, choose a proxy group and switch modes for everyday use, start with those basics. Before importing complex YAML, check the platform's release notes for supported fields; don't assume a full configuration from another client will work as-is. iOS users can open the App Store from the iOS section of the download page.
Clash Verge Rev: desktop overrides and rule management
Clash Verge Rev runs on Windows, macOS and Linux desktops and uses the mihomo core. It's a good fit if you use a remote subscription as a base and maintain local overrides for DNS, rules or proxy groups. Keeping provider-managed node updates separate from your own settings means you won't have to re-edit the same YAML after every subscription refresh.
Advanced features mean keeping the source configuration distinct from the final effective configuration. If a rule stops working, check its order, whether the override is enabled and whether the referenced proxy group exists. There's no need to configure service mode, TUN and complex scripts all at once. Add settings one at a time to make it easier to spot what caused a problem.
FlClash: a consistent interface on desktop and Android
FlClash uses Flutter for its interface and is part of the Clash Meta / mihomo core ecosystem. It's a good fit for users who switch between Android and desktop devices. Configuration switching, outbound modes and proxy groups follow similar interaction patterns across platforms, so there's less need to relearn where settings are. FlClash isn't listed as an iOS client on our site; iOS users should choose a separate app.
Similar interfaces don't mean identical system permissions. Android typically routes traffic through system VPN permissions; on desktop, distinguish between system proxy and TUN. Start with the subscription import guide to get one configuration working, then add local rules gradually. For DNS, Fake-IP and proxy group references, see the advanced configuration manual.
Clash Nyanpasu: desktop customization and configuration
Clash Nyanpasu suits users who want to customize their desktop interface and organize configurations. Keep the project's supported platforms separate from the packages listed on our site: our download center lists the Windows package, but that doesn't mean other platforms are unsupported. Before choosing a release, check which cores it includes, whether you need to select one, and which core extensions your configuration relies on.
Before trying a different core or configuration workflow, keep a working configuration as a reference. Unsupported protocols, ignored fields or changed rule behavior after switching cores don't necessarily mean your subscription has expired. If all you need is subscription import, these customization options aren't essential—Clash Plus or FlClash are better candidates to start with.
Clash for Windows: archive and migration reference
Often shortened to CFW, Clash for Windows historically had releases for desktop platforms beyond Windows. It belongs to the original Clash / Clash Premium ecosystem and is discontinued. Our site retains the Windows archive for reference and migration from older setups; it's not recommended as a long-term choice for new devices.
An older configuration that starts successfully may still lack protocols or rule fields added in mihomo. To migrate to Clash Plus, Clash Verge Rev or FlClash, import your subscription first, then recreate system proxy, TUN and local overrides as needed. Don't copy the entire old application folder as a shortcut, and don't rely on toggle names from old tutorials to find settings in a new client.
Clash Meta for Android: mobile YAML workflows
Often shortened to CMFA, Clash Meta for Android suits users with an existing Clash YAML subscription who want an Android-focused client. Check the package architecture and Android requirements before choosing an import method. Connecting for the first time usually requires system VPN permission. If another VPN app is already routing traffic, stop it first and then check how CMFA connects.
Android battery and background restrictions can interrupt persistent connections, so a disconnect after locking the screen doesn't automatically point to a bad node. Check battery settings, background permissions and logs together. Compared with FlClash, the main differences are mobile-specific controls and interface layout—not a guarantee that the same subscription will run faster in one app. Compare connection performance under the same conditions.
Surfboard: check the configuration format first
Surfboard is an Android proxy client, but it's not just Clash with a different interface. It has its own implementation and configuration syntax, so importing a Clash YAML file won't make every setting work. Users with Surfboard-compatible configurations who know its rule syntax can keep using their existing workflow. If you only have a Clash YAML subscription, ask your provider whether it offers a compatible format.
Converting formats involves more than changing a file extension. Protocol parameters, proxy group types, rule syntax and DNS behavior may all need remapping. If conversion takes more effort than your everyday needs justify, choose Clash Plus, CMFA or FlClash instead. Surfboard is included to show another Android option—not to suggest that every configuration works interchangeably across these clients.
ClashX Meta: archived macOS menu bar client
ClashX Meta is a macOS client in the Clash Meta core ecosystem, designed around menu bar controls. It's discontinued; our site keeps the download entry as a reference for migrating existing setups. The archived package has limited core capabilities. The name includes Meta, but that doesn't mean it supports every current mihomo feature or works with newer macOS network behavior.
For new installations, consider the macOS versions of Clash Plus, Clash Verge Rev or FlClash, and choose the package for Apple Silicon or Intel. When migrating an older setup, check not only the configuration but also whether the menu bar app has leftover startup items or the system proxy still points to an old port. Keep the old configuration for reference; there's no need to let two clients route traffic at the same time.
Migration checklist: before switching clients
The goal of migration is to keep a configuration you can understand, not to carry over every piece of historical state. Note your subscription source, selected proxy groups, proxy mode and local overrides. Subscription URLs may contain private access credentials—never include them in public screenshots or support requests. Then disable system proxy and TUN in the old client to prevent port or routing conflicts with the new one.
Check the configuration format. Distinguish Clash YAML, client-specific settings and Surfboard-compatible configurations. Being able to import a file doesn't mean every field works; if you see warnings, check what the core supports first.
Migrate the subscription first, then overrides. Establish a working connection with a minimal configuration before adding custom rules and DNS settings. Changes to node names in a remote subscription can also break local proxy group references.
Test one traffic-routing method at a time. Start with the system proxy or mobile VPN. Once basic access works, enable desktop TUN if needed. If a browser works but other apps don't, check whether those apps follow the system proxy.
Compare under the same conditions. Use the same subscription, proxy group and destination, and account for DNS and routing mode. Interface responsiveness and connection throughput are different issues; don't treat them as the same result.
Check behavior after restarts and updates. Test startup, wake from sleep, subscription refresh and system proxy restoration. Day-to-day reliability is usually more useful than a single successful test.
Recommendations and download options
Clash Plus is the top pick for most users. Choose the installer for your OS, import a subscription and verify your connection before moving to a more complex configuration workflow. Consider FlClash for a similar interface on Android and desktop, Clash Verge Rev for desktop overrides and rule management, or Clash Nyanpasu for more UI customization.
For Android-specific controls, consider CMFA; choose Surfboard if you already have a compatible configuration. Clash for Windows and ClashX Meta are retained as archive and migration references. The download center lists clients and packages by platform; files are not distributed directly on this page.