Clash Plus: get connected first
A good fit for new users who haven’t settled into a configuration workflow and want to get started on their device. After installation, open the configuration or subscription section and import a compatible subscription. Confirm that proxy groups appear, then go to the connection screen. Avoid changing DNS, rules and system routing all at once; if something goes wrong, it will be harder to find the cause.
Having downloads for multiple platforms doesn’t mean every version uses the same core or supports every YAML field. If your subscription provider requires a specific core, script or extended rule, check the documentation for your platform first. Once the basic connection works, decide whether you need finer-grained rule editing. We recommend Clash Plus as an all-around starting point; choose an advanced client based on actual compatibility needs.
Clash Verge Rev: desktop configuration and rule management
A good fit for desktop users who manage subscriptions regularly, use mihomo rules and need to distinguish between system proxy and TUN. Add your subscription on the configuration page and set it as active, then check your proxy groups and select an exit. To add local rules, learn how overrides work rather than editing a downloaded configuration directly—your changes may be overwritten the next time the subscription updates.
The broad set of controls also means understanding what each switch does. System proxy affects apps that follow your system proxy settings; TUN involves a virtual network adapter, routing and service permissions. Start with just one traffic-routing method and test it before enabling anything else. If you only switch exits occasionally, there’s no need to turn on every advanced feature just because it’s available.
FlClash: a similar workflow on desktop and Android
A good fit if you want to use the same configuration on a computer and an Android phone. The mihomo core lets you carry over what you know about rules, while a similar interface makes it quicker to find your way around. After importing, check the proxy group and active configuration on each device separately. A working connection on one device doesn’t mean the others are set up.
A shared interface doesn’t mean shared system permissions. Android usually requires VPN authorization; desktop may use the system proxy or TUN. File paths, service permissions and background restrictions also vary. Check local rule file paths before copying YAML. If your workflow depends on a custom script feature from another desktop client, confirm FlClash supports the equivalent rather than copying the entire setup as-is.
Clash Nyanpasu: desktop configuration and core selection
A good fit for desktop users comfortable distinguishing the interface, core and configuration. We provide a Windows download. Before importing, check the client information or core settings to see which core is running and choose a compatible configuration. Don’t assume protocol support based on the client’s name, or assume every selectable core is bundled with the download.
Interface customization and configuration management can make everyday organization easier, but changing the theme won’t change how connections are routed. If parsing fails, check the error field and active core instead of repeatedly changing subscriptions and masking the cause. For a straightforward first connection, Clash Plus or FlClash offers a simpler path. If you already have a desktop configuration workflow, compare it with Nyanpasu’s controls.
Clash for Windows: recognizing and migrating legacy setups
Discontinued Clash for Windows is often abbreviated to CFW. Page names like Profiles, Proxies and General in older guides usually refer to this interface. We keep the archived download mainly to help identify legacy setups. New users shouldn’t choose it as their long-term client just because search results turn up lots of guides.
Its original Clash / Premium lineage isn’t equivalent to today’s mihomo. Newer protocols and configuration fields may not parse, and legacy service components and system integration need to be reassessed. To migrate, keep your subscription URL and any essential custom rules, then rebuild the configuration in a new client. Don’t copy the entire old application folder or run two system proxy or TUN services at once.
Clash Meta for Android: per-app routing
Often abbreviated to CMFA, Clash Meta for Android suits users who want to inspect rules, switch proxy groups and route traffic by app on Android. After importing a configuration, check the proxy groups, tap Start and grant the system VPN permission. This VPN is Android’s traffic-routing interface; it doesn’t verify the subscription source or remote service.
Per-app routing and domain rules operate at different levels: app routing determines which apps are handled by the client; domain rules determine which exit a handled connection uses. If an app isn’t included in traffic routing, changing domain rules usually won’t help. If the connection drops in the background, check battery management and background restrictions before blaming the node.
Surfboard: check the configuration format before installing
Surfboard appears alongside Clash clients in the download options, but it doesn’t use the same core. It has its own implementation and a Surge-like configuration format, making it a fit for Android users who already have a compatible configuration. If your file uses Clash’s proxies, proxy-groups and rules structure, changing the file extension alone won’t make it a Surfboard configuration.
If you need to migrate, ask your configuration provider for the right format, then check protocol, policy group and rule support one by one. Conversion doesn’t guarantee feature parity. If you only have Clash YAML and no experience converting and validating configurations, CMFA, FlClash or a Clash Plus version compatible with your subscription will usually mean less troubleshooting.
ClashX Meta: legacy macOS menu bar setup
Discontinued ClashX Meta follows the legacy Clash Meta line and is built around menu bar controls. It is a separate client from ClashX and Clash Verge Rev; similar names don’t mean you can use the same installation steps. Existing users should note their menu bar proxy mode, subscription source and custom configuration locations before planning a migration.
A working legacy setup may not retain its permissions, proxy recovery behavior or core capabilities after a system upgrade. On a new Mac, prefer an actively maintained client. Compare Clash Verge Rev for graphical management of complex configurations, or FlClash for a similar workflow across devices. After migrating, quit the old client and check macOS network settings for leftover proxies.