This guide is for users who already have their own service provider and subscriptions and want to organize their Shadowrocket list. First, distinguish subscription sources from connection entries. Then record each source, adjust the display order, update subscriptions one at a time, and remove sources confirmed to be obsolete. Keep the subscription details you may need to restore access, don't assume similar names mean duplicates, and remember that deleted entries may return after the next update.
1. Understand the difference between subscription sources, nodes, and Config
A subscription URL provides a set of connection parameters; nodes are individual connection entries parsed from that source. One subscription can contain multiple nodes, and the same node may appear in more than one subscription. So the number of list entries doesn't equal the number of unique routes, and adding a subscription doesn't necessarily add a usable service.
On iPhone and iPad, use Home to review subscription groups and the server entries under each one. Config is for configuration files and rules, while Settings is for app preferences. Organizing the Home list and editing Config are separate tasks. In this guide, “grouping by source” means managing which subscription an entry belongs to. It isn't the same as a policy group in a configuration file and won't change rule matching automatically.
The steps below use the iPhone and iPad interface as an example. On Mac, Windows, Android, and Linux, identify subscription sources before managing individual entries. Menus and interactions vary by device, so don't assume a swipe gesture from the phone works on desktop.
2. Name sources and keep a recoverable record of each group
Before you begin, make sure you can retrieve the original URL for every subscription. Query parameters in a subscription URL may act as access credentials, so don't include them in public screenshots, documents, or group chats. If you need to record a source, save the full URL in a protected personal note. When troubleshooting publicly, share only a redacted hostname and the error message.
- Open Home, count the existing subscription groups, then check for server entries that aren't part of a subscription. Record manually added entries too; don't delete them as duplicates without checking.
- Open each subscription's edit screen and check the URL's hostname, path, and parameters. Don't identify a source by its display name alone, and don't change tokens in the URL just to make the entries look consistent.
- Use clear local labels, such as “Source A | Daily” and “Source B | Backup.” If the current interface has a Remark field, edit the label there. Don't change server connection parameters to use them as group names.
- Record each source name, its current entry count, and the currently selected node. Then update one subscription at a time so you can tell which source caused any changes.
Example: tracking notes for Source A
- Local label
- Source A | Daily
- URL
https://example.com/sub?token=xxxx- Count before organizing
- 12 entries, for illustration
- Why keep it
- Original URL is recoverable and entries load after an update
The URL shown is a nonfunctional example; use the address from your own records.
Example: tracking notes for Source B
- Local label
- Source B | Backup
- Access details
- Stored in a protected personal note
- Count before organizing
- 8 entries, for illustration
- What to check
- Whether it contains the same connection parameters as Source A
Source labels identify where entries came from; they don't indicate route quality or rule priority.
3. Reorder carefully: display order is not connection selection
The order of subscription groups, the order of nodes within a group, and the currently selected node are three separate states. Moving a group to the top of the list doesn't route all requests through it, and sorting by latency doesn't enable automatic switching. After organizing the list, check the selected item in Home and review Global Routing.
- Sort sources first: Keep frequently used sources somewhere easy to find. If the current interface offers an edit or drag-and-drop option, reorder the groups there. If not, use consistent labels to tell them apart; don't keep re-importing subscriptions to “push them to the top.”
- Then sort entries: If the interface offers sorting by name or latency, check which list the sort applies to. Note the currently selected node before sorting, then confirm it hasn't been mistaken for another entry afterward.
- Verify last: If you're using latency to help choose a node, test on the same Wi-Fi or cellular network. Test again after switching networks, and don't treat readings from different times or networks as directly comparable.
- Review after updates: A subscription update can change node names, counts, and order. Manual sorting isn't part of the provider's data, so don't assume the list will look the same after every update.
If Global Routing uses Config, check which Config is active and where its rules send traffic. For example, DOMAIN-SUFFIX,example.com,PROXY matches a domain suffix, while FINAL,PROXY is a final fallback. The order of entries in the list doesn't replace these rules. Don't switch to Direct just to organize subscriptions and then forget to restore your previous routing state.
4. Identify duplicate nodes: names are clues, connection parameters are evidence
Nodes with the same name may use different servers, ports, or authentication details. Entries with different names may also connect to the same endpoint. When checking for duplicates, compare at least the protocol, server address, port, authentication details, and transport settings. Compare authentication details locally; there's no need to copy them into a public conversation.
| What you see | What to check | What to do |
|---|---|---|
| Two entries have the same name | Protocol, address, port, authentication, and transport settings | Keep them if the parameters differ; use labels to tell them apart. |
| The same server appears with ports 443 and 8443 | The port and the server's actual configuration | Different ports may point to different services; don't delete either as a duplicate without checking. |
| The same subscription was imported twice | The full URL, including query parameters | After confirming one group updates correctly, remove the redundant source. |
| Two sources contain the same endpoint | Full connection parameters and source ownership | Decide which source to keep. Otherwise, an update may restore entries you've deleted individually. |
Here's a hypothetical example, not a product limit: two subscription groups contain 20 entries in total. A comparison confirms that one pair has identical connection parameters. You can mark that pair as duplicates, but you can't conclude that the remaining 19 entries are unique routes just by subtracting one from 20, or infer the number of independent exit points.
Takeaway: deduplicate sources first, then review entries within each source
If two groups use the exact same subscription URL, keep the one that updates correctly. If duplicate entries come from different URLs, decide which source to keep first. Deleting only entries generated by a subscription may not last; the next update could restore them.
5. Remove old subscriptions safely without disrupting the active connection
Removing a subscription only changes the list on this device. It doesn't cancel an account with the provider or stop a remote service plan. Likewise, an expired remote service doesn't necessarily remove old entries from your device right away. Before deleting anything, separately check whether you want to keep the local entries and whether the remote service is still active.
- Make sure you can restore it: Confirm that you can retrieve the original URL from a protected personal record or the original provider. If the link no longer works and you have no backup, don't make deletion your first troubleshooting step.
- Change the selected node: Check whether the currently selected node belongs to the group you plan to remove. Select a node you intend to keep and confirm it can make the required connection before removing the old group.
- Choose the right deletion level: Find the controls for the subscription group in Home. On iPhone and iPad, check the row's swipe actions. Use the menu that actually appears, and confirm you're removing a subscription source rather than an individual server.
- Read the confirmation: If a confirmation dialog appears, check the name and scope before proceeding. Don't delete several sources in a row; doing so makes it harder to tell which step caused entries to disappear.
- Update only the source you're keeping: After deletion, update the retained subscription and check the entry count, selected node, and routing state. If duplicates return, investigate which source they belong to instead of repeatedly deleting them.
If the number of nodes drops sharply after an update, pause cleanup. The provider may have changed the returned data, access to the URL may have changed, or the request may not have returned the expected format. Adding the same URL again will usually just create another group with the same problem. First check the original URL and the provider's status, then decide whether to import it again.
6. Common questions about organizing multiple subscriptions
Why did a node I deleted come back?
Check Home to see which subscription it belongs to. If the source still includes that node, an update may add it back. Once you've confirmed the source is valid, either keep the entire source or remove the redundant source after considering the impact. Repeatedly deleting individual entries isn't a lasting way to filter them out.
Two subscriptions have the same name. Can I delete one?
Open each subscription's edit screen and compare the full URLs, especially the paths and token parameters. Different tokens may correspond to different permissions or accounts. If the URLs are identical, make sure the group you plan to keep updates correctly and that your current connection doesn't depend on the group you plan to remove before deleting it.
Why am I still using the old node after sorting by latency?
Sorting changes the display order, not necessarily the selected node. Return to Home and check the selection indicator, then review Global Routing and the destination in the active Config. To switch nodes, select the intended entry explicitly; don't assume the first row is the active connection.
A subscription update failed. Should I delete and re-add it?
Keep the existing group for now. Check whether the URL was truncated or the token changed, and confirm the link's status with the original provider. If the current network can't reach the subscription URL, try updating on a network that can. The existing entries can still help you troubleshoot; deleting and re-adding won't fix a response problem on the remote end.
7. Checklist: review your subscriptions
The goal is to identify each source, keep records recoverable, and make connection choices easy to explain—not just to reduce the number of entries. Change one source at a time and review the results after each update; it's easier to find problems this way than by rebuilding the whole list at once. For more on rules and connection behavior, see the user manual or the setup guide.
- Every retained subscription has a clear source label, and its full URL is stored somewhere protected.
- No nodes were deleted just because they shared a name, and entries using different ports weren't treated as duplicates without checking.
- After updating subscriptions one at a time, you know which group each added, removed, or duplicate entry came from.
- The selected item in Home, Global Routing, and the active Config are all as expected.
- If you use On Demand, you've checked Settings → On Demand to make sure automatic reconnection isn't mistaken for an organization problem.
Get Shadowrocket and follow the setup steps
The iPhone and iPad app is a one-time $2.99 purchase on the App Store. The Mac (Apple silicon and Intel), Windows, Android, and Linux versions are free. Check the App Store listing for iPhone and iPad system requirements. The developer listed on the store is Shadow Launch Technology Limited. See the download page for instructions for all platforms; desktop and Android installers are provided on this site.