Clash Verge Rev: How To Add Subscriptions And Switch Nodes

What You Need Before Starting Clash Verge Rev

Clash Verge Rev makes subscription management much easier than editing a large YAML file by hand, but the interface still depends on a few pieces of information being correct. Before opening the client, obtain a valid subscription URL from a provider you trust. This is usually an HTTPS address containing an account token. It may look like an ordinary web link, but it can grant access to your complete proxy profile, so do not publish it in screenshots, issue trackers, browser history shared with other people, or public chat rooms.

This guide focuses on the everyday workflow: importing a subscription, refreshing it when the provider changes nodes, selecting a server, and choosing a proxy mode for applications and websites. You do not need to understand every field in a Clash configuration to complete these tasks. However, you should know the difference between a profile, a proxy group, a node, and a mode. Confusing these levels is the main reason a user thinks that an imported subscription is empty or that a selected server has no effect.

A profile is the configuration document loaded by the core. A subscription normally supplies or generates that profile. A node is one outbound server, while a proxy group is a menu that may contain individual nodes, automatic testing groups, or nested selectors. The mode controls how traffic is assigned: Rule mode follows the rules in the profile, Global mode sends most traffic through the proxy selection you choose, and Direct mode bypasses the proxy for normal connections.

Close other VPN clients and older Clash-based applications while testing. Two clients can compete for the same system proxy settings, local ports, DNS listeners, or TUN adapter. If you are moving from another application, first record which port and mode it used, then disable it completely before launching Clash Verge Rev. A clean baseline makes later symptoms much easier to interpret.

Import a Subscription into Profiles

Launch Clash Verge Rev and open the Profiles page from the left navigation. Depending on the release and bundled core, the page may show a URL input field near the top, an import button, or a small plus icon. The visual labels can change between builds, but the operation is the same: paste the provider’s subscription address into the profile import field and confirm the import.

Paste the complete URL rather than the shortened text displayed by a messaging application. If the address contains characters such as &, =, or a long token, make sure the clipboard did not remove the final characters. Do not add quotation marks around the URL. An address that opens a login page in a browser is not necessarily a usable Clash subscription; the endpoint must return a configuration format supported by the core, not an HTML account portal.

After confirmation, Clash Verge Rev sends a request through the current network path and attempts to parse the returned document. A successful import normally creates a new profile card with a name, update address, last update time, and a node count or related metadata. Click the newly imported profile to activate it. Importing a profile and activating it are separate actions: the profile can exist in the list while the core continues using an older active configuration.

If the application offers an option to rename the profile, choose a short name that identifies the provider or purpose without exposing your account token. Names such as Personal Main, Travel Backup, or Work Lab are easier to recognize than a long URL. Avoid using the same name for several subscriptions because it makes it difficult to confirm which document is currently active.

A profile can import successfully yet show no usable proxies when the provider response is expired, incomplete, encrypted in an unsupported format, or designed for a different client. Check the provider’s dashboard for an active plan and a current link. If the endpoint requires a special user agent or a conversion service, use only the provider’s documented option. Random online converters can expose the subscription token and may silently modify rules, DNS settings, or security-sensitive fields.

Refresh Profiles and Understand Update Results

Subscription links are not static lists. Providers may replace an unavailable server, change a hostname, update encryption parameters, or alter the number of available nodes. On the Profiles page, find the refresh or update control attached to the active profile and click it. Wait for the request to finish before switching to the Proxies page. A refresh usually downloads a new configuration; it does not always change the currently selected node immediately.

Use the result message and timestamp as evidence. A new timestamp with the same node count can still represent a successful update because the provider may have changed addresses or rules without changing the total number of entries. Conversely, a profile that appears unchanged after several days may indicate a cached response, an expired token, or an update request that never completed. If available, open the profile details or update log rather than relying only on a brief notification.

Automatic updates are useful when your provider changes infrastructure frequently, but select a reasonable interval instead of refreshing every few minutes. Excessive requests can consume a provider’s quota, trigger rate limits, or make the client look unreliable when the real problem is an endpoint refusing repeated downloads. If the interface supports scheduled updates, daily or several-times-per-day intervals are usually easier to manage than constant polling.

Protect the subscription as you would protect a password. If the URL is exposed, revoke or regenerate it from the provider dashboard. Deleting a local profile does not necessarily invalidate the remote token. Also remember that updating a profile may replace local modifications, depending on how the client and provider build the configuration. Keep custom changes in a documented override or separate local configuration only when you understand the merge behavior.

Open Proxies and Select the Right Node

Once a profile is active, open the Proxies page. You will often see several groups rather than one flat list. A group may be named PROXY, Proxy, 🚀 节点选择, Auto, or something specific to the provider. The first visible group is not automatically the group that controls every application. The rules in the profile decide which group receives traffic, so start by identifying the group used for general proxy traffic.

Click the group to expand its members. Individual entries may show a country label, region, protocol, or provider-generated name. Select a node by clicking its row or radio-style control. Clash Verge Rev should mark the choice as active, but the change affects only traffic routed through that group. A browser domain assigned to another group will continue using its own selection, and a DIRECT rule will bypass the selected proxy entirely.

Some groups provide latency testing. A test result measures a specific URL from the local client and should be treated as a signal, not a universal ranking. A node with the lowest result may have poor throughput, an unstable route to your target service, or a restrictive policy. Conversely, a node with slightly higher latency can perform better for video, downloads, or long-lived connections. Test several candidates and evaluate the actual websites or applications you use.

Keep a stable manual selection while diagnosing problems. Automatic groups such as url-test or fallback can change the active member as conditions change, making it difficult to tell whether a failure came from the node, the rule, or the group’s decision. After the basic path works, automation can be useful for resilience, but first establish one known-good node and record its behavior.

If you cannot find a suitable node, do not immediately assume that the subscription import failed. Look for collapsed groups, filters, search boxes, and nested selectors. A provider may separate nodes into regional groups and expose only the regional selector at the top level. Also inspect whether the profile contains a node count but the current group contains only DIRECT or REJECT members; that points to a profile rule or group-definition issue rather than a missing subscription.

Choose Rule, Global, or Direct Mode

The mode control is usually available on the dashboard or in the settings area. Rule mode is the practical default for most users. It lets the profile classify destinations and send them to different policy groups. Domestic services, private network addresses, advertising domains, and selected applications may go direct, while other destinations use the group you selected on the Proxies page.

Global mode is useful as a short diagnostic tool because it reduces the number of routing decisions. If a website works in Global mode but fails in Rule mode, inspect the rule chain and the group assigned to that website. Do not treat Global mode as proof that every node or every application is healthy. It can also send local services, banking pages, printers, software update endpoints, or company resources through an unsuitable path.

Direct mode disables proxy routing for ordinary traffic. It is useful when testing the underlying network, completing a captive portal, or confirming that the issue is related to Clash rather than the connection itself. If Direct mode works but Rule mode does not, compare DNS behavior, rule matches, and policy-group selections. Switching modes repeatedly without recording the result often creates the impression that the client is random when the observations were made under different routing conditions.

After changing the mode, wait a few seconds and reload the test website in a private or clean browser window. Existing connections can remain established under the old path, so a page that was already open may not reflect the new mode. For applications with persistent sessions, close and reopen the application or terminate its active connection from the application’s own controls.

1. Activate the intended profile on the Profiles page.
2. Choose a known-good member in the main proxy group.
3. Set Rule mode for normal day-to-day routing.
4. Open a new browser tab and test a permitted destination.
5. Compare Global and Direct mode only when diagnosing a specific mismatch.

Verify the Connection Without Guessing

A green status indicator means that the core is running; it does not prove that every application is using the proxy. First confirm that the selected profile is active, the proxy group shows the expected node, and the mode has not silently returned to Direct after a restart. Then inspect the Logs page while loading one test website. A useful log entry should show the destination, the matched rule or rule provider, the chosen policy group, and whether the connection succeeded.

If the browser works but a desktop application does not, check which proxy mechanism that application supports. System proxy settings commonly affect browsers and many WinINet-based applications, but command-line tools, games, sandboxed software, and applications with their own networking stack may ignore them. TUN mode can capture more traffic, but it introduces permissions, virtual adapter, routing, and DNS considerations. Enable it only after ordinary system proxy behavior is understood and only when your network policy permits it.

When a subscription refresh fails, separate the endpoint problem from the client problem. Copy the URL carefully, confirm that the account is active, check the computer clock, and test whether the provider endpoint is reachable on the current network. A certificate warning, captive portal, DNS failure, HTTP status error, or authentication response each suggests a different fix. Avoid replacing the URL with an untrusted mirror simply because it returns a faster error page.

When a node connects but a page still fails, test another node and examine the log for the exact destination. Some pages use multiple hostnames for login, static assets, APIs, and streaming. A rule that sends the main hostname to one group while sending an API hostname to DIRECT can produce a half-loaded page. DNS mode can also matter: a resolved address may not match the rule behavior you expected, particularly when fake-IP or redirection settings are involved.

Practical habit: Change one variable at a time. Keep the profile fixed, test two nodes, then compare Rule, Global, and Direct mode. Record the result with the destination and timestamp before changing DNS, TUN, or custom rules.

Before closing the client, confirm that the profile update time is current and that your preferred node is still selected. If you need the setup after reboot, enable the client’s startup option only after the manual workflow is stable. Also check whether the operating system restored another VPN or proxy application at login. A reliable Clash Verge Rev setup is not just a working subscription; it is a predictable chain from profile to group, node, mode, and application.

Compared with browser extensions, which usually cover only one browser and can leave desktop applications untouched, or older Clash clients that hide profile updates behind inconsistent menus, Clash Verge Rev gives you a clearer profile list, visible policy groups, refresh controls, and direct mode switching in one workspace. Those advantages make subscription setup and node selection easier to verify instead of relying on guesswork. If you want a maintained desktop workflow with these controls in one place, download Clash V.CORE and continue with the interface that best matches your operating system.