Proxy Clients Compared: Verge Rev, FlClash, CMFA and More
On this page
Five names dominate any proxy client comparison today: Clash Verge Rev, FlClash, Clash Meta for Android, NekoBox and v2rayNG. They overlap enough to be confused with each other and differ enough that picking blind leads to frustration — three of them are mihomo-based Clash clients, the other two belong to entirely different ecosystems.
The differences that matter in practice are four: which platforms it runs on, which core does the actual proxying, which configuration format it consumes, and how much it expects from you. This comparison goes through the five clients on exactly those axes, ending with concrete recommendations by scenario.
The mihomo family
Clash Verge Rev: the desktop mainstay
An open-source, community-maintained desktop client for Windows, macOS and Linux, built on Tauri with the mihomo core bundled inside. It is the most complete of the five: profile management with editing, system proxy and TUN mode, a service mode for privileged operation, and a full connections view for debugging. If you live on a desktop and want one client that does everything the core offers, this is the default answer — our download center carries version 2.5.2 for all three platforms.
FlClash: one interface everywhere
A Flutter-based open-source client with the mihomo core, running on Android, Windows, macOS and Linux with an essentially identical, deliberately simple interface on each. It trades some of Verge Rev's depth for clarity and cross-device consistency — a strong pick if you switch between phone and desktop and want zero relearning. Version 0.8.94 is available on this site for Android, macOS and Linux; the FlClash guide covers setup in detail.
Clash Meta for Android: the official one
CMFA is the MetaCubeX project's own Android client with mihomo built in — closest to the core, updated in step with it, and lean in interface. Configuration is profile-based with URL import, and it exposes core options that simpler apps hide. We carry version 2.11.32 in three APK flavors (arm64-v8a, armeabi-v7a, universal).
Outside the Clash family
NekoBox for Android
Developed by MatsuriDayo, NekoBox is built on the sing-box core rather than mihomo. That single fact changes the ecosystem around it: different configuration model, different rule system, broad protocol coverage through sing-box. It is a capable choice when your provider or protocols point that way.
v2rayNG
Developed by 2dust, v2rayNG is the long-established Android client of the v2ray/Xray core lineage. Its world revolves around per-server share links and its own subscription mechanism rather than Clash-style YAML with proxy groups and rules. Simple model, enormous installed base, most natural fit when your provider distributes Xray-style links.
Side-by-side comparison
| Client | Platforms | Core | Config format | Best for |
|---|---|---|---|---|
| Clash Verge Rev | Windows / macOS / Linux | mihomo | Clash/mihomo YAML | Desktop daily driver, power features |
| FlClash | Android / Windows / macOS / Linux | mihomo | Clash/mihomo YAML | Same experience across devices |
| Clash Meta for Android | Android | mihomo | Clash/mihomo YAML | Android with Clash subscriptions |
| NekoBox for Android | Android | sing-box | sing-box profiles / share links | sing-box ecosystem users |
| v2rayNG | Android | v2ray/Xray | Share links / own subscriptions | Xray-style providers |
Recommendations by scenario
- New to all of this, on a desktop: Clash Verge Rev — then follow the complete beginner's guide from install to first connection.
- Android with a Clash-format subscription: CMFA if you like staying close to the core, FlClash if you prefer the softer interface — both read the same YAML subscriptions.
- Phone and desktop, minimal friction: FlClash on both, one mental model.
- Provider only gives share links, or you want sing-box: NekoBox or v2rayNG — the dedicated introduction explains when each makes sense.
Note: every client above is in our download center — the mihomo-family apps across all platforms, and NekoBox and v2rayNG as arm64-v8a Android builds. For other architectures or older versions, use each project's official GitHub releases.