CLIENT GUIDE

Clash Client
Comparison & Selection

Start with your operating system and subscription format, then check core capabilities. Clash Plus is our everyday pick; for desktop overrides, Linux or advanced Android settings, narrow your options by use case.

Platform support Configuration compatibility Maintenance status

Platform × Core × Ease of use

Compare eight Clash clients

Platforms listed reflect the installers available on our download page, not every platform a project has ever supported. Ease of use refers to the effort involved in importing a configuration, enabling the client and troubleshooting—not speed or performance.

Swipe horizontally on smaller screens to see the full table. Select a client name to jump to its review.

Platform support, core, maintenance status, ease of use, standout features and intended users
Client Platforms Core / configuration format Maintenance Ease of use Key features Best for
Clash Plus
Top pick
Windows、macOS、Android、iOS Clash-compatible; core and field support vary by platform—see each client's documentation Actively maintained Beginner-friendly Subscription imports, proxy selection and cross-device use Beginners, everyday users and people using multiple devices
Clash Verge Rev Windows、macOS、Linux mihomo Actively maintained Beginner to advanced Configuration overrides, TUN and service mode Users who want more control over desktop configuration
FlClash Windows、macOS、Linux、Android mihomo Actively maintained Beginner to advanced Cross-platform interface, proxy groups and connection monitoring People who use both desktop and Android
Clash Nyanpasu Windows Supports core management; capabilities depend on the selected Clash, Meta or mihomo core Actively maintained Advanced Configuration management, core management and desktop UI customization Desktop users comfortable choosing and managing a core
Clash for Windows Windows Original Clash ecosystem; older setups may use a different core Discontinued Legacy setups can take more effort to troubleshoot Reproducing legacy configurations and workflows Users keeping a legacy setup or preparing to migrate
Clash Meta for Android Android Meta / mihomo family Actively maintained Beginner to advanced System VPN routing, per-app access controls and configuration management Users who want fine-grained control over Android proxy behavior
Surfboard Android Independent implementation; Surge-style configuration, not Clash YAML Actively maintained Check format compatibility Surge-style configuration and Android VPN integration Android users with a compatible configuration
ClashX Meta macOS Meta family Discontinued Legacy OS integration may require troubleshooting Menu bar access and local YAML management Mac users keeping a legacy workflow or preparing to migrate

Start with what you need to do

Beginners, power users, multiple devices and older PCs

Client-by-client reviews

Why choose each client—and what to keep in mind

For each option, see what it's good for, what to check before choosing it and where to go next. Differences in interface are not evidence of differences in network speed.

Clash Plus: a great starting point for everyday use

Top pick

A good fit for first-time Clash users and anyone who wants a similar workflow on desktop and mobile. Check platform availability and the subscription import process first. For everyday use, you'll generally just manage your configuration, choose a proxy group and enable the appropriate system-level routing. Clash Plus is listed first in our Windows, macOS, Android and iOS download sections. Its official site is clashplus.io.

Even cross-platform clients are constrained by each operating system's networking interfaces. Don't assume desktop TUN, service installation or DNS settings work the same way on a phone. If you need a specific advanced mihomo field, check that the current platform supports it. For iOS, follow the download page link to the App Store; for Linux, choose another client from the downloads list.

Find Clash Plus downloads for each platform →

Clash Verge Rev: desktop overrides and system integration

A good fit for users who maintain desktop configurations over time. Its mihomo core and configuration management interface make it easier to separate subscription content from local changes: subscriptions update proxy and rule sources, while local overrides preserve personal rules, DNS settings or port preferences. Windows, macOS and Linux users can check the download page for the right installer and follow the system-specific setup requirements.

Before enabling TUN or service mode, verify the basics using the system proxy. Service permissions, virtual network adapters and system routes add variables; running multiple proxy tools at once can make traffic paths hard to trace. Troubleshoot by checking the final effective configuration, then the logs and connection records—not just editing the original subscription file.

Download Clash Verge Rev →

FlClash: one client for desktop and Android

A good fit for people using a computer, Linux and Android. Built on mihomo, FlClash offers a cross-platform interface that makes configuration, proxy groups and connections easier to find. If you already have a Clash YAML subscription, import and enable it first, then check that proxy groups and rules loaded correctly. There's no need to change every advanced setting on the first run.

A similar interface doesn't mean identical permissions. Android requires system VPN authorization; desktop routing depends on system proxy or TUN settings. When switching devices, check the configuration update time, routing toggle and background restrictions on each one. Verifying configuration import separately from whether system traffic is reaching the core is more useful than reinstalling repeatedly.

Check FlClash platform support →

Clash Nyanpasu: for desktop users who want core management

A good fit for users who want to customize the desktop interface, manage multiple configurations and understand the difference between the client and its core. We list the Windows installer. Because Nyanpasu can manage cores, judge compatibility by the core actually in use—not just the app's name. Before using Meta- or mihomo-specific fields, confirm the selected core matches the information in the logs.

Switching cores adds troubleshooting steps beyond a routine subscription import. After a switch, recheck configuration parsing, rule behavior and TUN permissions; a configuration that worked with the old core may not behave the same way with the new one. For everyday connections, Clash Plus is the simpler choice. Consider a client with core management when you actually need that control.

Browse Windows clients →

Clash for Windows: for legacy setups and migration

Discontinued

CFW is a common abbreviation for Clash for Windows, and many older guides focus on its configuration and proxy pages and system proxy toggle. We keep an archived Windows download for reproducing existing setups, reading legacy configurations and planning a migration. For a new installation, choose an actively maintained client such as Clash Plus, Clash Verge Rev or FlClash.

The original Clash ecosystem and mihomo differ in protocol support, DNS fields and rule capabilities. Older installations may also have had their core changed manually. Before migrating, back up your subscription source and custom rules, then import the subscription into the new client. Don't copy the old app's cache, service directories or full settings folder over. Verify the new setup first, then disable the old app's startup entry.

See archived Windows downloads and alternatives →

Clash Meta for Android: fine-grained Android controls

CMFA is short for Clash Meta for Android. It's a good fit for Android users who want to manage Clash YAML, control per-app access and monitor connections. Its Meta/mihomo-family core works with Android's system VPN routing. On first launch, import a configuration, grant the system VPN permission, then check the VPN status in the status bar and the client's connection records.

If your phone disconnects, check battery optimization, background restrictions and other VPN apps. Android generally can't have two system VPNs route traffic for the same user at once; work profiles and other special cases also depend on system behavior. Choose an installer architecture supported by your device's ABI. If you're unsure, check the download page instead of guessing from the processor brand.

Download the Android app →

Surfboard: check for Surge-style configuration first

Surfboard is another proxy client, but it uses a different configuration system from Clash clients. Its independent implementation and Surge-style configuration make it a good fit for Android users who already have a compatible configuration source. Before choosing it, check the subscription provider's output format and whether its protocols are supported. Don't assume a Clash YAML URL can be imported as-is.

Converting formats doesn't guarantee full compatibility: rule types, proxy group behavior and DNS settings may need individual adjustments. If you only have Clash YAML and want to keep using mihomo features, Clash Plus, CMFA or FlClash is more likely to preserve compatibility. Simply changing a file extension doesn't complete a migration.

See Surfboard and Android alternatives →

ClashX Meta: an archived macOS menu bar client

Discontinued

A good fit for Mac users who need to read legacy configurations or keep a familiar menu bar workflow. It uses a Meta-family core and is primarily managed from the menu bar with local configuration files. We keep archived downloads for Apple silicon and Intel Macs. For a new installation or before upgrading macOS, compare actively maintained options such as Clash Plus, Clash Verge Rev and FlClash.

Archived apps may behave differently after a system upgrade, especially around permissions and restoring proxy settings. Before migrating, note the old ports, rules and local configuration paths. Quit the old client and turn off its system proxy before enabling the new one. If your browser still has connection issues, check macOS network settings for a leftover proxy address instead of running both clients at once.

See archived macOS downloads and alternatives →

Before you download

Subscription compatibility and client migration

Why can the same subscription behave differently?

A subscription provides configuration; the client manages it and integrates with the operating system; the core handles protocol and DNS parsing and traffic routing. A difference in any of these can change the result. For a fair comparison, use the same configuration, proxy selection and routing mode. System proxy and TUN setups cover different traffic, so their results can't be used to rank clients directly.

Migrating from an old client: what order should you follow?

  1. Save your subscription source and back up custom rules and local overrides separately. Subscription links may contain access credentials, so hide the full URL in screenshots or support requests.
  2. Quit the old client and disable its system proxy and startup entry. Keep a backup, and don't run both routing services at once.
  3. Import the subscription into the new client and verify the default configuration first. Then migrate ports, DNS, rules and TUN settings one at a time.
  4. Check connection records and matched rules. Once everyday apps work, remove the old service and configuration directories.

Where to go next

For installers and architecture choices, visit the client downloads page. For your first import, follow the subscription import guide. To write rules, configure DNS or understand Fake-IP, see the mihomo advanced configuration guide. If an import fails, the proxy doesn't work or you run into permission issues, use the help center to troubleshoot by symptom—it’s usually faster than repeatedly switching clients.