What Clash Verge Rev is (and why people pick it)

Clash Verge Rev is an actively maintained desktop GUI for Clash-compatible workflows. Under the hood it runs the mihomo core (formerly known as Clash Meta), which means you get modern protocol coverage, flexible DNS, and rule features that track today’s subscription ecosystems. Compared with juggling raw YAML and a separate binary, Verge Rev gives you profile management, one-click subscription refresh, a visual proxy picker, connection and log panels, and sane defaults for routing modes—without hiding the fact that everything is still standard Clash YAML when you need to edit it.

If you are migrating from older stacks, our Clash Meta upgrade guide explains how Premium-era configs map onto mihomo. This article focuses on installation and day-to-day use on Windows and macOS, which are the platforms most readers ask about first.

Before you download

Grab installers from our download page rather than random mirrors. The page tracks the client families we document here and keeps builds aligned with the guides. On Windows, choose x64 or ARM64 to match your CPU; on macOS, pick Apple Silicon versus Intel builds the same way. If you are unsure, Task Manager on Windows and “About This Mac” on macOS spell out the architecture in plain language.

Have at least one subscription URL or a local YAML profile ready. Most users paste a provider URL; advanced users sometimes import a hand-written file. Either path works once the client is installed.

Installing on Windows

Run the downloaded .exe and follow the setup wizard. Windows may show SmartScreen for applications that are not yet broadly reputation-scored; use “More info” and then “Run anyway” if you trust the source—here, the installer you obtained from our download page.

After installation you should see a tray icon. Right-clicking it is often the fastest way to toggle system proxy, open the dashboard, or quit the app. If the icon is missing, launch Clash Verge Rev from the Start menu once; some builds defer tray registration until the first successful start.

Service mode and elevation

On first launch, accept service mode when the client offers it. Service mode installs a small helper with elevated privileges so TUN (virtual network adapter) can come online reliably and you see fewer repeated User Account Control prompts than if you manually run the core as Administrator every session. TUN is the mode many users prefer for system-wide routing because it does not rely on applications respecting manual proxy settings.

If corporate policy blocks services, you can still experiment with system proxy mode, understanding that some apps ignore proxy environment variables and will bypass the tunnel unless you add rules or switch to TUN later.

Windows Defender and false positives

Network tools occasionally trigger heuristic alerts. If Defender quarantines a component, pause, verify the file hash against the publisher release if you want extra assurance, then add a controlled exclusion or restore the file. Random exclusions from unknown download sites are a bad idea; exclusions paired with a known-good installer are a pragmatic compromise many power users accept.

Installing on macOS

Open the .dmg, drag Clash Verge Rev into /Applications, and eject the disk image. The first launch may be blocked by Gatekeeper because the app is not signed through Apple’s notarized path for every fork. In that case open System Settings > Privacy & Security, scroll to the blocked app message, and choose Open Anyway once.

macOS will also prompt for network extensions and related permissions when you enable TUN. Approve them; without extension approval, the tun stack cannot attach. If something still fails, check whether a VPN or another filter is holding the network extension slot—only one extension family may own certain interfaces at a time.

Apple Silicon and Rosetta

Use the ARM64 .dmg on M1/M2/M3 Macs for native performance. The Intel build runs on Apple Silicon through Rosetta but costs extra battery and adds another variable when you debug connectivity. Match the build to the chip.

Folder permissions

Some environments need Full Disk Access or accessibility-related allowances for helper tools that enumerate processes when you use PROCESS-NAME style rules. If Verge Rev documents a specific macOS permission on your version, grant it deliberately rather than clicking through blindly.

First run: core version and language

Open Settings and locate the kernel or core section. You should see a mihomo version string. If the core is months out of date relative to upstream, use the in-app update action—Verge Rev can download and swap the binary for you, which is easier than manual replacement.

Set the UI language to your preference if the client ships bilingual labels. The profile language is independent: your YAML can use English keys even when the interface is localized.

Profiles and subscriptions

Clash Verge Rev organizes work into profiles. A profile is a YAML document plus metadata: remote rules, proxy groups, DNS stanzas, and tun sections all live there. To add a remote subscription, open the profile or subscription view, choose add, paste the URL, and save. The client fetches the feed, parses nodes, and merges them into the active configuration.

After import, click update or rely on scheduled refresh if your provider changes nodes frequently. When counts look wrong—zero proxies, or half the expected names—see the troubleshooting section; it is usually format, TLS interception, or a stale URL.

Local YAML instead of a URL

If you maintain a file yourself, copy it into the application profile directory and use import local file from the UI. Typical paths include %APPDATA%\io.github.clash-verge-rev.clash-verge-rev\profiles on Windows and ~/.config/clash-verge-rev/profiles on macOS, though the exact folder name can vary slightly by fork—trust the in-app reveal action if one exists.

For a deeper tour of keys like proxy-groups, rules, and Fake-IP DNS, read Clash YAML: routing rules, proxy groups, and Fake-IP on this blog.

System proxy versus TUN: choose deliberately

System proxy configures the OS-wide HTTP/SOCKS proxy settings so compliant applications send traffic through Clash. It is lightweight and easy to toggle off, but anything that ignores system proxy (many terminal tools, some games, odd Electron apps) will bypass the tunnel unless you add per-app wrappers.

TUN creates a virtual interface and routes eligible IP traffic through mihomo according to your rules—closer to “VPN-like” behavior for TCP and UDP flows that match the profile. TUN generally needs the service or extension permissions described earlier. Most users who want consistent behavior across browsers, IDEs, and background updaters eventually land on TUN for daily driving.

Daily use: proxies, rules, and logs

The Proxies tab is where you pick node or group outcomes—SELECT for manual choice, URL-TEST for latency-based auto pick, FALLBACK for ordered failover, and so on. Names come straight from your YAML; keeping group labels short and meaningful matters because you will click them often.

The Rules view helps you sanity-check which rule matched a flow. When a site misbehaves, do not guess: look at the hit, then adjust DNS, GEOIP, or domain rules as needed. Large community rule sets are convenient, but they are not magic—occasionally you must prepend a tighter rule for a stubborn domain.

The Logs panel is the honest narrator. Timestamped errors distinguish TLS handshake failures from DNS timeouts from outright bans. Copy relevant lines when asking for help; screenshots of empty dashboards rarely suffice.

For documentation beyond this walkthrough, the documentation hub collects broader topics that pair well with Verge Rev.

Updates: app versus core

Verge Rev ships on its own release cadence, while mihomo moves on another. Update the GUI when prompted to pick up interface fixes; update the core when you need protocol additions or upstream security patches. Doing both periodically is cheaper than debugging obscure failures on year-old builds.

If a release note mentions database or profile migrations, back up your profile directory before upgrading. Most upgrades are smooth, but YAML compatibility can shift at the margins.

Troubleshooting common issues

Most support threads boil down to a handful of patterns. Use the table as a first pass before you reinstall everything.

Habits that keep setups boring (in a good way)

Stable setups are mostly discipline: refresh subscriptions on a schedule you can remember, export profiles before big OS upgrades, and avoid stacking experimental tweaks the same week you change jobs or travel. Keep one known-good profile that is boring—direct domestic rules, conservative DNS—and experiment on a copy.

When something regresses after an OS patch, check vendor release notes first. Windows 11 and macOS both occasionally tighten sandboxing around network extensions; a one-line permission or plist change in the client release notes may save hours of packet tracing.

Closing thoughts

Clash Verge Rev is not the only mihomo GUI, but it is a practical choice when you want an actively maintained bridge between human-friendly controls and the full power of modern Clash YAML. Windows users should lean into service-backed TUN when policy allows; macOS users should respect Gatekeeper and extension prompts once so later launches are quiet. Pair those platform habits with sane subscription hygiene and occasional core updates, and the client tends to fade into the background—which is exactly what you want from infrastructure software.

When you are ready to install or upgrade alongside the rest of our maintained documentation, start from the download page so your build, checksum expectations, and help articles stay in sync. → Download Clash for free and experience the difference.