This guide is for users who already use their own subscriptions in Shadowrocket and want to organize multiple sources. Start by labeling and updating each subscription, then distinguish list order from routing behavior, and finally check connection settings and remove duplicates. The examples use the iPhone / iPad interface. Save your original subscription URLs before making changes, and remember that deleting a local entry does not cancel your service.
1. Understand the Difference Between Subscribe, Nodes, and Config
A subscription provides remote connection details; nodes are the individual connection entries returned by that subscription. One subscription can contain multiple nodes, and the same connection may appear in more than one subscription. Seeing two identical names in Home does not prove they are duplicates. Deleting a node also does not stop the remote subscription from providing it again.
Config manages configuration files, which are mainly used for rules and related settings. It is not the same as the subscription list in Home. Renaming subscriptions does not reorder rules or automatically route specific domains through a particular subscription. Before you begin, note the currently selected node, the Global Routing mode, and the Config in use.
2. Add Subscriptions Individually and Label Their Sources with Remarks
The simplest way to organize multiple subscriptions is to keep each one as a separate entry, rather than merging all nodes into an untraceable list. Use Remarks to identify the purpose and source, for example, “Source A | Daily” and “Source B | Backup.” Avoid generic labels such as “Subscription 1” and “Subscription 2,” and don’t use node counts that may change after an update.
-
Record the Current Setup
In Home, note the selected node and Global Routing mode; in Config, check which configuration is active. Save existing subscription URLs in a secure personal location rather than relying only on the node entries in the list.
-
Add a Source
Go to Home → tap “+” in the upper-right corner → Type → Subscribe, then enter the complete subscription URL from your provider in URL. Keep all query parameters; don’t remove anything after the question mark.
-
Add a Remark
Enter a recognizable source and purpose in Remarks, then save and return to Home. To edit an existing subscription’s Remarks, use the edit option for that subscription. Be careful not to open the editor for an individual node.
-
Check Each One Separately
After adding each subscription, check the nodes it contains before adding the next one. To fetch the list again, pull down to refresh in Home and confirm that the target subscription appears. Don’t add the same URL repeatedly.
Remarks are local labels and do not change remote connection settings. Node names supplied by a subscription may change after an update, so add remarks to the subscription entry rather than relying on renamed nodes as a long-term way to organize them. If two entries have exactly the same URL, first check whether the same subscription was imported twice, then decide which one to keep.
3. Sorting Changes Display Order; Global Routing Determines the Route
Organize subscription sources first, then sort nodes within each group. If Home shows drag handles in Edit mode, use them to reposition the relevant entries. If the current list offers sorting options, check whether they apply to the current subscription or the entire list. Sorting controls can differ between platforms, so don’t assume an action in one list works the same way everywhere.
- For everyday browsing: Put frequently used sources first, backups later, and use clear remarks.
- To sort by latency: Run Connectivity Test first, then compare the results from that test. A timed-out entry has no valid latency to compare.
- After an update: Remote node order, names, and counts may change. Check the updated list to see whether your local ordering was preserved.
- For actual use: Being first in the list does not mean a node is selected. After testing and sorting, check the selected node and the policies in your configuration.
Keep “organizing the list” separate from “changing the routing mode.” The three common modes below are in Global Routing; they are not subscription groups or node priorities.
Config
ConfigRoutes connections according to the rules in the current Config. Before using it, confirm that the policy names in the rules are valid and that proxy policies point to the intended node or policy group.
Best for: everyday rule-based routing
Proxy
Routes connections within its scope through the proxy. This can help temporarily rule out the effect of ordinary routing rules. It does not merge multiple subscriptions into an automatically optimized list.
Best for: temporarily checking whether the selected node works
Direct
Routes connections within its scope directly. Even if a node is selected in Home, that does not mean web traffic is going through it in this mode.
Best for: checking direct access over your local network
In short: confirm the selected node after sorting
After sorting or updating, explicitly select the node you want to use, then check Global Routing. Don’t infer the current connection route from a node’s position in the list.
4. Verify the Returned List Before Testing the Connection
Updating a subscription fetches the remote list again; it does not repair nodes one by one. Entries removed remotely may disappear after a refresh, while new entries are added. Local changes to subscription-provided nodes may also be overwritten by remote data. Before and after updating, compare source remarks, changes in node count, and the selected node—not just whether the loading indicator has stopped.
- Check the relevant source in Home first, then pull down to refresh if an update is needed. If you have multiple sources, verify each result separately; one successful update does not mean they all succeeded.
- If the update times out, first check that your network is working. Then make sure the subscription URL is complete and its access credentials are still valid. Don’t try to “fix” it by adding the same URL repeatedly.
- If the subscription URL is unreachable over a direct connection but an existing proxy connection works, go to Settings → Subscribe → Update via Proxy to enable updates through the proxy, then return to Home and refresh.
- Once the list loads, select a node and run Connectivity Test, then test the page you actually need to access. A successful update only confirms that the subscription data was fetched; it does not mean every node can connect.
On Demand controls when connections are established based on conditions; it does not combine subscriptions on a schedule or remove duplicate nodes. If the connection status changes automatically during troubleshooting, check the conditions under Settings → On Demand. Note the original settings before changing them, then restore them afterward if they suit your needs.
5. Compare Connection Settings to Find Duplicate Nodes
Nodes with the same name may use different connections, while differently named nodes may point to the same one. A reliable way to compare them is to check the subscription source first, then Type, address, port, authentication, and transport settings. The examples below are fictional and do not represent working services.
Entry A: Trojan | node-a.example.com | 443 | Credential A | SNI edge-a.example.com
Entry B: Trojan | node-a.example.com | 443 | Credential A | SNI edge-b.example.com
Entry C: Trojan | node-a.example.com | 8443 | Credential A | SNI edge-a.example.com
A and B use the same address and port but different SNI values, so they cannot be assumed to be the same configuration. A and C use different ports, 443 and 8443, so their connection settings are not identical either. For other protocols, check their specific fields too, such as UUID for VMess / VLESS, the encryption method for Shadowsocks, and the corresponding transport settings.
- Duplicate subscription entries: If the same URL was imported twice, check the remarks and usage, then usually keep just one source entry.
- The same connection appears in different subscriptions: Keep track of each source and check whether both subscriptions still need to be updated independently before deciding whether to remove either one.
- Duplicates within a subscription: Deleting a node locally may only affect the current list. It may reappear after the next update, so ask your provider about the remote subscription data.
- Settings are not identical: Don’t delete entries in bulk based only on similar names or addresses, or a single matching latency result. Compare them field by field first.
In short: remove duplicate sources first
If you confirm that the same subscription was imported more than once, removing the extra subscription entry is easier to maintain than repeatedly deleting individual nodes it provides. If settings differ, keep the entries and compare them first.
6. Check What You’re Deleting, Then Verify References After Updating
Deleting a single node is not the same as deleting an entire subscription. Check what you’re acting on: an individual node within a group, or a Subscribe entry that represents a source. When using a swipe action or edit option in Home, verify the name and scope before confirming. Don’t delete multiple similarly named sources in succession without checking each one.
- Keep the original URL, subscription remarks, and identifying details for the currently used node if you may need to restore them.
- If the source you plan to remove is currently in use, switch first to another connection that you’ve verified works.
- After deleting the target entry, confirm that your other subscriptions are still there and that you haven’t removed a source you wanted to keep.
- Return to Config and check policies that depend on specific node names, so they don’t keep referencing a name that disappeared after a source changed.
Deleting a local subscription entry does not cancel your service or change your account with your provider. If a subscription URL is exposed, deleting its entry from Home will not invalidate the URL. Ask your provider to replace the credentials, then update the local entry with the new URL.
Why does a node name revert after an update?
Node names may be supplied again by the remote subscription. Put long-term labels in the subscription’s Remarks. If you change node settings, record what you changed and check them after each update; don’t assume local changes will be kept permanently.
A deleted node came back. Was it not removed?
First check whether it came from a recently updated subscription. If the remote list still contains the entry, it will reappear when refreshed. Check the source in the corresponding Subscribe entry instead of repeatedly deleting a node that is being fetched automatically.
The subscription updated successfully. Why can’t I open a webpage?
In Home, confirm that the selected node did not change during the update, then run Connectivity Test and check Global Routing. If you use Config, also check the matching rule and policy. See troubleshooting for detailed steps.
If I move a backup subscription to the top, will Shadowrocket switch to it automatically?
No. Changing the list order alone does not switch connections. Go to Home and select the node you want to use. If Config uses a policy group, check how that group selects a node too. Verify list order, manual selection, and policy group behavior separately.