Client selection guideCLIENT MATRIX

Clash client comparison

Choose by operating system first, then check whether your config is supported. For a first install, start with Clash Plus. To inspect rule matches or debug overrides on desktop, compare it with Clash Verge Rev. If you already have a subscription, check its config format before deciding whether anything needs to be rebuilt.

Downloads by platform

Clash client comparison table

Platform links list only the downloads available on this site, not every release from each upstream project. Ease of use reflects the steps needed to import a config, switch modes, and view logs—not performance. On mobile, swipe horizontally to see the full table.

Client Platforms Core Maintenance Ease of use Key features Best for
Clash Plus Top pick Windows、macOS、Android、iOS View product details by platform Actively maintained Easy Import configs and select an outbound in the GUI First-time installs; switching between desktop and mobile
Clash Verge Rev Windows、macOS、Linux mihomo Actively maintained Moderate Config overrides, connection logs, system proxy, and TUN Desktop routing debugging and custom rule maintenance
FlClash Windows、macOS、Android、Linux mihomo Check maintenance announcements for the selected release Easy to moderate Cross-platform interface, config, and proxy group management Switching between desktop and Android
Clash Nyanpasu Windows Supports mihomo; check which core is selected Check the project's maintenance announcements Moderate Manage multiple configs; view connections and logs Desktop users who switch configs often
Clash for Windows Archived Windows Original Clash family Discontinued Moderate Keeps the legacy config and proxy group workflow Checking legacy setups and migrating old configs
Clash Meta for Android Android Clash Meta family Check the project's maintenance announcements Moderate Android VPN routing, proxy groups, and logs Android users with compatible configs
Surfboard Android Independent implementation; does not use the Clash core Check the project's maintenance announcements Easy to moderate Manage Surfboard-compatible configs and routing rules Android users with compatible configs
ClashX Meta Archived macOS Clash Meta family Discontinued Easy Switch proxy groups and system proxy from the menu bar Migrating legacy macOS configs

Clash Meta is an older name for mihomo. The table uses “Clash Meta family” to identify the core lineage of legacy releases; it does not mean they support every current mihomo field. To check compatibility, use the core actually bundled with your installer and the result of importing your config.

Client reviews: what to check before installing

Being able to import the same subscription does not guarantee the same routing behavior. Read the relevant review to check config format, traffic capture, and settings that are easy to miss during migration.

Clash Plus: import a config and make your first connection

Installing a client for the first time? Clash Plus offers a straightforward way to get started: import a config supported by your platform, select an outbound, and check whether the app's traffic reaches the client. It covers four popular desktop and mobile platforms listed on this site, making it a practical way to learn how configs, proxy groups, and connections work together on a device you already use. Traffic capture and config support vary by operating system, so don't assume a desktop YAML file will import unchanged on a phone. If your config uses custom DNS, rule sets, or overrides, start with a minimal version to verify connectivity, then add the extra fields back one at a time.

Clash Verge Rev: check rule matches in connection logs

A good fit for desktop users who know which proxy group traffic should use but need to find out which rule actually matched. Enable the system proxy, send a request from an app that uses system proxy settings, then check the connection page for the destination domain, matched rule, and selected outbound. If the app doesn't appear in the log, check which traffic is being captured before changing your rules. Test TUN separately if you need broader traffic capture. To keep subscription updates working, put local changes in overrides and compare the effective config before and after an update. Don't mistake a config copy saved by the client for the original subscription.

FlClash: keep desktop and Android workflows in sync

If you use both a computer and an Android phone, FlClash lets you reuse familiar config and proxy group workflows instead of learning a different interface on each device. To compare behavior, use the same compatible config on both, select the same outbound manually, and visit the same test site. The desktop may use the system proxy while the phone uses Android VPN, so the apps being captured can differ. One successful request alone doesn't prove a rule is broken. During migration, note your manually selected outbound and platform-specific toggles; reimporting a subscription won't restore these local choices. Linux users should also check that their distribution supports the package format offered here.

Clash Nyanpasu: tell config changes apart from core changes

If you keep separate daily-use and test configs, Nyanpasu can help you manage them independently. Note the active config and core, switch to the one you want to test, then check that proxy group names and rule providers load as expected. If a field fails only after switching cores, check whether that core supports it. If you only changed the active config, inspect its references and indentation first. Avoid changing the config, core, and traffic capture method at the same time; otherwise, it will be hard to tell what caused the difference. This site lists a Windows installer only; see the project's release notes for other platforms.

Clash for Windows: migrate from an archived setup

This client is discontinued. Its archived download is useful for recovering settings from an old setup, but it isn't recommended for a new installation. Before migrating, make separate notes of your subscription URL, local YAML, extra rules, and manually selected proxy groups—especially changes made only in the old client's enhanced config. After moving to a maintained client, import the original config and confirm it connects before migrating local rules one by one. A config that parses successfully only confirms that its syntax is accepted; check that connections match the same rules and use the same outbounds. Turn off the system proxy setting in the old client before switching to avoid sending traffic to its old port.

Clash Meta for Android: check Android VPN and rule loading

CMFA is worth considering if you already have Clash Meta-compatible YAML and are used to checking proxy groups and logs on your phone. After importing, check that all proxy groups are present and rule providers loaded successfully, then grant Android VPN permission and connect. If the connection drops soon after startup, check whether the config failed to parse or another app took over Android VPN. If it disconnects only in the background, check the system's battery settings. Desktop options such as system proxy and service mode don't apply directly on a phone. If your config uses newer mihomo fields, check that the installed core supports them instead of judging compatibility by the app name alone.

Surfboard: choose by config syntax, not file extension

Surfboard can route proxy traffic, but it isn't a Clash core with a different interface. If you already have a Surfboard-compatible config, import it and check that its policies and rules are recognized. If you only have a Clash subscription, first ask the provider whether it offers a compatible format. Renaming a Clash YAML file won't turn it into a Surfboard config; proxy groups and rule fields may not map directly. During migration, test one specific domain rule and one fallback rule separately. That's more reliable than checking only whether the import succeeded. If routing differs, compare the content actually loaded before changing rule order.

ClashX Meta: keep menu bar settings as migration notes

Useful for checking legacy configs on an older Mac, but not recommended as the default for a new device. Before migrating, note the active config, proxy mode, and manually selected groups from the menu bar, along with the mixed port and system proxy status. If your terminal or developer tools have a proxy address hard-coded, update it if the port changes. When choosing a new installer, check System Information to see whether your Mac has Apple Silicon or an Intel processor, then confirm the minimum macOS version. After installing, let the new client manage the system proxy on its own, send a new request, and check the connection log. Don't let two menu bar clients change the system proxy at the same time.

Choose a client by use case

New to Clash? Verify one connection first

Start with the Clash Plus download for your platform. On Linux, check Clash Verge Rev first. Import your config, use Rule mode, select an outbound manually, then test a request with a predictable route. Troubleshoot in this order: config loaded → traffic captured → rule matched. Don't enable multiple traffic capture options at once. For your first setup, follow the Getting Started guide.

Advanced: keep rule changes easy to roll back

On desktop, start with Clash Verge Rev and keep the original subscription separate from local overrides. When adding a rule, test it against one domain and check the matched rule and final outbound in the connection log. Expand the rule only after the result is correct. If routing changes after you switch traffic capture methods, first check whether the target app is passing through the client, then revisit the rules. See the config field reference for field syntax.

Multiple devices: use one config source, test each device

For iPhone, start with the Clash Plus iOS download. For desktop and Android, FlClash is another option to compare. First check that your subscription provides a format each platform can read, then note the selected proxy groups and system proxy or VPN settings on each device. Similar interfaces don't mean settings sync. You may be able to reuse a compatible config and its rules, but traffic capture permissions and local settings need to be checked on each device.

Older PC? Check the minimum system requirements first

Check your operating system version, processor architecture, and installer requirements before choosing a maintained client. If you only need proxying for a browser, try the system proxy before enabling TUN; there's no need to load every rule set for an initial test. An older version that once launched isn't necessarily a good long-term choice. Keep your original config for migration, then check startup and switching under the same workload before deciding whether to keep the new client.

Top pick: Clash Plus—download for your platform

For a first install, choose Clash Plus on any platform where it's available here. If you need Linux desktop routing, or want to debug overrides and inspect connection logs from the outset, start with Clash Verge Rev instead. If your current client and config work reliably, there's no need to switch just to standardize names. Migrate only when your operating system, core fields, or traffic capture method no longer meet your needs.

After installing, verify three things: the config loads, the client receives requests from the target app, and the actual outbound matches the expected rules. Once all three check out, enable launch at startup or automatic subscription updates. If something goes wrong later, this makes it easier to tell whether the change came from installation, routing, or an update.

Download Clash