Clash Verge Rev setup, with fixes for every step
Download, import a subscription, pick a node, enable the system proxy, choose the right mode, and know when you need TUN. Each step paired with the thing to check if it fails.
Written in the order you will do it, with the failure check attached to each step.
Applies to Windows and macOS; Linux is nearly identical.
Step 1: download
From the official Clash Verge Rev GitHub Releases page.
| System | File |
|---|---|
| Windows 64-bit | *_x64-setup.exe |
| Windows ARM | *_arm64-setup.exe |
| macOS Apple silicon | *_aarch64.dmg |
| macOS Intel | *_x64.dmg |
| Debian / Ubuntu | *.deb |
| Fedora / RHEL | *.rpm |
Not sure which Mac you have: Apple menu → About This Mac → the Chip line.
If macOS says the app is damaged, that is Gatekeeper, not a corrupted file:
sudo xattr -dr com.apple.quarantine /Applications/Clash\ Verge.appStep 2: import a subscription
- Left sidebar → Profiles
- Paste the subscription URL into the field at the top
- Import
- Wait for the fetch
Then the step people miss:
- Click the profile card so it becomes the active configuration. It will highlight.
Importing is not enabling.
If this step fails: sidebar → Logs, find the subscription fetch and read the status code. Then No nodes after importing.
Step 3: pick a node
- Sidebar → Proxies
- Groups at the top, nodes underneath
- Lightning icon tests the whole group
- Choose something with low latency
Discard timeouts, anything over 800 ms, and anything reporting 0 ms — that number is fake.
Latency alone is not enough to judge a node. The full method: How to actually test a free node.
Step 4: enable the system proxy
Settings → turn on System Proxy.
Browsers and most desktop applications will now route through the client.
Two more worth enabling:
- Start with system — so you do not have to remember
- Auto system proxy — takes over on launch
Step 5: confirm the mode is Rule
Top of the Proxies page: Rule / Global / Direct.
| Mode | Behaviour | When |
|---|---|---|
| Rule | Domestic direct, foreign proxied | Always, day to day |
| Global | Everything proxied | Temporarily, while debugging |
| Direct | Nothing proxied | Effectively off |
Global sends local traffic on a round trip abroad, which is inexplicably slow until you realise why.
Step 6: verify
Open any IP lookup page. It should show the node's region.
If it shows your own, work through the checklist below.
When you need TUN
Not by default. The system proxy already covers browsers and most applications.
Turn TUN on when you hit these:
- Steam downloads crawl
- Games will not reach their servers
curl,git,piptime out- Some desktop application refuses to sign in
Those programs do not read the system proxy setting and go straight out of the physical adapter. TUN creates a virtual adapter and captures everything regardless.
Before enabling it:
- Administrator rights required; the first run installs a service
- Security software may block the virtual adapter — the symptom is losing all connectivity the moment TUN is enabled
- Machines with VMware, VirtualBox or WSL occasionally get route conflicts
- Rules must be correct — TUN captures everything, so bad rules send local traffic abroad too
If TUN kills your connection entirely, in order:
- Disable your antivirus's network protection and retry, to identify the culprit
- Change the TUN implementation in settings (
system/gvisor/mixed) - Relaunch as administrator
- Device Manager → Network adapters → remove leftover TAP/TUN devices you do not recognise
- Reboot
Troubleshooting checklist
In order. Do not skip.
1. Is the profile selected? The card should be highlighted. Not selected means the config is not loaded.
2. Is the system proxy on? Settings page.
3. Is the mode Rule? Not Direct.
4. Are the nodes alive? Retest latency. All timing out means the subscription is dead — refresh it or replace it.
5. Read the log. Sidebar → Logs. Most people skip this and the answer is usually sitting in it.
6. Is your clock synced? Vmess nodes fail wholesale when the clock is off by a couple of minutes.
7. Try a different node. That one may simply have died.
8. Restart the client. Configuration changes need a reload.
Two deeper walkthroughs:
Settings worth adjusting
Subscription refresh interval
Per-profile, on the Profiles page.
- Paid subscription: 24 hours
- Free subscription: 4–6 hours — the list turns over fast
Pin a node for AI tools
Do not let ChatGPT or Claude ride an auto-selecting group; the rotating exit IP will sign you out.
Create a manual select group and route AI domains to it. Reasoning and rule syntax: Using ChatGPT over a free VPN.
Appearance
Settings has language options and follows the system light/dark theme.
Read next
- Free Clash nodes: get them and import them
- v2rayN setup
- No nodes after importing a subscription
- How to actually test a free node
Questions people keep asking
Is Clash Verge Rev the same as Clash Verge?
Rev is the community continuation after the original Clash Verge stopped being maintained, and it runs the Mihomo core. Use Rev; the original is no longer updated. Check the repository name when downloading.
Do I need TUN mode?
Not at first. The system proxy covers browsers and most desktop applications. Enable TUN when you find something that ignores it — games, Steam, command-line tools. TUN needs administrator rights and can conflict with security software.
Everything installed, but the browser still cannot reach anything.
Three usual causes. The subscription imported but was never selected as active. The system proxy toggle is off. Or the mode is set to Direct. Work through the checklist below in order.
Subscription refresh keeps failing.
Read the HTTP status code in the client log. 404 means the link is gone. A timeout usually means you currently have no route out at all — there is a way around that below. 403 often means the server wants a specific User-Agent.