Clash Client Comparison

Clash Verge Rev suits users who run a proxy client on their desktop day to day. It uses the mihomo core and supports common workflows such as importing subscriptions, switching policy groups, and configuring system proxy and TUN. If you already have a Meta-family configuration, check field support and how the client merges configuration before choosing based on appearance alone.

For advanced use, distinguish the original subscription from local overrides and the final runtime configuration. Changes made directly to a remote subscription may be overwritten at the next update; put persistent rules in an override mechanism supported by the client. TUN and service permissions are separate settings—successful import doesn't mean those permissions are in place. Best suited to desktop users who are comfortable checking logs and verifying rule matches.

FlClash is based on mihomo and supports Windows, macOS, Linux, and Android. If you already know your way around policy groups, rule modes, and subscription updates, its similar interface across devices can shorten the learning curve. This page uses the product name FlClash; internal app keys in the download list don't affect which option you choose.

A similar interface across platforms doesn't mean you can copy every network setting as-is. System proxy and service permissions on desktop differ from VPN authorization, per-app routing, and battery management on Android. When switching devices, import the configuration first, then check how traffic is routed on each one. If you have a working YAML configuration and use both a computer and Android, compare FlClash with Clash Plus in the same trial.

Clash Nyanpasu is a desktop GUI for users who care about interface layout, configuration management, and core selection. Keep project platform support separate from the installers available here: this site offers a Windows download, which doesn't mean an installer is available here for every platform listed by the project.

When using a client that manages cores, keep track of the core actually running—not just the name of the outer client. Switching cores can change protocol support, DNS behavior, or extension-field compatibility, so configurations that loaded before should be tested again. Beginners who only need to import a subscription may not need to explore these options. It's a better fit for desktop users with a clear interface preference who can recognize configuration errors.

Clash for Windows is often shortened to CFW. Despite the name, desktop builds were historically available for other operating systems too; this site provides a Windows archive only. Legacy interface labels such as Profiles and Proxies may still be useful when following old guides, but their instructions don't necessarily apply to every newer client.

Clash for Windows is discontinued and isn't a good default choice for a new device. Original Clash-family cores differ from Meta/mihomo in configuration support; matching file extensions alone don't guarantee compatibility with newer protocols or fields. To migrate, save your subscription URL and local rules, then import them into a maintained client. Back up the old app's data directory first; don't copy it directly over another client's data.

Clash Meta for Android, often called CMFA, is for Android users who need Clash YAML configurations. Its Meta/mihomo-family core sets it apart from the older Clash for Android: the formats may look similar, but don't assume protocol or field support based on the old product name.

After installing, grant system VPN permission, then check that the configuration is selected, nodes are available, and per-app routing is set as intended. Disconnects when the screen turns off or after switching networks may also be caused by background restrictions, not just the core. If you have a Clash subscription and want to choose which apps use the proxy, compare its workflow with FlClash. Select the right build for your device on the download page.

Surfboard is listed among the Android downloads, but it isn't a Clash GUI or a Meta/mihomo client. It has its own proxy implementation and uses Surge-style configuration. Before choosing it, check that your configuration provider explicitly supports Surfboard; then consider whether its interface suits you.

Pasting a Clash YAML URL into Surfboard doesn't guarantee it can parse the configuration. Conversion may also lose protocol parameters, policy group behavior, or some rules. If you already have a compatible configuration, you can stick with your familiar workflow. If you're new and only have a Clash subscription, choose a client that explicitly supports its format. Subscription URLs may contain access credentials, so don't submit them to an unfamiliar conversion service.

ClashX Meta uses a Meta-family core and retains the macOS menu bar workflow. It can help you review settings in an existing setup, but it is no longer maintained. The Meta in its name doesn't guarantee that an archived build includes every feature in current mihomo; check the core and configuration support in the actual package.

When changing Macs or upgrading macOS, recheck chip architecture, permission requirements, and compatibility with older apps. An app working on an older computer doesn't mean it will behave the same on a newer system. For a fresh install, consider Clash Plus or Clash Verge Rev first. When migrating, note your proxy ports, subscriptions, and rules, then restore them one by one to avoid carrying old permission issues into the new setup.