Client Guide / Platforms and Cores

Clash Client Comparison & Guide

Start with your device platform, then consider your configuration needs. Similar-looking interfaces don’t mean clients have the same core capabilities, subscription formats, or methods of routing system traffic.

Platforms, cores, and ease of use

Platform availability reflects the downloads listed on this site, not every build target supported by each project. Maintenance status is a general guide; check each project’s latest updates before installing.

On mobile, swipe horizontally to view the table. Core names can help assess configuration compatibility; they are not a performance ranking.

Clash ecosystem clients and related Android apps compared
Client Platforms listed here Core / configuration system Maintenance Ease of use Key features and best for
Clash Plus
Top pick
Windows、macOS、Android、iOS Clash rule compatibility and core implementation vary by platform; check the platform-specific documentation. Actively maintained Easy; a working configuration is still required Options for multiple platforms; good for beginners and multi-device users
Clash Verge Rev Windows、macOS、Linux mihomo Actively maintained Easy for basic use; moderate for overrides Subscriptions, overrides, service mode, and TUN; suited to advanced desktop setups
FlClash Windows、macOS、Linux、Android mihomo Actively maintained Easy to moderate Consistent cross-platform workflow; suited to desktop and Android use
Clash Nyanpasu Windows Clash-family core; available cores depend on the installed build Actively maintained Moderate Interface customization and configuration management; suited to users who want to tailor their desktop workflow
Clash for Windows Windows Original Clash / Clash Premium ecosystem, depending on the archived build No longer maintained Familiar to existing users; check compatibility before migrating Reference for older configs and Parsers workflows; not recommended for new installs
Clash Meta for Android Android Clash Meta family; supported fields depend on the bundled core Actively maintained Moderate Android VPN routing and rule configuration; suited to mobile users familiar with Clash
Surfboard Android Independent implementation with Surge-style configuration; not a Clash core Actively maintained Easy with an existing compatible config; more involved if conversion is needed Suited to Android users who already have a compatible config
ClashX Meta macOS Clash Meta family, depending on the archived build No longer maintained Easy for basic use; check older configs for compatibility Menu bar controls and a reference for older setups; migration is recommended

Where each of the eight clients fits best

Start with the entry that matches your device. This guide compares workflows and configuration effort, not unmeasured memory use or connection speeds.

Clash Verge Rev

Advanced desktop use

A good fit if you want to manage mihomo configs through a desktop interface. Common workflows include subscription management, system proxy, service mode, and TUN. To add rules to a subscription or adjust DNS, learn how overrides and merging work instead of repeatedly editing settings that a subscription update may overwrite.

More features mean more layers to keep track of. After making changes, check the final runtime config and confirm that overrides apply to the active subscription. TUN involves a virtual network adapter, permissions, and routing, so avoid enabling it alongside other options during your first import.

FlClash

Desktop and Android

Built on mihomo, FlClash suits users who want a similar workflow on desktop and Android. You can reuse the same rule concepts, but traffic routing differs: desktop often starts with the system proxy, while Android typically requires VPN permission.

Before choosing, check that the settings you need are available on your platform. Desktop and mobile differ in file permissions, background operation, and network switching; being able to import a config doesn’t make the runtime environments identical. When troubleshooting, start with a minimal config and add custom settings one at a time.

Clash Nyanpasu

Desktop configuration management

Best suited to desktop users who want to organize configs, customize the interface, and explore core options. This download list provides a Windows option. After installing, check which core is active and refer to its documentation to avoid assuming different cores support the same fields.

A customizable interface doesn’t mean stronger networking capabilities. If you just import a subscription and enable the system proxy, extra themes and settings may not be worth the added learning curve. Consider this client when you already have a clear configuration workflow and are comfortable checking logs and runtime configs.

Clash for Windows

No longer maintained

Often abbreviated CFW, this archived client is mainly useful for checking older setups and planning a migration. Existing users may rely on Parsers, scripts, or custom rules, but these aren’t interchangeable with overrides in newer clients. For a new install, choose a client that is still maintained.

For migration, keep the original subscription source, custom rules, and settings you actually need. Don’t overwrite the new client’s entire config directory. Fields supported by the original or Premium ecosystem also don’t prove compatibility with newer mihomo protocols or extensions.

Clash Meta for Android

Android rule configuration

Often abbreviated CMFA, Clash Meta for Android is suited to Android users who understand Clash subscriptions, proxy groups, and rule modes. On first connection, allow the VPN connection. If another network tool is already using Android’s VPN service, resolve that conflict before troubleshooting the config.

Background operation matters on mobile. Battery optimization, background restrictions, and network changes can all interrupt a connection, so don’t assume every drop is caused by a proxy node. Protocol and field support depend on the core bundled with the app; don’t apply current mihomo documentation to an older build without checking compatibility.

Surfboard

Best with a compatible config

Although Surfboard appears alongside Clash clients in the Android downloads section, it isn’t just another Clash interface. It has its own implementation and Surge-style configuration syntax; protocol parameters, policy expressions, and rules must follow its own configuration requirements.

Consider Surfboard if you already have a compatible subscription or know this format. If you only have Clash YAML, choose a client that can handle it directly. Config conversion also requires checking protocol and rule semantics; changing the file extension isn’t enough.

ClashX Meta

No longer maintained

An archived macOS client built around menu bar controls and configuration switching. Use it to check an existing setup, but don’t assume it supports new devices, macOS releases, or protocols just because it worked in the past.

For migration, compare Clash Plus, Clash Verge Rev, or FlClash. Keep your config source and essential rules, and choose the installer for Apple Silicon or Intel. Don’t copy old startup items and proxy settings wholesale; multiple clients could end up controlling the system proxy after login.

Narrow down your options by use case

Pick one candidate and test it with your existing config. There’s no need to install every client.

Migration checklist

The goal of migration is to restore the connections and rule behavior you need, not to copy every old setting. Save your working config and note the subscription source, proxy port, custom rules, and startup settings. Keep configs containing subscription credentials on your device; don’t post them in public forums.

  1. Check the config format. Confirm whether the subscription returns Clash YAML or a format specific to another client. If import fails, check the format and contents before changing system proxy settings.
  2. Stop the old client from routing traffic. Turn off its system proxy, TUN, and startup options, then quit the app. Two clients running at once may compete for listening ports or repeatedly change proxy and routing settings.
  3. Test a basic connection first. Select a config and proxy group in the new client, confirm the core is running, then enable one traffic-routing method. Once your browser works, check the apps you actually need to route through the proxy.
  4. Restore advanced settings one at a time. Add overrides, rule sets, and DNS changes last. Retest after each change, and check the logs and active config to pinpoint what changed.

If you just need to open websites, the system proxy is usually the easiest place to start troubleshooting. Look into TUN when you need to handle apps that ignore system proxy settings. Rule mode selects an outbound based on matches; global mode changes the routing policy, but doesn’t automatically route every system app through the proxy.

The takeaway: Clash Plus is our top pick for beginners and multi-device users. If you specifically need desktop mihomo configuration management, compare Clash Verge Rev and FlClash. Keep archived clients for migration reference, not new installs.

Download clients