· Client Comparison · 8 min read
Clash Verge vs. FlClash vs. ClashX Meta: Which Clash Client Should You Choose?
Compare popular Clash clients by platform support, kernel version, interface, TUN, and overrides. Find the right fit for beginners, multi-device users, and advanced users.
Start with your platform: Verge Rev, FlClash, or ClashX Meta
For desktop use, start with Clash Verge Rev if you want to manage subscriptions, rules, and local overrides in one place. If you use both desktop and Android, try FlClash. Mac-only users who prefer switching proxy groups from the menu bar may want to consider ClashX Meta, but check its release and maintenance status first. Verge Rev is the successor to the original Clash Verge; they are separate projects, not the same product with different installers.
| Client | Platforms | How you interact with it | What to check before installing |
|---|---|---|---|
| Clash Verge Rev | Windows、macOS、Linux | Manage subscriptions, proxies, and connections from the desktop app | System architecture, kernel version, and permissions for the TUN service |
| FlClash | Windows、macOS、Linux、Android | Similar configuration and proxy-group workflows on desktop and mobile | Android VPN permission and how to edit configuration in your target version |
| ClashX Meta | macOS | Switch configurations, outbound modes, and proxy groups from the menu bar | Project release status, macOS compatibility, and permissions for enhanced mode |
None of the three has an iPhone app. On a Mac, check your chip or processor under Apple menu → About This Mac. Choose an arm64 or universal build for Apple silicon, or an x64 build for an Intel Mac. On Linux, check the package format and whether your desktop environment supports the client's system proxy integration, as well as the CPU architecture.
Kernel versions: sharing mihomo doesn't guarantee identical behavior
Clash Meta is now called mihomo. The client version identifies the interface and integration features; the kernel version identifies the code that parses configuration, handles DNS, and forwards connections. Even when two apps both use mihomo, they may bundle different versions or transform the same subscription into different runtime configurations.
Record these three values before migrating
- Client version: Record the full version number from the About page or release notes. Use this version when comparing TUN controls, service installation, and configuration editing options.
- Running kernel version: Check the kernel information or startup log. You can run
mihomo -vto check a standalone mihomo binary, but the binary in your system path may not be the one the client is running. - Local listening ports: Check the active configuration for
mixed-portor the separateportandsocks-portsettings. For example, if the mixed port is set to7890, apps configured to use a proxy manually should use the actual listening address and port.7890is only an example, not a shared default across these three clients.
If migration fails, start with the first configuration parsing error. If it points to a protocol or field, check whether the target kernel supports it. If it points to a missing proxy group, make sure the target named in rules matches a name in proxy-groups. Node latency tests can't tell you anything about ports, permissions, or network routes until the configuration loads successfully.
System proxy vs. TUN: choose based on which apps need routing
mode: rule means connections that reach the kernel are routed according to rules. System proxy and TUN determine how connections reach the kernel. Switching to global mode won't automatically route apps that weren't passing through the client in the first place; enabling TUN doesn't switch rule mode to global mode.
- Desktop browsers: Start with the system proxy enabled and rule mode on. Check the destination domain and matched policy in the connections panel. The system proxy mainly affects apps that honor the system proxy settings.
- Desktop apps that ignore the system proxy: Check whether the app has its own proxy settings before considering TUN. Actual permission requirements for Verge Rev and FlClash desktop vary by operating system and version. For ClashX Meta's enhanced mode, check the documentation and permissions for your installed version.
- Android: FlClash routes traffic through Android's VPN interface. If another VPN is running, check whether switching will interrupt an active connection. Typically, only one VPN service can be active per Android user or profile.
Subscription overrides: will local changes survive an update?
A subscription is a remote configuration source; an override is a local change applied by the client. Editing a downloaded remote configuration directly may work until the next update replaces it. When comparing clients, distinguish between editing a standalone local configuration, editing a cached copy of a remote subscription, and attaching a persistent override to a subscription. All three may be labeled “Edit,” but updates handle them differently.
Verge Rev is a good fit for desktop users who manage multiple subscriptions and want to keep merged configurations or script processing separate from the original subscriptions. FlClash offers a similar workflow across devices, but check how editing, overrides, and import and export work in your target version. Don't assume desktop options are available on Android. ClashX Meta is better suited to choosing a prepared configuration from the menu bar; if you rely on a full override workflow, first confirm that your version preserves those changes.
Check override persistence with a single rule
- Choose a domain that should bypass the proxy and that you're authorized to test. Add a rule in the form
DOMAIN,example.com,DIRECTto a test configuration, replacing the example with a domain you're permitted to use. - Place the rule before any rule that could match first, especially a trailing
MATCHrule. Rules are evaluated in order, so adding a new rule after the catch-all won't work. - Update the subscription once and reapply the configuration. Close existing connections, then make a new request. Check the matched rule and outbound route in the connection log. If the rule has disappeared, the change wasn't saved in the persistent configuration. If it's still there but doesn't match, check the rule order and the request's actual destination first.
Choose a client and migrate based on your workflow
- New to this, using one computer: Start with Verge Rev. Import a subscription, choose a proxy group, and enable the system proxy. If you only use a Mac and prefer menu bar controls, consider ClashX Meta, provided its release and kernel versions meet your OS and configuration requirements.
- Desktop and Android: Try FlClash first. You can reuse the same subscription, but check ports, app routing, local network access, and DNS settings separately on each device. Similar interfaces don't mean local settings sync automatically between devices.
- Advanced users managing rules and overrides: Prioritize the ability to inspect the final runtime configuration, preserve local changes, and review matched connections. Run a full subscription update in your target client before migrating your everyday configuration.
Before switching, note your old client's proxy ports, selected proxy groups, and any essential overrides, then turn off its system proxy and TUN. Don't let two clients listen on the same port or both modify system routes. In the new client, use rule mode to test one direct connection and one proxied connection, then restore custom DNS, overrides, and TUN one at a time. If something breaks, rolling back the last change makes it easier to find the cause than reinstalling the client, updating subscriptions, and changing nodes all at once.