v2rayN Subscription Groups and Node Filtering: Organize Multiple Subscriptions

Understand subscription groups, node remarks, and list filters

A subscription link points to a server list maintained by its provider. When v2rayN updates a subscription, it reads the returned content and places the servers in the corresponding subscription group. Even if two links contain nodes with the same name, keep them as separate sources to start with; the node name alone cannot tell you which subscription it came from.

Use group remarks to identify a source or purpose, such as “Work · Primary” or “Backup · Update as needed.” Node remarks usually come from the subscription and may change with the next update. Search and filtering on the main screen affect the list you see, not the subscription source. To control which nodes are imported into a group over time, check the filter options in that group’s settings.

Create groups before adding filters. If you restrict multiple subscriptions to the same keyword from the start, an update may leave each group with only a few similarly named nodes, making their sources harder to identify.

Add groups and name multiple subscriptions

Here’s an example with two subscriptions: one for everyday use and one as a backup. Have both subscription links ready before you start. Links may contain access credentials, so don’t include them in public screenshots, shared documents, or search fields. Button labels can vary by version; the key is to open the Subscription Group settings and save each subscription as a separate entry.

1. Open settings

   In the v2rayN main window, go to “Subscription Group” → “Subscription Group Settings.” Make sure you’ve opened the window for managing subscription links, not the search field in the node list.

2. Add the primary group

   Click “Add,” enter “Everyday · Primary” in the remarks field, and paste the first complete subscription link in the address field. Save, then check that the link is assigned to this group.

3. Add the backup group

   Click “Add” again, enter “Backup · Update as needed” in the remarks field, and add the second link. Don’t paste both links into the same field or use node remarks in place of group remarks.

4. Update each group

   Return to the main window, select a group under “Subscription Group,” and update it. If your version only offers an option to update all subscriptions, check the results for each group afterward.

5. Verify the sources

   Switch between groups to view their nodes. First confirm that each group contains the expected entries, then set up filters. Don’t rely on the total node count after a single update to determine whether each subscription succeeded.

Filter nodes by keyword and test on a small scale

Node names often include a region, route, or provider-specific label, such as “Hong Kong,” “Japan,” or “Backup.” Whether a filter matches depends on the names actually returned by the subscription, not the region you expect. First review a few complete remarks in an unfiltered group, identify words that appear consistently, and then choose what to keep.

If your version has a “Filter” field in the group settings, start with one keyword in one group—for example, “Hong Kong.” Save and update that group, then compare the item count before and after filtering to confirm the expected nodes remain. To match multiple terms, check whether the field supports regular expressions. Only if it does, use an OR pattern such as “Hong Kong|Japan.” Don’t assume commas or spaces separate keywords in every version.

These numbers illustrate an organizational approach; they aren’t v2rayN limits or defaults. If a group becomes empty after filtering, clear its filter and update it again, then check whether the subscription itself returned any content. Also clear any temporary search term in the list so “not visible in search results” isn’t mistaken for “no nodes in the subscription.”

• Choose terms that persist in node names. Don’t use current speed-test results, sequence numbers, or dates as long-term filter criteria.
• Set filters separately for the primary and backup groups. A match in one group doesn’t mean the other uses the same naming convention.
• Check the filter results again if the provider changes its node names. An outdated filter may hide newly named nodes.

Plan updates to avoid disrupting the nodes you’re using

Groups help manage sources; updates keep their contents in sync. For everyday use, check the primary subscription first and update the backup as needed. This example uses a manual check of the primary group every 24 hours as a reminder, not a recommendation to set the same automatic update interval for every group. Choose a schedule based on how often the subscription changes and how frequently you use it.

Before updating, note the selected group and node name. Afterward, check that group for added, removed, or renamed entries before switching nodes. A provider may remove nodes, which can disappear after syncing. Don’t treat subscription-generated node remarks as permanent personal labels; keep your own organizational notes in the group remarks instead.

“Update succeeded” means the subscription content was processed; it doesn’t guarantee that every node can connect. Once you’ve checked the list, test an actual connection with one node. If it fails, troubleshoot the node parameters, core logs, and system proxy settings separately—repeatedly changing filter terms won’t fix a connection problem.

FAQs: empty lists, duplicate nodes, and update timeouts

Change one thing at a time while troubleshooting: check the subscription link first, then the group filter, then temporary searches and connection status. This helps pinpoint whether the issue is with fetching content, displaying the list, or connecting to a node.

Once everything is organized, keep group remarks that identify each source and check regularly that the filters still match the node names in use. When adding a third subscription, create a separate group, update it once without a filter, and follow the same checks.