For users who already have their own service provider and subscriptions, this guide covers checking sources, organizing groups, changing display order, checking for duplicates, removing old entries, and reviewing updates. It distinguishes subscription records, nodes within a subscription, and policy groups in Config, so identical names aren't mistaken for duplicates and removed items don't return on the next update. The steps use the iPhone / iPad interface; on other platforms, use the equivalent options available in the app. This site does not provide, sell, or recommend nodes or subscriptions.
Subscriptions, Nodes and Policy Groups: What's the Difference?
Most subscription organization in Shadowrocket takes place in Home. A subscription is a source for retrieving a list of nodes; a node is an individual connection configuration in that list; policy groups in Config let rules reference a selection or testing policy. These are related but not interchangeable. Changing the remark for a group of nodes in Home to “Daily” does not create a policy group named “Daily” in Config.
First identify which layer you're editing, then decide whether anything needs to be removed. Removing a subscription manages its source; editing rules manages configuration; Settings → On Demand controls when connections are triggered and does not organize subscriptions. Keep the three interface locations and four Global Routing options below distinct when troubleshooting.
Organizing the list does not change Global Routing. Proxy, Direct, Config and Scene are different traffic-handling options. For example, with Direct selected, choosing a node in Home does not mean the current request is routed through that node. Note the current option before cleanup, then restore the same test conditions afterward.
Import by source: give each subscription a clear name
Before adding a subscription, expand the existing groups in Home and check the URL and remark on the subscription's edit screen. The same source might appear in the list after being imported both from a link and in a batch; different names don't mean different sources. Conversely, different paths or tokens on the same domain may return different content, so comparing domains alone isn't enough.
- Keep a record of your existing subscription sources somewhere secure, along with their corresponding remarks in Home. Subscription URLs may contain access credentials, so don't include the full link in a public screenshot.
- If you need to add a subscription, tap the add button in the upper-right corner of Home, select Subscribe under Type, then enter your own subscription URL and a recognizable remark.
- Save and wait for the list to load. Confirm that the new nodes appear under the expected subscription group instead of relying on the total node count to determine whether the import succeeded.
- If an existing subscription's URL has changed, edit the existing subscription record first. Keep both records temporarily only when you need to compare the old and new lists side by side.
Use remarks that identify both the source and its purpose, such as “Personal subscription A | Daily” and “Personal subscription B | Backup.” Don't include live latency results in subscription names: test results change, while group names should remain stable. Avoid using only a region name, too; if both sources include the same region, it becomes difficult to tell which subscription a node belongs to.
Group and sort: find the right node before comparing latency
When organizing nodes, first view them by subscription source, then adjust the display order within each group. If the list is filtered or a search is active, clear the criteria first so that hidden items aren't mistaken for deleted ones. Whether renamed nodes and manual sorting persist after an update depends on the current version's update behavior and the content returned by the source. Don't rely on local changes as a long-term maintenance strategy.
Daily source record
- Subscription remark
- Personal subscription A | Daily
- Where to look
- The corresponding subscription group in Home
- What to check
- URL, node count, currently selected item
- Why sort
- Keep the lookup order consistent to avoid selecting the wrong item
Names identify the source; they don't indicate connection quality or a recommended order.
Backup source record
- Subscription remark
- Personal subscription B | Backup
- Where to edit
- The edit screen for the corresponding subscription in Home
- What to check
- Whether the source is separate and was imported more than once
- Why sort
- Keep it separate from your daily source, and find it when needed
Whether to combine the two records depends on the actual connection settings.
- Change the display order: Use the editing or sorting option available in Home. If there's no drag handle, don't mistake another action that appears after a long press for sorting.
- Find by name: Useful when you remember a node's identifier. Numbers in a name are just source labels; they don't indicate bandwidth, load or actual location.
- Check latency: Run Connectivity Test for all nodes in the same test session, then review the results. A timeout means only that this test didn't finish in time; it doesn't prove that the subscription is invalid.
- Keep your selection: Confirm the selected item again after sorting. Changing an item's position in the list is not the same as changing the active connection.
Duplicate Nodes: Matching Names Aren't Enough
First check where the duplicates appear. If an entire subscription group is duplicated, check the subscription URL first. If only some entries within a group share a name, open their details and compare the connection settings. Different protocols supported by Shadowrocket use different authentication and transport fields, so matching only the address and port isn't enough to establish that two entries are identical.
| What you see | What to compare | How to decide |
|---|---|---|
| Two groups contain nodes with the same names | Subscription URLs, source records and settings within each group | Once you confirm the same source was imported twice, keep one source record |
| Same name and server address | Protocol, port, authentication and transport settings | They may still be different connection configurations; don't delete either one yet |
| Same address, different ports | For example, ports 443 and 8443, and the protocol used for each | Treat them as different connection configurations; the port examples don't imply an available service |
| An item returns after deletion and an update | The original list returned by the source | The source still includes the item; deleting it locally didn't change the remote list |
For VLESS or VMess, compare the identity and transport settings as well as the server and port. For Trojan and Hysteria2, check their respective authentication and TLS settings. The Shadowsocks encryption method and password are also part of its configuration. For WireGuard, check the corresponding fields, including keys and peers. Compare settings on your own device and don't share credentials publicly.
Bottom line: remove duplicate sources before handling duplicates within a group
If two subscription records point to the same source, removing the extra source is more effective than deleting nodes one by one. Only decide whether to keep both lists after confirming that the sources are different and the connection settings match.
Don't assume there's a one-tap deduplication option that works for every protocol. If the current interface offers a cleanup feature, check its comparison scope before using it and keep a source record you can import again. If you're unsure about an entry, keep it and add a remark; that's easier to undo than deleting a batch based on names.
Remove an Expired Subscription: Switch Connections First, Then Remove the Source
Before deleting anything, distinguish between a failed subscription fetch and a failed connection through a node in the subscription. The first means the list couldn't be retrieved; the second means an existing connection configuration couldn't complete communication. A temporary network issue, a change in subscription authorization or an empty remote list can all look like an update failure, but each requires a different response. Don't clear every subscription after the first timeout.
- Confirm an alternative connection: If you're using a node from the subscription you plan to remove, first select another configuration you've confirmed works, or disconnect when appropriate. This helps prevent losing network access while you organize the list.
- Keep recovery information: Privately record the subscription URL and remark. If you already have a secure copy of the original details, there's no need to make an extra screenshot containing credentials.
- Remove the intended source: Find the subscription in Home and use its edit or delete option. On iPhone / iPad, if a swipe action is available on the row, open it by swiping left. In the confirmation dialog, check whether you're removing the entire subscription or just one node.
- Check the result: Make sure the group and its entries were removed, and check for any manually copied nodes elsewhere. Don't mistake a local copy for a failed subscription deletion.
- Check configuration references: If a policy group in Config references the name of a removed node, open the current configuration and check its references and available options before resuming normal use.
Deleting a local subscription record does not change the status of your remote account or revoke credentials in a URL that has already been exposed. If you're deleting it because the URL was leaked, manage the credentials through the original source's account settings, then update the subscription URL on any devices that need it.
Review After Updating: Trace Duplicates to Their Source
After organizing the list, update one subscription at a time. Check the group's node count, names and currently selected item before updating the next source. If duplicates return, you'll know which source or import caused them instead of facing a full page of similar entries after updating everything. When comparing counts, remember that a source may legitimately add or remove nodes.
- Before updating, note the number of entries in each source. Afterward, check that each source still appears only once.
- If an update restores an item you deleted manually, first check whether it's still in the remote list. Don't add the subscription again to “replace” it.
- If only the name changed, compare the connection settings instead of assuming the renamed entry is a new node.
- After Connectivity Test, verify the connection using the same network and test destination. This helps avoid attributing network changes to sorting.
Why does updating the same subscription add another group?
In Home, check whether you imported the same link again using the add button. Update an existing subscription record instead of creating a new Subscribe record. If two records do point to the same source, keep the one you've verified, remove the extra record, and check the list again.
Why do deleted nodes come back after an update?
Updating a subscription retrieves the source list again; deleting an item locally doesn't change the source. First check which subscription provides the item. If the source keeps returning it, review display filters or manage the source instead of repeatedly deleting it as a permanent fix.
Should I delete and re-add a subscription after an update timeout?
Keep the record for now and check that the URL is complete, then check your network and Global Routing. If the subscription URL needs an existing connection to be reached, check Settings → Subscribe for Update via Proxy. Before enabling it, confirm that an existing connection works to avoid a loop where the subscription can neither update nor connect.
Why isn't traffic routed as expected after sorting and selecting a node?
Return to Home and check Global Routing. Sorting nodes won't change Direct. With Config selected, check the rules and policy groups in the current configuration; with Scene selected, check which scene is active. Confirm how the request is actually being handled before deciding whether the node selection took effect.