Start with your device, then check configuration compatibility. Clash Plus is our top pick for a first install. If you need to manage mihomo configurations directly, compare the available desktop and mobile clients.
The core determines supported fields and protocols
PROFILE
The client determines how configurations are managed
Our pick: start with Clash Plus
For first-time users who mainly need to import a subscription and choose a proxy policy, our top pick is Clash Plus. The download page links to versions for Windows, macOS, Android and iOS. Install the iOS app from the App Store; the official site is clashplus.io. Get set up and verify your connection on your primary device first—it’s easier to troubleshoot than installing several clients at once.
This recommendation does not mean every platform offers the same underlying features. If you need a specific protocol, rule-provider field, DNS policy or configuration override, check the core and client documentation. Linux users can choose between Clash Verge Rev and FlClash. For desktop clients that let you edit mihomo configurations directly, compare Clash Verge Rev with Clash Nyanpasu.
Platform availability reflects the installers linked on this site, not every build the projects have ever released. Difficulty refers to the configuration knowledge needed to import a subscription and set up basic routing; it is not a performance rating. Scroll horizontally to view the table on narrow screens.
Platform support, core, maintenance status, ease of use, standout features and ideal users
Clash Meta family; capabilities depend on the bundled core
Discontinued
Menu bar controls; check field compatibility when migrating
Menu bar access, local configurations and policy switching
Users migrating older macOS configurations
Eight client reviews
These reviews cover the clients linked from the download page. Each one outlines who it suits and what to check before installing or migrating.
Clash Plus: an easy start across multiple devices
Top pick
Clash Plus is a good fit if your priorities are importing subscriptions, choosing policies and staying connected day to day. It leads the Windows, macOS, Android and iOS download sections on this site, making it easy to find the right installer for each device. The recommendation is based on platform availability and a straightforward setup—not on unverified speed or resource-use claims.
Before installing, check that your subscription format and required protocols are supported on your platform. In particular, don’t assume TUN, script overrides and system proxy settings map one-to-one when moving a desktop setup to iOS. Import the configuration using a supported method, then test your policies and target apps. For advanced fields, follow the platform-specific documentation.
Clash Verge Rev: manage mihomo configurations on desktop
Clash Verge Rev runs on Windows, macOS and Linux desktops and uses the mihomo core. It suits users who want to manage subscriptions in a graphical interface while learning about rule overrides, DNS and TUN. For a basic connection, import a configuration and enable the system proxy; there’s no need to turn on every advanced option on your first run.
For advanced use, understand the difference between the original subscription, client-side overrides and the configuration ultimately passed to the core. Edits to a downloaded subscription file may be overwritten when it updates. Put local rules you want to keep in the client's override workflow. TUN also depends on system permissions and service status—not just a toggle in the interface.
FlClash: a consistent experience on desktop and Android
FlClash uses the mihomo core, with downloads for Windows, macOS, Linux and Android on this site. It’s worth considering if you use both a computer and an Android phone and want less of a learning curve between interfaces. Subscription, policy group and rule concepts carry over, but that doesn’t mean system-level traffic routing works the same way on every platform.
On desktop, distinguish between the system proxy and TUN. Android routes connections through system VPN permission. After importing the same subscription on both, check DNS, background operation and per-app access controls separately. Similar interfaces don’t mean configurations sync automatically; confirm subscription update intervals and local edits on each device.
Clash Nyanpasu: core management and configuration overrides
Clash Nyanpasu suits desktop users who want to understand how the client and proxy core work together. This site provides a Windows download. When choosing a client, consider how it organizes configurations and handles overrides, as well as which core is actually selected—not just the interface theme. With mihomo, supported configuration fields are determined by the core version in use.
The final rule order can change when the same subscription goes through different merge or override workflows. After moving to Nyanpasu, start with a single subscription and minimal overrides. Verify that basic proxying works, then restore local rules one at a time. Changing the core, DNS and TUN all at once makes it difficult to identify the source of a problem.
Clash for Windows: archived builds and legacy configuration migration
Discontinued
Clash for Windows, often called CFW, is a legacy desktop client. Common releases use the Clash Premium core. It is neither an older name for Clash Verge Rev nor the same as mihomo. This site keeps an archived Windows download for checking older setups and migration reference; it is not the recommended choice for a first install.
A new client being able to read an old configuration does not guarantee that it will handle everything the same way. During migration, check legacy configuration merges, script handling, policy group names and local paths. Don’t add fields for a newer core to an older setup and expect them to work. A safer approach is to keep a copy of the original configuration and rebuild a minimal working setup in a maintained client.
Clash Meta for Android, often abbreviated CMFA, retains Meta in its name as a nod to the project's history; its current core development line is mihomo. It suits users who already have Clash configurations and want to use configuration lists and policy groups for everyday Android use. Choose the package for your device's processor architecture, then grant system VPN permission.
The Android VPN icon confirms that a system tunnel is active; it doesn’t guarantee that subscription nodes, DNS and routing rules are all working correctly. If the connection drops after the screen locks, check battery optimization and background restrictions. If an app bypasses the proxy, check per-app access controls. Android generally allows only one standard VPN service at a time, so avoid running another VPN tool alongside it.
Surfboard: an Android option with a different configuration format
Surfboard appears in the same download list, but it is not simply another interface for a Clash core. It has an independent proxy engine and its own supported configuration syntax. It suits Android users who already have compatible configurations or specifically want this workflow. Renaming a Clash YAML file’s extension does not make it a compatible configuration.
When evaluating Surfboard, first check whether your subscription provider offers a compatible format and whether the required protocols and rule syntax are supported. Even after converting a configuration, verify policy groups, DNS and rule order; a converter may not preserve the full meaning of the original. If you only have a Clash configuration and want to import it directly, compare Clash Plus, CMFA or FlClash first.
ClashX Meta uses the macOS menu bar and belongs to the Clash Meta family of clients. This site keeps an archived download for existing users checking older configurations. Supported protocols and fields depend on the core bundled with the app; having Meta in the name does not guarantee support for every current mihomo feature. For a new install, consider Clash Plus, Clash Verge Rev or FlClash instead.
Before switching clients, note your system proxy settings, configuration location and any locally added rules. Choose the correct installer for Apple Silicon or Intel, and check the package documentation for macOS compatibility. After migrating, quit the old client and check your system proxy settings. Otherwise, the system may still point to the old listening port, leaving the new client unable to connect.
Save your configuration source and local changes. Note your subscription source, manually added rules, policy groups and DNS settings. Never expose access credentials in subscription links when sharing screenshots or configurations.
Run only one client at a time. Quit the old client and check whether the system proxy still points to its port. Use the new client's current listening address and port; don’t copy them from an old screenshot.
Build a basic setup from the original subscription. First confirm that the new client can parse the configuration, then restore overrides. If a field triggers an error, distinguish between an incompatible format, an unsupported core field and a missing policy group. Don’t simply delete every item that reports an error.
Test traffic routing and rule-based routing separately. First check whether an app's connection reaches the client, then check which rule it matches. The system proxy affects only apps that honor system proxy settings. Test TUN separately if you need broader traffic routing.
Re-enable automatic updates and startup last. Confirm that subscription updates don’t overwrite local rules and that the configuration still works after a restart, then remove the old client. This preserves a way to roll back and reduces troubleshooting when several variables change at once.
Choosing a client determines how configurations are managed and how system traffic is routed; it won’t fix an expired subscription, an unavailable proxy server or incorrect rules. If the same issue appears in multiple clients, investigate the configuration source and network conditions instead of continuing to switch apps. See FAQs for connection and DNS troubleshooting, or the glossary for explanations of cores, policy groups and proxy modes.