Keep subscriptions organized by source: identify each group, arrange the list, then check for duplicates. This guide is for users who already have subscriptions. It covers identifying sources in Home, updating with Subscribe, sorting and deleting entries, and the differences between subscription nodes, manually added nodes, and Config policy references. This helps prevent removed entries from returning after an update and protects the connection you're currently using.
1. Understand Subscription Sources, Node Lists, and Config Policies
In Shadowrocket, subscription URLs retrieve a set of server configurations. Imported nodes appear in Home, while Config handles rules and policy settings. Adding two subscriptions to the list does not automatically combine them into a failover policy. Moving a group to the top does not guarantee that requests will use one of its nodes.
Before organizing your list, note the selected node and the current Home → Global Routing setting. Proxy, Direct, Config, and Scene are different routing modes; list order is not a routing setting. In Config mode, check which policies the active configuration actually references. The expanded group in Home alone does not tell you where traffic is routed.
2. Import and Name Subscriptions One at a Time to Avoid Duplicates
The steps below use Home on iPhone / iPad; menus may differ on other platforms. To add a subscription, open the add menu in the upper-right corner of Home, select Subscribe for Type, enter a URL you already have, and add a note to identify its source. To update an existing subscription, use its existing entry rather than importing the same URL again from the add menu.
- Import the first subscription and confirm that its group and nodes appear correctly in Home before adding the next one. This makes it easier to identify which source is causing a problem.
- Use notes that distinguish sources, such as “Personal—Primary” or “Personal—Backup.” Avoid generic notes like “Subscription,” and never include the full token.
- Expand each group and note its node count, a few representative names, and any displayed update time. If no time is shown, don't assume the update succeeded.
- Before adding a subscription, check the URLs of existing entries. An identical URL is a clear sign of a duplicate source, but different URLs may also return the same set of nodes and require further comparison.
The example URL https://example.com/sub?token=xxxx illustrates the URL format only and cannot be used to import a subscription. Query parameters in a real URL may determine what it returns. Don't remove them just to make the URL “look consistent,” and don't change its capitalization or encoding arbitrarily.
3. Grouping and Sorting: Organize Sources First, Then Nodes Within Each Group
Keep subscriptions grouped by source: put frequently used sources first, backups later, and delete sources you no longer use only after confirming they're no longer needed. Use the edit, sort, or group controls available in your current interface. Menus and gestures may vary across platforms, so don't assume an iPhone swipe is the standard way to do this everywhere.
| What to organize | How to organize it | What to verify |
|---|---|---|
| Subscription groups | Name groups by source; collapse backup groups if supported | You can still identify which subscription each entry belongs to |
| Manual order | Reorder items using the edit or sort controls in the current list | Check whether an update rebuilds the order from the source content |
| Sort by name | Standardize source notes first, then sort by name | Number and text prefixes can affect the sort order |
| Sort by test results | Run tests again on the same network, then sort by the results | Test latency is not the same as sustained download speed |
Tip: Choose a source first, then compare nodes within that group
Collapse groups you're not comparing, then test and sort the target group. This helps prevent nodes with the same name from different sources being mistaken for the same entry.
Sorting makes nodes easier to find; it doesn't change rules in Config. Subscription updates may also rebuild node names and order, so don't rely on an entry staying “at the top.” Clear source notes and records of the policies used by your active configuration are more reliable than memorizing list positions.
4. Identifying Duplicate Nodes: Matching Names Don't Mean Matching Connections
Nodes with the same name may come from different sources, while differently named nodes may connect to the same server. To check for duplicates, compare at least the protocol, server address, port, and authentication parameters. The fields to compare vary across Shadowsocks, VMess, VLESS, Trojan, Hysteria2, and WireGuard; an address alone can't confirm that two configurations are identical.
Entries that are more likely to be duplicate sources
- Source
- The same subscription was added twice
- Server
- Both use node-a.example.com
- Port
- Both use port 443
- Protocol parameters
- Protocol, authentication, and transport parameters match
Example domains are for illustration only. Before keeping one source, check the current selection and any references to it.
Entries you shouldn't merge based on name alone
- Name
- Both show the same region name
- Server
- Server addresses may differ
- Port
- They may use different ports, such as 443 and 8443
- Protocol parameters
- Authentication, TLS, or transport parameters may differ
The same port doesn't mean the same service, and matching names don't mean configurations are interchangeable.
Open the node details on your device to compare entries. Don't copy passwords, UUIDs, keys, or other authentication details into public records. If two subscriptions are different outputs from the same source, first confirm which format works with your client, then decide which to keep. Don't assume the subscription with more nodes is more complete.
- The same subscription was imported twice: Keep one source, switch the current selection, then delete the duplicate subscription.
- Two sources contain the same node: First check whether you still need other content from both sources. Don't rush to delete an entire group.
- A manual node duplicates a subscription node: Check whether the manual entry is an intentionally kept copy before removing it.
- Duplicates return after an update: The subscription still includes those entries. Deleting them locally doesn't guarantee they'll be absent from the next update.
5. Before Deleting an Inactive Subscription, Switch Nodes and Check References
One failed update isn't enough to conclude that a subscription is inactive. Check your device's network, confirm the URL is complete, and find out whether the original provider has replaced it. If only one node fails to connect, don't delete the entire source. Update the original subscription first, then check whether other nodes in the same group have the same problem.
- Note the subscription and node sources you plan to remove. If the selected node belongs to that subscription, switch first to a working node you intend to keep.
- If you're using a custom Config, check whether it references nodes from this source by name. Deleting the source won't update those references for you.
- Delete the subscription from its management menu. Read the confirmation prompt and make sure the action applies to the entire subscription, not just one node.
- Return to Home and check the groups and current selection, then test the connection with a destination you actually need to reach. A vanished entry alone doesn't mean the cleanup is complete.
If you only want to declutter the list temporarily, collapse the group instead of deleting and reimporting it. Changes to subscription-generated node names or connection parameters may be overwritten by a later update. If you need to manage a node independently, keep it clearly separate from subscription entries and check for updates yourself.
6. Updating Subscriptions and Troubleshooting Common Issues
After organizing your list, update subscriptions one at a time rather than adding every source again. After each update, check the group name, node entries, and current selection to tell whether the source content changed or the subscription was imported twice. Update options in Settings → Subscribe control how subscriptions are fetched; they don't set separate traffic-routing rules for each subscription.
Why are there more nodes after refreshing?
First check whether Home contains two subscriptions with different notes but the same URL, then identify which group the added entries belong to. If there's only one source and deleted nodes have returned, they are still included in the subscription's response. Repeatedly deleting individual nodes won't resolve the cause.
A subscription update timed out. Should I delete and re-add it?
Keep the existing entry for now. Confirm the URL is complete and check your network. In Settings → Subscribe, check Update via Proxy. Change this setting only if you have a working proxy and the subscription URL needs to be accessed through it; then retry updating the existing subscription based on your network conditions.
Why isn't the node at the top of the list being used?
Return to Home and check the selected node and Global Routing. Sorting the list doesn't turn Direct into proxy routing. In Config mode, also check the rules and policies in the active configuration. List position doesn't determine where traffic goes.
I deleted a subscription. Why does its name still appear in Config?
The subscription list and configuration file are separate layers. Open Config, check the active configuration, and find any policy references to the old node name. Replace them with an available target, then test. Don't delete the entire active configuration just to remove an old name.
7. Final Checks After Organizing Subscriptions
A successful cleanup leaves sources identifiable, prevents duplicate imports after updates, and makes the current route easy to verify. The goal isn't to minimize the node count. If different sources are clearly named and their purposes are understood, matching node names don't necessarily need to be merged.
- In Home, check the note for each group and keep only the subscription entries you need from each source.
- Update each subscription separately and check for duplicates again to make sure you haven't added the same source twice.
- Check the selected node and Global Routing. In Config mode, also review references to the relevant policies.
- If Settings → On Demand is enabled, check the automatic connection conditions so a connection change after switching networks isn't mistaken for a sorting result.
- Test the connection to a destination you actually use. Store subscription URLs securely, and never include full credentials in screenshots or public support requests.
For future maintenance, update existing entries rather than reimporting them. Change the relevant URL when a source changes, and delete the entire source only after confirming it's no longer needed. Keeping these actions separate reduces duplicate nodes and makes troubleshooting easier.
Download Shadowrocket and Continue Setup
Get the iPhone / iPad version from the App Store for a one-time $2.99 purchase. The Mac (Apple Silicon / Intel), Windows, Android, and Linux versions are free. Check the App Store listing for iPhone / iPad system requirements. Developer: Shadow Launch Technology Limited. Find platform download options on the download page, and follow the guide for your first connection and Config setup.