Clash Verge Rev vs FlClash vs Clash Nyanpasu: Which Client Should You Pick?

The starting point: same core, different shells

In November 2023, the original Clash core repo was archived and legacy clients like Clash for Windows stopped receiving updates. Every GUI client still actively maintained today has moved to the mihomo core (formerly Clash Meta). Clash Verge Rev, FlClash, and Clash Nyanpasu are the three with the largest install bases.

Same core means same protocol support. Whether Shadowsocks, VMess, VLESS, Trojan, Hysteria2, TUIC, or WireGuard works is determined by mihomo, not by the client shell. On this front, all three are tied.

The real differences come down to four things: which operating systems each one supports, what tech stack the UI is built on, how much configuration help it offers, and how heavy it is on system resources. This guide compares exactly those four points and gives platform-specific picks.

Clash Verge Rev: the desktop feature ceiling

Clash Verge Rev is the community-maintained continuation of the now-archived Clash Verge, licensed under GPL-3.0. It's built on Tauri: the UI runs in the system's built-in WebView (WebView2 on Windows, WebKit on macOS), with core logic written in Rust. It doesn't ship a bundled browser engine, so its install size and memory footprint stay well below typical Electron-based apps.

Platform coverage includes Windows, macOS (separate builds for Intel and Apple Silicon), and Linux (DEB / RPM). Feature coverage spans the full workflow: system proxy, TUN mode, subscription management, rule and log viewing, connection management, and in-app core updates.

Configuration enhancement is where it really stands out. Merge (override profiles) lets you patch rules and proxy groups without touching the original subscription, while global scripting uses JavaScript to programmatically transform your config. Both survive subscription refreshes, which makes it well suited to users maintaining long-term custom rulesets.

Verdict: the most feature-complete desktop client available, and the default pick for Windows and macOS daily drivers.

FlClash: one interface for desktop and Android

FlClash is built on Flutter, producing installers for Windows, macOS, Linux, and Android from a single codebase, with a Material-style interface.

Its main selling point is cross-device consistency. Page layouts, setting locations, and workflows stay nearly identical between your computer and your Android phone, so switching devices doesn't mean relearning the app. It runs on the mihomo core with the same protocol support as Clash Verge Rev; traffic is routed via VpnService on Android, and desktop builds support both system proxy and TUN mode.

The trade-off shows up on desktop: the layout density and control sizing lean toward mobile conventions, which takes some adjustment if you're used to traditional desktop apps. Flutter's desktop rendering engine also pushes memory usage to a moderate level — higher than Tauri-based apps, though still lighter than typical Electron apps.

Verdict: the top choice if you use both a computer and an Android phone. If you're desktop-only and want a tighter, more compact UI, check the other two first.

Clash Nyanpasu: swappable cores, deep customization

Clash Nyanpasu shares Clash Verge Rev's Tauri architecture and GPL-3.0 license, with coverage for Windows, macOS, and Linux.

What sets it apart is core flexibility. Besides mihomo, it also keeps Clash Premium and Clash Rust as switchable core options, letting you test how the same config behaves across different cores. For daily use, stick with mihomo — Clash Premium is no longer updated and its protocol support is stuck on an old baseline.

The interface is highly polished, with extensive theme, color, and layout customization plus rich animations. Core features like subscription management, rule viewing, connection logs, TUN mode, and system proxy are all covered.

The trade-off is complexity. First-time setup means deciding on a core, theme, proxy mode, and a handful of other toggles — less straightforward than Clash Verge Rev for beginners.

Verdict: best for advanced users who care about visual customization or need to switch cores to troubleshoot compatibility issues.

Quick comparison table

Beyond these three: macOS, Android, iOS

A lighter macOS option: ClashX Meta

A native macOS menu bar app built on the mihomo core. Great if all you need is a menu bar toggle without a full-featured panel; if you need subscription enhancements and detailed logging, Clash Verge Rev is still the better fit.

Another Android option: ClashMetaForAndroid

Also featured on our download page, this Android client runs on mihomo with a UI that stays close to native Android conventions. Pick between this and FlClash based on your priority: FlClash for cross-device consistency, this one for a more native feel.

iPhone and iPad: Clash Plus

None of the three clients above are available on iOS. Install Clash Plus from the App Store — see the setup guide for subscription import and first-connection steps.

Quick picks by use case

1. Windows daily driver, only installing one app: Clash Verge Rev.
2. Desktop plus Android, want a consistent workflow: FlClash.
3. macOS, just need a menu bar toggle: ClashX Meta; need full features: Clash Verge Rev.
4. Want to switch themes or swap cores: Clash Nyanpasu.
5. Linux desktop: Clash Verge Rev or FlClash — both ship Linux packages.
6. iPhone / iPad: install Clash Plus from the App Store.

Notes on switching or running multiple clients

Subscription links work across all three clients — just copy and paste to migrate. The proxies, rules, and proxy-group structure in a YAML config are portable, too, but client-specific enhancements are not — Clash Verge Rev's Merge profiles and scripts, or Clash Nyanpasu's core-switching settings, will need to be rebuilt after switching clients.

All three clients default to mixed port 7890. Running two at once causes a port conflict, and whichever client started second will have a broken proxy. Keep only one running at a time.

TUN mode requires elevated permissions in all three clients: a service install on Windows, a password prompt on macOS. Use either TUN mode or system proxy — never both at once. See the protocol guide for how TUN works, and the glossary for term definitions.

FAQ