This guide is for users who already have their own service provider and subscription details. When organizing Shadowrocket, first distinguish subscription sources, nodes returned by subscriptions, and manually added nodes. Name entries by source, update one group at a time, check for duplicates, and remove subscriptions you no longer use. The goal is to preserve updateable source entries, not just shorten the current list.
1. Understand Subscribe, the Node List, and Config
A subscription is a URL used to retrieve node details; a node is a server entry used to connect. One Subscribe entry can return multiple nodes, and adding the same subscription twice may create two separate source groups. Seeing two entries with the same name in Home does not automatically mean one should be deleted.
Home is mainly for viewing nodes, choosing a connection, and managing subscriptions; Config is for configuration files and rules; Settings is for app preferences. Organizing subscriptions does not mean editing Config, and there is no need to change Global Routing first. The steps below use the common iPhone / iPad interface as a reference. Menu locations and interactions may differ on other platforms, so gestures such as swiping or long-pressing should not be assumed to work the same way everywhere.
For example, the same address may provide Trojan and VLESS connections; similar names do not necessarily mean they are the same node. Proxy, Direct, Config, and Scene under Global Routing affect how traffic is handled—they are not subscription categories. Switching from Config to Proxy will not merge duplicate subscriptions or reorder groups.
2. Group by Source: Name Entries Before Updating
Groups should first answer “Where did these nodes come from?”—only then should you decide which region to put first. Keep one recognizable entry for each valid subscription. If your provider includes multiple regions in one subscription, there is no need to import the same URL repeatedly just to group by region. Source groups and traffic policies are different things.
- Record the current setup. In Home, note each subscription name, the number of nodes in each group, and the node currently in use. Back up configuration details you maintain yourself, and store subscription URLs securely elsewhere. Do not assume that exporting a Config includes all subscription credentials.
- Open the subscription editor. From Home, open the information or editing option for the relevant subscription and check its URL. To add one, use Home’s add option, set Type to Subscribe, and enter your own URL. Do not paste a complete subscription URL into a single node’s server address field.
- Use consistent names. In fields such as Remarks, use labels like “Source A | Daily” and “Source B | Backup.” To rename an existing entry, edit its remark rather than adding the same URL again.
- Save and update each source separately. Return to Home and use the update option for that subscription. Check that its nodes appear under the expected source. Process one source at a time so you can tell which action changed the count.
How to label a daily-use source
- Remark
- Source A | Daily
- Type
- Subscribe
- Verify source
- Compare with the complete URL you saved
- Organization goal
- Keep one entry for each valid source
Remarks help identify sources; they do not change server settings or subscription contents.
How to label a backup source
- Remark
- Source B | Backup
- Type
- Subscribe
- Credential storage
- Keep it in your own secure records
- Update check
- Test nodes only after confirming the update succeeded
“Daily” and “Backup” are custom remarks, not built-in connection policies.
Subscription URLs often contain access credentials. When checking them, compare the complete URL, including query parameters. If you report an issue to someone else, hide tokens, passwords, and any information that could identify your account. Do not assume two subscriptions have the same source just because their URLs share a domain.
3. Sort Subscription Groups and Nodes Separately
Sorting can mean three different things: changing the display order of subscription sources, viewing the node order within a source, or temporarily choosing a node by latency. Decide which level you want to change, then use the editing or sorting controls available at that level. Sorting options may vary by platform; do not assume that a drag gesture on one platform is a universal menu option.
| Organization goal | What to sort | What to check after updating |
|---|---|---|
| Put frequently used sources first | Subscription groups in Home; reorder them using a drag handle if edit mode provides one | If there is no manual sorting control, use clear remarks to identify groups instead of repeatedly deleting and re-adding them |
| Find a region by name | Nodes in the current group; use the name sorting or filtering options actually available in the interface | If your provider changes node names, their previous name-based order may change |
| Find an available node for now | Run a latency or connectivity test for the current group, then review the results | Test results vary with network conditions and do not represent a permanent ranking |
If the current interface does not offer the sorting option you need, note each source’s purpose in its remark and find nodes by name. There is no need to re-import a whole group just to create an order. Subscription updates may reload the names and order supplied by your provider, so do not treat a temporary display order as a permanent custom list.
Bottom line: Label each source first, then choose a node within its group
Use “Source A | Daily” to find the right group, then test the node you need from that group. Do not delete other sources based on a single latency ranking, and do not assume that lower latency means better page loads, download speeds, or sustained connections.
4. Update Each Group—Don’t Add It Again
Updating a subscription retrieves new content for an existing source; importing it again may create another source entry. This is one of the first things to check when your node list keeps growing. To get the latest nodes, update the original Subscribe entry rather than scanning the same subscription QR code or pasting the same URL again each time.
- Before updating, note the group’s node count and currently selected node. Avoid changing multiple sources at once.
- Update the existing entry and first confirm that the operation succeeded. A timeout, a parsing error, and a successful response with no content are different outcomes; a list that has not changed does not tell you which one occurred.
- After updating, check node names and counts. If the count jumps, first check whether a second subscription group was added, then check whether the original group actually gained entries.
- Choose a node confirmed to belong to that source and test the connection. If needed, check Global Routing in Home as well, so you do not mistake traffic routed through Direct for a test of the selected proxy node.
Suppose you start with 12 nodes in Source A and 8 in Source B, for 20 total. If you import Source A again and a second A group appears, the total could rise to 32. This example illustrates duplicate imports; it is not a guaranteed result of an update. If there are still only two source groups, check the returned content instead of immediately deleting the 12 new entries.
If an update fails, keep the existing entry and check that the subscription URL is complete, the credentials are valid, and your current network can reach the URL. If Settings → Subscribe offers Update via Proxy, enable it only if appropriate for your access conditions; updating through a proxy also requires an existing working connection. Do not clear all nodes before confirming that you can retrieve the content again.
5. Remove Duplicate Nodes: Compare Parameters, Not Just Names
A matching name, a matching address, and the same connection are not the same thing. A node name is only a display label; the connection also depends on the protocol, server address, port, authentication fields, and settings such as TLS and transport. Before cleaning up, determine whether duplicates are at the subscription-source level or within a source’s node list.
- Same name, different ports: For example,
443and8443on the same server are different endpoints. Do not merge them based on name alone. - Same address, different protocols: Shadowsocks, VMess, VLESS, Trojan, Hysteria2, and WireGuard use different connection parameters. Sharing a domain does not make their entries duplicates.
- Same protocol and endpoint, different credentials: Entries with different passwords, UUIDs, or keys cannot be assumed interchangeable. Do not share screenshots that reveal these fields.
- The same URL appears in two source entries: First confirm that the complete URLs and returned content match. Keep one source that updates successfully and remove the duplicate entry.
- Matching parameters within one source: Note the differences and check with your own service provider. If you delete an entry only locally, it may reappear on the next update.
Manually added nodes are generally not part of a subscription’s update content. Even if one uses the same endpoint as a subscribed node, deleting the subscribed entry may not affect the manual one. Check source groups and standalone entries separately, and do not mistake a same-named node left in the list for a failed deletion.
Bottom line: Remove duplicate sources at the source level; check returned data for duplicate content
If the complete URL is duplicated, remove the extra Subscribe entry first. If there is only one source but duplicates return after an update, check the subscription’s returned content. This avoids having to delete the same entries manually after every update.
6. Before Deleting a Subscription, Check Connections and Config References
Deleting a single node, an entire subscription source, and a Config file are three different operations. Before removing a source, check whether it contains the node currently in use and whether any policy selections in Config still refer to its names. Removing a group can leave references broken or change the selected item, causing connections to behave differently than expected.
- Save any information you need. Store the subscription URL securely and note any remarks you want to keep. Confirm that you can recover the information before making an irreversible deletion.
- Switch the current node. If you are using a node from the source you plan to remove, first select another tested, working node. Disconnect before cleanup if necessary.
- Open the source-level controls. In Home, find the exact subscription name and use that entry’s edit, swipe, or context-menu option. Make sure you have selected the entire subscription source, not an individual node.
- Read the deletion prompt. Check whether it names the source and its nodes, then confirm the deletion. Do not delete an unrelated Config file just to clean up the list in Home.
- Check references and connectivity. Return to Config to review the policy selections actually in use, then go to Home to check the selected node and Global Routing. Finish with a connection test.
Removing a Subscribe entry from Shadowrocket only clears a local record. It does not change your provider account, stop remote service, or automatically invalidate an old token. If a subscription URL has been exposed, reset its credentials in your provider account according to the provider’s procedures, then edit the existing local entry.
7. Common Questions About Managing Subscriptions
Why did a node reappear after I deleted it?
First check whether you deleted a node or the Subscribe source. If you deleted only a node within a group and the source still returns it, it may reappear on the next update. Check whether the same URL was imported more than once. If there is only one source, verify its returned content instead of repeatedly deleting the node.
Why didn’t changing a subscription remark rename its nodes too?
Subscription remarks and node names belong to different levels. A remark identifies the source; each node name comes from its own node entry. Return to Home to confirm that you changed the source entry. There is no need to add the subscription again just to make all the names match.
The update succeeded, but I can’t find a node I had before. What should I do?
Check the name, address, and protocol in the original source first to see whether the node was renamed or reordered. If it was removed, choose another available node in the group and check whether Config still refers to the old name. Do not restore a duplicate subscription just because the old name is missing.
Will multiple subscriptions automatically share traffic?
Importing multiple sources does not automatically distribute traffic across them. Actual outbound routing depends on Global Routing in Home, the selected node, and the rules and policies in Config. Organize your sources first, then check connection policies separately; the number of subscriptions does not determine which connection traffic uses.
A simple maintenance routine is to check source names, update one group at a time, investigate unusual node counts, and test the current node. Shadowrocket does not provide, sell, or recommend nodes or subscriptions; this guide explains how to manage information you already have. Get the app separately from service details—a client download does not include a connection plan.