For anyone managing multiple subscriptions on one computer. Create a group for each provider, then search within each group by region or route name. Compare connection settings before removing duplicates. Keep manual nodes you want to retain in a separate local group instead of mixing them with subscriptions that refresh.
Create a Group for Each Subscription
Start with one group per subscription URL. Two providers may both name a node “Hong Kong 01.” Grouping by source makes it clear which subscription to update and which provider to contact, even when node labels match. The steps below use the v2rayN 7.x desktop interface; button labels or locations may vary slightly between minor versions.
Get Your Subscription URLs
Copy each complete subscription URL from the provider’s account page. Keep the query parameters intact—don’t copy only the domain. Subscription URLs may contain access credentials, so don’t include them in screenshots or public support posts.
Add the First Group
In the main window, select “Subscription Group” → “Subscription Group Settings,” then click “Add” in the group management window. Enter “Subscription A” as the remarks and paste the matching URL into the address field. Save and return to the main window.
Save Each Source Separately
Repeat the steps to save the second URL as “Subscription B.” First check that each label matches its URL. If a provider supplies two URLs for different purposes, give each one a separate group.
Update the Current Group
Select “Subscription A” in the main window, then choose “Subscription Group” → “Update current subscription (without proxy).” Once nodes appear in the group, switch to “Subscription B” and repeat. When adding subscriptions for the first time, updating them one at a time makes it easier to spot a URL that needs attention.
Check Which Group Each Node Belongs To
Switch between the two groups and confirm that each contains the expected nodes. If a group appears empty, clear the search field in the main window and check the update log to tell whether the list was filtered or the subscription failed to import.
Filter Nodes by Keyword
Select the subscription group you want to search, then enter a term from a node’s remarks in the search box above the list. For example, if Subscription A uses “Hong Kong 01,” search for “Hong Kong.” If Subscription B uses “HK-01,” try HK separately. Don’t assume the client treats a region abbreviation and its full name as equivalent, or that a place name in the remarks confirms the node’s actual exit location.
Search the Main Window
RecommendedThis only narrows the visible list; it doesn’t delete nodes or change what gets imported during future updates. Clear the search field to show all nodes in the group again.
Best for: Quickly finding a region, route, or node number
Filter a Subscription Group
Go to “Subscription Group” → “Subscription Group Settings,” open the group you want, and check the filter field in its edit window. This controls which nodes are imported during an update. Test with a simple term first. To undo the filter, clear the field and update the current subscription. Clearing the main-window search won’t restore nodes that weren’t imported.
Best for: Consistently named nodes when you only want to import some of them on each update
This example illustrates filtering; it isn’t a client limit or a performance benchmark. Suppose Subscription A has 12 nodes, 5 of which have “Hong Kong” in their remarks:
Verify Node Names Before Filtering
If a subscription uses both “Hong Kong” and HK, search each term separately and check which nodes match. When providers often rename nodes, keeping the full subscription and searching as needed makes it easier to catch missing entries than filtering them out during updates.
Remove Duplicate Nodes and Sort the List
Node remarks are display names, not unique identifiers. Two nodes named “Hong Kong 01” may connect to different servers, while nodes with different names may use identical settings. If you spot possible duplicates, narrow the list to one source and open each node’s edit window to compare its settings. Close the window when you’re done; there’s no need to change anything.
- Compare connection settings first: Check the protocol, server address, and port, followed by credentials, transport, and security settings. For example, a node using port
443and another using8443should not be merged just because their remarks match. Even with the same address and port, keep nodes separate if their transport paths or TLS server names differ. - Then decide what to delete: Only consider removing a duplicate from a local group once you’ve confirmed it was imported more than once. A node in a subscription group may reappear after the next update if it’s still in the provider’s list. There’s no need to merge nodes from different sources, even if their settings currently match; either subscription may change independently.
- Sort based on what you need to check: To find nodes with the same name, sort by remarks. To compare connectivity, test candidate nodes on the same network using the same latency test, then sort by the relevant column. Review nodes with no test result or a timed-out test separately. Sorting by latency doesn’t sort by download speed.
Keep Local Nodes When Updating Subscriptions
Treat a subscription group as the list supplied by the provider, not as a permanent collection. Updates may recreate subscribed nodes, so don’t rely on renamed, deleted, or reorganized entries in a subscription group as permanent changes. To keep a node, save a separate local copy instead of renaming the original.
- In “Subscription Group” → “Subscription Group Settings,” add a group named “Keep Locally” and leave the address blank. Use this group for manual nodes; don’t enter a provider’s subscription URL.
- Copy the single-node share link, switch to the “Keep Locally” group, and import it with Ctrl + V. Confirm that the node appears in the local group, and leave the original in its subscription group. Share links contain connection credentials, so don’t post them in public channels.
- Switch back to a source group with an address and select “Update current subscription.” When the update finishes, return to the local group and confirm the manual copy is still there. Test the connection to check whether the saved configuration is still present and the server settings still work.
A local copy retains the connection settings from when it was imported. If the provider changes the server address, credentials, or transport settings, the subscription may receive the new configuration, but the local copy won’t update automatically. Compare it with the updated subscription node, confirm the new entry works, then replace the old local copy.
Subscription Updates and Node Filtering FAQ
The update says it completed, but no nodes are showing. Why?
First, make sure you’re viewing the group you updated and clear the search field in the main window. If it’s still empty, open the group settings and check for a filter. Try clearing the filter, saving, and updating the current group. Then check the log to see whether any nodes were recognized and imported.
Subscription A updates normally, but Subscription B times out. What should I do?
Select Subscription B, update it by itself, and check the log instead of repeatedly updating all subscriptions. If a direct connection to the URL times out and Subscription A has a node you’ve confirmed works, use that node to maintain the connection, then retry B with “Update current subscription (through proxy).” If the log says the server denied access, check whether the subscription is still active in your provider account.
Why did my edited node remarks revert after an update?
Refreshing a subscription reloads the remarks provided by the service. To keep a custom name, import the single-node link into a local group with no subscription URL and rename the local copy. Leave the original node in its source group so you can compare its settings with future updates.
Why do I see only one or two nodes after switching groups?
Check whether the search box still contains a keyword from the previous group. If clearing it restores the node count, only the visible list was narrowed. If not, check the group’s filter settings and the latest subscription update log.