Keep each subscription under its own source, using clear labels and a consistent order instead of repeatedly importing every server into one list. This guide assumes you already have subscriptions from your providers. It covers managing groups in Home, updating a single subscription, understanding what deletion affects, and identifying duplicates. To clean up safely, remove duplicate subscription sources first, then check for any remaining servers so they do not reappear after an update.
1. Understand subscriptions, servers, and Config
In Shadowrocket, a subscription is a source for retrieving a list of servers. One subscription can contain multiple servers, and the same server may appear in more than one subscription. Source groups in Home help organize these entries, but a group name does not determine which route a request takes.
Config manages rules and other configuration content; it is separate from server subscriptions. Adding a second server subscription does not enable a second set of rules, and reordering the Home list does not change rule-matching order. Settings contains options for app behavior. Identify what you are working with before updating or deleting anything to avoid mistakes.
2. Group subscriptions by source and label them clearly
Keep one subscription record for each active source. When organizing your subscriptions, check each record’s label and address in Home, then name each source. The editing control may appear differently across platforms—as an edit button, item details, or a context menu. Before making changes, confirm that you have selected a subscription record, not an individual server within its group.
- Check the address. Open the edit or details view for an existing subscription and compare the full address. If the same address has been saved twice, consider keeping just one copy instead of importing it again.
- Label each source. For example, use “Source A | Daily” and “Source B | Backup.” These are local organizational labels; do not include an account name, password, or full subscription token.
- Keep sources separate. Leave each subscription’s servers associated with their original source. Don’t manually copy every server into a single list just to make the names consistent.
- Label exceptions. If you need to add a server manually, note its purpose separately so you won’t mistake it for a leftover subscription entry later.
If two links differ only in their tokens, the matching domain alone does not prove that they are duplicates. They may belong to different accounts, permissions, or output scopes. Check their purpose in your provider’s account page before deciding which to keep. Do not submit subscription links to public comparison tools.
3. Sorting changes display order, not routing
When organizing your list, set the order of the groups first, then sort the servers within each group. Put frequently used sources first and backup sources later to make them easier to find. In Home, use the drag handle or sorting option actually shown in the edit or sorting view. Clicking a server usually selects it; it does not move the entry.
| Item | Suggested organization | What this does not change |
|---|---|---|
| Subscription source group | Set its display position based on use, such as daily or backup | The source address or content returned by the provider |
| Servers within a group | Sort by a name or test result using the available options | Actual server bandwidth or availability |
| Currently selected server | Choose manually based on use, then test the connection | Rule order in Config |
| Rules or policy groups | Check separately in the current configuration | Source labels and group positions in Home |
Bottom line: list position does not determine the actual route
The first item in the list is not necessarily the server handling a request. After sorting, check the selected server, Global Routing, and policy references in Config, then verify the route with an actual request.
If Global Routing is set to Direct, switching servers alone will not test proxy routing. With Config, requests are handled according to its rules; Proxy and Scene also have their own routing behavior. Don’t change these settings just to organize the list, and don’t treat display order as automatic failover.
4. Update one subscription and check what changed
To check a particular source, update that subscription individually rather than refreshing every source at once. Find its record in Home, open its action menu, and use the update option for that source. Before updating, note the selected server’s name, its source, and the number of entries in the group. Compare these details after the update.
Before updating
- Where to check
- Home → edit or details view for the target subscription
- Source identifier
- Local label and subscription address
- Current selection
- Server name and associated subscription
- List state
- Number of entries in the group and any manual changes
Check the address locally only. Do not include the full token-bearing link in public notes.
After updating
- Update target
- The single subscription source updated in this operation
- Content changes
- Servers added, removed, or renamed
- Selection state
- Whether the original server still exists and is selected
- Configuration references
- Whether any server name references are now invalid
If something looks wrong, check the returned content and account status first. Don’t try to fix it by importing the subscription again.
For example, if a group contains 12 servers before an update and 10 afterward, that only means the returned list differs from the previous one. It does not prove that two entries were lost from your device. Check whether the provider changed the available servers, renamed entries, or returned incomplete content. The numbers here are for troubleshooting only and do not describe any real service.
- Only one source fails: Check whether the link is valid, the account is in good standing, and the provider has changed the address.
- All sources fail: Check the device’s internet connection, whether the current network can reach the subscription addresses, and the specific error shown in the app.
- Update succeeds but the group is empty: Don’t delete other working sources right away. First check whether the remote service returned a recognizable server list.
- A manual rename is reverted: The updated remote content may have changed the entry again. Keep long-term labels at the source level rather than relying on temporary renames of subscribed servers.
5. Before deleting, check whether you are removing a subscription or a server
Deleting an individual server is different from deleting its subscription source. If you delete a server from a subscription but it remains in the remote list, a later update may add it back. Deleting the source affects how that subscription is managed and may also remove its associated entries. Read the confirmation prompt and follow the scope it specifies.
- Switch away from the server first. If you are connected through the source you plan to remove, select a working server from a source you are keeping and verify that the connection works. Switching may interrupt an active connection.
- Check configuration dependencies. If a config or policy group directly references the name of a server you plan to delete, update that reference first to avoid an unavailable selection or a broken policy.
- Open the delete control for the intended record. Confirm whether you are removing a source record or an individual server. Avoid bulk-clearing anything unless its scope is clear.
- Read the confirmation prompt. After confirming, return to Home and check that the source title and group entries were removed as expected. Then look for any entries that remain on their own.
- Verify the sources you are keeping. Update each retained source individually and confirm that it works before cleaning up the next group.
6. Remove duplicate servers by checking connection details, not just names
Duplicate servers usually come from one of three situations: the same subscription was added more than once, a server was imported manually and then added through a subscription, or different sources include the same endpoint. Identify duplicate sources first, then check whether the servers themselves are duplicates. Deleting entries in bulk based only on their names can remove the wrong servers: entries with the same name may use different protocols or connection settings.
| What you see | What to check | What to do |
|---|---|---|
| Two groups have similar names and content | Whether the full subscription addresses and their purposes match | If they match, keep one source and check for leftover entries |
| Two servers have the same name | Type, address, port, and authentication settings | If the settings differ, don’t merge them based on name alone |
| Same address, different ports | For example, server settings using port 443 versus 8443 | Treat them as separate connection endpoints and check their purpose |
| A server reappears after deletion | Whether a subscription source still provides that entry | Check the source or the filtering options provided by your provider |
Even when the address and port match, compare the Type, account or password, and transport security settings. For example, Trojan entries with different TLS Server Names or transport settings, and VLESS entries with different identities or transport parameters, are not necessarily duplicates. Check authentication fields only on your device; never copy them into a public table.
Bottom line: if an entry returns after an update, check its source first
There is little point in repeatedly deleting entries that a retained subscription continues to return. Remove duplicate sources first. If you want to limit the content from a source long-term, check whether your provider offers the relevant subscription output options.
For entries confirmed as manually imported duplicates, keep one copy with complete settings and a clear purpose. After cleanup, select the server you want to use and make a request using your usual configuration to check the connection. A test only reflects network conditions at that time; one low latency result is not a reliable basis for long-term priority.
7. Frequently asked questions about managing multiple subscriptions
Will adding a second subscription overwrite the first one?
When added as a new subscription record, it should be managed separately from existing sources. Editing an existing record and replacing its address changes that original source. Before saving, check whether you are in the add-new flow or editing an existing subscription. Then return to Home and confirm that both sources are listed.
Why does my manually arranged order change after a subscription update?
The remote list order or entry names may have changed, or the current sorting method may have been reapplied to the new content. Check the sorting method for that group and reapply your preferred order. For easier long-term identification, use stable source labels rather than relying on a server always appearing on a particular row.
Can I restore the original group after accidentally deleting a subscription?
Get the original subscription link from your provider, add it again, and update it. Servers still available remotely can be retrieved, but do not assume that local labels, manual changes, or the previous selection will be restored automatically. Check each item after reimporting.
Why are my requests not using the server I selected from the backup subscription?
First check whether Global Routing is set to Direct. If you use Config, check the matching rule and its policy reference. A specific policy group in the configuration may select another server; a selection in Home does not override every explicit reference. Reimporting the same subscription will not fix a routing issue.
After organizing your subscriptions, check in this order: no source was accidentally removed from Home, individual updates work, the selected server is present, Config has no invalid references, and actual requests follow the expected route. Use the same labeling convention whenever you add a source to keep duplicate entries from making the list hard to navigate again.
Get Shadowrocket and learn how to configure it
Get the iPhone / iPad version from the App Store for a one-time payment of $2.99. The Mac (Apple Silicon / Intel), Windows, Android, and Linux versions are free. Check the App Store listing for iPhone / iPad system requirements. The developer is Shadow Launch Technology Limited. Find download options for each platform on the download page; see the guide for importing an existing subscription and checking your connection.