Clash Verge Rev: How To Add Subscriptions And Switch Nodes

What “add a subscription” means in Clash Verge Rev

If you searched for Clash Verge Rev subscription setup, how to add a Clash subscription, or how to switch proxy nodes, you are probably at the point where the application is installed but has no usable profile. Clash Verge Rev does not provide proxy servers by itself. It is a client that reads a compatible configuration, connects to the servers described by that configuration, and applies routing rules to your traffic.

For most users, the fastest starting point is a subscription URL supplied by a provider or generated by infrastructure they control. That URL may return a YAML profile, a provider-specific configuration, or a converted Mihomo-compatible profile. Once imported, the profile normally contains proxy nodes, proxy groups, rules, DNS settings, and other runtime options. The client then turns that information into a selectable working profile.

This guide follows the complete everyday workflow: copy a subscription link safely, import it into Clash Verge Rev, refresh it when nodes change, choose a node or proxy group, select an operating mode, and verify that the traffic is using the expected route. The names of buttons can vary slightly between releases, but the underlying workflow remains consistent across current Clash Verge Rev builds in 2026.

A subscription link is also a credential. Anyone who obtains it may be able to retrieve your configuration or consume your provider quota. Treat it like a password: do not post it in screenshots, public issue trackers, chat groups, or browser history shared with other people. If the link is exposed, revoke or regenerate it through the provider rather than assuming that deleting the local profile is enough.

Prepare the subscription before importing it

Before opening the client, confirm that you have the right type of link and that the source is trustworthy. A normal web page URL, a single-node share link, and a subscription URL are not interchangeable. A subscription usually returns a complete list of nodes and groups, while a single-node link may only describe one server. Your provider should identify which format is intended for Clash, Clash Meta, Mihomo, or Clash Verge Rev.

Check these details first:

• Client compatibility: choose a profile format that supports Mihomo or Clash Meta when the provider offers several choices. Legacy Clash syntax may omit newer features used by current clients.
• Expiration and traffic limits: verify that the account is active and has remaining data. A successful import does not prove that the subscription still has usable service.
• Access method: copy the full URL, including every query parameter. Trimming the final characters can turn a valid subscription into an empty or unauthorized response.
• Privacy: do not replace a private subscription with a link copied from an unknown forum unless you understand who operates it and what traffic policy applies.
• Update interval: note whether the provider expects manual updates, daily refreshes, or a particular user-agent. This matters when a profile appears to import successfully but never receives new nodes.

On Windows, you can usually copy the URL from the provider dashboard with a dedicated copy button. If the link is displayed in a long text field, click inside the field and use the platform copy shortcut rather than selecting only the visible portion. On macOS and Linux, the same principle applies: make sure the clipboard contains the complete HTTPS address and not an explanatory label placed next to it.

Do not paste the subscription into the browser address bar merely to test it unless you understand the exposure risk. Browsers may save the address in history, sync it to another device, or display the returned configuration in a way that can later be captured by extensions or screenshots. Import it directly through the client whenever possible.

Add a subscription profile in Clash Verge Rev

Open Clash Verge Rev and look for the Profiles or Profile section in the left navigation. This is separate from the Proxies section: Profiles hold configuration documents, while Proxies is where you select groups and nodes after a profile has loaded.

In the Profiles view, locate the input field for a remote profile or subscription URL. Depending on the build, it may appear beside an add button, under a “New” control, or inside a menu with options such as Import, Download, or Remote Profile. Paste the complete subscription URL, give it a recognizable name if the interface asks for one, and confirm the import.

1. Open Profiles in the sidebar.
2. Select the control for adding a remote or subscription profile.
3. Paste the complete subscription URL into the URL field.
4. Optionally assign a short name such as the provider name and plan region.
5. Confirm the download and wait for the profile to finish parsing.
6. Click the imported profile to make it the active configuration.

The first download can take longer than expected if the provider is busy or the returned configuration is large. Avoid clicking the import button repeatedly; duplicate requests can create several profiles with identical names and make later troubleshooting confusing. Wait for a success message, an updated timestamp, or a visible profile entry before trying again.

After the profile appears, check whether it is marked as active. An imported profile that is merely stored locally may not control the running core. Clash Verge Rev generally indicates the active profile with a highlight, check mark, or status label. If the client offers both “select” and “update,” select the profile first, then allow the core to reload it.

If the import fails, read the error instead of immediately changing proxy settings. A timeout can indicate that the subscription endpoint is unreachable, while a parse error suggests that the response is not valid for the selected core. An authorization or HTTP 403 error usually points to an expired link, an account restriction, or a provider-side access policy. Test the link only through a trusted method and ask the provider for a Clash Meta or Mihomo format when the returned document is incompatible.

Refresh the profile and keep nodes current

Subscription data changes over time. Providers may remove overloaded servers, rotate addresses, add new regions, or change proxy group definitions. Refreshing the profile downloads the latest version; it does not necessarily change which node is currently selected. This distinction is useful because you can update the node list without assuming that the client has silently switched your route.

Return to Profiles, find the imported subscription, and use its refresh, update, or download-again action. Wait until the timestamp changes and watch for a completed status. If the provider supplies usage information in response headers, Clash Verge Rev may display traffic or expiration details after the refresh, although not every provider exposes those fields.

Use a consistent refresh routine:

• Refresh before diagnosing a node that has been failing for several hours.
• Refresh after your provider announces maintenance or server replacement.
• Refresh after importing the profile on a second computer if the two devices show different node lists.
• Do not refresh every few seconds; repeated downloads can trigger rate limits or consume provider resources.
• Keep a backup of important local overrides before replacing a profile.

A remote profile can be overwritten during an update if you edited its downloaded YAML directly. For durable changes, use the client’s override or merge mechanisms when available. Local edits inside a remote file are often temporary because the next refresh may replace the entire document. Separate your personal adjustments—such as a preferred DNS mode or an additional rule—from the provider-managed subscription whenever the interface supports that separation.

If a refresh succeeds but the old nodes remain visible, check whether you are looking at a different profile or a cached provider response. Confirm the profile name, update time, and active status. You can also deactivate and reactivate the profile, but avoid deleting it until you have confirmed that the subscription URL is still available.

Choose a node or proxy group

Once a profile is active, open the Proxies section. You may see a tree of proxy groups rather than one flat list. Common groups include a general selection group, an automatic latency group, a regional group, and a fallback group. The group name is not itself a server; it is a policy container that decides which member handles traffic.

To switch manually, open the main proxy group and click the node you want to use. A check mark or highlight normally confirms the selection. If the profile contains nested groups, selecting a group may require a second choice inside that group. For example, the top-level “Proxy” group may point to “Auto Select,” and “Auto Select” may calculate a result from several regional nodes.

Latency tests are useful for narrowing the list, but they are not a complete quality measurement. A node can respond quickly to a small HTTP probe and still perform poorly under long downloads, video playback, or many concurrent connections. Compare stability, packet loss, and real application behavior. If a node repeatedly disconnects, switch to another member rather than repeatedly restarting the entire client.

When you need a specific location, do not rely only on the country flag or the node label. Labels are supplied by the profile publisher and can be outdated. Verify the apparent exit region through a service you trust, and remember that some websites use their own location databases that may disagree. For ordinary browsing, a stable nearby node is often more useful than a distant node with a more attractive label.

Select the right operating mode

Clash Verge Rev normally offers several operating modes, commonly including Rule, Global, and Direct. The exact names can vary, but the concepts are consistent. Mode selection controls how the client decides whether traffic goes through a proxy, follows a rule, or bypasses the proxy.

• Rule mode: applies the rules in the active profile. This is usually the best everyday choice because local services can remain direct while selected domains use a proxy group.
• Global mode: sends proxy-aware traffic through one selected proxy group. Use it as a diagnostic tool or when you deliberately want a broad proxy path, but expect local websites and regional services to behave differently.
• Direct mode: bypasses proxy routing. It is useful for testing your normal connection, but it will not solve a service that requires the proxy path.

For most browsing scenarios, start with Rule mode and make sure the system proxy switch is enabled if you want ordinary desktop applications that respect the operating system proxy to use Clash Verge Rev. These are separate controls: selecting a node does not automatically mean that every application is connected, and enabling the system proxy does not help an application that ignores system proxy settings.

Some applications use their own proxy fields, while command-line tools may require environment variables such as HTTP_PROXY and HTTPS_PROXY. Other programs need the client’s TUN capability because they do not respect HTTP proxy settings at all. TUN mode can provide broader interception, but it may require administrator permission and can interact with other VPN software, endpoint security, DNS filters, or corporate network policies.

Change one control at a time. First select the active profile, then choose the mode, then enable the system proxy if appropriate, and finally test the target application. Changing the node, mode, DNS behavior, and TUN status simultaneously makes it difficult to know which change solved or caused the problem.

Verify the route and troubleshoot common failures

After selecting a node, open the client’s Connections or Logs view and generate a fresh request from the application you are testing. Look for the destination hostname, the selected rule, the chosen proxy group, and the final node. This is more reliable than assuming that a green status icon proves every application is routed correctly.

A useful verification sequence is:

1. Confirm that the subscription profile is active and recently updated.
2. Confirm that the intended node or group has a visible selection marker.
3. Confirm that the selected operating mode is Rule or Global rather than Direct.
4. Confirm that the system proxy switch is enabled for applications that depend on it.
5. Open a new browser tab or restart the test application to create fresh connections.
6. Inspect Connections and check whether the destination uses the expected rule and proxy group.
7. Compare the result with another node if the first route is slow or inconsistent.

If the profile is empty, the provider may have returned an invalid response, an expired account page, or a format that the selected core cannot parse. If nodes appear but all connections fail, test a different node and inspect the logs for DNS, TLS, timeout, or authentication clues. If the browser works but a desktop application does not, that application may ignore system proxy settings. If only one domain fails, inspect its rule match before concluding that the whole subscription is broken.

A common mistake is selecting a node inside a group that is not actually used by the active rules. For example, you may choose a fast server in a regional group while the rule set sends the target domain to a different “Proxy” group. Trace the complete path shown in the Connections panel: destination, matched rule, group, and final node. If the profile uses nested groups, make the selection at the group referenced by the matching rule.

When troubleshooting, temporarily switching to Global mode can help distinguish a rule problem from a node problem. If the target works in Global mode but fails in Rule mode, review the matching rule, rule order, domain list, and the group assigned to that rule. If it fails in both modes, compare another node, test DNS behavior, and check whether the service itself is unavailable. Return to Rule mode after testing rather than leaving a broad route enabled without understanding its effect.

Do not publish full logs or configuration files without redacting subscription URLs, passwords, private IP addresses, identifiers, and provider tokens. A short error message and a sanitized destination hostname are normally enough to begin troubleshooting.

A practical daily workflow for stable browsing

Once the initial setup works, daily operation should be simple. Keep one clearly named profile active, refresh it according to the provider’s schedule, and use Rule mode unless a particular task requires a broader route. Choose a stable automatic group for general browsing and a manual regional node only when a service genuinely needs a specific exit location.

When performance drops, avoid repeatedly clicking every node at random. First check whether the issue affects one website or all applications. Then inspect Connections, compare the current node with one alternative, and refresh the profile if the provider has announced changes. This approach preserves useful evidence and prevents temporary failures from becoming a confusing pile of configuration changes.

It is also worth keeping a small record of what works: the profile name, the preferred group, whether your browser relies on the system proxy, and whether any application requires TUN or its own proxy settings. That record makes reinstallations and device migrations much faster. Never store the subscription token in an unsecured shared document; record only the provider account location or a redacted label.

Clash Verge Rev is more transparent than many one-click VPN clients because it lets you see profiles, groups, rules, connections, and logs as separate layers. That visibility may feel more complex during the first setup, but it gives you a way to identify whether the problem is the subscription, the selected node, the operating mode, the system proxy, or the destination service.

Compared with simple VPN apps that often hide node selection, provide limited diagnostics, or force every application through one tunnel, Clash Verge Rev lets you refresh provider data, choose a specific group, keep local traffic direct, and verify real connections in the logs. If you want that balance of practical control and observable routing for your subscription workflow, the next step is to choose the client build for your platform.

Download Clash for free and browse freely →