Why Node Switching Matters After Setup

If you already finished installing Clash Verge Rev and imported a subscription, the next practical skill is learning how to switch nodes in Clash Verge Rev and run a quick Clash Verge Rev speed test to find a stable server. Installation gets you connected; node selection keeps you fast. A profile may list dozens of servers across Hong Kong, Japan, Singapore, the United States, and more — picking the wrong one leads to high latency, buffering streams, or timeouts even when your subscription is valid.

Clash Verge Rev uses the same Mihomo (Clash Meta) core as other modern Clash clients, so proxy groups, URL tests, and manual selection behave the way experienced Clash users expect. The difference is the Tauri-based UI: the Proxies page centralizes every group from your YAML profile, and the built-in latency test gives you one-click feedback without opening a browser speed site.

This guide assumes Clash Verge Rev is installed on Windows 11 or macOS, a profile is active, and System Proxy or TUN mode is enabled. If you have not reached that stage yet, start with our Clash Verge Rev Windows 11 installation tutorial first, then return here for day-to-day node management.

Before You Switch Nodes

Confirm these conditions so node changes actually affect your traffic:

• Active profile: On the Profiles page, one subscription must be selected (highlighted). An empty or expired profile shows nodes but cannot route traffic.
• Proxy enabled: System Proxy or TUN mode must be ON on the Home dashboard. Switching nodes while the proxy is off only updates the config — nothing reaches the internet through Clash until you toggle it back on.
• Rule mode (recommended): Leave routing on Rule for normal use. Global mode sends everything through the selected group; Direct bypasses the proxy entirely.
• Fresh node list: If your provider rotated servers overnight, click the refresh button on Profiles before testing latency. Stale nodes often show timeout in tests.

Understand the Proxies Page Layout

Open Clash Verge Rev and click Proxies in the left sidebar. This page mirrors the proxy-groups section of your subscription YAML. What you see depends on how your provider structured the profile, but most configs include a few common patterns.

Nodes vs. Proxy Groups

A node (or proxy) is a single server endpoint — for example HK-01 or US-LA-03. A proxy group is a container that holds one or more nodes and defines how Clash picks among them:

• select: You choose the active node manually. This is the group most users interact with daily.
• url-test: Clash periodically tests latency and can auto-switch to the fastest node (often labeled Auto or Auto Select).
• fallback: Tries nodes in order until one responds.
• load-balance: Distributes connections across members — less common in consumer subscriptions.

Your rules file decides which group handles each type of traffic. A typical setup routes foreign domains through a group named Proxy, 🚀 Node Select, or SELECT, while domestic traffic goes DIRECT. When you switch nodes, you usually change the selection inside the group your rules reference — not a random nested list that nothing points to.

Windows and macOS: Same Workflow

Clash Verge Rev shares one interface across platforms. On Windows 11 you may also reach quick controls from the system tray icon; on macOS, use the menu bar icon for mode toggles. Node selection itself always happens on the Proxies page — click a group header to expand it, then click a node name to activate it. The active node shows a highlight, check mark, or colored indicator depending on your theme.

Manually Switch Nodes in Clash Verge Rev

Manual selection gives you full control when you need a specific country, a provider-recommended streaming node, or a server that passed your latency test.

1. Open Proxies and locate the main selection group. Common names include Proxy, Node Select, ♻️ Auto Select (if it is a select-type group), or your provider brand name.
2. Click the group row to expand the node list if it is collapsed.
3. Click the node you want. The UI updates immediately and Mihomo routes new connections through that server.
4. Keep the previous window open and load a website. If pages fail, try another node or refresh the profile — the server may be down independent of your client settings.

Some profiles nest groups inside groups. Example: rules send traffic to Proxy, and Proxy contains only HK, JP, and US sub-groups, each with individual servers. In that case, either select a sub-group (if it is select-type) or drill into the sub-group and pick a concrete node. If you change a nested list that your rules never use, your public IP will not change — always follow the group named in your provider documentation.

Switch Policy Groups (Not Just Nodes)

Many subscriptions ship multiple policy groups for different tasks. Switching groups is different from switching nodes: you change which bucket of servers your traffic uses, then optionally pick a node inside that bucket.

Typical Group Types in Provider Profiles

• General / Node Select: Default group for everyday browsing and most blocked sites.
• Streaming: Optimized for Netflix, Disney+, YouTube Premium, or regional platforms. Providers often refresh these separately from general nodes.
• Gaming: Lower jitter routes, sometimes limited to specific regions.
• Region shortcuts: Groups like 🇭🇰 Hong Kong, 🇯🇵 Japan, 🇺🇸 US that filter nodes by location.
• Auto / URL-Test: Lets the core pick the lowest-latency member automatically on a timer.

How to Change the Active Group

Clash Verge Rev does not replace your YAML rules — it exposes the groups your config defines. To route streaming traffic through a dedicated pool, your rules must already point those domains to the streaming group. From the user side:

1. Identify which group your task needs (read your provider's FAQ if unsure).
2. On the Proxies page, open that group and select a node, or select an Auto sub-group inside it.
3. If your provider offers a master select group (for example 🎯 Strategy) that lists other groups as members, change the master selection to Streaming or Gaming instead of digging into individual servers.
4. Verify on the Connections or Logs page that new sessions hit the expected outbound name when you open the target site.

When a site still uses the wrong exit after a group change, the domain may be matched by a different rule (for example DIRECT or a fixed region rule). That is a ruleset issue, not a Proxies UI bug — check whether your provider updated rules or consult their support chart for which group handles each service.

Run a Clash Verge Rev Speed Test (Latency Test)

The built-in test is the fastest way to compare servers without leaking traffic to third-party speed-test websites. Here is how to use it on Windows and macOS.

Test One Node

1. On the Proxies page, hover over a node row or look for the lightning bolt icon beside the name.
2. Click the icon to start a single-node latency test. After one or two seconds, a number appears — typically 123 ms or timeout.
3. Lower is better for interactive use. Under 100 ms to your target region is excellent for browsing; gaming may need consistent sub-80 ms depending on the game server location.

Batch Test an Entire Group

1. Expand the group you want to evaluate (usually your main select group or a regional folder).
2. Click the group-level test button — often a lightning icon on the group header or a Test All action in the toolbar at the top of the Proxies page.
3. Wait while Clash Verge Rev tests each member sequentially or in parallel (behavior depends on core settings and group size). Numbers populate next to every node.
4. Sort mentally or by displayed order: pick the lowest stable result, not a one-off spike. If a node shows timeout, skip it — the server or path is unreachable from your network.

What URL Does the Test Use?

Mihomo sends a HEAD or GET request to a test URL defined in your profile — often http://www.gstatic.com/generate_204 or a provider-custom endpoint. Clash Verge Rev surfaces the result as delay only. You can sometimes change the test URL in Settings → Clash settings (field names vary by version) or inside the YAML under each url-test group. Using a closer test URL yields more relevant numbers for your actual browsing, but only edit this if your provider allows custom configs.

Latency Test vs. Real-World Speed

A Clash Verge Rev speed test in the UI is a latency test. It does not measure 4K streaming headroom or torrent throughput. Use it to eliminate slow or dead nodes quickly. After picking a winner, optionally run a browser download or your provider's bandwidth page if you need confirmation for heavy use cases.

Using Auto and URL-Test Groups

Not everyone wants to click nodes daily. Many profiles include an Auto, Auto Select, or ⚡️ URL-Test group that re-tests members every few minutes and keeps the fastest node selected.

1. On Proxies, open your master select group and choose the Auto / URL-Test entry instead of a fixed server.
2. Trigger a manual batch test once so the group has fresh measurements before you rely on it.
3. Let the core rotate automatically. When latency rises (for example after peak hours), the group may switch members without your input.

Auto groups trade control for convenience. Streaming platforms that block rotating IPs may fail when Auto jumps between countries — switch to a manual streaming node for those sessions. Gaming sessions benefit from manual picks too, because unexpected mid-game node changes can drop packets.

Find the Lowest-Latency Node: Practical Tips

Numbers on screen are only the starting point. Use these habits to stay on a fast route:

• Match region to content: Low ping to Japan does not help if you need a US streaming catalog. Filter by the region group first, then test inside it.
• Ignore outliers: One node at 40 ms among many at 200 ms may be a measurement glitch. Test twice before committing.
• Watch for timeouts: Repeated timeouts mean the node is offline or blocked on your ISP — not something Settings can fix.
• Refresh after provider maintenance: Providers reboot clusters regularly. A node that won yesterday's test may fail today until you refresh the subscription.
• Combine with Logs: The Logs page shows DNS errors, TLS failures, and which outbound handled each request. If latency looks fine but sites break, logs reveal protocol or SNI issues unrelated to ping.
• Tray quick switch (Windows): Right-click the tray icon — some builds expose recent groups or mode toggles for faster changes without opening the main window.

Troubleshooting Node and Test Issues

Selected Node Does Not Change My IP

• Confirm you edited the group your rules actually use (see the Connections page while loading a foreign site).
• Disable Auto parent groups that override manual child selections.
• Switch to Global mode briefly, change the node, retest IP, then return to Rule mode — this isolates whether rules were pinning a different outbound.
• Clear browser DNS cache or use a private window — old IP lookup tabs lie about changes.

Every Node Shows Timeout in Tests

• Check System Proxy / TUN is ON and the profile is not expired.
• Refresh the profile; your subscription token may have rotated.
• Test on another network (phone hotspot) to rule out ISP blocking of provider endpoints.
• Inspect Logs for core startup errors — a corrupted profile parse can leave zero working outbounds.

Latency Swings Wildly Between Tests

Wi-Fi interference, VPN double hops, or background downloads skew results. Use Ethernet when benchmarking, pause large downloads, and run three tests on the same node before deciding. If only url-test groups fluctuate, increase the interval in YAML or stick to manual select for stability.

macOS-Specific Notes

On macOS, Clash Verge Rev needs network extension or system proxy permissions granted at first launch. If tests always timeout while Windows on the same account works, open System Settings → Privacy & Security and confirm the app retains network access. TUN mode on Apple Silicon may prompt for an additional helper install — approve it or rely on System Proxy for browser-only testing.

Frequently Asked Questions

How do I switch nodes in Clash Verge Rev?

Open Proxies, expand your main select group, and click the server name you want. The highlight moves to that node and new connections use it immediately while the proxy toggle is on. On Windows and macOS the steps are identical.

Where is the Clash Verge Rev speed test button?

Look for the lightning bolt icon next to each node or on the group header for batch testing. Some versions place a Test All control at the top of the Proxies page. If icons are hidden, widen the window — narrow layouts collapse action buttons into a context menu (right-click the node row).

Does the built-in test measure download speed?

No. It reports HTTP latency in milliseconds. That is ideal for comparing nodes inside Clash, not for measuring your ISP's maximum bandwidth. Use a dedicated speed site after you pick a node if you need throughput numbers.

Should I use Auto or pick a node manually?

Use Auto / URL-Test for general browsing when your provider maintains healthy pools. Switch manually for streaming unlocks, gaming, or any task that requires a fixed country. Auto groups may change outbounds while you watch a geo-restricted title and trigger mid-session blocks.

Why are node names in Chinese or emoji?

Providers label servers for their audience. Names like 🇭🇰 HK-01 or JP-Tokyo are cosmetic. Focus on the region flag and latency number unless your provider publishes a legend mapping names to hardware locations.

Can I switch nodes from the command line?

Clash Verge Rev is GUI-first. Power users can hit the Mihomo external controller API if enabled in Settings, but most readers should stay on the Proxies page. API switching requires knowing group and node exact names from the YAML — easy to mistype.

Summary

Switching nodes in Clash Verge Rev comes down to three skills: know which proxy group your rules use, run the built-in latency test to eliminate slow servers, and pick a manual node or Auto group that matches your task. On Windows 11 and macOS the Proxies page works the same way — expand a group, test, click, verify on Connections or a quick IP check. Refresh subscriptions after provider maintenance, and prefer stable manual routes when streaming or gaming.

Generic VPN apps hide all of this behind a single country picker and never expose per-app routing or group-level policy. Legacy Clash for Windows tutorials stop at "pick a node" without explaining url-test groups, nested selectors, or why your IP stuck on the wrong outbound. Clash Verge Rev keeps the full Clash model — transparent groups, one-click batch latency tests, and rule-aware switching — in a client that still receives updates in 2026. The Clash ecosystem underneath supports the same YAML workflows across platforms; if you want that flexibility without fighting abandoned software, the download page lists current builds for every major system in one place.

Download Clash free for all platforms →