Clash Verge Rev Subscription Setup: How to Add a Profile

Understand subscriptions, profiles, and active configurations

In Clash Verge Rev, a subscription is a URL that lets the client retrieve a configuration from a provider. The profile created from that URL is the local entry you can refresh and select later. These terms are related, but they are not interchangeable: adding a subscription does not necessarily mean that the profile is already active, and selecting a profile does not automatically make every application use the proxy.

A profile typically contains or produces the settings that the Mihomo-compatible core needs, including proxy servers, proxy groups, rules, and DNS behavior. The client presents those settings through its interface, where you can choose a profile, inspect available groups, and manage connections. A provider may update the profile remotely, so refreshing it can replace nodes, adjust group names, or change rules without changing the subscription URL you originally saved.

This distinction helps explain several common surprises. A profile can appear in the list while its configuration has not loaded successfully. A profile can load correctly but leave traffic on DIRECT because its rules or selected group call for that behavior. Or the profile may be active while system proxy mode is disabled, so only applications configured to use Clash can send traffic through it. Treat profile import, profile activation, proxy selection, and system-wide routing as separate checks rather than one “connected” switch.

ℹ Keep the URL private: Many subscription links contain an account token. Anyone who obtains the full URL may be able to use or refresh the configuration. Do not post it in screenshots, issue reports, chat rooms, or public configuration files.

The instructions below focus on adding a subscription URL to the desktop application, updating the profile, and choosing it for use. Menu labels can vary slightly between Clash Verge Rev releases and operating systems. If your screen uses a different label, look for the equivalent Profiles or subscription-management area rather than assuming the configuration is missing. Do not paste private URLs into unfamiliar websites to “test” them; use the client and the provider’s own account page instead.

Prepare a valid subscription URL before importing

Obtain the subscription URL from the provider’s authenticated dashboard or another channel the provider explicitly identifies as official. A normal subscription address is generally an HTTPS URL, although the exact host and path are provider-specific. Copy the entire link, including its query string if one is present. A missing character at the end can make an otherwise valid address fail, and copying only the visible portion of a wrapped link can produce a profile that never updates.

Check that the subscription is still active and that the provider has not issued a replacement link. Some services separate account sign-in links from configuration subscriptions; a browser login address may open a web page but cannot be imported as a profile. If the provider supplies several formats or endpoints, choose the one intended for Clash, Mihomo, or compatible clients. Do not assume that a generic download button and a subscription endpoint are the same thing.

Before you import, decide how to identify the profile. A short name such as “Personal” or “Work test” is easier to recognize than a long URL, especially when you later add a second provider or a temporary configuration. Avoid putting account names, email addresses, or subscription tokens in the visible profile name if you may share screenshots. Profile names are local labels; changing the label does not change the provider or the contents of the subscription.

It is also worth recording the provider’s documented refresh interval and usage limits. Repeatedly refreshing a working subscription every few seconds is rarely useful and may trigger rate limits. If you are migrating from another client, keep the old profile until the new one has been tested. That gives you a comparison point and a recovery option if the new profile imports but contains different groups or rules.

⚠ Use authorized access: Follow the provider’s terms, local law, and any workplace or school network policy. A successful import only confirms that the client received configuration data; it does not grant permission to route traffic through a network where proxy use is prohibited.

Add a subscription URL in Clash Verge Rev

The import process is easiest to troubleshoot when you make one change at a time. First open Clash Verge Rev and confirm that the application has finished starting. If another Clash-compatible client is already running, close it temporarily during initial testing. Two clients can compete for system proxy settings or network interfaces, making it difficult to tell whether an import problem is actually a routing conflict.

Open the profile area. In the main window, locate the section labeled Profiles or its equivalent. This is where local configurations and subscription-based profiles are listed. If the list is empty, that is not by itself an error; it usually means no profile has been imported into this application yet.
Choose the subscription import action. Use the control for adding a remote profile, importing from a URL, or adding a subscription. Avoid choosing a local-file import option unless the provider gave you a configuration file to save on your device. A URL and a downloaded YAML file follow different import paths.
Paste the complete URL. Copy the subscription address from the provider’s account page and paste it into the URL field. Check the beginning and end of the value for accidental spaces, line breaks, or quotation marks. If the address is long, do not retype it from a screenshot; copy it directly from the trusted source.
Set a recognizable profile name. Use a concise label that describes the purpose rather than exposing account details. If the interface offers a separate display-name field, use it to distinguish this subscription from local test files or other providers.
Confirm the import and wait for completion. Clash Verge Rev must contact the subscription endpoint, download the response, and parse the returned configuration. A brief delay is normal. Do not repeatedly click the import control while the request is in progress, because duplicate entries can make the profile list harder to manage.
Verify that the new profile appears. Look for the label you assigned and check for an error indicator or an empty configuration preview. If the application reports success, that establishes that the profile was added; it does not yet prove that a proxy node is selected or that system traffic is routed through it.

If the application offers an option to update the profile after importing, use it once and wait for the completion status. Then open the profile’s details or configuration view if available. You are looking for evidence that the response contains usable proxy groups or other expected configuration data, not for a particular node count that must match another user’s screen. Providers can change server lists and group layouts at any time.

A successful import should leave a profile entry that you can select. Select it only after confirming that it is the profile you just added, especially if several entries have similar names. Once selected, the interface may expose proxy groups in a separate section. Choose a permitted group or node there if the configuration requires a manual choice. Do not edit provider-managed configuration fields merely to make the screen look like a tutorial image; an update may overwrite those edits.

Refresh the profile and switch configurations safely

A subscription profile is usually a saved reference to a remote configuration, not a frozen copy that updates itself continuously. To retrieve the provider’s latest data, return to the profile list and use that profile’s refresh or update control. Wait for the request to finish before switching profiles or closing the application. A successful refresh should update the profile’s data or show that the current version is already up to date; it should not normally require you to paste the subscription URL again.

After refreshing, confirm which profile is active. Many interfaces distinguish the selected profile from the profiles merely stored in the list. Select the intended entry, then inspect the proxy-group view. Depending on the configuration, the group may offer a selector, an automatic latency test, or a fallback policy. A selector reflects a manual choice; a test group may choose among members according to its configured behavior. If the group is empty or reports unavailable members, refreshing the profile alone may not resolve a provider-side outage or an invalid configuration.

When changing from one profile to another, allow the client a moment to apply the new configuration. Existing connections may remain open briefly, while new connections use the newly selected settings. If you rely on a particular application, test it after the change rather than judging the switch only by a “running” indicator. Also check the system proxy toggle if you expect ordinary desktop applications to use Clash Verge Rev. Some tools use their own proxy settings and will not follow the operating system’s proxy setting automatically.

Keep a distinction between updating the subscription and editing local preferences. The subscription refresh obtains the provider’s latest version; local preferences may include a display name, an update interval, or other client-side options. If the client supports profile merging or overrides, changes to those files can affect the result without changing the remote URL. Make a backup before experimenting, and keep a brief note of what you changed so that a later refresh does not turn troubleshooting into guesswork.

For routine use, refresh when the provider recommends it, when expected nodes or groups are missing, or when the provider announces a configuration change. If a refresh fails, avoid deleting the only copy of a working profile immediately. A temporary network problem may be all that occurred, and retaining the previous entry lets you compare the old data with the provider’s current status. Remove stale duplicates only after you have identified which profile is active and confirmed that the replacement works.

Troubleshoot failed imports and profiles that do not appear

Start with the exact error message and the stage at which it appears. “Unable to download” points toward access to the URL, DNS, TLS, authentication, or a provider outage. “Parse” or “format” errors more often indicate that the response was not a configuration in the format the client expected. A profile that imports but contains no useful groups suggests a different problem from a URL that cannot be reached at all. Separating these cases prevents unnecessary edits to a valid configuration.

Check the address: Confirm that you copied the complete subscription URL from the provider’s authenticated page, that it has not expired, and that it is intended for a Clash-compatible client. If the provider has rotated or revoked the link, request a new one through its official support channel.
Check basic connectivity: Temporarily test the import on a stable network you are authorized to use. Captive portals, restricted Wi-Fi, DNS filtering, and a second VPN can interfere with a request even when ordinary browsing appears to work. Do not disable security software indiscriminately; use its logs or approved network diagnostics to identify a specific block.
Check the response format: If a browser or provider tool shows that the URL returns a login page, an access-denied message, or an HTML error page, the client cannot parse it as a profile. A successful HTTP response is not necessarily a valid subscription response.
Check for duplicate profiles: Search the list for the name you assigned and for an older entry using the same provider. The import may have succeeded under a default name, or you may be looking at another profile with similar groups. Rename entries locally if needed so you can identify the correct one.
Check application and core status: If profiles repeatedly fail to load or the client reports a core error, restart Clash Verge Rev and review its logs before changing the subscription. A core startup failure and a subscription download failure are different issues, even if both result in no usable proxy groups.

If the subscription imports but traffic does not use the expected route, verify the active profile first, then inspect the selected proxy group, the relevant rule behavior, and the system proxy state. A profile refresh cannot correct a group that is deliberately set to DIRECT, and enabling system proxy mode cannot make a broken subscription endpoint download successfully. Test one application and one destination at a time, and note whether the connection reaches the local Clash listener before changing DNS or routing settings.

For a useful support report, include the Clash Verge Rev version, operating system, the exact stage that fails, and a redacted error message. Remove subscription tokens, account identifiers, private server addresses, and any configuration lines the provider treats as confidential. Avoid sharing a complete profile or debug log publicly without reviewing it; logs can reveal more than the visible error, including hostnames, local addresses, or authentication-related data.

Some clients make the first import look simpler by hiding most profile and group details, while manual YAML editing offers control but can make a basic subscription update unnecessarily fragile. Clash Verge Rev provides a practical middle ground: keep the provider URL in a manageable profile, refresh it when needed, and inspect the active group separately from system proxy behavior. If that separation makes subscription setup easier to understand, you can download Clash V.CORE and use its maintained client options to manage profiles with a clearer workflow.