Start with your device platform and subscription format, then compare core capabilities and workflows. Similar interfaces do not guarantee interchangeable configurations.
Top pick: Clash PlusCompare eight clientsChoose by use case
Recommendations and Comparison Scope
For first-time users, Clash Plus is the easiest place to start. The downloads page lists it as the top pick for Windows, macOS, Android and iOS. Set up a subscription, choose a policy and enable system integration before exploring rule-based routing. Its official site is clashplus.io. Features and setup differ by platform, so don't assume desktop instructions apply to mobile.
If you need desktop mihomo configuration management, compare Clash Verge Rev. If you want a similar interface on desktop and Android, consider FlClash. Linux users can choose between the Clash Verge Rev and FlClash download options on this site. If you're using an older client, back up your configuration before considering a switch. Discontinued clients are included for reference, not as the default choice for a new setup.
The platform column covers installers available on this site's download page, not every platform a project has ever supported. Maintenance is labeled as active or discontinued; active maintenance is not a promise about update frequency or long-term support. Check minimum system requirements, processor architecture and package details before downloading.
Ease of use describes the effort involved in importing a subscription for the first time, understanding settings and handling permissions; it isn't a score. The table is wide, so scroll horizontally within it. The next section covers each client's trade-offs.
Client comparison covering installers available on this site; check each release's documentation for core and feature details
Meta family; features depend on the archived package
No longer maintained
Familiar to existing users; menu bar workflows require knowing where to find configuration settings
Menu bar management and system proxy; verify support for newer protocols and system versions separately
Existing Mac setups and reference for migrating legacy configurations
Original Clash, Clash Meta and mihomo have some configuration compatibility, but not every field works both ways. Common domain rules may be similar, while newer protocols, DNS extensions, TUN settings and policy group options can differ. See the core compatibility guide for syntax details. Don't judge compatibility by the words Clash or Meta in a product name alone.
What to Expect from Eight Clash Clients
Clash Plus: A Top Pick for Beginners and Common Platforms
Clash Plus supports Windows, macOS, Android and iOS, making it easy to find an installer for each device. For your first setup, check that your subscription is recognized by the version for your platform. After importing it, confirm the configuration is enabled, choose a policy and turn on system integration. Test subscription downloads, core startup and app connectivity separately to make it easier to pinpoint problems.
Across multiple devices, you can reuse a subscription source that works with each platform, but don't assume every advanced feature works the same way everywhere. Mobile relies on the system VPN interface and background policies; desktop setup may also involve system proxy settings, ports and permissions. If you need complex custom rules or a specific protocol, check the documentation for your platform before considering a client with a dedicated mihomo workflow. iOS users can go to the store via this site's iOS installation option and find product details at clashplus.io.
Clash Verge Rev: Desktop Rules and System Integration
Clash Verge Rev suits users who prefer to manage configurations on desktop. This site provides installers for Windows, macOS and Linux. Its mihomo core supports configurations with rule mode, policy groups and TUN, but whether they work depends on the imported configuration, system permissions and network environment. If you only need browser access, start by testing the system proxy. Consider TUN only if an app doesn't respect system proxy settings; it's not a required step for a first-time setup.
For advanced use, pay close attention to how configuration extensions interact with subscription updates. Direct edits to a downloaded configuration may be overwritten during an update. Before using the client's extension features, confirm that the final configuration has the right rule order and policy group names. This client suits users who are comfortable checking logs and distinguishing client settings from core settings—not those expecting more interface options to mean faster connections. View desktop download options →
FlClash: A Familiar Workflow on Desktop and Android
FlClash runs on Windows, macOS, Linux and Android and uses the mihomo core. It's a good fit if you want a similar interface and configuration workflow across devices. A consistent layout reduces the effort of finding subscription, proxy group and log settings. Even with the same subscription URL, check DNS, permissions and configuration status on each device. A working connection on your computer doesn't mean your phone is set up too.
Desktop system proxy settings and Android VPN integration aren't interchangeable. On mobile, also watch for battery optimization, background restrictions and conflicts with other VPN apps. If you're sharing a full YAML configuration, keep nodes, policy groups and general rules, but manage ports, listen addresses and platform-specific integration settings separately. FlClash suits people using a computer and Android together; device setups that include iOS require a different compatible client. View Android download options →
Clash Nyanpasu: Multiple Cores and Desktop Configuration
This site provides a Windows installer for Clash Nyanpasu. Its multi-core management is a key point to consider when choosing it. Users with different configuration files can select a core to suit each setup, but must know which core is running and check that it supports the configuration's protocols, DNS fields and extensions. Switching cores doesn't automatically convert an old configuration into a fully compatible format.
If you just want to import a subscription and get connected, start with Clash Plus. Consider Nyanpasu if you want to organize desktop configurations differently and are willing to check the final configuration and logs. When testing, change one thing at a time—for example, keep the existing configuration and switch cores first, then adjust rules separately. Otherwise, if parsing fails or policy group options change, it can be hard to tell whether the cause is an interface setting, configuration content or core capability. View Windows download options →
Clash for Windows: Legacy Setups and Migration Reference
Clash for Windows is no longer maintained, but this site retains a Windows archive for reproducing older setups and comparing migration options. Many online tutorials still use screenshots of its interface. They can help explain concepts such as Profiles, Proxies and the system proxy, but don't rely on them for current menu paths, permission requirements or protocol support. The bundled core in an older release should not be assumed to match current mihomo.
If your existing setup is stable, save your subscription source, manual rules and port settings before testing an actively maintained client separately. New protocol fields or changes in operating system behavior may exceed the capabilities of an older core, so don't choose an archived client for an older computer just because its interface is familiar. After migrating, confirm the new client controls the system proxy before closing the old one to avoid local proxy port conflicts. View archived and alternative clients →
Clash Meta for Android: Connect a Phone with Existing YAML Configurations
Clash Meta for Android, often abbreviated as CMFA, suits Android users with an existing Clash YAML subscription or configuration file. It uses a core from the Meta/mihomo family; check the bundled core for specific compatibility details. After importing a configuration, make sure it's selected, start the connection and grant Android VPN permission. Seeing a configuration name in the list doesn't mean traffic is being proxied.
Common variables on Android include background restrictions and VPN conflicts. If another VPN is connected, decide which app should handle system integration first; disconnect it before switching clients. To manage traffic by app, check the client's app selection settings and distinguish between excluding an app and routing it directly—these work at different levels. This client suits phone users familiar with Clash configurations. New users can start with the Clash Plus download option for their platform. View Android clients →
Surfboard: An Android Option with Its Own Configuration System
Surfboard is listed alongside clients in the Clash ecosystem to cover Android users with different configuration sources; that doesn't mean it uses the original Clash or mihomo core. It has its own configuration system, with syntax similar to some Surge-style configurations, but supported fields, protocols and features vary. Don't assume a full Clash YAML link can be used as a native Surfboard configuration.
Surfboard is a reasonable choice if your subscription provider offers its format or you already maintain compatible rules. If you only have a Clash configuration, conversion adds another step to verify. Some nodes may carry over while policy group behavior, rule providers or DNS settings are lost. Before choosing Surfboard, check the output format, rule behavior and update process—not just whether the node list appears. View Surfboard download options →
ClashX Meta: macOS Menu Bar Client for Legacy Setups
ClashX Meta is a macOS menu bar client built on a Meta-family core, included as a reference for existing Mac configurations and familiar workflows. This site marks it as no longer maintained. Meta in the name doesn't mean the archived package has every feature in current mihomo or can parse newer protocols and extension fields. For a new setup, consider the macOS options for Clash Plus, Clash Verge Rev or FlClash.
Before migrating from ClashX Meta, note the active configuration, mixed port, policy group selections and launch-at-login setting. Once the new client starts successfully, confirm that the system proxy points to its port and disable automatic control by the old client to prevent settings being overwritten after a restart. A menu bar app and a full-window app offer different workflows; window size alone doesn't indicate resource use. View macOS alternatives →
Choosing a Client for Beginners, Power Users, Multiple Devices or Older Computers
These recommendations aren't ranked by appearance or unverified performance figures. Connection quality also depends on your subscription service, selected node, network conditions and protocol implementation. To compare clients, use the same device, configuration and system integration method so you can assess interface experience separately from network results.
Configuration Checks Before Switching Clients
Save your configuration source and manual changes. Record your subscription URL, rule edits and policy group selections. Store configuration files with access credentials securely. Don't post full subscription links or configurations in public comments.
Check the import format. Confirm whether you have a full Clash YAML file, a node list or a Surfboard configuration. Importing nodes doesn't mean DNS, rules and policy groups were preserved too.
Check policy group names and rule order. After migration, make sure every referenced policy group exists and specific rules come before fallback rules. Matching filenames don't guarantee the same routing behavior. If needed, see the rule matching guide.
Test system proxy and TUN separately. Stop the old client first to prevent port conflicts and integration issues. Set the system proxy port in the new configuration and confirm the basic connection works before testing TUN or mobile VPN integration, if needed.
Check restarts and subscription updates. After a manual subscription update, verify that your local changes remain. Restart the device and confirm that only the intended client starts and handles network traffic. Keep a backup of the old configuration until you've tested your everyday apps.
The same subscription behaves differently in two clients. What should I check first?
First confirm that both clients imported the same configuration and selected the same node in the policy group. Then compare core support, DNS and system integration. Converting a subscription can change rules and policy groups; system proxy and TUN may also affect different apps. Align your test conditions before blaming client speed.
Can I install multiple clients at once?
You can keep multiple clients installed for comparison, but usually only one should handle system integration at a time. Two programs may compete for the same port or repeatedly overwrite system proxy settings; on mobile, they may also compete for the VPN interface. Disconnect the old client before switching, then start the new one and check its logs.
I already use Clash for Windows or ClashX Meta. Do I need to migrate right away?
Plan your migration based on system compatibility, protocol needs and risk. There's no need to overwrite an existing setup in a rush, especially without a backup. Both clients are no longer maintained, so choose an actively maintained client for new devices. For an existing setup, back it up, test an alternative client separately, then confirm configuration updates and system integration still work after a restart.
Once you've confirmed your platform and configuration needs, go to the client downloads page and choose the right build for your architecture. Clash Plus is the recommended starting point; if you need a particular core or configuration workflow, use this comparison to choose an alternative.