Clash Verge Rev Subscription Setup: A Step-by-Step Guide

Before You Start: Client, Subscription URL, and Permissions

Clash Verge Rev separates the user interface from the proxy core that handles profiles, DNS, rules, and traffic forwarding. After installation, the application can open normally while still having no usable proxy configuration. The first practical task is therefore to import a subscription profile, update it successfully, and confirm that the profile contains available proxy nodes.

This guide assumes that Clash Verge Rev is already installed on Windows or macOS and that a provider has issued a subscription URL. The URL is usually a long https:// address containing an account token. It is not the same as a single server address, and it should not be pasted into public chats, screenshots, issue reports, or configuration files shared online.

Use a current Clash Verge Rev build. A maintained build with the mihomo core is preferable because modern subscriptions may include protocols, rule providers, or DNS fields that older cores cannot parse.
Prepare the complete subscription URL. Copy the entire address from the provider dashboard. Do not remove query parameters or line breaks that appear to be part of the URL.
Check the provider's usage limits. A subscription may have an expiration date, traffic quota, device limit, or update frequency restriction. A successful import does not mean the account has unlimited access.
Allow the required permissions. System proxy changes may require administrator approval on Windows, while macOS may request permission to install a privileged helper or modify network settings.

Treat the Subscription URL as a Password

Anyone who obtains the URL may be able to download your profile and consume the associated traffic quota. If the address has been exposed, revoke or regenerate it through the provider's account panel, then remove the old profile from Clash Verge Rev and import the replacement.

Import a Subscription Profile Step by Step

Open Clash Verge Rev and locate the profile or subscription area in the left navigation. The exact labels can differ slightly between releases, but the workflow is the same: add a remote profile, paste the URL, save it, and wait for the application to download and parse the YAML configuration.

Copy the complete subscription URL from your provider's dashboard. If the provider offers a copy button, use it instead of selecting the address manually.
Open the profile management page in Clash Verge Rev and choose the option for adding a remote subscription or importing from a URL.
Paste the URL into the subscription field. Give the profile a recognizable name such as Home subscription or Work nodes; avoid names that reveal your account token.
Save or confirm the entry. Clash Verge Rev should request the remote resource and display a download or parsing status.
After the profile appears in the list, click it to make it the active profile. The proxy page cannot use nodes from an inactive profile.
Open the proxies or connections page and verify that proxy groups and individual nodes are visible. If the page is empty, the profile may not have loaded correctly or the provider may have returned an incompatible format.

A subscription generally contains more than a list of servers. It may include proxy groups, rule providers, DNS settings, fake-IP exclusions, and a final routing rule. The application usually stores a downloaded copy locally, while the subscription URL remains available for later updates. Editing a downloaded profile manually can be useful for advanced users, but local changes may be overwritten when the remote profile is refreshed.

What you see	Likely meaning	First action
The profile is listed but has no proxies	The response was empty, invalid, or not a Clash-compatible configuration	Check the URL and ask the provider which client format to use
The profile shows a download error	The URL is expired, blocked, mistyped, or unreachable	Open the URL in a browser and check its expiration or access status
Proxies appear but groups are missing	The provider's group definitions were not parsed or the core is too old	Update Clash Verge Rev and inspect the generated configuration
The profile loads and groups are visible	The import stage is complete	Update the profile, select a node, then enable a traffic mode

Update the Profile and Understand What Changes

Importing a subscription is not a one-time operation. Providers commonly change node addresses, certificates, ports, proxy groups, and rule-provider URLs. Clash Verge Rev therefore provides an update action for each remote profile. Use it whenever the provider publishes a new configuration or when several nodes stop working at once.

To update, open the profile list, find the imported subscription, and click its refresh or update control. Wait for the request to finish before switching to another profile. A successful update normally preserves the profile name while replacing the downloaded configuration with the newest response. If the provider has changed the subscription format, the update may also add or remove proxy groups.

Update Frequency and Provider Limits

Some providers attach an update interval to the subscription URL. Repeatedly clicking update within a short period may trigger a rate limit or temporarily disable the address. Do not use frequent manual updates as a way to test whether a node is working. Profile updates download configuration data; they do not continuously measure every node.

If the client supports scheduled updates, choose a moderate interval that follows the provider's recommendation. A daily update is often sufficient for a normal subscription. After an update, check whether the active profile has changed. Some providers rename groups or reorder nodes, so a previously selected node may no longer be available.

Remote Profiles Versus Local Overrides

A remote profile is the provider-managed source. A local override is a separate layer used to adjust selected settings, such as adding a personal rule, changing a group name, or excluding a private network from TUN capture. Keeping these layers separate is safer than directly rewriting the downloaded file.

Do not casually replace the entire provider configuration with a small hand-written file unless you understand the required fields. Removing the proxy groups, DNS block, or final MATCH rule can make traffic appear connected while requests are actually sent through an unexpected path. For a first setup, use the provider profile as supplied and make only one change at a time.

A Profile Update Is Not a Node Test

Updating downloads configuration; it does not prove that every node is reachable. If the profile updates successfully but one node fails, test another node or use the group's latency or URL-test function when available.

Choose a Proxy Node and Test the Connection

After the profile is active, open the proxies page. You may see individual nodes together with groups such as Proxy, Auto, Fallback, or a provider-specific name. A group is not necessarily a server. It is a policy that decides which member node will be used, either through manual selection, latency testing, fallback behavior, or load balancing.

Select the main proxy group used by the profile's rules. The group may be named Proxy, Global, or something similar.
Choose a specific node if you want predictable behavior. Start with a nearby region and a node that reports a reasonable latency.
Alternatively, choose an automatic group such as url-test if the configuration provides one. This group measures a test URL and selects according to its configured tolerance and interval.
Open the connection or log page and generate a small test request. Confirm that the request is matched by the expected rule and sent to the selected group.
Test more than one destination. A node can reach one service while failing another because of routing, remote restrictions, congestion, or DNS behavior.

Latency is only one measurement. A low ping or fast HTTP test does not guarantee high download speed, stable long-lived connections, or access to every destination. A practical comparison should consider connection success, response time, sustained throughput, packet loss, and stability over several minutes.

Selection method	How it behaves	Best use
Manual node	You select one server and keep it until changing it	Stable testing and predictable troubleshooting
URL-test group	Measures a configured URL and prefers a responsive member	Routine use when several nodes are available
Fallback group	Uses an ordered list and moves on when a member fails the health check	Basic resilience when the provider configures suitable checks
Load-balance group	Distributes requests according to the group's strategy	Advanced usage where session behavior is understood

Select the Right Mode: Rule, Global, or Direct

Clash Verge Rev usually exposes three familiar modes. The mode determines how the configuration's proxy groups and rules are applied; it does not create a proxy connection by itself.

Rule mode checks each request against the rule list. Domestic or trusted destinations may use DIRECT, while other traffic is sent to a proxy group. This is the normal choice for everyday use when the subscription includes a complete rule set.
Global mode sends matching traffic through the selected global proxy group instead of following the usual direct-versus-proxy split. It is useful for diagnosing rule problems or testing whether a destination works through a particular node, but it can add latency to traffic that would normally be direct.
Direct mode bypasses the proxy for supported traffic. Use it as a troubleshooting control or when no proxy is needed. If every mode behaves the same, the problem may be unrelated to routing, such as a blocked URL, DNS failure, or local firewall issue.

For a first setup, choose rule mode, select the main proxy group, and leave advanced rule editing alone. Rules are evaluated in order. A broad rule placed above a specific rule can capture traffic earlier than expected, while a final MATCH rule determines what happens to everything not matched above it.

Global Mode Can Hide a Rule Problem

If a site works only in global mode, do not assume the node is broken. The profile's rules may be missing the destination, may be ordered incorrectly, or may send it to DIRECT. Switch back to rule mode and inspect the connection log to see the matched rule and selected outbound.

Turn On System Proxy and Decide Whether to Use TUN

System proxy mode writes HTTP and SOCKS proxy settings that many desktop applications understand. Enable it from the main control area after selecting the profile, node, and traffic mode. Windows or macOS may show a permission prompt; approve it only for the installed Clash Verge Rev application.

System proxy mode is not the same as full-device capture. Browsers and ordinary HTTP clients usually follow the operating system's proxy settings, but some applications ignore them, use their own proxy configuration, or connect through protocols that are not covered by those settings. DNS requests may also follow a separate path. If an application must be handled even when it ignores the system proxy, TUN mode may be appropriate.

What TUN Mode Adds

TUN creates a virtual network interface and allows the mihomo core to capture a broader range of IP traffic. Depending on the configuration, it can install routes, detect the active network interface, and redirect DNS through the Clash DNS module. This is useful for applications without HTTP proxy support, but it requires more permissions and can interfere with other VPN, firewall, virtualization, or corporate network software.

Do not enable several VPN-style traffic capture tools at the same time. If TUN is enabled, disable other VPN clients, transparent proxy services, or network accelerators during testing. On Windows, check whether another application has installed conflicting routes. On macOS, review the network extension or VPN permission prompt and remove stale profiles only when you know which application created them.

Setting	Coverage	Typical first-use choice
System proxy only	Applications that honor HTTP or SOCKS system settings	Start here for browsers and basic desktop testing
TUN mode	Broader IP traffic, including many apps that ignore system proxy	Enable after system proxy works and only when broader capture is needed
Both enabled	Depends on the client's routing and DNS handling	Use the client's recommended combination, avoiding duplicate VPN tools

Verify the Setup and Fix Common Failures

A complete setup should be checked in layers rather than judged by whether one page opens. First confirm that the profile is active, then confirm that a node is selected, then confirm that the traffic mode and system proxy state are correct. Finally, inspect the connection log to identify the rule and outbound used for a real request.

Confirm the imported profile shows a recent successful update and contains proxy groups.
Confirm the main group has a selected node rather than an empty or unavailable choice.
Set rule mode and enable system proxy. If using TUN, wait for its status to become active before testing.
Open the connection log and visit a test destination. Check the matched rule, DNS result, outbound group, and final node.
Test both a destination expected to use DIRECT and one expected to use the proxy. This helps reveal an incorrect rule order.

Typical Symptoms and Causes

No traffic appears in the log: the application may not honor the system proxy, the system proxy switch may be off, or TUN may not have started. Test with a browser that uses system settings before investigating the profile.
The profile cannot update: verify that the URL is complete, not expired, and not limited to another client format. A browser opening an error page does not mean Clash can parse the response.
Nodes exist but every connection fails: test another node, check the provider's status, and inspect whether the local network blocks the transport. Avoid changing DNS, rules, and TUN simultaneously because that removes useful evidence.
Only some websites fail: inspect the matched rule and DNS mode. A domain may be sent direct when it should use the proxy, or fake-IP and domain sniffing settings may need to match the provider's configuration.
Internet stops after enabling TUN: turn TUN off and restore system proxy mode first. Then check for another VPN, conflicting routes, DNS hijacking settings, or a permission failure before trying TUN again.

Change One Variable at a Time

When troubleshooting, record the active profile, mode, node, system proxy state, and TUN state. Change only one of them, repeat the same test, and compare the log. This is much faster than replacing the whole configuration after every failed request.

Safe Maintenance After the First Setup

Once Clash Verge Rev is working, keep the routine simple. Update the subscription according to the provider's interval, update the client and mihomo core through trusted distribution channels, and remove profiles that are expired or no longer needed. Do not keep multiple copies of the same subscription URL in notes, cloud documents, or shell history.

Before changing advanced DNS, rule, or TUN options, export or otherwise preserve the settings you can recreate. A provider update may overwrite downloaded content, while a local override may continue applying an old rule after the remote profile changes. Review the active profile after every major update, especially if the provider has changed group names or added a new DNS section.

The reliable beginner workflow is therefore: import the subscription, update it once, activate the profile, select a node, use rule mode, enable system proxy, and verify requests in the log. Add TUN only when an application requires broader capture. With that order, each failure has a clear place to investigate, and the subscription remains manageable as nodes and provider rules change.