Clash Verge Rev Download & Setup Guide 2026 | Complete Tutorial

What is Clash Verge Rev

Clash Verge Rev is the community-driven desktop client many users now treat as the spiritual successor to Clash for Windows. It keeps the familiar Clash YAML workflow, but the surrounding stack is much more current: active maintenance, a modern desktop shell, and a bundled mihomo core.

As of 2026-03-13, the stable release is v2.4.6. The GitHub repository clash-verge-rev/clash-verge-rev has about 102k stars, and the bundled core is mihomo (Meta) v1.19.19. That combination matters because it gives former Clash users a familiar config model without trapping them in an abandoned client.

It is also built with Tauri, which is a Rust-based desktop framework and noticeably lighter than Electron. In practical terms, that usually means quicker startup, lower memory overhead, and a smaller always-on footprint.

Why people treat it as the CFW successor

The biggest reason is continuity. Clash Verge Rev still speaks Clash YAML, so your subscription URLs, local YAML files, proxy groups, and routing rules are usually much easier to carry over than when moving to a totally different protocol ecosystem.

• Community maintenance: it keeps moving instead of freezing on an old stack.
• Cross-platform support: Windows, macOS, and Linux all use the same general workflow.
• Modern core: mihomo brings newer rule and protocol support.
• Lighter shell: Tauri is simply a better fit than an aging Electron wrapper for many users.
• Familiar mental model: the Clash-style subscription and routing logic is still intact.

Download and install

The recommended download source is the official GitHub Releases page. For a clean start in 2026, choose the stable release v2.4.6. Avoid random mirrors, repacked installers, or forum uploads when you can use the official release channel instead.

Pick the installer that matches your operating system:

• macOS: usually a .dmg.
• Windows: usually a .exe installer.
• Linux: commonly a .deb, depending on distro packaging.

Windows steps

1. Download the correct .exe package for your system.
2. Run the installer and complete the default setup flow.
3. Allow network and proxy-related permissions on first launch.
4. Expect an elevated prompt later if you enable TUN mode.

macOS steps

1. Open the .dmg and drag the app into Applications.
2. Allow the app in macOS security settings if Gatekeeper blocks the first launch.
3. Grant local network and related system permissions.
4. Approve the extra authorization flow if you turn on TUN.

Linux steps

1. Install the matching package such as .deb.
2. Use your package manager or graphical installer to complete setup.
3. Verify that system proxy and networking permissions are available.
4. Check distro-specific TUN requirements before enabling full traffic capture.

First-time setup

On first launch, keep the order simple: import your subscription, choose a mode, then test real connectivity. That is the fastest way to confirm the client is healthy before you start adding advanced routing logic.

1. Import a subscription URL: add the provider link in the profile or subscription area.
2. Choose a mode: start with Rule mode unless you have a specific reason to use Global or Direct.
3. Update the profile: fetch the latest nodes and generated config.
4. Enable the proxy layer: use system proxy or TUN depending on your app mix.
5. Test a few destinations: try direct sites, proxied sites, and one or two apps you use daily.

Subscription management

Good subscription habits matter more than many people expect. Clash Verge Rev lets you add, update, and organize multiple profiles, and that becomes especially useful when you separate daily, backup, or test providers.

• Add clearly named profiles: make each source easy to identify.
• Update immediately after import: confirm the link is valid before doing anything else.
• Use auto-update carefully: daily or periodic refresh is usually enough.
• Handle multiple subscriptions cleanly: clear group naming prevents routing confusion.
• Back up before major changes: especially before core or rule adjustments.

When migrating from older clients, the first thing worth checking is proxy group naming. A profile can import successfully while still routing differently if the group names no longer match your old rule references.

Proxy modes explained

Clash Verge Rev usually gives you four modes that matter most in daily use: Rule, Global, Direct, and Script. The right default for most people is still Rule mode because it balances automation with control.

• Rule mode: recommended for most users because domains, IPs, and rules decide traffic automatically.
• Global mode: sends all proxy-eligible traffic through one route and is useful for quick testing.
• Direct mode: bypasses the proxy layer and is useful when isolating whether a problem comes from routing.
• Script mode: applies JavaScript logic to routing decisions and is aimed at advanced setups.

If you are unsure, keep Rule as the default and treat the other modes as tools for special situations rather than permanent replacements.

TUN mode

TUN mode matters when system proxy alone is not enough. Some apps ignore normal proxy settings or generate traffic outside the usual browser-and-desktop-app path. TUN makes the client much better at handling those cases by capturing more system traffic.

That does not mean everyone should leave it on permanently. It is more powerful, but it also asks for elevated privileges and can increase complexity when troubleshooting permissions or conflicts with other network tools.

• Enable it when: apps do not respect system proxy or you need fuller traffic capture.
• Skip it when: browser-based proxy use already works and you want the simplest setup.
• Expect elevated access: admin approval is common on both Windows and macOS.
• Watch battery and CPU: the overhead is not always dramatic, but it can be real on laptops.

Enhancement scripts

Enhancement scripts are where Clash Verge Rev moves beyond a basic subscription client. JavaScript scripts let you override or extend routing logic in ways that would be awkward or noisy in plain static rules.

That can mean dynamic route decisions, special handling for certain services, or policy tweaks layered on top of your normal Clash config. It is powerful, but it also increases the number of moving parts in your setup.

The practical rule is simple: stabilize your YAML workflow first, then introduce scripts one at a time so you can still debug the result when behavior changes.

Profiles and config structure

Even if you live in the GUI most of the time, understanding the YAML structure still pays off. Many routing surprises trace back to how the config is assembled rather than to the user interface itself.

• proxies: individual nodes with protocol and connection details.
• proxy-groups: the policy groups your rules actually point at.
• rules: the routing logic that decides which traffic goes where.
• rule-providers: external rule sets that keep large configs maintainable.
• dns: often a hidden cause when rule matching looks wrong.

You do not need to handwrite everything, but you should know that group names, provider references, and DNS choices all influence the final behavior more than many beginners expect.

Comparison: Clash Verge Rev vs V2RayN vs ClashX

This table is meant to help you choose the right direction quickly rather than declare one universal winner.

In short: choose Clash Verge Rev for the smoothest Clash-style continuation, V2RayN for broader protocol ambitions, and ClashX when macOS-native behavior matters most.

Common issues

1. Subscription import fails

Confirm the full URL, any required auth parameters, and whether the provider has rotated the link. Many import failures come from expired or copied-partially links rather than the client itself.

2. TUN mode is not working

Check elevated privileges, system network extension approval, and conflicts with other VPN or proxy tools. TUN issues are often permission issues first.

3. CPU usage is too high

Start by reducing aggressive testing, simplifying scripts, and checking whether you enabled heavy rule sets or verbose logging. Then add advanced features back gradually.

macOS note

Clash Verge Rev works well on macOS, especially if you want the same interface across multiple desktop platforms and you need mihomo-native features.

Clash Verge Rev works great on macOS, but if you prefer a native Swift app with menu bar integration, ClashX is purpose-built for Mac. You can start from the download page.

FAQ