Clash client platform and feature comparison
Platform availability below refers to the installers offered on our download pages, not every operating system a project has ever supported. Maintenance status helps distinguish everyday options from archived clients; it does not indicate a specific update schedule. Check the download page and client documentation for minimum system requirements, processor architecture, and available features.
| Client | Platforms available here | Core or configuration format | Maintenance status | Ease of use | Features and limitations | Best for |
|---|---|---|---|---|---|---|
| Clash Plus | Windows、macOS、Android、iOS | Check each platform’s documentation; don’t infer the core from the name | Actively maintained | Easy: start by importing a subscription | Available for desktop and mobile; permissions and configuration options vary by operating system | First-time installations and users with multiple devices |
| Clash Verge Rev | Windows、macOS、Linux | mihomo (successor to Clash Meta) | Actively maintained | Moderate: requires understanding modes and traffic routing | Desktop configuration management, rule-based routing, and TUN | Everyday desktop use and advanced configuration |
| FlClash | Windows、macOS、Linux、Android | mihomo | Actively maintained | Easy to moderate | Cross-platform interface; desktop proxy settings differ from mobile VPN permissions | Users who switch between desktop and Android |
| Clash Nyanpasu | Windows | Supports core management; available cores depend on the installer | Actively maintained | Moderate: lots of settings to explore | Configuration management, interface customization, and core selection | Users who want to fine-tune their desktop workflow |
| Clash for Windows | Windows | Original Clash family; older builds may differ | Discontinued | Familiar to existing users; not recommended as a starting point for new users | Reference for old configurations and interfaces; limited support for newer syntax | Users migrating an existing setup |
| Clash Meta for Android | Android | Clash Meta family | Discontinued | Moderate: requires managing VPN permissions and background restrictions | Android VPN routing and configuration import | Android users with existing configurations |
| Surfboard | Android | Independent implementation with Surge-style configuration | Actively maintained | Depends on whether you already have a compatible configuration | Not a Clash core; Clash YAML cannot be used as-is | Users already working with its configuration format |
| ClashX Meta | macOS | Clash Meta family | Discontinued | Most controls are grouped in the menu bar | macOS menu bar access; check compatibility with newer system versions | Users maintaining existing macOS setups |
On narrow screens, swipe horizontally within the table. Ease-of-use ratings describe configuration tasks—not speed, connection quality, or resource usage.
Original Clash, Clash Meta, and mihomo: what’s the difference?
The client handles the interface, subscription management, and system settings. The core reads configuration files, handles connections, and applies rules. Clash Meta extended the original Clash core, and mihomo continues that line of development. A legacy client may import a file without supporting every protocol, rule, or DNS field it contains.
Choose a core based on your existing configuration: does the subscription explicitly require mihomo? Does it use fields that older cores don’t support? Do its rule sets depend on a particular database? Don’t assume compatibility just because an app has Clash in its name. Surfboard uses a separate configuration format, so check which output format your subscription provider offers.
Choose a client by use case
Eight Clash clients reviewed
Clash Plus: our top pick for first-time setup and multiple devices
Clash Plus is available from our download pages for Windows, macOS, Android, and iOS, making it a good starting point for first-time users. Its main advantage is broad device coverage—not identical settings across every platform. Before importing, check your subscription format. After import, make sure the configuration is selected and grant any permissions your operating system requires. For iOS, use the App Store link on the download page. See the product information at clashplus.io. If your configuration relies on specific mihomo extensions, check support for your platform first.
Clash Verge Rev: desktop-first rule management
Clash Verge Rev runs on Windows, macOS, and Linux desktops and uses the mihomo core. It suits users who want a graphical interface along with room to configure rules, DNS, and TUN. Keep the original subscription separate from local overrides so a subscription refresh doesn’t overwrite your changes. System proxy and TUN are different routing methods. If an app isn’t using the proxy, check how it handles network traffic before enabling more options. Linux users should also check package format and permission requirements for their distribution.
FlClash: a similar workflow on desktop and Android
FlClash runs on Windows, macOS, Linux, and Android, and uses the mihomo core. Its similar interface across desktop and Android can make switching between devices easier. Don’t copy every setting from one platform to another: desktops may use a system proxy, while phones usually route traffic through a VPN interface. App exclusions and background restrictions also differ. When switching, import the same compatible configuration on both devices, then test routing and DNS separately.
Clash Nyanpasu: desktop configuration and interface management
Our site offers a Windows installer for Clash Nyanpasu. It suits users willing to spend time organizing configurations, customizing the interface, and understanding core selection. To check whether a subscription’s features are supported, look at the core currently in use—not just the client’s name. For initial troubleshooting, stick with the default workflow: make sure the configuration loads before adding overrides or changing cores. Changing several things at once makes errors harder to pinpoint. If you just want to import a configuration and get started, there’s no need to choose this client for its extra settings.
Clash for Windows: for reference on older setups, not recommended for new installs
Clash for Windows is discontinued, but we keep an archived installer in the Windows section. Users familiar with its old interface may still be able to set up basic configurations, but its older core has limited support for newer protocols and rule syntax, and behavior may vary between historical builds. It’s best used to locate existing settings, note proxy ports, and plan a migration—not as a long-term choice for a new device. Before switching clients, quit the old one and turn off the system proxy to prevent its processes from holding ports open.
Clash Meta for Android: a reference for existing Android setups
Clash Meta for Android, also known as CMFA, is a discontinued Android client from the Clash Meta family. Its setup involves VPN permissions, configuration selection, and Android background-process restrictions. If you’re migrating an existing setup, make a separate note of any per-app proxy list; these settings may not be included in the subscription file. For a new device, compare Clash Plus and FlClash on the download page before deciding whether to keep the old setup. Being able to import an old configuration doesn’t guarantee compatibility with newer Android versions.
Surfboard: check the configuration format before installing
Surfboard is an Android client, not another interface for a Clash core. It’s independently developed and uses Surge-style configuration; check its own documentation for supported protocols, rules, and features. It suits users who already have a subscription in the right format or know how to maintain one. If you only have Clash YAML, don’t expect Surfboard to handle it the same way. Even if your provider offers multiple formats, check that conversion preserves the rules and policies you need.
ClashX Meta: the legacy macOS menu bar workflow
ClashX Meta uses a core from the Clash Meta family and is controlled mainly from the macOS menu bar. It’s discontinued. Existing users can refer to it when locating old configurations and proxy settings; for a new install, compare Clash Plus, Clash Verge Rev, or FlClash instead. When migrating, choose the right installer for Apple Silicon or Intel, and check whether login items or network proxy settings still point to the old app. The macOS menu bar interface and core compatibility are separate considerations.
Discontinued clients and migration steps
An archived download keeps an older client available for reference; it doesn’t mean the client is right for every new system. When deciding whether to keep using Clash for Windows, Clash Meta for Android, or ClashX Meta, consider system compatibility, core capabilities, and ongoing maintenance. Even if your existing setup still works, keep a record of the settings you’ll need to migrate.
- Save essential settings. Note the configuration source, selected policies, listening ports, app exclusions, and custom rules. Subscription URLs may contain access credentials; keep them private and don’t share them in public screenshots or forums.
- Keep subscriptions and local changes separate. Subscription files usually don’t include every client preference. Check for separate override files, rule sets, or scripts, and assess their compatibility individually.
- Turn off routing in the old client. Before quitting it, disable the system proxy or VPN and check startup items. Don’t let two clients compete for the same listening ports or network routing permissions.
- Test the new client’s basic connection first. Import the configuration and make sure it’s selected, then check browser access, rule matching, and DNS resolution. Once the basics work, re-enable TUN, local network access, or custom overrides one at a time.
- Keep notes so you can roll back. Once your usual apps work as expected, remove old login items and configurations. If migration runs into problems, troubleshoot by symptom in the troubleshooting guide instead of reinstalling repeatedly.
Final checks before installing
Choose in this order: operating system and architecture, configuration format, maintenance status, routing method, then interface preferences. A client doesn’t replace a subscription service, and changing interfaces won’t fix problems with the underlying network route. A successful import only means the file was accepted; check that the configuration loaded, the right policy is selected, and app traffic is routed as intended.
If you don’t need to preserve an existing setup, Clash Plus is our top pick. For a desktop workflow built around mihomo configuration, compare Clash Verge Rev; for a mix of desktop and Android, consider FlClash. Choose Surfboard only if its configuration format fits, and keep discontinued clients for reference when maintaining existing setups.
The download page lists installers by platform and architecture. After installing, follow the Clash installation guide to import your subscription, choose a mode, and test the connection. If you’re unsure how subscriptions and clients work together, start with the Help Center usage guide.