How to Manage Multiple Shadowrocket Subscriptions: Groups, Sorting, Updates, and Duplicate Nodes

Understand Subscribe entries, the node list, and Config

A Subscribe entry stores a subscription URL and retrieves the content returned by that URL when updated. Nodes shown in Home are connection entries imported or generated during an update; Config is where rules and policies are configured. These are related, but they are separate layers: changing the display order in Home does not change rule order in Config or the order returned by the subscription source.

For example, if you have two subscription sources, A and B, plus a manually added node, first identify which source each belongs to before making changes. Don't delete one just because two entries are both named “Backup.” Matching names only mean the display labels are the same; they don't prove the server address, port, protocol, or authentication settings match.

Group multiple subscriptions by source using remarks

In everyday use, “subscription groups” should mean organizing nodes by their Subscribe source—not creating a policy group with the same name. Give each subscription entry a stable, recognizable Remarks value, such as “Personal Line A” and “Personal Line B.” Don't put the full subscription URL in a remark or use a number that changes with latency results to name a source.

1. Open Home and review the existing subscription groups and their headings. Check whether the address you want to add is already there.
2. If you need to add one, tap the add button in the upper-right corner. On the add screen, set Type to Subscribe, then enter the URL and Remarks. Field locations may vary by app interface.
3. After saving, return to Home and check the new entry's group and the nodes it returned. If the same URL is already listed, edit the existing entry instead of adding it again.
4. To edit an existing subscription, open the action menu from its group heading in Home and choose the edit action. Check the URL and Remarks, then save. Make sure you're not opening the settings for an individual node.

Query parameters in a subscription URL may contain access credentials. To check whether two URLs match, compare the complete values—but never share them in public screenshots, chat messages, or troubleshooting reports. The URL below only illustrates the field format; it is not a usable subscription. Always use a URL you already have.

Update individually: confirm the target, then check the result

When you have several subscriptions, update one source at a time while troubleshooting. This helps determine whether a particular URL failed or the current network is affecting all subscriptions. Bulk updates are useful for routine maintenance after you've confirmed that each source works, but not for diagnosing a new issue.

1. In Home, find the group heading for the subscription you want to update. Touch and hold it to open its action menu, check the heading, then select the update action. Menu wording and available actions may vary by interface.
2. Wait for the request to finish and review the success or error message. Don't trigger the update repeatedly.
3. Return to the target group and check that the node names and contents look right. A successful fetch doesn't guarantee that every node can connect; test connections separately.
4. If only one source fails, open that subscription's edit screen and check the URL. Look for spaces or line breaks added during copying, or missing query parameters.

For a timeout, distinguish between an unreachable subscription URL and content that can't be parsed. For the first, check network access and whether the URL is valid. For the second, confirm that the returned content is still in the expected format for that subscription. Don't import an error page as new nodes, and don't assume a subscription request is working just because a webpage opens in a browser.

Manual sorting: display order isn't policy selection

Before sorting, decide which order you want to change: the subscription groups, the nodes within a group, or the candidate order in a Config policy. These are not interchangeable. Moving a node to the top of Home doesn't make rules use it automatically; the actual connection also depends on Global Routing and the current configuration.

• Manual reordering: In Home, look for a list editing or sorting option. If the current list has an Edit option and drag handles, enter edit mode, drag the row you want, then finish editing. Only drag items at levels that show handles; a long-press menu for a node is not a sorting control.
• Automatic sorting: If the current interface offers sorting by name or latency, first check what the setting applies to. Sorting by latency can change as test results change, so it isn't a reliable way to keep source groups in a fixed order.
• Order after an update: Updating a subscription may regenerate its list. Note the current order, update once, and check whether the order is preserved. If it reverts to the source order, don't rely on local positioning to maintain long-term categories.
• No sorting option: Different list levels may offer different actions. If there's no edit or drag control, don't repeatedly delete and re-add entries to “reorder” them. Use subscription remarks to keep sources identifiable.

When using Config with Global Routing, the current configuration determines the rules and policies. Proxy and Direct handling are also separate from list order. You don't need to change Global Routing just to move an entry higher in the list, and changing FINAL is not a fix for display order.

Remove duplicate nodes: check for duplicate sources before comparing connection settings

Duplicates most often come from adding the same subscription URL more than once, or from two different subscriptions that contain the same connection. Handle the first case to avoid seeing the same entries again after future updates. Deleting a single subscription-generated row usually won't keep it from returning the next time the subscription updates.

For example, ports 443 and 8443 on the same server are different endpoints. Two connections on port 443 also aren't interchangeable if one uses Trojan and the other VLESS. Even with the same protocol and port, differences in UUID, password, TLS server name, or transport path can change how a connection works. Compare sensitive fields only on your own device; don't share the full settings.

Check references before deleting, then verify the connection

Deleting an individual node and deleting an entire subscription entry have different effects. The first removes one connection entry; the second removes a subscription source and its associated content. Before you act, check the selected node in Home, then look in Config for policies that depend on the name you're about to remove. A group heading alone isn't enough to confirm that deletion is safe.

1. Note the remark for the source you want to keep and confirm that it updates successfully. Don't treat “the nodes are still in the list” as proof that an update worked.
2. If you're currently using a node you plan to delete, first switch to a retained node you've confirmed works. If you're using Config, also check which nodes the relevant policies actually select.
3. Return to Home, open the action menu for the subscription group you want to remove, and choose delete. If deletion is available by swiping, first confirm the row is a subscription entry, not an individual node.
4. Check the confirmation message to see which item will be deleted and what the action affects, then confirm. Afterward, check the groups, nodes, and Config references.
5. Test that the websites or services you need still work. Removing a local entry from the client does not end your service relationship with the provider.

If the source you're keeping hasn't updated successfully, don't clear all subscriptions and rebuild them first. A safer approach is to confirm that you can recover the URL and settings, then clean up one entry at a time. Treat backups or notes that contain credentials as sensitive information.

Common questions about managing multiple subscriptions