Client Selection / Platforms and Configs

Clash Client Comparison
Platforms, cores, and ease of use

Start by narrowing down your operating system, then check config format, maintenance status, and permission requirements. For a fresh install, start with Clash Plus. If you already rely on a specific config workflow, compare desktop mihomo clients, Android options, and archived releases.

Platforms and architectures Config compatibility Maintenance status

Platforms / Cores / Workflows

Compare Eight Clients

Platform availability reflects what this site's download center lists, not every platform a project supports. Ease of use refers to config setup and permissions, not performance. Features may also differ across platforms for the same client.

On narrow screens, scroll horizontally. Select a client name in the table to jump to its review.

Platform support, cores, and ideal users for each client
Client Platforms listed here Core / Config system Maintenance status Ease of use Key features and considerations Best for
Clash Plus
Top pick
Windows、macOS、Android、iOS Check each platform's product details for core and config compatibility Actively maintained Easy; import a config and grant the required system permissions Available on multiple platforms; choose an installer or app store for your system First-time users and anyone using both desktop and mobile
Clash Verge Rev Windows、macOS、Linux mihomo; continues the Meta config ecosystem Actively maintained Moderate; requires understanding configs, system proxy settings, and service mode Config management, rule-based routing, TUN, and config overrides Users who want control over desktop configs
FlClash Windows、macOS、Android、Linux mihomo Actively maintained Easy to moderate; platform-specific permissions still apply Cross-platform UI, config import, proxy groups, and rule management Users who switch between desktop and Android
Clash Nyanpasu Windows Supports managing multiple cores; available cores depend on the build Actively maintained Moderate to advanced; check core compatibility and config fields Desktop config management, core selection, and UI settings Power users comfortable managing config differences
Clash for Windows Windows Original Clash family; refer to archived builds No longer maintained Familiar to long-time users; check carefully before migrating newer configs Reproducing compatibility with existing configs and legacy workflows Users keeping an old setup for troubleshooting
Clash Meta for Android Android Meta / mihomo family Actively maintained Moderate; requires VPN permission and managing background restrictions Clash YAML configs, rule-based routing, and runtime logs Android users with existing Clash configs
Surfboard Android Independent implementation; Surge-style config system, not a Clash core Actively maintained Easy with a compatible config; migrating formats can be difficult Policy groups and routing rules within its supported feature set Users with configs compatible with Surfboard
ClashX Meta macOS Meta family; refer to archived builds No longer maintained Few basic steps; verify compatibility with newer systems yourself Menu bar controls, config switching, and system proxy Users maintaining an existing macOS workflow

Client Reviews

Config Workflows and Trade-offs

The reviews below follow the order in the comparison table. Before choosing, check the format your subscription provides, then review the client's logs and config documentation. Similar product names do not guarantee compatibility, and a setting with the same name may work differently across platforms, especially when it comes to routing system traffic.

Clash Plus: The First Choice for a Fresh Install

If you don't already have a preferred client, Clash Plus is our top pick. The download center offers options for Windows, macOS, Android, and iOS, making it a straightforward way to establish a clear installation and config import process. For your first setup, follow the instructions for your platform. Import a config, choose an outbound, and grant any required permissions before exploring extras such as launch at startup or LAN access.

Availability across platforms doesn't mean configs sync automatically, or that every version uses the same core or supports identical fields. Before migrating an existing config, check its protocols, rule format, and subscription import method. Test advanced DNS, scripts, and overrides individually. On iOS, get the app through the App Store link in the download center. See the product details at clashplus.io (opens in a new tab).

Go to Downloads →

Clash Verge Rev: Desktop Config Management

Clash Verge Rev suits users primarily on Windows, macOS, or Linux who want more control over mihomo configs. Start with config import and the system proxy. Install the relevant service and enable TUN only if you need to route traffic from more apps. If something goes wrong, this approach makes it easier to tell whether the cause is the config, system proxy, or virtual network adapter.

Config overrides and merge options let you retain local settings, but they can also make the active config differ from the original subscription. After changing ports, DNS, or rule order, inspect the effective config rather than only the subscription editor. If your device is managed by an organization, check whether service installation and network extensions are allowed. Reinstalling the client won't solve a permissions issue.

Browse Desktop Downloads →

FlClash: A Consistent Experience on Desktop and Android

Based on mihomo, FlClash is available here for desktop systems and Android. If you switch between a computer and an Android phone, its similar interface can make it quicker to find configs, proxy groups, and settings. Users with an existing mihomo config can start by importing the same base config, then adjust how traffic is routed on each system.

A shared interface doesn't eliminate differences between operating systems. Android requires VPN permission and background settings; desktop systems have separate controls for the system proxy, TUN, and service permissions. Before copying a config, check whether file paths, network interface names, or listen addresses are specific to the original device. Don't copy desktop file paths to a phone or assume the desktop system proxy toggle works like Android's connection button.

See FlClash Download Options →

Clash Nyanpasu: Managing Core and Config Differences

Clash Nyanpasu is for users who want more control over their desktop config workflow. This download center lists Windows installers; check the project documentation for other release platforms. Its multi-core management can help compare how a config behaves across cores, but available options, how cores are obtained, and whether they are bundled depend on the build you install.

Back up your config before switching cores, and note the protocols, rule providers, and DNS fields in use. A field accepted by one core may not work with another. Start with a minimal config to verify the connection, then restore overrides and advanced options one at a time. If you only need to import a subscription for everyday use and don't need to switch cores, consider a client with a simpler setup.

View Windows Clients →

Clash for Windows: Archived Use and Alternatives

Clash for Windows is no longer maintained. Archived builds are mainly useful for reproducing an old setup, checking legacy settings, or assisting with a migration—not as a reason to keep using a familiar interface in a new environment. Changes to system permissions, newer protocols, and config fields may exceed what an older build can handle. Starting successfully doesn't mean every feature still works as expected.

Looking for a Clash for Windows alternative? Start with Clash Plus. If desktop config management for mihomo is your main concern, compare Clash Verge Rev and FlClash. For a migration, export your config source, proxy group selections, and local rules, then set up the system proxy and TUN again. Don't copy the entire old app folder or let two clients compete for the same mixed port or system proxy.

Explore Alternatives →

Clash Meta for Android: A Mobile Option for Existing YAML Configs

Clash Meta for Android, often abbreviated as CMFA, suits Android users with existing Clash YAML configs who want to keep using rule-based routing. The features available depend on the Meta- or mihomo-family core included in the client build. On first launch, import and select a config before granting VPN permission. A config that exists but isn't enabled is a different issue from a parse error.

Android battery optimization, background restrictions, and other VPN apps can affect connectivity. If the connection drops, first check whether the system stopped the process or another app took over the VPN, then review rules and DNS. Match the package to your device's processor architecture. If you're unsure, follow the download page's instructions rather than judging by file size. Keep a copy of the original config to avoid losing local edits when a subscription updates.

View Android Downloads →

Surfboard: Check the Config System First

Surfboard shares some use cases with the Clash ecosystem, but it isn't a Clash GUI and doesn't use a Clash core. It has an independent implementation and a Surge-style config system; consult the product documentation for exact compatibility. If you already have a Surfboard-compatible config, you can keep using its policy groups and rule structure. If you only have a Clash YAML subscription, first check whether your provider offers a compatible format.

Changing a file extension doesn't convert a config. Protocol parameters, policy group syntax, rule types, and DNS behavior may all differ, and online converters don't guarantee that the original meaning is preserved. If you do need a converter, don't submit subscription URLs containing credentials to an untrusted service. For new users whose configs are based on Clash YAML, an Android client that explicitly supports the format is usually easier to troubleshoot.

Browse Android Clients →

ClashX Meta: Existing macOS Menu Bar Workflows

ClashX Meta is a macOS menu bar client using a Meta-family core, and is no longer maintained. It's useful for reference or reproducing compatibility with older configs, but isn't recommended as the default for a new device. A compact menu bar interface doesn't mean the core is recent or that it works with current macOS network permissions.

After replacing a Mac or upgrading macOS, recheck the processor architecture, system proxy, and required permissions. Don't assume an old device's results apply to the new one. Before migrating, note where configs are stored, where subscriptions come from, and which local rules are in use. Then install a maintained client and test a basic connection. Once verified, quit the old client and confirm the new one controls the system proxy to avoid leftover ports interfering with connectivity.

See macOS Alternatives →

Choose by Use Case

Beginners, Power Users, Multiple Devices, and Older PCs

Final Recommendations

Start with Clash Plus; Let Config Needs Guide Your Alternatives

For a fresh install, start with Clash Plus and choose your operating system in the download center. Linux users can compare Clash Verge Rev and FlClash on the download page. If your current config workflow is reliable, there's no need to switch just for a different interface. Consider changing clients when your system is no longer supported, required config fields aren't supported, or the app's maintenance status makes it a poor fit.

The download center also lists the Mihomo core for users managing processes on servers or routers. It's a core, not a desktop client with a full GUI, so you'll need to manage startup options, config paths, logs, and permissions yourself. That's why it isn't grouped with the GUI clients above as an easy-to-use option.

  1. Check your device. Verify the OS version and architecture, then choose the matching platform in the download center.
  2. Check your config. Confirm the subscription format, required protocols, and rule fields, and keep a copy of the original config.
  3. Test separately. Quit the old client and use the new one to verify a basic connection before enabling advanced traffic-routing settings.
  4. Complete the migration. Verify subscription updates, rule matching, and behavior after a system restart, then remove the old client's startup and proxy settings.

If you see a parse error or connection issue, first note the exact error, client name, and platform. For installation and migration steps, see the Platform Guides; for the difference between system proxy and TUN, see the FAQ.

Downloads: Choose a Client by Platform →