127.0.0.1 / Client Selection

Clash Client Comparison & Selection

Start by ruling out clients that don't support your device, then check whether they can import your existing config. For everyday connections, Clash Plus is a good place to start. For rule overrides, connection checks, or apps that ignore system proxy settings, compare clients by core and traffic-routing method.

mixed-port / Quick Comparison

Compare Eight Clients

Platform entries show only the systems covered by client pages on this site, not every platform supported by the upstream projects. Ease of use reflects the steps needed to import a config, choose a proxy, and verify the connection—not performance.

Swipe horizontally on narrow screens. Clash Meta was renamed mihomo, though older clients may still use the former name.
Client Platforms covered here Core or implementation Maintenance status Ease of use Key features Best for
Clash Plus Windows、macOS、Android、iOS Check platform-specific release notes Actively maintained Easy Import configs and choose a proxy in a graphical interface First-time installs and everyday use on desktop or mobile
Clash Verge Rev Windows、macOS、Linux mihomo Actively maintained Moderate Config overrides, connection details, TUN Desktop users who need detailed traffic routing
FlClash Windows、macOS、Android、Linux mihomo Actively maintained Easy to moderate Similar interface on desktop and Android Users who switch often between a computer and Android device
Clash Nyanpasu Windows mihomo available; other options depend on the build Actively maintained Moderate Core switching, config management Users who need to compare core behavior
Clash for Windows Windows Original Clash core, as included in the archived release Discontinued Moderate Config list, proxy switching, system proxy Users reviewing old configs or migrating an existing installation
Clash Meta for Android Android Clash Meta(mihomo) Actively maintained Moderate Config profiles, runtime logs, per-app settings Android users who already have a Meta config
Surfboard Android Independent implementation; not a Clash core Actively maintained Moderate Own config format, rule-based routing Android users with a compatible config
ClashX Meta macOS Clash Meta Discontinued Easy to moderate Menu bar proxy switching, system proxy Users reviewing or migrating legacy macOS configs

rules / Client Reviews

How the clients differ in practice

If you use a subscription, first check which config formats your provider supports. If you have a local YAML file, keep a copy of the original. The reviews below cover each client's strengths and settings that are easy to miss when migrating.

Clash Plus

Top pick

After installing, try the three basic steps: import a config, choose a proxy, and verify the connection. You usually don't need to learn YAML first. A config appearing in the list only means the client has read it; select it, then make sure the desktop proxy or mobile connection is enabled. Desktop and mobile have different system permissions and settings, so don't assume the same routing steps apply to both. If your config relies on a specific protocol or core field, check the release notes for your platform before choosing a client explicitly marked for mihomo.

Clash Verge Rev

A good fit for desktop users who switch between work and personal configs or want to see which rule a domain matched. Use the connections view to check where traffic is going. To keep local rules, add them as overrides and verify the result after subscription updates. Start with the system proxy if it meets your needs. If an app ignores it, consider TUN and check that the required service permissions are granted and the virtual interface is ready. Change one setting at a time when testing to pinpoint whether the issue is a routing rule or the traffic interception method.

FlClash

When you use both a computer and an Android phone, similar workflows for configs, proxy groups, and connection controls make it easier to switch devices. Confirm the config works on one device, then import it on the other and check the selected proxy. Similar interfaces don't mean selections sync automatically. If the computer works but the phone disconnects after the screen has been off, check the phone's VPN connection and background restrictions before changing shared rules.

Clash Nyanpasu

Best for users who specifically need to compare cores or rotate between multiple configs. First check which core options are included in your build, then note the active core, port, and config. When switching cores, keep the test config the same and use the same apps for retesting; this helps separate field compatibility issues from differences in existing settings. If you're just getting started with a subscription, use the default working core—there's no need to configure every core just to try them out.

Clash for Windows

Discontinued

Archived releases are mainly for checking legacy setups, not for new installations. When migrating, save your subscription URL or local config, note the proxy port and old proxy group names, and check whether your browser, terminal, or other tools point to the old port manually. Quit the old client and disable the system proxy it set before launching the new one. If the new client uses a different port, update any apps with a manually configured proxy address so connection failures aren't mistaken for config incompatibility.

Clash Meta for Android

A good option to compare if you're an Android user with a Meta-format config who also needs to view logs. After importing, select the config profile, grant VPN permission, and test with an app. To route only certain apps through the client, check the per-app settings. Choose an installer based on your device's CPU architecture, not how the system interface looks. If you're unsure, check the download page's universal package notes. If the connection comes up but only some apps fail, check the app scope and the rules for the affected domains first.

Surfboard

This Android tool uses its own config format; it isn't a drop-in replacement for Clash YAML. If you already have a compatible config, first check that it includes proxies, proxy groups, and rules, then enable the system VPN connection. If your provider only offers Clash-format subscriptions, ask whether a separately adapted config is available. Being able to open the subscription URL doesn't mean Surfboard can correctly read its protocols and rules. Recheck routing after switching clients.

ClashX Meta

Discontinued

When migrating from an older Mac, the archived release can help you check the previous menu bar proxies, configs, and system proxy state. Before reinstalling, identify whether your Mac has Apple silicon or an Intel processor, then choose a maintained client that supports your architecture. After migrating, check that the system proxy points to the new client's listening address, then test your browser and terminal—they may not use the same settings. Make sure any local rules from the old menu bar client were exported with the config; the subscription name alone doesn't confirm this.

DIRECT / Use Cases

Choose a Client by Use Case

config.yaml / Final Recommendations

Clash Plus for Everyday Use

If your device is supported and you mainly import configs and switch proxies through a graphical interface, start with Clash Plus. For Linux desktops, look at Clash Verge Rev. If you want a similar workflow on Android, compare it with FlClash. Before reinstalling, save your original config and note the proxy port. Run the old and new clients separately to avoid having both compete for the same listening port.

Download Clash