Clash Verge Rev: How To Add Subscriptions And Switch Nodes

What this Clash Verge Rev workflow actually solves

If you have installed Clash Verge Rev but the dashboard still shows no usable traffic, the missing piece is usually not the application itself. Clash Verge Rev is a client and routing interface; it does not automatically include proxy servers. You need to add a compatible subscription, let the client download its profile, refresh that profile when the provider changes it, and then select a proxy node or proxy group for real connections.

Searches such as how to add a subscription to Clash Verge Rev, Clash Verge Rev nodes not showing, and how to switch servers in Clash Verge Rev describe the same beginner workflow. This guide follows it from beginning to end: prepare a subscription URL, import it safely, confirm that the profile contains proxies, test latency without confusing speed with reliability, choose a node, select a proxy mode, and troubleshoot the common cases where the interface looks correct but applications remain on a direct connection.

The names may differ slightly between Windows, macOS, and Linux builds, and the interface can change between releases. Look for the same concepts rather than relying on one exact button position: Profiles or Subscriptions for remote configuration, Proxies for node selection, Connections for live traffic, and Settings for system proxy, mixed port, DNS, and TUN options.

Prepare a compatible subscription before importing it

A subscription is normally a private URL that returns a Clash-compatible configuration or a provider-generated profile. It may be presented as a long HTTPS link, a button labelled “Clash,” or a universal subscription link that lets the client convert the provider’s format. It is not the same thing as a single server address, and it is not an activation key that belongs in the operating system network settings.

Before opening Clash Verge Rev, check the following details with the service that issued the link:

• Format support: confirm that the link returns Clash, Mihomo, or another format supported by your installed build. A V2Ray-only or mobile-specific link may need conversion before Verge Rev can use it.
• Expiry and quota: a valid-looking URL can still return an expired account, an exhausted data quota, or an empty profile. Check the provider dashboard if the import succeeds but no proxies appear.
• Device and connection limits: some plans limit simultaneous connections. Repeated testing on several devices may consume a connection slot or trigger a provider policy.
• Privacy: treat the URL like a password. Anyone who obtains a tokenized subscription link may be able to download your profile or use your allocated traffic.
• Protocol expectations: note whether the provider supplies TCP, TLS, WebSocket, HTTP/2, QUIC, or other transports. Older clients may not parse every modern option correctly.

Do not paste a live subscription URL into a public issue, chat room, screenshot, or browser translation service. If you need support, redact the host, path, token, and query string. A useful diagnostic screenshot shows the error message and the general profile name, not the credential-bearing URL.

It is also worth removing competing network tools temporarily. A second Clash client, a commercial VPN, a corporate endpoint agent, or a browser-only proxy extension can make testing confusing. Two applications may attempt to control the system proxy at the same time, while a TUN adapter from one tool can intercept traffic before you know which policy handled it.

Add a subscription in Clash Verge Rev

Launch Clash Verge Rev and open the area labelled Profiles, Subscriptions, or a similar profile-management entry. The first screen may be empty, or it may contain a local example profile. A local example does not provide working nodes; it only demonstrates configuration structure.

1. Copy the subscription URL from your provider’s account page. Use the copy button where available instead of manually selecting a long URL, because one missing character can produce an apparently mysterious parsing failure.
2. Paste the URL into the profile input field. Give the profile a recognizable name such as “Home subscription” or “Work test,” but avoid putting the private token in the visible name.
3. Choose Add, Import, or Download. Verge Rev should contact the subscription host and retrieve the profile. The first download may take several seconds if the profile contains many nodes.
4. Select the new profile. An imported profile may exist in the list without being active. Click it or use its activation control so that the Proxies page reads rules and proxy groups from that profile.
5. Wait for parsing to finish. Do not immediately switch between pages while a download or conversion task is still running. A profile that is only partially written can appear in the list but fail when activated.

After activation, open the profile’s details or preview if the client provides one. You should see familiar Clash sections such as proxies, proxy-groups, and rules. You do not need to edit them just to use the subscription. In fact, direct edits to a remotely managed profile are often overwritten during the next update.

If the import reports a successful download but the profile has no nodes, inspect the response rather than repeatedly clicking Add. The provider may have returned an HTML login page, a rate-limit notice, a JSON error, or a profile that requires a special user-agent. A browser opening the URL successfully does not prove that the response is a valid Clash configuration; browsers may follow redirects or display an error page that Verge Rev cannot interpret.

Refresh the profile and understand update behavior

Subscriptions change over time. Providers may remove an overloaded relay, change a certificate, add a new region, or update a proxy group. Clash Verge Rev usually lets you refresh a profile manually from the profile list. Use the refresh or update icon next to the imported entry, then wait until the download and parsing status completes.

A manual refresh is useful when a provider tells you that nodes were replaced or when the current list suddenly becomes empty. It is also a good first step after changing your plan. However, refreshing cannot repair an expired account or a blocked subscription host. If the updated profile contains the same old nodes and the provider confirms that changes were published, check whether the client is serving a cached response or whether the subscription URL itself has changed.

Keep the following distinction in mind:

• Profile update: downloads a newer configuration and may change nodes, groups, rules, and DNS settings.
• Node latency test: measures selected proxies against a test URL. It does not download a new profile.
• Client update: installs a newer Clash Verge Rev application. It may improve compatibility, but it does not automatically renew your subscription.
• Connection retry: starts a request again using the current active configuration. It does not prove that the profile is current.

If your provider offers an update interval, choose a moderate schedule rather than refreshing every few minutes. Excessive requests can trigger rate limits, waste battery on a laptop, and make it harder to tell whether a failure is caused by the subscription host or by a selected node. For a stable setup, update when the client starts or once per day, then refresh manually when there is a concrete reason.

Test node latency without mistaking it for real speed

Open the Proxies page after activating the profile. You may see individual nodes, regional groups, and automatic groups such as “Auto,” “URL-Test,” or “Fallback.” A latency test often displays a number in milliseconds. Lower is generally better for responsiveness, but the number is only a snapshot of one request to one test endpoint.

A node showing 80 ms can still perform badly during a long video stream if it has limited bandwidth or unstable packet delivery. Conversely, a node showing 180 ms may be perfectly usable for browsing, messaging, or an API request that values reliability more than instant response. Treat the test as a filter, not a final verdict.

When comparing nodes, consider these signals together:

Run a small test set rather than selecting the lowest number from dozens of entries without checking anything else. Compare one or two nearby regions, one stable-looking backup, and the automatic group if your provider supplies it. If every node times out, test the subscription host and your ordinary internet connection first. A universal timeout usually points to a wider issue than one overloaded server.

Switch nodes and choose the correct proxy group

Most Clash profiles do not ask you to select an individual node for every website. Instead, rules send traffic to a proxy group, and that group points to the node currently in use. On the Proxies page, identify the group used by the active rules. It may be called “Proxy,” “Global,” “🚀 Proxy,” “Main,” or a provider-specific name.

Click the group, then choose a node from the available list. The selected entry should become visually highlighted. If you select a server inside a nested group, you may need to return to the parent group and confirm that the parent is now using that child group. This is why changing a node sometimes appears to have no effect: you changed a group that your current rules do not reference.

Common group types behave differently:

• Select group: you manually choose one node. This gives you predictable control and is useful for troubleshooting.
• URL-Test group: the client tests candidates against a URL and prefers a responsive result. It may switch later as test results change.
• Fallback group: the client uses an ordered list and moves on when the current entry fails according to its health check.
• Load-balance group: traffic may be distributed across multiple entries, so repeated requests can leave through different nodes.

For your first test, use a manual selection group. Pick one node, wait a few seconds, and generate a fresh request. Once you know the profile works, an automatic group can reduce maintenance. Keep at least one manually tested backup in mind, because an automatic group can choose a technically responsive node that is poor for a particular service or region.

After switching, open Connections and look at a new request. The connection row should show the destination, the rule that matched it, and the chain or group used. Existing connections may keep their previous route, so close and reopen the affected application or create a new browser request before judging the change.

Select Rule, Global, or Direct mode deliberately

Node selection alone is not enough. Clash Verge Rev also needs a mode that determines how traffic is classified. The usual choices are Rule, Global, and Direct, although wording and placement vary by build.

• Rule mode: applies the profile’s rule list. This is the normal choice when you want some destinations proxied and others to remain direct.
• Global mode: sends traffic through the selected global proxy group, subject to the client’s supported behavior. It is useful as a short diagnostic because it removes many rule-matching variables.
• Direct mode: bypasses proxy routing. Use it to confirm that the ordinary connection works or to temporarily suspend proxy traffic.

Start with Rule mode if the subscription contains a reputable rule set. In Connections, inspect whether a test domain is marked with a proxy rule or DIRECT. If you expect a destination to use a node but it shows DIRECT, switching nodes will not fix the problem; you need to review the matching rule, the active profile, or the selected proxy group.

Global mode is valuable for diagnosis, not always as a permanent setting. It may send local services, banking sites, printers, intranet resources, and latency-sensitive applications through a remote route unnecessarily. If Global mode works while Rule mode fails, compare the relevant domain rule and the group it references. Do not assume that Global mode proves every application is configured correctly, especially when the application ignores the system proxy.

Direct mode can help separate two questions: whether your local internet connection is healthy and whether a remote node is usable. Switch to Direct briefly, test an ordinary site, then restore the intended mode. Avoid leaving Direct enabled simply because a browser tab works; that result only proves the browser can reach that particular destination without Clash routing.

Make applications use the selected route

Desktop applications can learn about Clash in different ways. Many browsers and standard HTTP clients follow the operating system’s system proxy, while some command-line tools, games, virtual machines, containers, and background services do not. If the Clash dashboard shows a healthy node but Connections remains empty when you open an application, the application may not be using Clash at all.

For ordinary desktop testing, enable the system proxy option in Clash Verge Rev and confirm that the operating system proxy points to the client’s local HTTP or mixed port. The exact port can be found in Settings. Do not guess a port from an old tutorial, because profiles and builds may use different defaults.

For software that ignores system proxy settings, consider TUN mode if your operating system, permissions, and organization policy allow it. TUN creates a virtual network interface that can capture more traffic than an HTTP proxy, but it also introduces more moving parts: administrator approval, DNS behavior, route conflicts, firewall interaction, and possible overlap with another VPN adapter. Enable it only after the basic subscription and node workflow works.

Terminal tools may need explicit environment variables, for example:

HTTPS_PROXY=http://127.0.0.1:7890
HTTP_PROXY=http://127.0.0.1:7890

Use the actual mixed or HTTP port shown by your client, and follow your organization’s security policy. A terminal test that succeeds only after setting these variables demonstrates environment inheritance, not a defect in Clash Verge Rev. Conversely, a browser request that appears in Connections does not prove that a separate desktop application has adopted the same route.

Troubleshoot imports, empty lists, and failed switches

The profile imports but no nodes are visible

First confirm that the profile is active rather than merely present in the list. Then refresh it and inspect the provider response if the client offers a preview. Check expiration, remaining quota, format compatibility, and whether the URL requires a special conversion service. If the provider recently changed its format, update Clash Verge Rev before trying to edit the downloaded YAML manually.

Every node shows timeout

Test a normal website without the proxy and check whether the subscription host itself opens. If the local connection is fine but every node times out, the provider may be offline, the profile may contain stale endpoints, or your network may block the transport used by the nodes. Try one alternative profile only if it comes from a trusted source, and compare the timestamps of the profile update and the node test. Do not infer that a new subscription is valid merely because it downloaded successfully.

Switching a node produces no visible change

Verify that you changed the group referenced by the current rule. Generate a new request after the switch, because long-lived connections may remain attached to the old route. Then inspect Connections for the actual outbound chain. If the row says DIRECT, the issue is mode or rule selection; if it shows the same old node, the parent group may still point elsewhere or the application may be bypassing Clash.

The node works but browsing is slow

Compare several nodes at different times, not only their latency values. Check whether DNS resolution is delayed, whether the selected route is overloaded, and whether the destination itself is rate-limiting your requests. A nearby node is not automatically better if its transit path is congested. Keep Rule mode lean, avoid routing local services unnecessarily, and use a stable manual node while investigating automatic group behavior.

A repeatable workflow for daily use

Once the setup works, keep the routine simple. Refresh the profile only when scheduled or needed, select a manually verified backup before changing important settings, and use Connections to verify the first request after every node switch. When a service fails, record the active profile, mode, group, node, and matching rule before making changes. That small record prevents random toggling from hiding the original cause.

Separate provider problems from client problems. If the profile cannot download on two networks, contact the provider or inspect the account. If the profile downloads but only one application fails, inspect that application’s proxy behavior. If all applications fail after enabling TUN, review permissions, DNS, firewall rules, and conflicting adapters. This layered approach is faster than reinstalling Clash Verge Rev every time a single node becomes unavailable.

Compared with simpler single-switch VPN apps, which can hide the difference between a dead server, an ignored system proxy, and a misclassified domain, Clash Verge Rev gives you profile refresh controls, selectable groups, rule visibility, node testing, and live connection evidence. Those controls add a few concepts at the beginning, but they make subscription changes and server switching much easier to verify; if you want a client that lets you follow the complete workflow rather than guess what the switch changed, you can download Clash and begin with the same profile-and-node process described here.

Download Clash for free and browse freely →