Client Guide · Platforms and Configuration Compatibility

Clash Client Comparison and Selection Guide

Start with your operating system and subscription format, then compare cores, permissions and configuration tools. Whether your subscription works matters more to a smooth first setup than the look of the interface.

8 clients Desktop and mobile Archived projects clearly marked

Client Comparison and Ease of Use

The platform column shows which installers are available in our download center; it is not a complete list of platforms supported by each project. Maintenance notes are general and do not imply the same update cadence on every platform.

Scroll horizontally to view the table on narrow screens. Select a client name to jump to its review below. Ease-of-use ratings reflect typical use after importing a subscription, not performance.

Eight clients compared by platform, core, maintenance status, ease of use, standout features and ideal users
Client Platforms with installers here Core / configuration system Maintenance Ease of use Key features Best for
Clash Plus
Top pick
Windows、macOS、Android、iOS mihomo ecosystem configuration; core capabilities vary by platform Actively maintained Easy: start by importing a subscription Subscription import and proxy selection; mobile apps use system network permissions First-time installs and desktop-plus-phone setups
Clash Verge Rev Windows、macOS、Linux mihomo, formerly the Meta branch Actively maintained Moderate: requires understanding configuration and service permissions Configuration management, overrides, TUN and log viewing Users who need advanced desktop settings
FlClash Windows、macOS、Linux、Android mihomo Actively maintained Easy to moderate: learn basic use before advanced settings Cross-platform interface, proxy group management and connection monitoring Users on both desktop and Android
Clash Nyanpasu Windows Multi-core workflows; features depend on the selected core Actively maintained Moderate to advanced: distinguish interface settings from core settings Core selection, configuration management and desktop interface customization Desktop users comfortable managing multiple configurations
Clash for Windows Windows Legacy Clash/Premium ecosystem; varies by archived build Discontinued Moderate: many legacy guides, but compatibility needs checking Legacy configurations, Profiles and older rule workflows Users referencing or migrating a legacy setup
Clash Meta for Android Android Meta/mihomo-based Actively maintained Moderate: requires managing VPN and background permissions Android VPN traffic routing, configuration management, rules and logs Users who want detailed control over Android proxy settings
Surfboard Android Independent implementation; not a Clash/mihomo core Actively maintained Depends on whether you already have a compatible configuration Proprietary configuration format, rule-based routing and Android VPN traffic routing Users with an existing Surfboard-compatible configuration
ClashX Meta macOS Clash Meta-based; does not include every current mihomo feature Discontinued Basic operation is straightforward; maintaining legacy configurations takes work Menu bar controls, system proxy and configuration switching Users who want to keep a legacy macOS workflow

Client Reviews and Migration Notes

These reviews focus on how each client works in practice, not screenshots, past popularity or feature counts. Advanced settings may move between versions, so check which configuration and core are active before making changes.

Top pickFirst install

Clash Plus: Import Subscriptions and Switch Proxies

Clash Plus is a good fit if all you need is to import a subscription, enable a configuration and choose a proxy. There’s no need to adjust DNS or TUN settings right away: first confirm the subscription imports successfully, then verify the connection in rule mode. Find desktop and Android installers in our download center; the iOS link goes to the App Store. Project website: clashplus.io.

Being our top pick doesn’t mean every device uses the same settings. System proxy settings on Windows and macOS, VPN authorization on Android, and network extension permissions on iOS are different system features; don’t assume their switches work the same way. You can reuse the same subscription across devices, but set local ports, launch at startup and background permissions on each device separately. If your subscription uses custom overrides or scripts, check platform support before adding them to your main configuration.

When to look elsewhere: Choose Clash Plus when you want a straightforward daily setup. If you need a Linux desktop client or depend on a specific client’s scripting features, compare the options below.

Clash Verge Rev: Desktop Configuration and Override Management

Clash Verge Rev runs on Windows, macOS and Linux desktops and uses the mihomo core. It suits users who understand subscriptions, proxy groups and rule-based routing, and want more control over overrides and system integration. When troubleshooting, check separately whether the configuration is active, the core is running and the system proxy is enabled. Don’t keep switching proxies when the configuration hasn’t taken effect.

For advanced setups, preserve the ability to update your subscription. To add local domain rules or change DNS, use the client’s merge, override or script features rather than editing content that the next subscription update will overwrite. TUN also requires a service and permissions, so note your existing settings before enabling it. This client suits users willing to read logs and maintain local configurations; don’t turn on every option just because the menus are there.

FlClash: A Shared Workflow Across Desktop and Android

FlClash uses mihomo, with desktop and Android installers available here. Its cross-device appeal is a similar interface and workflow: once you know how to import configurations, choose proxy groups and check connections, there’s less to relearn on another device. That doesn’t mean configurations, selected proxies or subscriptions sync automatically; use the export, backup or import options the client actually provides.

When migrating, test standard rules first, then check system-dependent features such as app-based routing, DNS and TUN. On Android, also check VPN authorization and battery restrictions; on desktop, make sure another proxy app isn’t using the mixed port. FlClash suits users who want a similar workflow on a computer and Android phone. If your main device is an iPhone, check the other client’s configuration format and platform limitations too.

Clash Nyanpasu: Multiple Cores and Desktop Workflows

Our download center offers a Windows installer for Clash Nyanpasu. It suits users comfortable separating the graphical interface, core and configuration layers—especially those managing multiple configurations or checking compatibility across cores. Choosing from multiple cores doesn’t make one configuration compatible with all of them. Check its fields and protocols against the core you enable.

For your first setup, choose a core and keep it fixed, import the subscription, then configure the system proxy. Don’t change cores, DNS and TUN all at once while troubleshooting, or you won’t know which change affected the result. Interface customization can improve your workflow, but isn’t a reason by itself to choose this client. What matters is whether you need its configuration tools and can use logs to pinpoint issues such as failed DNS resolution or service startup.

Discontinued

Clash for Windows: A Reference for Migrating Legacy Setups

Clash for Windows is often called CFW. Many older guides cover its Profiles, Proxies and General pages, but the number of guides doesn’t say anything about maintenance. CFW is discontinued; its archived download is mainly for understanding an existing setup and migrating configurations. It’s not recommended for first installs on new devices, and an old interface that still opens doesn’t guarantee compatibility with current subscriptions.

When migrating from CFW, back up your subscription source, local rules, scripts and system settings separately. Legacy Clash/Premium configurations overlap with mihomo but differ in some fields and behavior, so copying the configuration folder isn’t enough. Import the original subscription into the new client and verify it first, then restore custom settings one at a time. Use CFW briefly for comparison only after exiting the new client, to avoid port conflicts or both apps changing the system proxy.

Clash Meta for Android: Android Rules and Background Operation

Clash Meta for Android, often called CMFA, is an Android client based on Meta/mihomo. It suits users who want to inspect configurations, rules and logs, not just start a connection. Android routes traffic through a VPN service, unlike the system proxy on desktop. If another app on your device also uses a VPN service, check whether both can run at once; the VPN icon in the notification bar alone doesn’t show where traffic is going.

When choosing an Android client, factor in background restrictions too. If the connection drops when the screen locks, the cause may be the system’s battery settings—not the subscription or proxy. Allow necessary background activity, then review how configurations update and how often speed tests run; don’t use repeated speed tests to keep the connection alive. The installer’s architecture must also match your device. If unsure, check the architecture notes in the download center rather than assuming an install failure means the client can’t use your subscription.

Surfboard: Check the Configuration Format First

Surfboard is an Android proxy client, not a Clash/mihomo client with a different interface. It uses its own configuration syntax and supported protocols, so first check whether your subscription provider offers a compatible format. A Clash YAML link isn’t automatically importable just because it contains proxy server details. Conversion also may not preserve every rule, proxy group or protocol setting.

If you already have a compatible configuration and know its rule system, consider Surfboard for Android VPN routing and everyday proxy selection. If you’re new and only have a Clash subscription, a client from the same ecosystem is a better starting point and avoids conversion variables. If importing fails, check the response and its format before changing system DNS; network settings won’t fix a file the client can’t parse.

Discontinued

ClashX Meta: A Legacy macOS Menu Bar Setup

ClashX Meta uses the macOS menu bar and can help you understand an existing legacy setup, but the project is discontinued. Its Meta-based core doesn’t mean it includes every feature in current mihomo. For a new install, choose a maintained client. If keeping an old setup, watch for changes to macOS, permissions and configuration field compatibility.

To migrate to another macOS client, quit the old app and turn off its system proxy first. Then check network settings for any remaining loopback address and port. Choose the right installer for Apple Silicon or Intel. App launch failures, insufficient service permissions and subscription parsing errors are different issues; follow the relevant error message. A simple menu bar doesn’t mean fewer network settings, and enabling the system proxy doesn’t route traffic from every app.

Narrow Down Your Options by Use Case

Compatibility Checks Before Installation

  1. Check your OS and device architecture. Find your platform in Windows System Information, About This Mac on macOS or your Android device settings. Don’t choose an installer based only on the client name in the filename.
  2. Check the subscription’s response format. The client needs configuration content it can read, not just a link that opens in a browser. Troubleshoot an incompatible format separately from an expired link.
  3. Note your current network settings. Record the system proxy address, mixed port, TUN status and custom rules. Run only one client that takes over system traffic at a time during migration.
  4. Test in stages. First verify import and rule mode, then check DNS, TUN and app-based routing. If something breaks, undo the most recent change and check the relevant logs.

Once you’ve chosen a client, visit the download center to find installers by platform. If you have network issues after installation, see the troubleshooting FAQ. This page doesn’t rank performance; results also depend on configuration size, network conditions and your device.