Clash Verge Rev: How To Add And Manage Subscriptions

What Clash Verge Rev Needs Before You Start

Clash Verge Rev is a graphical desktop client built around a Clash-compatible core, commonly mihomo. The client provides the interface for importing profiles, selecting proxy groups, changing modes, and enabling system integration; the core does the actual work of parsing the YAML configuration, connecting to nodes, resolving DNS requests, applying rules, and forwarding traffic. Installing the application alone does not give it a usable proxy configuration. The first practical task after installation is therefore adding a profile, usually from a subscription URL supplied by your service provider.

A subscription URL is not the same thing as a single server address. It normally points to a provider-managed document that contains multiple proxy nodes, proxy-group definitions, rules, DNS preferences, and sometimes client-specific parameters. When the provider changes a node, removes an expired server, or adds a new location, the subscription can generate an updated configuration. Clash Verge Rev downloads that configuration and stores a local copy for use by the core.

Before adding anything, confirm that the link is a Clash or mihomo-compatible subscription link. Some providers offer separate links for different clients, such as sing-box, Surge, Shadowrocket, or a generic Base64 list. A generic link may not contain the YAML structure expected by Clash Verge Rev. If the provider supplies several formats, choose the one explicitly labelled Clash, Clash Meta, mihomo, or YAML.

Add a Subscription Profile in Clash Verge Rev

Open Clash Verge Rev and go to its profile management area. Depending on the release and operating system, the navigation may be labelled Profiles, 订阅, or use a profile-shaped icon in the sidebar. The wording can vary slightly between builds, but the workflow is the same: enter a remote URL, give the profile a recognizable name, download the configuration, and select the resulting profile for use.

1. Open the profiles page

   Launch the application, allow it a moment to start the bundled core, and open the profile management page. If the page is empty, that is normal for a fresh installation. You may see an input field for a remote profile URL, an import button, or a menu that provides options such as Import from URL and Import local file.

2. Paste the subscription URL

   Copy the complete URL from your provider dashboard and paste it into the remote-profile field. Avoid adding spaces before or after the address. If the link contains query parameters, keep the entire string intact; cutting off everything after a question mark or ampersand can make the provider return an incomplete or invalid configuration.

3. Name the profile clearly

   If Clash Verge Rev asks for a name, use something that identifies both the provider and its purpose, such as Work subscription, Personal monthly plan, or Provider-A primary. Clear names become important once you add a backup subscription or a manually edited local profile. A descriptive name also reduces the risk of updating or deleting the wrong item.

4. Download and activate the profile

   Choose the import, download, or save action. Clash Verge Rev will request the remote document and usually display a new profile entry after parsing succeeds. Click that entry or use its selection control to make it the active configuration. Importing a profile and activating a profile are separate actions in many clients: the first stores the file, while the second tells the core which file to load.

After activation, open the main dashboard or proxy page and check whether proxy groups and node names are visible. If the profile contains groups such as Proxy, Auto, Fallback, or regional groups, the configuration has probably loaded correctly. If the application shows only an empty page, a parser error, or no selectable groups, return to the profile details and inspect the download result before changing unrelated network settings.

Understand Profile Downloads and Updates

A subscription profile has two different states to keep in mind: the remote source and the local snapshot. The URL is the source address; the YAML file downloaded from that address is the snapshot currently being used. Clash Verge Rev does not need to contact the provider for every connection, so the client can continue using the last successful snapshot when the provider is temporarily unreachable. That convenience also means an old snapshot can remain active longer than expected if updates fail silently.

Use the profile page's refresh, update, or download-again action when you want the latest node list and rules. Some builds show a circular-arrow icon beside each profile, while others place update commands in a three-dot menu. After an update, check the timestamp or status message and confirm that the profile remains selected. A successful download does not always mean that the newly downloaded configuration was automatically activated.

Action	What it changes	When to use it
Import from URL	Creates a local profile from a remote subscription	First-time setup or adding another provider
Update or refresh	Downloads a newer version of the same profile	Nodes disappear, rules change, or the provider publishes updates
Switch active profile	Changes which configuration the core loads	Testing a backup profile or separating work and personal settings
Import local file	Loads an existing YAML configuration without a remote URL	Offline testing or using a manually maintained configuration

If updates repeatedly fail, test the URL in a normal browser only when you understand the privacy implications and the provider permits it. A browser may download a file, show an access-denied response, or request authentication. Check for common causes such as an expired subscription, exhausted traffic quota, a mistyped URL, an account-bound link, certificate interception by a restrictive network, or a provider requiring a particular user-agent. Do not assume that a profile update failure is caused by the selected proxy node: the update request may be made before the new profile is available, and the application may be using the direct network path.

Choose a Proxy Group and Test a Node

After the profile loads, open the proxy or dashboard view and identify the top-level group used by the rules. A configuration may contain several layers: a rule-selected group, a regional group, an automatic latency group, and individual nodes inside that group. Selecting a node in the wrong group may have no visible effect because traffic is still being sent through another parent group.

For a first test, choose a simple selector group if one is available. A selector usually lets you click a specific node manually. If the profile provides an automatic group, its behaviour depends on the group type and health-check settings. A url-test group can periodically measure a test URL and prefer a node with lower measured delay, while a fallback group generally uses the first available member according to its health status. The lowest latency number is not automatically the best choice: routing distance, congestion, bandwidth, packet loss, and the provider's remote server all affect actual browsing performance.

1. Start with a manual selection

   Pick one node from a nearby region or from the provider's recommended group. This gives you a stable baseline and makes later troubleshooting easier. Avoid changing several groups at once because you will not know which change affected the result.

2. Run a delay or health check

   Use the built-in test action if present. The displayed delay measures the response from Clash Verge Rev to a test endpoint, not the complete time needed to load every website. A node with a slightly higher delay may still perform better for large downloads or long-lived connections if it has less packet loss.

3. Check real browsing performance

   Open several ordinary websites and observe page loading, streaming stability, and whether images or scripts fail. Test more than one node and keep the same destination during comparison. This avoids confusing a temporary website issue with a proxy problem.

When a node appears available but websites still fail, inspect the active group hierarchy. The rule may send the destination to DIRECT, REJECT, or a different proxy group. The node itself can be healthy while the rule engine intentionally chooses another route. The dashboard's connection or traffic view is useful for confirming which rule and group handled a request.

Select the Proxy Mode for Daily Browsing

Clash Verge Rev commonly exposes modes such as Rule, Global, and Direct. These modes determine how the loaded configuration is applied, not which subscription is active. Changing the mode cannot repair an invalid profile or an unavailable node, but it can change whether a destination follows the configuration's rule set.

Mode	Traffic behaviour	Best use	Main limitation
Rule	Matches domains, IP ranges, processes, or other rules and sends traffic to the selected group	Normal daily browsing and mixed domestic/international traffic	Depends on the quality and freshness of the rule set
Global	Sends traffic handled by the client through one selected proxy group	Testing a node or temporarily forcing a consistent route	May proxy destinations that should normally go direct
Direct	Uses the normal network path instead of proxy forwarding for matched traffic	Comparing direct connectivity or troubleshooting the local network	Does not provide proxy access and may expose the usual network route

Rule mode is generally the practical default because it allows the configuration author to separate direct services from proxied services. Global mode is valuable as a diagnostic tool: if a website works in Global mode but fails in Rule mode, the likely cause is a rule, group selection, DNS decision, or direct-route problem rather than the node itself. Direct mode is useful for checking whether the underlying connection works without Clash, but remember to switch back after testing.

System proxy and mode selection are also separate settings. Enabling Rule mode does not automatically force every application to use Clash. The operating system's HTTP and SOCKS proxy settings must be enabled through the client for proxy-aware applications, while applications that ignore system proxy settings may require TUN mode if you need broader traffic interception. TUN mode can affect DNS and local routing, so it should be enabled only after the basic subscription, node, and system-proxy workflow is working.

Fix Common Subscription Setup Problems

The URL cannot be downloaded

Verify that the address is complete and still active. If the provider dashboard generates a link only after selecting a client format, regenerate it using the Clash or mihomo option. A response containing an HTML login page, an expired-message page, or a plain error text is not a valid Clash configuration. Also check whether your current network blocks the provider domain. If the provider gives you a temporary access link, its expiration time and usage quota may be separate from the subscription's billing period.

The profile downloads but will not parse

Parsing errors usually indicate that the downloaded content is not valid YAML or that the configuration uses fields unsupported by the bundled core. Confirm that the provider generated a mihomo-compatible profile rather than a configuration for another client. YAML is sensitive to indentation, but a remotely generated file should normally already be formatted correctly. If you manually edit it, use spaces instead of tabs and preserve the indentation beneath fields such as proxies, proxy-groups, and rules.

The profile loads with no usable nodes

Look at the node list and inspect whether the provider returned an empty configuration, expired nodes, or only groups with missing members. An empty result can be caused by quota exhaustion, an account restriction, a provider-side conversion error, or a subscription format mismatch. Downloading the same profile again will not fix a provider-side empty response, so check the account dashboard or contact the provider after confirming the URL is correct.

The node works but browsing fails

First check whether the system proxy is enabled and whether the browser has a separate proxy setting that overrides the operating-system setting. Then compare Rule mode with Global mode. If Global works and Rule does not, inspect the matched rule and proxy group. If both modes fail, check DNS errors, local firewall permissions, the node's protocol support, and whether the provider allows the destination. A successful latency test only proves that a test request received a response; it does not guarantee that every protocol or website will work.

Maintain a Safe and Reliable Profile

Once the basic setup works, keep the configuration simple enough to recover. Do not delete the last known-good profile immediately after importing a replacement. Store a local backup only when the configuration belongs to you or the provider permits it, and remember that a downloaded YAML file may contain node credentials and other sensitive connection data. If you use manual overrides, document what they change so that a future subscription refresh does not leave you wondering whether the problem came from the provider or from a local modification.

Use one profile name per subscription and avoid repeatedly adding the same URL. Duplicate entries can create confusion about which snapshot is current and which profile is active. If you maintain a work and personal setup, keep their profiles separate and check the active profile before starting a sensitive session. Update periodically according to the provider's normal schedule rather than refreshing continuously; frequent requests may consume account quota or trigger provider-side rate limits.

For routine browsing, a sensible sequence is: update the profile, confirm the timestamp, select a healthy node or automatic group, use Rule mode, enable the system proxy, and test a few destinations. When something breaks, reverse that sequence one variable at a time. This method distinguishes subscription problems, node problems, rule problems, DNS problems, and local application settings instead of treating every failure as a generic “Clash does not work” error.

Get the Clash Client and Setup Resources

After installing Clash Verge Rev, the essential workflow is straightforward: import a compatible subscription URL, activate the downloaded profile, update it when necessary, select a healthy proxy group, and use Rule mode for normal browsing. Start with the least complicated settings, then add TUN or custom DNS only when you have a specific need.

Open the download page Read the installation guide

Download Clash client