What is Clash Verge Rev?

Clash Verge Rev (often shortened to CVR) is a community-maintained fork of the original Clash Verge project. The upstream Clash Verge app is no longer actively updated; CVR carries the work forward with ongoing feature work, bug fixes, and a bundled Mihomo core (formerly known as Clash Meta), which is generally faster and more capable on modern protocols. The interface stays clean and approachable, while day-to-day behavior on Windows is polished enough that CVR has become one of the most popular Clash GUI clients on the platform.

Compared with many other Clash front ends, CVR tends to win on a few practical points: modest CPU and memory use, first-class support for the Windows system proxy, and a visual workflow for profiles, proxies, and rules that you can understand without reading YAML all day. If you have never used a proxy client before, you can still follow this tutorial end to end in a single sitting. We will move from download and installation to everyday use, with clear checkpoints so you know you are on the right track. For a broader view of Clash on other systems, you can also browse the Clash official home page after you finish the basics here.

Before you install: system requirements and caveats

Take a minute to confirm that your PC matches the expectations below. Most issues during first setup come from mismatched architecture, blocked firewall rules, or policy-restricted networks—not from the app itself.

  • Operating system: Windows 10 (version 1909 or later) or Windows 11. A 64-bit (x64) install is strongly recommended.
  • Runtime dependencies: Some builds expect the Microsoft Visual C++ Redistributable. Current Windows images usually include it already; if the app fails to start, install the latest supported redistributable from Microsoft and retry.
  • Windows Defender Firewall: After installation, Windows may ask whether Clash Verge Rev may communicate on private or public networks. Allow the app on the profile you actually use, or outbound tests will look “broken” even when the profile is fine.
  • Third-party antivirus: Heuristic scanners sometimes flag generic proxy binaries. If you trust the source, add the install folder to your exclusion list instead of fighting repeated quarantine events.
  • Administrator rights: The installer and TUN mode both touch drivers and routing tables. Use an account that can approve UAC prompts when asked.
If you are on a managed school or office network, check whether running a local proxy is allowed. Some enterprises block unknown processes or force a corporate proxy, which can prevent CVR from working no matter how carefully you configure it.

Download the Clash Verge Rev package for Windows

Official release artifacts are published on GitHub. Before you click anything, decide which CPU architecture you need. Nearly all desktop and laptop PCs sold in recent years are x64 (AMD64). If you use an ARM-based Windows laptop (for example some Snapdragon devices), download the arm64 build instead of guessing.

If you do not want to compare checksums and release notes on GitHub, use our curated Clash client download page to grab a recent stable build for Windows without hunting through asset lists.

Choose the right Windows package format

On a typical GitHub Release page you will see several Windows artifacts. Here is how to think about them:

File type What it is Recommendation
.exe (setup) Standard wizard installer; creates Start menu and desktop shortcuts; uninstalls cleanly through Settings. ★★★★★ Best default
.msi Windows Installer package; similar capabilities to .exe; handy for scripted or silent deployment. ★★★★☆
portable.zip Extract-and-run layout; avoids registry churn; convenient on USB drives or temporary machines. ★★★★☆

For most readers, the .exe installer is the fastest path: fewer manual steps, predictable upgrade behavior, and an uninstall entry that Windows understands. Pick the portable archive only when you deliberately want a folder you can copy between devices without running a setup program.

Install Clash Verge Rev step by step

After the download finishes, installation is intentionally boring—which is a good thing. Follow the highlights below so you do not miss a permission prompt.

  1. Launch the installer and accept UAC
    Double-click the downloaded .exe. When Windows shows the User Account Control dialog, choose Yes so the installer can write under your profile. That prompt is normal for desktop software, not a sign of malware by itself.
  2. Pick an install location (optional)
    The default path is usually similar to C:\Users\YourName\AppData\Local\Programs\clash-verge-rev. You may point the wizard at another drive if you prefer, but staying on the default path avoids odd permission edge cases with tightly locked folders.
  3. Finish the wizard and open the app
    Wait for the progress bar to complete—often well under a minute on an SSD. Leave Run Clash Verge Rev checked on the last screen, then click Finish to land directly in the main window.
On first launch, SmartScreen may show “Windows protected your PC” because the binary is not signed with an expensive commercial certificate. Click More info, then Run anyway. That workflow is common among open-source networking tools and does not, by itself, prove anything about code quality—always download from a source you trust.

First launch and interface overview

When Clash Verge Rev starts, you should see a tray icon (a small leaf-style logo near the clock) and a main window. Closing the window does not always quit the app: the core keeps running in the background until you explicitly exit, which is what you want if system proxy integration should stay active.

The UI is split into a left sidebar and a larger content pane. These are the pieces you will touch most often:

  • Proxies: Lists proxy groups and individual nodes. You can switch nodes manually or run latency tests to pick a responsive server.
  • Profiles: Where subscription URLs live. Add, update, rename, or delete remote profiles and choose which profile is active.
  • Connections: A live table of flows through the core—useful when you wonder which app is using the tunnel.
  • Logs: Streaming log output from Mihomo. When something fails, this is often the fastest place to read the precise error.
  • Rules: Read-only visibility into the rule chain your active profile loaded, helpful when you are learning how traffic is classified.
  • Settings: Global switches such as system proxy, TUN, autostart, themes, and core-related options.

Import a subscription link

CVR does not include servers out of the box. You need a valid subscription URL from a provider you trust (sometimes called an “airport” in Chinese-speaking communities) or from infrastructure you operate yourself. The URL is an HTTPS endpoint that returns a YAML configuration with nodes, credentials, and often embedded rule providers.

Import it into Clash Verge Rev like this:

  1. Open the Profiles screen
    Click Profiles in the sidebar to manage remote configurations.
  2. Create a remote subscription
    Use the + button, choose a Remote entry, and paste the full subscription URL into the URL field without trimming hidden characters.
  3. Set a readable name
    Fill in Name with something you will recognize later—for example the provider name plus billing cycle—so multiple profiles stay distinguishable.
  4. Save and wait for the download
    Press Save. The client fetches the YAML over HTTP(S). Within a few seconds you should see node counts and a fresh timestamp on the profile card.
  5. Activate the profile
    Click the profile card so it shows the active state (typically a highlighted border). Only the active profile drives your proxy list and rules.
Security note: Treat unknown subscription links like untrusted configuration files. A malicious profile can steer specific domains through attacker-controlled nodes or tamper with DNS behavior. Stick to providers you can verify, rotate credentials if a link leaks, and review node names occasionally for anything unfamiliar.

Turn on the system proxy

After your profile is active, browsers and many desktop apps still will not use Clash until the system proxy points at the local listener. In CVR, enable the System Proxy toggle in the top control strip. The app then configures Windows to send HTTP and HTTPS traffic to the default loopback endpoint (commonly 127.0.0.1:7890, though your profile may define a different mixed port—if in doubt, read the port shown in the UI or profile).

Pick a proxy mode that matches your scenario

Most builds expose three high-level modes. Understanding them prevents the classic “everything is slow” or “nothing connects” confusion.

  • Rule: The core evaluates your rule set per connection. Domestic targets often go DIRECT, international sites use your selected proxy group, and ad or malware domains may be dropped. This is the right default for most people.
  • Global: Every eligible flow uses the chosen outbound. Useful for debugging or fully tunneled environments, but local sites may become slower because they also ride the remote path.
  • Direct: Traffic leaves your machine without a proxy hop while the app keeps running—handy when you need a quick return to a normal ISP path without uninstalling anything.

Rule-based routing in plain language

Rule routing is the feature that separates Clash-class clients from “single SOCKS port” tools. Instead of one blunt switch, you maintain an ordered list that decides, for each connection, whether to proxy, bypass, or reject. Providers frequently ship curated rule providers (community sets such as ACL4SSR, Loyalsoldier, or blackmatrix7-style bundles are common examples) so you are not writing hundreds of lines by hand on day one.

If you need customization, many UIs offer an override layer that merges snippets without destroying the upstream subscription file. The table below shows typical building blocks you will see in YAML:

Use case Rule type Example
Send a whole suffix through your proxy group DOMAIN-SUFFIX DOMAIN-SUFFIX,google.com,Proxy
Force an exact hostname to bypass DOMAIN DOMAIN,example.com,DIRECT
Bypass a private LAN range IP-CIDR IP-CIDR,192.168.0.0/16,DIRECT
Send mainland China IPs direct (when GEOIP data is available) GEOIP GEOIP,CN,DIRECT
Final catch-all after everything else MATCH MATCH,Proxy
Rules evaluate from top to bottom. The first match wins, so put specific entries above broad ones and keep MATCH at the bottom as your intentional fallback. If you invert that order, you will spend hours wondering why a single stubborn domain never reaches the policy you expect.

Optional: TUN mode for apps that ignore the system proxy

System proxy mode only affects programs that honor WinHTTP/WinINET proxy settings. Plenty of software does not: some games, assorted .NET utilities, and command-line tools like curl or git unless you set environment variables separately. That gap shows up as “the browser works, but nothing else does.”

TUN mode installs a virtual adapter and redirects traffic at a lower layer so far more processes are covered. It is powerful, which also means you should expect extra UAC prompts and occasional conflicts with other VPN clients that own similar routes.

Enable TUN in Clash Verge Rev roughly as follows:

  1. Install service mode
    Under Settings, find the service installation control for the core, approve UAC, and wait until the UI shows that service mode is active (often indicated by a green or “on” state).
  2. Toggle TUN on
    Enable the TUN switch. Mihomo should create the virtual interface and program split routes according to your profile.
  3. Approve firewall prompts
    If Windows Firewall asks for network access, allow it for the correct profile (private vs public) so the adapter is not silently blocked.
  4. Turn on DNS hijacking if offered
    Combining TUN with DNS hijacking helps prevent accidental DNS leaks where queries bypass your tunnel. Read your provider documentation before mixing this with corporate DNS requirements.

Verify that the proxy path is actually working

Once system proxy or TUN is active, run three quick checks before you assume success:

  • Browser sanity check: Open a site you normally cannot reach without a tunnel. If it loads, at least part of your stack is functioning.
  • Egress IP check: Visit a service such as https://ip.sb or https://whatismyip.com and confirm the reported address matches your proxy provider, not your home ISP.
  • Live connections: In the Connections tab, trigger traffic from an app and confirm you see entries classified with the policy names you expect.

If the browser passes but CLI tools fail, you are probably still on system-proxy mode without environment variables, or TUN is off— revisit the previous sections instead of immediately blaming the node list.

Common issues and fixes

Issue 1: Proxy on, but sites still do not load

Work through this sequence before you reinstall:

  • Confirm the profile card in Profiles is selected and shows a successful last update.
  • Open Proxies, run latency tests, and make sure at least one node returns sensible milliseconds instead of timeouts.
  • Verify the System Proxy toggle is actually enabled if you are not using TUN.
  • Check that the mode is Rule or Global, not Direct.
  • Look at Windows Firewall outbound rules for Clash Verge Rev; a blocked executable looks exactly like a dead upstream.

Issue 2: Speed is poor or video buffers constantly

Throughput is dominated by the remote node and your ISP path to it, not by the GUI wrapper. Run batch latency tests, pick a closer region if available, and confirm you have not exhausted provider bandwidth quotas—some plans throttle instead of hard-disconnecting when the quota hits zero.

Issue 3: Launch Clash Verge Rev on Windows startup

In Settings, enable Launch on startup (wording may vary slightly by version). After that, Windows should bring the tray app up automatically and reapply your last proxy settings without a manual click.

Issue 4: Stay on a current build

CVR can notify you when a newer release exists; you can also open the About section and trigger an update check. If you prefer a manual path, download the latest package from our download page and install over the existing copy.

Want a Clash client with a steadier release cadence?

Community forks move fast when volunteers have time, but that flexibility has trade-offs you might feel in production use:

  • Unpredictable maintenance windows: Critical fixes ship when contributors are available, not on a corporate SLA.
  • Windows churn: Semi-annual Windows updates occasionally break assumptions in networking stacks; you may wait for a patched build.
  • Fragmented documentation: Answers may be scattered across issue trackers, chat groups, and third-party blogs, which raises the learning curve.
  • Slower UI polish: Smaller teams deprioritize nice-to-have interface work compared with security or protocol updates.

If you would rather standardize on a client that tracks Mihomo closely, ships for multiple desktop and mobile platforms, and bundles sensible defaults for subscriptions, rules, and optional TUN, the Clash build we distribute is aimed at exactly that workflow. Compared with piecing together bleeding-edge releases on your own, a maintained installer path usually means fewer surprises when you simply need stable connectivity during work or travel.

When you are ready to compare installers side by side, download Clash for free from our official download page and see whether the experience matches what you need day to day.

Download Clash from this site