Manage Multiple Subscriptions: v2rayN Subscription Groups and Server Filters

Keep multiple provider subscriptions organized in separate groups, and use filter rules to remove informational entries from your v2rayN server list.

At a glance

For v2rayN users with two or more subscription URLs. Create a group for each provider and record the unfiltered server list, then use remark-name regex rules to exclude announcements, data-usage notices, and expiration alerts. Update only the group you changed, verify that your frequently used servers remain, and learn how to restore the list by clearing the filter.

Subscription Groups and Filter Scope

In v2rayN, each subscription group corresponds to a subscription profile. Even if two providers both name a server “Tokyo 01,” its group identifies where it came from. A group name is an organizational label; it does not replace a server remark or determine which server is currently in use.

Subscription groupFetch contentParse entriesMatch remarksAdd to list

Create Groups by Provider and Record a Baseline

These steps use the Chinese menus in v2rayN 7.x. In the main window, open the “Subscription Group” menu. Manage groups under “Subscription Group Settings.” Update commands may be listed separately for updates with or without a proxy, so make sure you choose “Update Current Subscription” rather than “Update All Subscriptions.”

  1. Go to “Subscription Group” → “Subscription Group Settings” → “Add.” Enter a name that identifies the provider, such as “Provider A · Primary.” Paste Provider A’s subscription URL into the optional address field. Leave the filter field blank for now, then save.
  2. Create another group the same way, named “Provider B · Backup.” Give each group its own subscription URL. If one provider offers two separate plans, include the plan name in the alias rather than using only a region.
  3. Select Provider A’s group in the main window, then use the corresponding command in the “Subscription Group” menu to update the current subscription. Select Provider B’s group and repeat. If the first update fails, check the URL and download method before adding any regex rules.
  4. Clear the list search. For each group, record the total number of entries, the full remarks of two frequently used servers, and the exact spelling of informational entries. If an entry reads “Data remaining: 80 GB,” preserve the original text—including its colon—so you can write and verify the rule accurately.

Remark Regex: Exclude Informational Entries Only

Matching words at the start of a remark is more reliable than searching for a keyword anywhere in it. For example, “Hong Kong 03 · Traffic Optimized” is a server name, while “Data remaining: 80 GB” is an informational entry. Excluding every remark containing “traffic” would remove both.

Provider A: Chinese-Language Notices

Example remark
Remaining data: 80 GB (English translation)
Filter expression
^(?!\s*(?:\u5269\u4f59\u6d41\u91cf|\u5230\u671f\u65f6\u95f4|\u5957\u9910\u516c\u544a)\s*[:\uff1a]).+$
What the filter keeps
Remarks that begin with one of the specified terms followed by a colon are excluded.

Matches both full-width and standard colons, with optional spaces before the colon.

Provider B: Bracketed Labels

Example remark
[NOTICE] Maintenance
Filter expression
(?i)^(?!\s*\[(?:notice|expire)\]).+$
What the filter keeps
Exclude remarks that begin with one of the specified bracketed labels.

Case-insensitive for English letters; ordinary bracketed region labels are still kept.

Paste the expression into the filter field for the corresponding group exactly as shown—without quotation marks or slash delimiters. In the rule, ^ anchors the match to the start of the remark, and (?!…) means the text that follows must not match the condition in parentheses. Both examples keep only non-empty remarks; if your subscription contains blank remarks, do not use these expressions to determine whether those entries are valid servers.

The rules check only the remark text; they do not distinguish between VMess and VLESS entries. Region names in remarks are labels supplied by the provider. If the list contains both “Announcement:” and “Plan announcement:”, first check whether both prefixes appear on informational entries, then add conditions using the exact wording you find.

Update One Group and Verify the Results

Use the six example remarks below to check Provider A’s expression. The counts are calculated from the examples and do not indicate the provider’s server count or network speed. When updating your subscription, use your own baseline list instead.

6
Test remark
2
Excluded as informational
4
Kept as server name
Server remarkExpected resultWhy
Data remaining: 80 GBExcludeSpecified prefix followed by a full-width colon
Expiration date: 2026-12-31ExcludeSpecified prefix followed by a standard colon
Tokyo 01KeepDoes not start with an informational prefix
Tokyo 02KeepDoes not start with an informational prefix
Hong Kong 03 · Traffic OptimizedKeepKeyword appears in the middle of the remark
Hong Kong 04 · VLESSKeepProtocol label is not a filter condition
  1. Open Provider A’s group in “Subscription Group Settings,” enter its rule, and save. Return to the main window, select Provider A’s group, and update the current subscription only. Saving the settings does not reprocess the existing list.
  2. Check the update result, then compare the list against your baseline. Confirm that the informational entries you targeted are gone and that your frequently used servers are still there. A lower total count alone does not prove the filter is correct; the provider may have added or removed servers at the same time.
  3. Check whether the currently selected server is still in the list. If it was removed, select another server from the entries you kept, then test the connection in the apps you use. A server remaining in the list does not prove that it is reachable.
  4. After verifying Provider A’s results, configure the corresponding rule for Provider B. Keep a copy of the last verified expression for each group. If the provider changes its naming, update only the affected group so you can compare results and roll back easily.

Filter Problems and How to Recover

Why do I only see announcements after entering “announcement”?

The filter field keeps remarks that match the expression. Entering announcement by itself selects entries containing that word. Clear the filter and update the group again, then use a negative lookahead anchored to the start. For example, if remarks use the “Announcement:” prefix, ^(?!\s*Announcement\s*[::]).+$ keeps other non-empty remarks.

Why are data-usage notices still showing after I save?

First make sure the correct group is selected, then update its subscription and wait for the update to finish. If the entry is still there, compare its remark with the expression character by character. For example, if the rule uses “Data remaining” but the remark says “Remaining data,” adjust the rule to match the actual prefix.

A frequently used server disappeared after the update. How do I restore it?

First copy the current rule to a local note, then clear the filter field for that group. Save and update the current subscription. If the server returns, narrow the original rule. If it is still missing after an unfiltered update succeeds, check whether the provider renamed it or removed it from the subscription.

The subscription update timed out. Is the filter rule wrong?

Treat a timeout as a subscription fetch failure first. Check that the URL has not expired, then confirm whether the update command uses a proxy. If the subscription must be fetched through a proxy, select another server that you have already verified works, then retry using the proxy-enabled option for “Update Current Subscription.” Check remark matching only after the download succeeds.

Download v2rayN