When managing multiple subscriptions, keep them grouped by source and distinguish display order from the selected node and routing policy. This guide assumes you already have subscriptions from your providers. It walks through adding, checking, updating, and removing subscriptions in Home on iPhone and iPad, and explains how to identify duplicate nodes. Start by checking for duplicate subscription sources rather than deleting entries in bulk just because their names look alike.
1. Understand the difference between subscription groups, nodes, and Config
A Shadowrocket subscription is a source of remote nodes, not a single fixed node. Updating a subscription fetches its latest content. Nodes in Home are individual connection settings, including the protocol, server address, port, and authentication details. Config holds settings such as rules; it is separate from the subscription list in Home.
You can keep multiple subscriptions in Home, each as a separate group. Identifying sources by subscription name is easier to maintain than copying all nodes into one manual list. Expand a group to view its nodes, or collapse it to browse other sources. Collapsing a group only changes what is displayed; it does not disable the subscription or switch the selected node.
2. Add multiple subscriptions one source at a time
Before adding a subscription, check whether the same source is already in Home. Subscription URLs often contain access credentials, so a display name alone cannot tell you whether it is new. Don’t share screenshots containing a full token publicly. The address below is an example format, not a working subscription.
https://example.com/sub?token=xxxx
-
Open the add screen
Go to Home, tap “+” in the upper-right corner, and select Subscribe under Type. Don’t enter a subscription URL in the Address field for an individual node.
-
Enter the source URL
Paste your complete subscription link into URL and check the beginning, path, and query parameters. Don’t remove the token or edit parameters to make the address shorter.
-
Add a remark
Enter a remark in Remarks that helps identify the source, such as “01-Daily-A” or “02-Backup-B”. Don’t include a password, full email address, or subscription credentials.
-
Save and verify
Tap Done to save, return to Home, and wait for the results. Expand the group to check its nodes. Once the import succeeds, add the next subscription. To fetch the latest content again, pull down on Home to refresh.
If the same source is already there, open that subscription’s edit screen and check its URL instead of adding it again with “+”. If your provider changes the subscription address, keep a secure backup of the old URL before editing the existing entry. This helps avoid confusion from having both the old and new groups in the list.
Numeric prefixes in remarks make sources easier to identify consistently. They may affect the order when sorting by name, but they don’t force the same display order across every screen or change connection priority.
3. Grouping and sorting: display order is not connection priority
First decide what you want to achieve: make frequently used sources easier to find, or find a node that connects on your current network. For the first, use subscription remarks, group collapsing, and list sorting. For the second, use connection tests and check actual access. Don’t assume the first item in the list is the primary node for automatic failover.
| What to organize | What to do | What to check |
|---|---|---|
| Subscription groups | Use different Remarks for each source. Expand the group you want to view and collapse the others. | You can clearly identify which source each node belongs to. |
| Name order | Use the list’s name-sorting option. Standardize names first, then check the order. | The names are reordered, but don’t infer which node is selected from its position. |
| Test result order | Run Connectivity Test in Home, then use the available option to sort by test results. | Compare results only on the same network and using the same test method. |
| Node used for the connection | Select the node you want in Home and check the selected indicator. | Make sure a specific node is selected; expanding a group alone doesn’t select one. |
Sorting controls may vary by platform and screen. Use drag-to-sort only if the interface explicitly offers it; don’t mistake an edit action in a long-press menu for sorting. If the option you need isn’t available, keep sources grouped and use consistent remarks. There’s no need to repeatedly delete and re-import subscriptions just to change their display order.
Bottom line: check the selected node, then check the order
After sorting, select the node you want to use again and check Global Routing. A tidier list is just an organizational change; verify separately whether the active connection has switched.
Connectivity Test reports reachability or latency under specific test conditions. It does not measure sustained download speed or prove that every website is accessible. Track node counts, test results, and display order separately after an update. Don’t mistake “new entries moved to the top” for “the active node switched automatically.”
4. Update subscriptions and remove expired sources
A failed update doesn’t necessarily mean the whole subscription has expired. First check whether the error is a network timeout, an authentication failure, or content that couldn’t be parsed. Then decide whether to remove it. If a source still provides a working connection, don’t clear all its nodes before troubleshooting—you may need them to test the update path.
- Manual update: Return to Home and pull down to refresh. Wait for the source to respond, and check whether other subscriptions are failing too. If they all fail, start by checking your device’s network connection and the fetch path.
- Fetch via proxy: If a direct connection can’t fetch the subscription and you already have a working node, connect first. Then go to Settings → Subscribe, check Update via Proxy, turn it on if needed, and retry.
- Authentication errors: If you see HTTP 401 or 403, check your subscription credentials and account status. Changing the node order won’t fix an invalid token.
- Unexpected content: If the response is a login page or error page rather than parseable subscription content, check that you copied the complete URL and ask your provider to verify it.
Before deleting, check these three things
- Make sure you’re deleting the subscription source, not a single node within its group. Deleting a source usually removes the nodes it manages. If the confirmation dialog offers an option to keep them, check what that option does before proceeding.
- Keep any URL you still need somewhere secure, along with its remark and essential update settings. Backing up the Config file alone does not back up all subscription credentials.
- If the selected node belongs to this source, select another working node first. Then delete the target subscription from Home. On iPhone or iPad, check the swipe actions and verify the name and confirmation prompt before proceeding.
After deleting, return to Home and check the groups and selected node, then run another connection test. Removing a local subscription does not close your provider account, end remote service, or revoke a token. If you’re deleting it because credentials were exposed, reset them in your own service management portal too.
5. Remove duplicate nodes: check the source, then the connection settings
Nodes with the same name aren’t necessarily duplicates, and different names don’t necessarily mean different connections. Compare the protocol, server address, port, authentication details, and relevant settings such as TLS, SNI, and transport. For example, 443 and 8443 are different ports on the same server, so don’t merge them just because the address matches.
| What you see | What to check first | What to do |
|---|---|---|
| Two groups contain almost the same entries | Are the subscription URLs identical, or are they the old and new addresses for the same account? | Once the new address updates correctly, keep only the source you need. |
| A group contains entries with the same name | Do the protocol, address, port, or transport settings differ? | Keep entries with different settings. If they’re identical, check the source list. |
| A manual node looks like a subscription node | Was the manual entry copied from a subscription as a backup? | Once you’ve confirmed the subscription entry works, remove the manual copy if you no longer need it. |
| A manually deleted node comes back after an update | Does the remote subscription still include that entry? | Edit the source list or use a subscription filtering option if the interface provides one. |
Don’t assume there’s a deduplication button that can safely merge entries across all sources. Automatically deleting by name can remove entries that use different protocols; deleting by address can remove connections with different ports, authentication, or transport settings. If a node is managed by a subscription, a local edit may also be overwritten the next time it updates.
A safer order is to remove duplicate subscription sources first, then remove manually copied entries, and finally check for duplicates within the source list. Record the number of entries in each group before and after cleanup, then check again after the next update. If the same entries return, the issue is still in the remote content or duplicate import process—not that the delete action failed.
6. Check Global Routing after organizing subscriptions
If you see no change in access after organizing subscription groups, check Home → Global Routing. It determines how connections select a policy; subscription order does not. The comparisons below apply only to Shadowrocket’s own settings.
Config
RecommendedSelect policies according to the rules in the currently enabled configuration. Check the active Config and the policies used by rules such as DOMAIN-SUFFIX, IP-CIDR, GEOIP, and FINAL.
Best for: everyday use with existing routing rules that you want to keep applying.
Proxy
Route intercepted traffic through the proxy. This can help you temporarily check whether rules are affecting access to a destination; make sure the selected node is working.
Best for: briefly testing the selected node and narrowing down a rule-related issue.
Direct
Connect intercepted traffic directly. In this mode, changing the node in a subscription usually won’t produce the expected proxied access.
Best for: checking direct connections on your local network.
Scene
Route traffic according to configured scene conditions. Check which scene matched and which policy it uses; the node order in Home isn’t enough.
Best for: setups with configured scenes and a clear purpose for each one.
If switching nodes makes no difference, check the selected indicator, connection status, Global Routing, and the rules that actually match—in that order. Don’t test switching by adding the same subscription again; that only creates duplicate sources in the list.
7. Frequently asked questions about managing multiple subscriptions
Why did the node order change after an update?
The source may have returned the nodes in a different order, or entries may have been added or removed. Apply your preferred sorting again after the update and check the selected node. Don’t identify a connection by its position as “the first node.”
Can I combine two subscriptions into one?
Copying nodes creates manual entries, but it doesn’t create a merged subscription that stays in sync. To keep updates from each source, keep the Subscribe entries separate. Don’t combine two URLs in a single URL field.
The update succeeded. Why weren’t any nodes added?
A successful update means the content was fetched and parsed; the source may not have changed. Expand the group and check the names and entry count. If filters are configured, check whether they’re hiding new entries.
Will deleting a node affect other subscriptions?
First make sure you’re deleting an individual node, not a subscription group. They have different effects. Check which source the node belongs to, then verify that the other groups are still there after deletion. Don’t identify the item by name alone.
Is restoring Config enough when moving to a new device?
Don’t assume it is. Save subscription URLs and remarks securely as well. On the new device, check the sources in Home, then make sure the rules and policies in Config can still find the relevant nodes or policy groups.