What Is Clash Verge Rev?
Clash Verge Rev is one of the most popular graphical clients for the Clash proxy stack. After the original Clash Verge project stopped receiving updates, the community fork continued development under the Rev name. The app runs on the Mihomo core (formerly Clash Meta), which adds modern protocols, stronger rule matching, and reliable TUN support compared with the legacy Clash core.
If you searched for a Clash for Windows alternative after CFW was archived in 2023, Verge Rev is usually the first name you will see. It ships for Windows, macOS, and Linux, stays open source, and receives frequent kernel updates. For many desktop users in 2026, it has become the default Mihomo GUI: clean layout, subscription management built in, and enough depth for power users who want overrides and custom routing.
This guide is the most complete Clash Verge Rev setup walkthrough for 2026 on our site: from download through subscription import, rule-based routing, TUN mode, and node selection. You do not need prior YAML experience if you follow the steps in order.
Download and Install
Before you import any subscription, confirm your system meets the baseline requirements below. Using the wrong architecture (for example x64 on Apple Silicon without Rosetta) is a common reason installs fail silently or crash on first launch.
| Operating system | Minimum version | Architecture |
|---|---|---|
| Windows | Windows 10 1903 or later | x64 / ARM64 |
| macOS | macOS 10.15 Catalina or later | Intel / Apple Silicon |
| Linux | Ubuntu 20.04+, Arch, Fedora, etc. | x64 / ARM64 |
Windows installation
- Visit our download page and grab the latest
.exeinstaller for Clash Verge Rev. - Run the installer and accept the default path, typically under
%LOCALAPPDATA%\Programs\Clash Verge. - Launch the app from the desktop shortcut or Start menu.
- When Windows Firewall asks for network access, choose Allow so the core can bind local ports.
macOS installation
- From the download page, download the
.dmgfor your chip: ARM64 for M-series Macs, x64 for Intel. - Open the disk image and drag Clash Verge Rev into Applications.
- On first launch, macOS may block the app. Open System Settings → Privacy & Security and click Open Anyway.
- For TUN later, allow the system extension when prompted and reboot if macOS requires it.
Linux installation
Linux users can run the AppImage without a system package manager, which is handy on immutable distros:
chmod +x clash-verge_*_amd64.AppImage
./clash-verge_*_amd64.AppImage
On Debian or Ubuntu you may prefer the .deb package:
sudo dpkg -i clash-verge_*_amd64.deb
First Launch: Interface Overview
The main window splits into a left sidebar and a content panel. Knowing these five areas saves time when something does not connect:
- Proxies — View proxy groups, run latency tests, and pick the active node.
- Profiles — Add remote subscription URLs, update configs, and switch the active profile.
- Rules — Read-only list of routing rules loaded from the active YAML profile.
- Connections — Live sessions and traffic stats for debugging.
- Settings — Outbound mode (Rule / Global / Direct), system proxy, TUN, DNS, language, and theme.
Import a Subscription URL
A Clash subscription URL is the backbone of your setup. It delivers node lists, proxy groups, and starter rules from your provider. Without a valid profile, the Mihomo core has nothing to route through.
- Open Profiles in the sidebar.
- Click New → Import from URL.
- Paste the HTTPS link from your provider (never share it publicly).
- Name the profile—for example by provider or region—then confirm.
- Click Activate on the profile row so it becomes the running config.
Switch to Proxies and confirm groups and nodes appear. Set auto-update to roughly 24 hours so expired nodes get refreshed without manual clicks. Stale subscriptions are a leading cause of “everything times out” reports.
Rule-Based Routing and Outbound Modes
Rule-based routing is what makes Clash practical for daily browsing: domestic or LAN traffic can go direct while international or blocked destinations use the proxy. Most provider subscriptions already ship curated rule sets and remote rule providers—you rarely need to write rules from scratch on day one.
Choose the right outbound mode
In Settings, under outbound / system proxy options, you will see three modes:
- Rule — Recommended default. Traffic follows YAML rules (direct vs proxy per domain/IP).
- Global — Forces all matched traffic through the selected proxy group. Handy for short troubleshooting sessions.
- Direct — Disables proxy routing; equivalent to pausing Clash without uninstalling.
Also enable System Proxy in Settings when you want browsers and most desktop apps to respect Clash automatically. Rule mode plus system proxy covers the majority of web browsing and streaming use cases.
Profile overrides without editing the subscription
Providers overwrite your file on every update. To add personal rules—such as sending a company intranet domain direct—use Merge / Override on the active profile:
- In Profiles, click Override (or merge script) beside the active entry.
- Add prepend rules so they run before provider rules:
prepend-rules:
- DOMAIN-SUFFIX,internal.example.com,DIRECT
- IP-CIDR,192.168.0.0/16,DIRECT,no-resolve
prepend-rules inserts entries at the top of the rule chain, giving them priority over later MATCH rules from the subscription.
Enable TUN Mode (System-Wide Capture)
System proxy settings only affect applications that honor HTTP/SOCKS configuration. TUN mode creates a virtual network interface and routes TCP/UDP at a lower layer, which helps command-line tools, some games, and apps that ignore OS proxy settings.
Windows
- Open Settings and enable TUN Mode.
- Approve the UAC prompt so the service can install drivers.
- On first run, WinTun downloads (roughly 2 MB). Wait until the toggle stays on without errors.
- Check Connections to see sessions flowing through the tunnel.
macOS
- Enable TUN Mode under Settings.
- Allow the system extension in Privacy & Security and reboot if required.
- Test with
curl https://example.comin Terminal; traffic should follow your active rules.
https://1.1.1.1/dns-query) under DNS settings to reduce leaks and random resolution failures.
Proxy Groups, Latency Tests, and Node Selection
Open Proxies to see how your provider organized nodes. Names differ by subscription, but you will commonly find:
- Manual select — You pick a country or server manually.
- URL-Test / Auto — Mihomo periodically tests latency and picks the fastest node.
- Fallback — Tries nodes in order until one responds.
- Final / catch-all — Handles traffic that did not match earlier rules.
Run a latency test and switch nodes
- Click the lightning icon beside a group to ping all members (default test URL is often
https://www.gstatic.com/generate_204). - Green numbers mean lower latency; red or timeout means that node is unusable right now.
- Click a node name to activate it immediately—no restart required.
Troubleshooting: Common Issues
Profile imports but sites still do not load
Verify outbound mode is Rule, System Proxy is on, and at least one node shows reasonable latency. If every node times out, test the subscription URL in a browser while connected through another network path, then contact your provider.
Full disconnect after enabling TUN
Open DNS settings. Set a working local nameserver (router IP or a public resolver you trust) and a fallback DoH endpoint such as https://1.1.1.1/dns-query. Disable TUN, apply DNS changes, then enable TUN again.
Subscription update fails with a network error
Updates need outbound connectivity. Temporarily switch to Global mode with any working node, update the profile, then return to Rule. If updates still fail, the subscription token may be expired.
Crashing on macOS 14 or 15
Older builds used kernels that conflict with newer macOS releases. Use Check for updates inside Settings and move to the latest Rev release before debugging rules or TUN.
WinTun driver will not install on Windows
Run the app as administrator once, and pause aggressive antivirus scanning during driver install. Some security suites flag WinTun as suspicious even though it is widely used by VPN and tunnel software. Re-enable protection after a successful install.
Summary: Strengths, Limits, and What to Do Next
You now have an end-to-end picture of Clash Verge Rev configuration in 2026: install the desktop client, import a subscription, stay on Rule mode for smart split routing, optionally layer overrides, enable TUN when you need deeper capture, and manage nodes with latency tests.
Verge Rev excels on desktop Mihomo workflows, but it is not the answer for every user:
- Learning curve — Proxy groups, rule providers, and merge scripts take time if you have never used Clash.
- No mobile builds — There is no official iOS or Android Verge Rev port; phones need a different Mihomo GUI.
- TUN setup friction — Permissions and DNS tuning vary by OS version.
- Advanced overrides — Script-based merges reward users who already know YAML or JavaScript.
Browser-only “VPN” extensions often route just the browser, leak DNS outside the tunnel, and rarely expose rule-based split routing. Stock OS proxy dialogs cannot manage dozens of nodes, URL-test groups, or provider subscriptions. Compared with those options, Clash’s Mihomo stack gives you transparent rules, measurable latency per node, and TUN when you need full-device coverage—if you are willing to spend a few minutes on setup.
If you want the same Mihomo power with less manual tuning—and clients for phone and tablet as well as desktop—the builds on our site streamline subscription import, ship sensible defaults for routing and TUN, and stay consistent across Windows, macOS, Android, iOS, and Linux so you are not maintaining separate tools per platform.