Clash Client Comparison

Built on mihomo, this client suits desktop users who want to manage remote subscriptions, inspect proxy groups and configure network routing. The basics are similar across Windows, macOS and Linux, but service installation, permission prompts and system proxy behavior differ.

Advanced users can use configuration overrides to keep local changes separate from remote subscriptions. Before editing, distinguish the original subscription, override content and final running configuration. Otherwise, changes in the editor may not affect active connections. Linux users should also check their distribution’s package format instead of choosing an installer based only on a desktop screenshot.

Built on mihomo for desktop systems and Android, this client suits users who want a more consistent workflow across devices. Similar page layouts make it easier to find configuration, proxy and connection controls, but network permissions, background operation and tray behavior are still determined by the operating system.

Before choosing FlClash, check that your usual configurations load correctly, then see how connections recover after switching networks. On Android, check battery management; on desktop, distinguish the system proxy from TUN. Differences with the same subscription may come from DNS, routing methods or platform settings—not the client name alone.

For desktop users willing to learn how core selection and configuration processing work. Treat its interface and core management as separate things: whether a protocol in a configuration file works depends on the running core and its supported features, not simply on whether the interface shows a toggle for it.

This site provides a Windows installer; the platforms supported by the project are not the same as the packages listed here. If you have a complex setup, keep the current client’s running configuration, then check subscription processing, rule overrides and port settings one by one. If you only need a basic connection, there is no need to add core-management steps to your initial setup.

Often abbreviated as CFW, this legacy client was historically built for other desktop platforms as well as Windows. It follows the original Clash core and should not be assumed to support the protocols and configuration extensions in current mihomo.

The archived installer is mainly for reproducing a legacy setup, reading an existing configuration or assisting with migration. An older core may not parse newer protocol fields in a subscription. Operating system updates can also introduce compatibility issues with services and network routing. For a new installation, choose a maintained client. When migrating, copy the subscription and necessary rules; avoid replacing the entire old application directory.

An Android client based on the Meta/mihomo core, suited to users already working with Clash YAML configurations. It routes traffic through Android’s system VPN interface, which requires permission on the first connection. A VPN indicator confirms that a tunnel is active, but does not by itself prove that every app is being routed as expected.

Check configuration loading, proxy group selection and app-level routing together. If the connection drops in the background, check battery optimization and background restrictions before investigating the subscription or nodes. Choose an installer for your processor architecture. Universal and architecture-specific packages differ in packaging, not inherently in protocol support.

Surfboard is an Android proxy client, but it is not another interface for mihomo. It has an independent implementation and uses Surge-style configuration syntax. Its presence in the same download list does not mean it can read Clash YAML directly or supports every field in other configuration ecosystems.

For users with a working Surfboard configuration or a subscription service that explicitly provides the matching format. If you only have a Clash subscription, changing the file extension is not enough to make it importable. When converting configurations, check protocol support, proxy group types and rule semantics. A successful parse does not guarantee that the original routing behavior has been preserved.

This client uses the Meta core family and is designed around the macOS menu bar. Existing users accustomed to its interface can use the archived package to check legacy configurations, but its bundled core is limited to that archived build and should not be confused with current, maintained mihomo clients.

When replacing a Mac or upgrading macOS, reassess compatibility instead of migrating only the app. Choose the correct installer for Apple silicon or Intel, then check system proxy settings, launch at login and helper services. For a new installation, start with Clash Plus. If you need more complete desktop configuration management, compare Clash Verge Rev and FlClash.