Client comparison · Platform and config compatibility
Clash Client Comparison and Selection Guide
Start with your device, then check the core and config. Clash Plus is our top pick; choose another option if you need desktop rule management, a multi-device workflow, or support for a legacy setup.
The platforms covered here match the download options on this site; they do not represent every build available for each project. This comparison focuses on practical requirements, not performance scores.
Narrow down your options
Best for beginners: Clash Plus
If you want to import a subscription, choose a rule mode, and turn on a proxy on your laptop or phone, start with Clash Plus. Our download page lists builds for Windows, macOS, Android, and iOS. Get the basics working first, then explore rules, DNS, and how traffic is routed. See clashplus.io for platform-specific features and release notes.
For advanced desktop config management, compare Clash Verge Rev. If you want a similar interface on your computer and Android, consider FlClash. For managing Clash configs on Android only, look at Clash Meta for Android. Linux users can choose between Clash Verge Rev and FlClash—there's no need to pick an app from another platform just to match its name on mobile.
Eight clients · Six comparison points
Compare platforms, cores, and maintenance status
“Ease of use” describes how much setup you need to understand; it is not a quality rating. “Actively maintained” does not guarantee compatibility with every OS version, so check system requirements and release notes before installing. On phones, swipe horizontally to view the full table.
Platforms listed on this site, core, maintenance status, ease of use, standout features, and recommended users
Legacy Meta core; not the same as a current mihomo build
No longer maintained
Basic use is easy; troubleshooting legacy setups may take work
Menu bar controls and traditional config file workflow
Reference for migrating an existing macOS setup
The core name and the app name are not the same thing. Meta is a development branch of the Clash core, continued by mihomo. Clients may bundle different builds and merge or override config settings. To determine whether a YAML field takes effect, check the running core, config syntax, and the final config generated by the client.
Client reviews
Workflows and config compatibility
The reviews below explain why you might choose each client and what to check first. Node quality, subscription contents, and your local network often affect the experience more than the interface does. Switching clients is not a universal fix for connection problems.
Clash Plus: From subscription import to everyday use
Our top pick because the setup flow is easy to follow: download the right build, import a config, choose a proxy group and mode, then enable the system proxy or connect through the mobile VPN. For newcomers to the Clash ecosystem, getting this basic workflow running is more useful than comparing a long list of advanced settings. Find downloads for desktop and mobile on our site; for iOS, use the download page to open the App Store.
Keep in mind that network permissions and background behavior vary by OS, even for apps with the same name. Don't assume desktop features such as mixed ports or LAN sharing work the same way on a phone. Check the platform details at clashplus.io before relying on an advanced feature. New users can follow our subscription import and connection guide.
Clash Verge Rev: Desktop rules and config extensions
A good fit for desktop users who understand rule modes and want to manage multiple configs, edit rules, or enable TUN. The mihomo core provides the config features, while the graphical interface handles day-to-day management. Knowing which does what makes troubleshooting easier: you can tell whether a rule failed to match, a config was overridden, or a service lacks permission.
Advanced features also mean more to check. Whether custom content survives a subscription update depends on the extension or override method you use. Before enabling TUN, check the service component, permissions, and possible conflicts with other VPNs. Linux users should confirm the package format and desktop environment rather than relying on a similar-looking filename.
FlClash: A similar workflow on desktop and Android
If you regularly switch between a laptop and Android, FlClash's similar interfaces make it easier to find your configs and proxy groups. It uses the mihomo core, so you can follow the same Clash config approach while handling proxy activation separately on each device. Our site lists downloads for desktop and Android.
A similar interface does not mean the systems behave alike. A desktop app using the system proxy and an Android app routing traffic through a VPN are different setups. On phones, also check battery optimization and background activity restrictions. Cross-platform does not mean configs sync automatically: back up and review subscription URLs, local edits, and personal settings on each device.
Clash Nyanpasu: Know the difference between the client and its core
Clash Nyanpasu suits users who want to explore desktop config management, core selection, and runtime settings. Our download list includes a Windows build. Multi-core management gives you more options, but you need to know which core is currently running. The client name alone does not guarantee support for every protocol or config field.
If a config works in another client but fails to start here, check the error log and selected core before rewriting all your rules. Keep a working copy before switching cores, then check compatibility for DNS, proxy protocols, and newer fields. If you just want to import a subscription and get connected, start with our top pick and explore advanced workflows later.
Clash for Windows: Archived setups and migration
Clash for Windows is no longer maintained. It still appears in older guides, screenshots of legacy configs, and existing PC setups, so the archived download can be useful for reference—but it is not recommended for new devices. Familiarity with its interface does not mean its legacy core supports every protocol and field in current subscriptions.
Before migrating, save your subscription source and local rules, then rebuild the config in an actively maintained client. Don't copy the entire old program folder or assume the new client will inherit old services, TUN drivers, or system proxy settings. If a port is already in use, exit the old process and make sure only one client is routing traffic.
Clash Meta for Android: Managing configs on Android
Often shortened to CMFA, Clash Meta for Android suits Android users who want to manage Clash configs and check rules and connection details. It follows the Meta/mihomo line; supported features depend on the installed build. The first connection requires Android VPN permission, unlike enabling a system proxy on desktop.
If the connection drops when your phone locks, don't assume the node is down. Check background activity, battery optimization, network switching, and whether another VPN app is using the connection. When installing, check whether the ARM64, ARM, or universal build is right for your device. An APK installing successfully does not guarantee that background operation and every network feature are configured correctly.
Surfboard: Check the config format first
Surfboard is listed in our Android downloads, but it is neither a Clash GUI nor a Clash-core client. It primarily uses Surge-style configs and suits users who already have a compatible config source and understand the format differences. Renaming a Clash YAML file won't migrate its proxy groups, rules, and DNS settings intact.
Before choosing Surfboard, check whether your provider offers a compatible option and confirm support for the protocols and rule types you need. If converting a subscription, never send a private subscription URL to an untrusted online tool. Even a successful conversion may not preserve all functionality. If you only have a Clash config and want to get started quickly, choose another compatible client.
ClashX Meta: The legacy macOS menu bar workflow
ClashX Meta follows the Meta core line and centers on menu bar controls and config file workflows. It is no longer maintained. Use it to understand an existing macOS setup or old instructions; for a new installation, consider actively maintained options such as Clash Plus, Clash Verge Rev, or FlClash.
Whether an old installer launches is separate from whether its permissions, traffic routing, and configs work on a newer OS. Before migrating, note your system proxy settings, listening ports, and local rules, then quit the old client and remove any startup items you no longer need. Check the package type for your Apple Silicon or Intel Mac rather than relying on past installation experience.
Narrow down your options by use case
For beginners, power users, multiple devices, and older PCs
Before switching clients
Keep your config and test traffic routing separately
Moving to another client involves more than importing a link. Subscriptions usually contain proxies and rules, while system proxy settings, startup behavior, service components, and TUN permissions belong to the local device. Record these separately to avoid a situation where the new client loads its config but apps still connect to an old port.
Back up what works: Save the subscription source, local rules, overrides, and proxy groups you select manually. Don't share files containing private information.
Stop the old client from routing traffic: Quit it and check system proxy and VPN settings to prevent multiple apps from competing for a listening port or routing traffic at the same time.
Verify a basic setup first: Import the config, select rule mode, and confirm it loads before enabling the system proxy or mobile VPN. Check the logs to see which rules match instead of relying on the toggle color.
Re-enable advanced features one at a time: Once the basic connection works, set up TUN, DNS, LAN sharing, and launch at startup as needed. Test after each change to make troubleshooting easier.
If import fails, check the format, indentation, and core compatibility first. If the client starts but apps can't connect, check traffic routing, DNS, and the firewall. See the troubleshooting handbook for detailed steps or the FAQ for the basics. Once you've chosen a client, head to the platform downloads page and select the right build.