When managing multiple subscriptions, verify their sources first, arrange their display order, then deal with duplicates. This guide assumes you already have your own provider and subscriptions. It explains the difference between subscription entries, nodes within a subscription, and configuration files in Shadowrocket, with steps for updating, cleanup, and recovery checks. This site does not provide, sell, or recommend nodes or subscriptions.
Understand subscriptions, nodes, and configuration files
A subscription URL can return multiple nodes. Each node contains the protocol and parameters needed to connect to a server. After importing multiple subscriptions, Home shows subscription sources and their node lists. Check which subscription a node belongs to rather than treating every entry with the same name as a duplicate. Rule files in Config match traffic; they are separate from the subscription list in Home.
Subscription update options in Settings affect how updates work. Settings → On Demand manages connection triggers; it does not group subscriptions or remove duplicates. Don’t change On Demand settings to clean up the list, or you may conflate a list issue with an automatic connection issue.
The steps below focus on managing subscriptions in Home. The location of edit, sort, and delete controls may vary by platform, so use the options available in your current interface. The items to check and the order of checks remain the same. Don’t assume a swipe gesture available on one platform is a button on every platform.
Group by source: keep one subscription entry per URL
Grouping is about identifying each source, not repeatedly copying nodes by region. Add a label that distinguishes each subscription you already have, such as “Personal — primary” or “Personal — backup.” Labels help identify sources; they don’t change server addresses, account access, or service periods, and they don’t turn two identical subscriptions into separate services.
- In Home, open each subscription’s edit screen and check its URL and Remarks. When noting a source, don’t share the full URL if it contains credentials.
- To add a subscription, open the add menu in Home, select Type → Subscribe, enter a subscription URL you already have, and add a label that helps you identify it. If the same URL is already listed, check the existing entry before adding another.
- Return to Home and identify each group’s nodes by its subscription title. If the current interface supports collapsing groups, collapse sources you aren’t using and expand only the group you’re checking to reduce the risk of deleting the wrong item.
- Update that subscription on its own, confirm that the returned nodes belong to the expected source, then move on to the next one. If the update fails, keep the existing entry and investigate the error instead of repeatedly importing it.
Two URLs that look different may return the same nodes—for example, if you updated your access credentials but kept both the old and new URLs. Conversely, nodes with identical names may belong to different accounts. Check your own service records to verify the source; names alone aren’t enough.
Sorting changes list order, not the active connection
When organizing the list, distinguish the order of subscription groups from the order of nodes within each group. Arrange the sources first, then sort the nodes within each group to make the right entry easier to find. If the current interface offers name or latency sorting, check what it applies to before using it; don’t assume one sort action affects every subscription.
Organize by source
- Item to organize
- Subscription entries in Home
- How to identify it
- Remarks and subscription URL
- Suggested order
- Primary source first, backup source next
- Check for
- Duplicate imports of the same URL
After arranging subscription sources, check the nodes within each group.
Organize by node
- Item to organize
- Nodes within one subscription
- Sort by name
- Makes nodes easier to find by their existing names
- Sort by latency
- Run latency tests on the same network first
- Check for
- Currently selected node and active routing strategy
Being first in the list doesn’t mean a node is selected or will automatically handle traffic.
Latency test results reflect the response under the network conditions and test method at that moment. They aren’t download speeds and don’t guarantee access to every website. If you switched between Wi-Fi and cellular before or after testing, don’t compare the results directly. Test again under the same network conditions.
- Global Routing → Proxy routes traffic handled by the proxy through the selected proxy mode. List order does not select a node for you.
- Global Routing → Config handles traffic according to the active configuration’s rules and policies. Changing the order in Home doesn’t change the policies referenced by those rules; check them separately.
- Global Routing → Direct isn’t a suitable mode for testing whether a proxy node works.
- Global Routing → Scene involves scene settings; it isn’t a subscription sorting feature.
Duplicate nodes after an update: find out where they came from
Before removing anything, compare nodes within each group, then compare across groups. Names are display labels only. To determine whether two entries represent the same connection, check at least the protocol, server address, port, and authentication parameters. For TLS, also check the actual connection settings, such as Server Name. Don’t change passwords, certificate verification, or protocol parameters just to tidy the list.
| What you see | Check first | What to do |
|---|---|---|
| Two groups have similar node names and counts | Are the URLs of the two subscription entries identical? | After confirming which source is valid, remove the duplicate subscription entry rather than deleting nodes one by one. |
| Two nodes in the same group have the same name | Do the protocol, address, port, and account parameters match? | If the parameters differ, keep both. If they match, check what the subscription returns. |
| A node reappears after you delete it manually and update | Is the node still included in the subscription’s returned list? | Address the source content. Deleting a node locally once won’t permanently change the remote list. |
| A standalone node outside the subscription has the same name | Did you import a link or copy a node separately? | Once you’ve confirmed the manual copy has no separate use, delete it. |
In short: remove duplicate sources at the source; check returned content for duplicates within a source
Keep one subscription that updates successfully, then remove redundant copies. If a single update returns duplicates, check with your own provider instead of repeatedly adding the subscription.
For example, two nodes with the same name may use ports 443 and 8443. Don’t delete one based on the name alone; those port numbers don’t identify the protocol either. Even when the address and port match, different accounts or transport parameters may represent different connections. If you can’t confirm, keep both and note their sources to avoid deleting a working configuration.
Remove an outdated subscription: check, delete, then verify
One timed-out update doesn’t mean a subscription is permanently unusable. A temporary network issue, a changed URL, an expired account, or an empty response from the remote server can all cause an update failure or an unexpected list. Check your own service records before deciding whether to edit the existing URL or remove a source you no longer use.
- Keep a way to restore it. Make sure you can still retrieve the subscription URL through your usual channel. If you need a backup, use an available in-app backup option and store it securely as sensitive information.
- Check what depends on it. See whether the currently selected node belongs to the subscription you plan to remove. If a policy group in Config refers to a specific node name, check those references too.
- Choose what to delete. Deleting a node is different from deleting an entire subscription. Before deleting a subscription in Home, confirm the target and read the confirmation prompt, especially whether it will also remove nodes from that source.
- Verify the remaining sources. After deleting, update only the subscriptions you still need. Check that the groups and nodes look as expected, then test access. If the currently selected node was removed, select a working one again.
Deleting a subscription in the app doesn’t cancel your provider account or revoke access to its URL. If the URL was exposed, reset its credentials through your own service channel; removing the entry from your device won’t invalidate an exposed URL.
Common questions about managing multiple subscriptions
Why does a deleted node come back after an update?
First, check which subscription the node belongs to. If the remote source still returns it, the node may reappear on update. Check the source content. If the same subscription was imported more than once, keep the working entry and remove the redundant one rather than deleting the node again after every update.
Can I remove duplicates with one tap based on node names?
Don’t use names as the only criterion. Open the node details in Home and check the protocol, address, port, and account parameters. Handle same-name entries with different parameters separately. If the current interface doesn’t offer a deduplication feature, don’t look for a fixed menu that isn’t there; check each group by source instead.
Should I delete and re-add a subscription if an update fails?
Keep the existing entry while you check whether the URL is complete, the account is active, and the current network can retrieve the subscription content. Retry only that source. Removing and re-adding won’t fix invalid credentials or a remote outage, and may lose the label and your local organization.
Why hasn’t anything changed after I moved a node to the top?
Return to Home and check which node is selected, then review Global Routing. If you’re using Config, also check which rules and policies are actually applied. Sorting only changes how items are displayed; it doesn’t change the selected policy or edit rules.
After organizing your subscriptions, make sure each source is identifiable, URLs aren’t duplicated, updates can be verified, and the active policy is clear. Use the same process whenever you add a subscription; it’s usually easier to troubleshoot than clearing and reimporting everything on a schedule. For more on how rules and policies work together, see Configuration Field Reference.
How to Get Shadowrocket
The iPhone and iPad version costs $2.99 as a one-time purchase on the App Store. The developer is Shadow Launch Technology Limited; check the App Store listing for system requirements. The Mac (Apple silicon and Intel), Windows, Android, and Linux versions are free. See the download page for platform-specific instructions; installers for other platforms are available from this site. Buying the app doesn’t include a proxy service subscription.
Go to Downloads View tutorials