For desktop users with two or more subscriptions who often lose track of servers. Create a separate group for each provider, filter by server name to keep preferred regions, then plan updates and latency tests. This guide uses two groups and 12 sample entries to demonstrate filtering, while clarifying the difference between list search, subscription filters, and routing rules—so server management isn't mistaken for automatic failover.
Subscription Groups, Name Filters, and Routing Rules: What's the Difference?
In v2rayN, subscription groups organize servers by source. Put Provider A and Provider B in separate groups so you can tell which source returned new configurations after an update and more easily investigate expired subscriptions, renamed servers, or duplicates. Group names are local labels; they don't change the server-side settings or combine two subscriptions into one connection.
Name filters apply to server entries in a subscription; routing rules apply to connection requests. A group containing only Japan servers doesn't mean Japanese websites will automatically use that group. With the standard single-server setup, connections still depend on the active server and routing configuration. Group labels alone don't tell you where traffic goes.
| Feature | What It Applies To | What It Helps With |
|---|---|---|
| Subscription groups | Servers from the same source | Separating providers, updating individually, identifying sources |
| List search | Entries currently visible in the list | Finding a name temporarily without changing subscription import rules |
| Subscription name filter | Server entries imported during an update | Keeping selected names and reducing irrelevant entries |
| Routing rules | Connection criteria such as domains and destination addresses | Choosing a direct connection or a specified proxy outbound |
Create a Group for Each Provider: Import the Full List First
In the main window, go to “Subscription Groups” → “Subscription Group Settings,” create a group, and enter a note and subscription URL. Menu locations can vary between desktop versions, so look for the same setting in your installed version. Use a name that identifies both the source and purpose, such as “Provider A - Daily” or “Provider B - Backup.” Names like “Fast” or “Favorites” alone can make the source hard to identify later.
- Back up your existing configuration first. Use the backup method available in your version. If you copy the configuration folder, exit the client first to avoid copying files while they're being written. Backups contain subscription credentials, so store them securely.
- Create one group per source. Add the corresponding subscription URL to each group. Leave the filter field empty on the first import; don't start with a complex expression.
- Update only the new group. In the “Subscription Groups” menu, choose the option to update the current subscription. Make sure the intended group is selected, then check the update log.
- Check the actual server names. Note whether regions are written in Chinese, English, or abbreviations, and whether names include multipliers, route numbers, or purpose labels. Use this information to decide what to filter.
These two cards show example management setups, not default client settings. Set an automatic update interval only if your version provides that option. If it doesn't, update manually. Check backup groups regularly, even if you rarely use them.
Provider A - Daily
- Source
- Provider A's dedicated subscription URL
- Purpose
- Everyday browsing and work connections
- Regions
- Hong Kong, Japan
- Update schedule
- Check every 24 hours
Import the full list once before adding region filters.
Provider B - Backup
- Source
- Provider B's dedicated subscription URL
- Purpose
- Switch manually if the primary connection has issues
- Regions
- Singapore, Japan
- Update schedule
- Check every 72 hours
These intervals are maintenance suggestions. Actual timing depends on runtime and client behavior.
Server Name Filters: Check Whether the Field Uses Regex
In Subscription Group Settings, some versions label the relevant field “Alias Regex Filter.” Here, “alias” usually means the server's display name, not its address or protocol. If the interface explicitly says the field accepts regular expressions, you can use the examples below. If it's a plain keyword field, read its description before entering regex syntax.
For regex filters that keep entries when a match is found, Hong Kong|Japan keeps entries whose names contain “Hong Kong” or “Japan”—it doesn't exclude them. Don't assume commas separate conditions: in a regex, Hong Kong,Japan usually searches for that exact comma-separated text, so it may match nothing.
| Goal | Regex Example | Check Before Using |
|---|---|---|
| Keep entries matching either of two region names | Hong Kong|Japan | The names actually contain these characters |
| Also match common English abbreviations | (?i)Hong Kong|Japan|HK|JP | Case-insensitive; may also match abbreviations within longer names |
| Keep only names beginning with HK | (?i)^HK | Names don't have a number, space, or decorative character before the prefix |
| Exclude names containing either of two phrases | ^(?!.*(?:Remaining Data|Expiry Date)).*$ | The field supports regex and keeps entries that match |
| Match a decimal point in a name | 0\.5x | Escape the period so it matches a literal dot, not any character |
Filters match name text; they don't check a server's actual location. A name containing “Japan” only means it matches the rule. Check the provider's details and test the connection to determine whether it uses a relay, where its exit is located, or whether it supports a particular service. Similarly, filtering names for “VLESS” won't reliably identify the protocol, since subscription names may not include protocol details.
12 Sample Entries: Check That the Filter Keeps the Right Servers
The examples below are for illustrating the process, not speed-test results or actual server counts from any provider. Suppose each of two groups has six entries: Provider A keeps Hong Kong and Japan, while Provider B keeps Singapore and Japan. After filtering, four entries remain. These numbers demonstrate the filtering logic only; they say nothing about subscription size or connection quality.
| Group and filter | Six original names | Entries kept |
|---|---|---|
Provider AHong Kong|Japan |
Hong Kong01, Japan01, US01, Germany01, Remaining Data, Expiry Date | Hong Kong01, Japan01 |
Provider BSingapore|Japan |
Singapore02, Japan02, US02, UK02, Remaining Data, Expiry Date | Singapore02, Japan02 |
Before checking the results, clear the list search box and review the current group's entry count. Otherwise, hidden search results and entries removed during import can combine and lead to a false conclusion. After saving filter settings, you usually need to update the relevant subscription again to rebuild the imported list. Closing the settings window alone may not change existing entries.
Bottom Line: Check Names Before Broadening the Filter
If Provider A doesn't retain two entries in this example, check whether the server names are actually “HK01” and “JP01” before changing the subscription URL. Expand the expression only after confirming the update succeeded and the field behaves as expected.
Updates, Sorting, and Speed Tests: Follow a Consistent Routine
Subscription updates may replace server names, addresses, ports, and authentication settings, or remove entries that are no longer available. Manual edits to subscription servers may be overwritten by the next update. To keep custom configurations long term, save them in a separately managed group rather than relying on temporary edits in the subscription list.
- Update one group first. Check the log for fetch and import results before updating the other group. If something goes wrong, it's easier to trace the source when you update groups separately.
- Then review the names. Sort by note or name and check for duplicates, changes in naming format, and whether backup regions remain after filtering.
- Test a small set of candidate servers. Start with three to five servers per group. Pause large downloads and keep network conditions consistent during testing. Concurrent batch tests use bandwidth and may consume subscription traffic.
- Choose the active server last. Once the target server is confirmed to work, set it as active, then test it with the website or app you actually use. The lowest latency number in the list doesn't necessarily mean the fastest download speed.
Latency, connectivity, and download speed tests measure different things. Lower latency means a faster response along the tested path, not necessarily higher throughput to your target website. A timeout may also be caused by the test target or your local network. To compare two providers, test each under the same network conditions, at the same time, and against the same target. Record when you tested, not just one number.
Common Issues: Empty Lists, Duplicate Servers, and Failed Updates
Why is the whole group empty after I save a filter?
Check the subscription update log first to distinguish between “no content received” and “content received, but no entries matched.” For the first case, check your network, subscription expiry, and URL. For the second, clear the filter field and update the group again. If the full list returns, add a rule starting with a region name that appears in the list. Prefixes, full-width punctuation, and differences between Chinese and English can all affect matching.
Why do deleted servers reappear after the next update?
Deleting a local entry doesn't remove the server from the subscription source. The next import reads the source again. To keep a type of entry from appearing, adjust the group's import filter instead of deleting it manually each time. To restore previously filtered servers, broaden the rule and update again; clearing the list search box won't restore data that wasn't imported.
Both groups have “Japan01.” Should I delete one?
Don't delete an entry just because its name matches another. Different providers may use the same region number while having different addresses, ports, protocols, and authentication details. Switch groups to confirm the source. If two groups were created for the same subscription URL by mistake, keep one source configuration and remove the duplicate import. Don't change server-side settings just to make entries easier to identify.
Will grouping providers automatically switch between them?
Groups don't provide automatic failover. In a standard setup, you need to select an available server manually; more complex multi-outbound, load-balancing, or routing strategies require separate configuration. Keep both sources up to date and verify that the backup server connects before considering additional strategies. Having a group doesn't mean a backup connection has taken over.
What should I hide in screenshots before sharing them for troubleshooting?
Hide full subscription URLs, account credentials, authentication identifiers, and server connection details. A token or path in a subscription URL may grant access directly; hiding only the domain may not be enough. When asking about filters, share redacted server names, the filter expression, and the update error text. If a full URL has already been exposed, reset it in your provider account before updating the local group.