What is Clash Verge Rev?

Clash Verge Rev (often shortened to CVR) is a community-maintained, open-source graphical client for Clash built on the Mihomo core (formerly Clash.Meta). When the original Clash Verge project stopped receiving updates, the community fork continued development under the “Rev” line. CVR keeps a clean desktop UI while tracking new Mihomo features, protocol support, and security fixes—making it a natural upgrade path if you are coming from older tools such as Clash for Windows (CFW).

Clash Verge Rev targets Windows, macOS, and Linux. You can paste a subscription URL from your provider and let the app pull nodes and policies without hand-editing a large YAML file by hand. Advanced features include TUN (true system-wide capture), multiple profiles, and Overrides so your custom rules survive subscription refreshes.

CVR is desktop-only. For Android or iOS you will need a separate mobile Clash-compatible client or a solution that covers all platforms from one vendor.

System requirements

Before you download, confirm your environment meets the minimum versions below.

Download and install

You can get official-style packages from this site’s download page; builds are hosted for fast access without relying on third-party mirrors.

Windows

After you download the .exe installer:

1. Run the installer.
2. If SmartScreen shows “Windows protected your PC”, choose More info → Run anyway.
3. Follow the wizard, pick an install folder, and finish setup.
4. Launch from the desktop shortcut or Start menu.
5. Allow network access if Windows Firewall prompts on first start.

macOS

After you download the .dmg:

1. Open the .dmg and wait for the volume to mount.
2. Drag Clash Verge Rev into Applications.
3. Open it from Applications.
4. If macOS says the app is from an unidentified developer, open System Settings → Privacy & Security and use Open Anyway for this app.

Linux

Pick a package format that matches your distro:

• Debian / Ubuntu: install the .deb with sudo dpkg -i clash-verge-rev_*.deb
• Fedora / RHEL / CentOS: install the .rpm with sudo rpm -i clash-verge-rev_*.rpm
• Universal: use the .AppImage, mark it executable, and run it directly

First launch and UI overview

Clash Verge Rev uses a two-pane layout: navigation on the left, detail on the right. The sections you will use most often are:

• Proxies — policy groups and servers; pick a node or an auto / URL-test group when your config defines one
• Profiles — add, update, and activate subscription-backed profiles
• Rules — inspect the active rule list and how traffic is classified
• Connections — live connections; filter by app or domain and drop entries when debugging
• Logs — verbose trail for diagnosing handshake and routing issues
• Settings — system proxy, TUN, launch at login, theme, and core options

A light / dark toggle in the header keeps the UI readable for long sessions.

Import a subscription URL

Your provider gives you a private subscription URL (usually HTTPS). CVR downloads the profile, parses nodes, and can refresh it on a schedule.

1. Open Profiles from the sidebar.
2. Click New or the + control.
3. Paste the subscription URL into the URL field.
4. Enter a clear name (for example, “Primary provider”).
5. Save; the app fetches the profile and lists servers.
6. When the card shows a successful update, activate that profile.
7. Switch to Proxies, choose a policy group, and pick a low-latency node or auto mode.

Rule-based split tunneling

Mihomo’s rule engine lets you send traffic to DIRECT, a Proxy policy group, REJECT, or custom actions. A solid profile keeps domestic services direct (lower latency, less metered bandwidth) while overseas or sensitive domains use your proxy—and ad or tracker domains can be dropped when your rule sources include block lists.

Common rule types

Use community rule sets (recommended for beginners)

Authoring thousands of lines by hand is unnecessary. High-quality community bundles—Loyalsoldier/clash-rules is a widely cited example—group domestic, overseas, and ad domains with maintained IP supplements. Pair them with your provider subscription for predictable behavior.

• Domestic destinations stay on DIRECT
• Major overseas services ride your Proxy group
• Known ad domains can be rejected when the set includes blocking data
• GEOIP-style coverage reduces misrouting for local CDNs

Overrides in Clash Verge Rev let you prepend or append snippets without editing the fetched subscription YAML directly, so your tweaks persist the next time the profile syncs.

TUN mode for system-wide proxying

TUN creates a virtual interface so the kernel can steer traffic through Mihomo—not only HTTP/HTTPS aware apps that honor “system proxy” settings. That matters for CLI tools (curl, git, pip, npm), many games, UDP-heavy voice or video sessions, and any binary that ignores PAC or manual proxies.

• Command-line utilities that bypass application-level proxy settings
• Game launchers and clients (Steam, Epic, Battle.net, etc.)
• UDP-heavy apps
• Programs with no HTTP proxy support

Turn on TUN

1. Open Settings.
2. Locate the TUN mode toggle and enable it.
3. Approve elevation (UAC on Windows or admin password on macOS / Linux).
4. Wait until the status shows enabled / healthy.

Troubleshooting

All nodes show high latency or fail health checks

Likely cause: stale subscription data or every outbound is offline.

Fix: Update the profile in Profiles. If nothing improves, confirm billing, expiry, and traffic quota with your provider.

Some foreign sites still load as if unproxied

Likely cause: the hostname matched a DIRECT rule or never hit a proxy rule.

Fix: Switch the relevant policy group to Global temporarily. If Global works, expand your rule sources or add Override entries for those domains.

Network drops immediately after enabling TUN

Likely cause: virtual adapter stack conflict, another VPN product, or an incomplete privileged install.

Fix: Disable TUN, restart CVR, relaunch elevated on Windows, then retry. Try changing stack mode from System to gVisor in TUN advanced options if clashes continue.

macOS reports the app “can’t be opened” or “damaged”

Likely cause: Gatekeeper quarantine flags on unpacked apps.

Fix:

xattr -cr /Applications/Clash\ Verge\ Rev.app

Subscription fetch times out

Likely cause: the subscription host is flaky from your network, or your current proxy intercepts the download.

Fix: Pause system proxy, fetch again, or set a subscription request header (some providers tune routing on User-Agent—for example clash-verge).

Need one client for desktop and mobile?

Clash Verge Rev excels on desktop stacks, but it does not ship Android / iOS apps, and Windows environments missing a current WebView2 runtime can struggle to render the UI. Managing desktops and phones with separate YAML flows also adds friction.

• No mobile builds — you need another client on phones and tablets
• WebView2 on Windows — outdated or missing runtimes break the interface on some PCs
• Configuration sprawl — hard to keep policies identical across many devices

If you want a single workflow across Windows, macOS, Linux, Android, and iOS, the Clash build we publish here uses the same Mihomo family of features, ships curated rule packs, and stays aligned with modern transports (for example VLESS, XTLS, Hysteria 2) as the core evolves—download the bundle that matches each platform from our site when you are ready to consolidate.