v2rayN Subscription Groups and Server Filtering: Organize and Filter Multiple Subscriptions

Organize multiple subscriptions by source, filter servers by keyword, remove duplicates and stale entries, and set update intervals to keep your server list easy to navigate.

At a glance

With two or more subscription URLs, start by grouping them by source and updating each group separately. Check the original server remarks before adding filters. Don’t delete servers just because they share a name—compare their connection settings and sources first. Finally, set separate update intervals for your primary and backup groups so an update doesn’t leave you searching for a configuration that was there before.

Subscription Groups: One Group per Source

A subscription URL retrieves a batch of configurations; a share link contains just one. Don’t paste a single share link into the subscription URL field, and don’t combine multiple sources in one group and sort them out later. A group name should tell you where its entries came from. Filter by region within a group rather than splitting groups by region.

Group by sourceFetch subscriptionParse configurationsFilter by remarksGroup entries
  1. In the main window, open “Subscription Groups” → “Subscription Group Settings” and click “Add.” Enter an alias and subscription URL. For example, label the first URL “Source A | Primary” and the second “Source B | Backup.” There’s no need to include an account name, email address, or subscription token in an alias.
  2. After saving, select “Source A | Primary” in the main window and use the “Subscription Groups” menu to update the current subscription. Update this group by itself first, then repeat for the backup group. Don’t start with “Update All Subscriptions.” If the menu offers “through proxy” and “without proxy,” the former uses your existing proxy connection, while the latter requests the subscription URL directly. This setting only determines how the subscription is fetched this time.
  3. Leave the filter blank for the first update. For each group, note the number of entries, two or three original server remarks, and one configuration you’ve confirmed works. If the list suddenly becomes empty later, these notes can help you tell whether the subscription returned no results or the filter removed them all.

Server Filtering: Match Keywords in Remarks, Test One Group First

Use the main window’s search to find an entry in the current list. “Filter Regex” in a subscription group instead filters imported results by server remark when you update that group. After saving a filter, update the current group to check that it works; the existing list won’t show whether it took effect. A remark that says “Hong Kong” doesn’t prove the server is physically located there. Regex checks text only—it doesn’t test the connection or change routing.

Source A | Remarks use full region names

Example original remarks
Hong Kong 01, Japan 02, Singapore 03
Filter regex
Hong Kong|Japan
Expected results
Hong Kong 01, Japan 02

The vertical bar means either option can match. A match anywhere in the remark is enough.

Source B | Remarks start with region abbreviations

Example original remarks
hk-01、JP_02、SG-03
Filter regex
(?i)^(HK|JP)[-_]
Expected results
hk-01、JP_02

Case-insensitive; requires the remark to start with a region abbreviation followed by a specified separator.

This rule for the second group is more specific than searching for HK alone, and it will also miss Hong Kong-HK-01 and HK 01. Only require a prefix and separator if the provider consistently uses the same naming format. Don’t copy the Chinese filter from Group A into Group B: even when both offer the same region, their naming conventions may be completely different.

Duplicate or Unavailable Servers: Check Settings and Test Results, Not Just Names

Two sources listing “Hong Kong 01” doesn’t mean they point to the same server. Even the same address and port can use different protocols or authentication settings. Compare at least the protocol, address, port, authentication parameters, and transport. If the configuration uses TLS or other security settings, compare those parameters too. Treat two entries with different remarks as functional duplicates only when their connection settings match.

What you seeWhat to check firstWhat to do
Two entries have the same remarkSource, protocol, and connection settingsIf the settings differ, keep both and distinguish them by group.
A manually deleted entry comes back after an updateCheck whether the entry is still in the sourceIf the naming pattern is consistent, filter within the group. If only a few configurations are duplicates, keep them and note their sources.
Only one entry in a group keeps failingUnder the same test conditions, can a known-working entry in the group connect?If the comparison entry works, test the failing one again. If it continues to fail, disable that entry for now; there’s no need to delete the whole group.
Entries in both groups fail at the same timeCurrent network, core logs, and test targetFirst check for a general issue using a different working test target, then decide whether to remove any entries.

To test availability, check the entries under investigation and a known-working entry on the same network and against the same test target. A latency result only means that test passed; it doesn’t guarantee that requests will work in practice. Also try a request from the application you normally use. Before deleting or filtering out your active configuration, select and verify another working one.

Deciding What to Remove: Find the Source of Duplicates First

If the same subscription URL was added twice, keep the group you’ve verified and remove the duplicate subscription entry. If different sources occasionally provide the same server, keep the source information rather than deleting an entire group just to remove one duplicate.

Update Intervals: Start with Daily for Primary and Weekly for Backup

Open “Subscription Groups” → “Subscription Group Settings,” then double-click a group and check the automatic update interval in the edit window. The values below are suggested starting points for organizing two subscription groups, not client defaults. If the field is in minutes, enter the converted values shown. If your version uses a different unit, convert according to the unit shown in the interface. Make sure automatic updates are enabled for both the group and the relevant client settings.

1,440 minutes
Suggested starting point for the primary group: update daily
10,080 minutes
Suggested starting point for the backup group: update weekly
1 group
Update this group manually after changing a filter

Update Frequency Can’t Fix a Filter Rule

If a provider’s remark changes and the filter drops the same servers every time, loosen the group’s rule first and update that group alone to check the new remark format. Then restore your usual schedule. Shortening the update interval will only make the same result happen more often.

Download v2rayN