Clash Verge Rev vs the Original Clash Verge (Differences, Download & Migration)
Many people searching “Clash Verge Rev” can’t quite tell how it relates to “Clash Verge”. This is a one-stop explainer plus migration guide.
If you only want to download and install the latest version, jump straight to Download & install.
In one sentence #
Clash Verge Rev = today’s de-facto official, updated Clash Verge.
The original Clash Verge (by zzzgydi) was archived and discontinued in 2024. Clash Verge Rev is the community-maintained continuation, built on the newer Mihomo kernel. If you’re downloading Clash Verge today, download Rev.
Project history #
The original Clash Verge (archived) #
- Author: zzzgydi
- Repo: github.com/zzzgydi/clash-verge (archived)
- Last version: around 1.3.x (please verify against the repo releases)
- Kernel: Clash Meta
- Status: maintenance stopped for personal reasons; the repo is archived read-only
Clash Verge Rev (community-maintained) #
- Maintained by: the community, multiple contributors
- Repo: github.com/clash-verge-rev/clash-verge-rev
- Current version: v2.5.1 (actively updated)
- Kernel: Mihomo (the continuation branch of Clash Meta)
- Status: active maintenance, regular releases
“Rev” stands for Revival / Revised — i.e. the “revived / improved” version.
Detailed comparison #
| Dimension | Original Clash Verge | Clash Verge Rev |
|---|---|---|
| Maintenance | ❌ archived in 2024 | ✅ active |
| Kernel | Clash Meta | Mihomo (Clash Meta’s successor) |
| Protocols | VMess / VLESS / Trojan / SS / SSR | the above + Hysteria2 / TUIC v5 / WireGuard, etc. |
| TUN mode | supported, but weaker performance/stability | rewritten, much better performance and compatibility |
| UI | early Tauri, untouched since 2024 | Tauri 2.0, dark mode, tray menu, continually improved |
| Windows 7 | some old versions worked | not supported since v2.x |
| Multi-platform | Windows / macOS / Linux | same, with more complete Linux Arm support |
| New protocols | ❌ no longer tracked | ✅ tracks Mihomo upstream |
| Auto-update | no new versions to update to | ✅ one-click update in the GUI |
Why you should use Rev #
If you’re still on the original, here’s why you should migrate to Rev:
- Security — older Clash Meta builds had memory-safety bugs that were later fixed; the original no longer receives patches.
- Protocols — Hysteria2, TUIC v5 and similar only work properly on Rev; many providers have fully switched to these newer protocols.
- Stability — Mihomo heavily rewrote core paths: TUN mode, DNS leak prevention, rule matching.
- Ecosystem — all new subscription converters, rule providers and third-party tutorials are written for Rev by default.
Download & install #
You can get the latest Clash Verge Rev from our download page in one click (with a GitHub Proxy mirror):
👉 Go to the Clash Verge download page
Or grab it straight from the official repo releases:
Full migration steps (original → Rev) #
Step 1: back up subscriptions and config #
In the original, open Settings → Profiles and copy each subscription URL into a note. If you have custom rules, also back up the clash-verge user directory (paths below).
| OS | Original config directory |
|---|---|
| Windows | C:\Users\<your-username>\.config\clash-verge\ |
| macOS | ~/Library/Application Support/io.github.zzzgydi.clash-verge/ |
| Linux | ~/.config/clash-verge/ |
Step 2: fully uninstall the original #
- Windows: uninstall from Control Panel, then delete the config directory above.
- macOS: drag the .app to Trash, then delete the Application Support directory.
- Linux:
sudo apt remove clash-verge(or your package manager), then delete~/.config/clash-verge/.
Step 3: install Clash Verge Rev #
Grab the installer for your platform from the download page and install it normally. Don’t install into a path with non-ASCII characters.
Step 4: re-import subscriptions #
Launch Rev → Profiles → New → paste the subscription URL.
Step 5: reset the network mode #
- Proxy mode: choose “Rule” based on the rule set your provider supplies.
- Network mode: start with “System Proxy”; once it works, switch to “TUN mode”.
- Latency test: a good test URL is
http://www.gstatic.com/generate_204(more test URLs).
Step 6: verify #
- Open https://www.google.com to confirm access.
- Open https://ip.sb to confirm your IP switched to the node’s location.
Common migration questions #
Q1: The subscription URL errors with “cannot parse”? #
Usually the provider’s subscription converter outputs YAML fields that differ between old Clash Meta and newer Mihomo. Ask your provider’s support to switch the output to the Mihomo / clash.meta format.
Q2: A node won’t connect after migration? #
It may use a newer protocol (e.g. Hysteria2) that the original silently skipped, while Rev recognizes it but needs it configured correctly. Check that the node’s type field was handled properly by the subscription converter.
Q3: Can I reuse my old custom rule files? #
Almost always, yes. Mihomo is compatible with Clash Meta’s rule syntax; it only adds a few new types. If a rule doesn’t take effect, check the latest syntax in the Mihomo docs. See also our guide on adding custom rules.
Summary #
| Your situation | Recommendation |
|---|---|
| Already on Clash Verge Rev | just keep it updated |
| On the original Clash Verge | strongly recommended to migrate to Rev per this guide |
| Never used it, first install | install Rev directly; don’t bother with the original |
| Saw a third-party “cracked / enhanced Clash Verge” | don’t install it — this is free open-source software with no paid edition; so-called cracks are usually malware |
Download: Clash Verge download page · Client comparison: Clash Verge alternatives · Custom rules: How to add rules · On Android: Clash Verge for Android alternatives.