November 9, 2026 · Advanced · About 9 min read

Shadowrocket Subscription Management: Organize, Sort, Remove, and Find Duplicate Nodes

When you import multiple subscriptions, the node list can quickly become cluttered. This guide explains how to group subscriptions, change their order, remove inactive subscriptions, and avoid duplicate nodes when updating.

At a glance

When managing multiple Shadowrocket subscriptions, first confirm where each one came from, then group and sort them before addressing duplicates. This guide assumes you already have your own provider and subscriptions. It explains how subscriptions, nodes, and Config differ, how to keep records you can revert to, and how to identify duplicate nodes by updating subscriptions one at a time. This site does not provide, sell, or recommend nodes or subscriptions.

Understand the roles of subscriptions, nodes, and Config

A subscription is a remote URL used to retrieve a list of nodes. A node is a connection entry in that list, containing a server address, port, protocol, and authentication details. Config organizes rules, policies, and other settings. Deleting a node is not the same as deleting a subscription, and changing the display order does not change routing rules.

Start in Home to review each subscription and its nodes, then check the active configuration in Config. Subscription-related options in Settings control update behavior. This guide uses the iPhone / iPad interface as a reference; on other platforms, check the actual interface rather than assuming the same controls or gestures are available everywhere.

3 places to check
Home, Config, and Settings: review the list, configuration, and preferences
2 types of deletion
Deleting a node and deleting its subscription source are separate actions; confirm what each one affects
Update one at a time
Update one subscription at a time to track changes to the list

For example, two entries may both be named “Hong Kong 01,” but one uses Trojan and the other Shadowsocks. The name alone does not make them duplicates. Even with the same protocol and address, different ports, authentication details, or transport settings may mean they should remain separate.

Group by subscription source and use recognizable names

Grouping should answer “Where did this entry come from?” before focusing on a tidy list. Give subscriptions names that identify their source or purpose over time, such as “Everyday” and “Backup.” These are personal labels; the app does not automatically route traffic based on them, and a backup subscription will not automatically take over a connection.

  1. Find an existing subscription in Home, open its edit screen, and check the saved URL. Do not show the full address in public screenshots or chats.
  2. Use distinct notes for subscriptions from different sources. If the current interface supports collapsing subscription groups, collapse each group after reviewing it before moving on.
  3. Keep manual nodes separate from subscription-provided nodes in your records. A manually added entry will not automatically receive the same changes when a remote subscription is updated.
  4. After organizing, update each subscription separately and confirm that its nodes still belong to the expected source. Do not assume entries with similar names belong to the same group.

Do not import the same URL repeatedly just to make a node appear in multiple categories of use. Categorizing by purpose and managing sources are different tasks: policies in Config can organize traffic by purpose, while each source should ideally have one clearly identified subscription entry.

Everyday subscription review

Source name
Everyday
Where to check
The subscription’s edit screen in Home
Address check
Compare character by character with the original URL you have
Update method
Update it separately first, then review the nodes in the group

This card is an example of an organization record, not an app configuration to import.

Backup subscription review

Source name
Backup
Why keep it
Different source, with an ongoing use case
Before deleting
Confirm that no active policy references it
Privacy
Do not share tokens or authentication details in the URL

“Backup” is just a note; check your policy configuration separately if you need automatic switching.

When sorting, distinguish display order from the actual outbound connection

When using the sorting options available in Home, first decide what you need to find. Sorting by name helps locate a specific entry; sorting by latency helps compare results from the same test run; manual ordering is useful for keeping frequently checked entries easy to find. Available options depend on the current app interface, so do not assume every platform supports the same drag-and-drop controls.

GoalWhat to doWhat not to assume
Find a specific nodeUse a consistent naming format, then search or sort by nameBeing at the top means it will be selected
Compare current response timesRun the same latency test on the same networkLower latency guarantees higher throughput
Keep frequently used sources handyLabel subscriptions clearly and adjust their display using the available optionsList order is the same as failover order
Check the actual outbound connectionReview Global Routing, the active configuration, and the selected nodeThe node’s position in the list tells you what is being used

In Global Routing, Proxy, Direct, Config, and Scene are routing modes, not node sorting options. Proxy routes connections through a proxy, Direct connects directly, Config follows the active configuration, and Scene applies the selected scene. When using Config, a rule’s policy may point to a different node than the one just selected in Home. After sorting, check policy references instead of relying on the top entry in the list.

Bottom line: Keep test conditions consistent before changing the display order

Run a test on the same network, then organize names and order for your needs. Do not switch between Wi-Fi and cellular while comparing latency readings taken under different conditions.

Find duplicate nodes after an update by checking each source

Duplicates usually have one of three causes: the same subscription was imported more than once, different subscriptions returned the same node, or a node from a subscription was also saved manually. Deleting only the row that looks duplicated may not solve the problem; it can reappear after the next update because it is still included in the remote list.

Record the current stateUpdate one subscriptionIdentify the sourceCompare fieldsRemove and verify
  1. Note the subscription names containing the two suspected duplicates. If you take a screenshot, show only names and groups, not authentication details.
  2. Update only the first subscription and note which entries are added, removed, or renamed. Repeat the same steps for the second subscription. Do not refresh everything at once.
  3. Open the node editor and compare the protocol, server address, port, authentication details, and transport settings in order. Matching names alone are not enough to justify deletion.
  4. If the same URL was imported twice, keep the subscription with a clear source that updates correctly, then remove the extra subscription entry.
  5. If the remote list itself contains duplicates, check the subscription content you have access to. Deleting a single node locally does not ensure that future updates will exclude it.

For example, two nodes may point to the same server and both use port 443, but one uses VLESS and the other Trojan. They are still different connection configurations. Even when the protocol matches, differences in applicable fields such as TLS, transport path, or SNI may need to be preserved. A port number alone does not establish the protocol or whether a service is available.

Do not edit query parameters in a subscription URL to “merge addresses.” Different tokens may correspond to different permissions or content, and the same hostname does not mean the subscriptions are identical. Compare URLs locally; do not paste full links into online text comparison tools.

Check the impact before removing an inactive subscription

One timed-out update does not mean a subscription is permanently inactive. Before deleting it, distinguish a network request failure from an empty remote response, expired authentication, or intentional deactivation. If the request failed, keep the existing record while checking the URL and update path. Delete it only after confirming it is no longer needed.

Removing a local subscription record does not cancel the remote service or invalidate a URL that has been exposed. If a link has been shared publicly, replace the relevant credentials through your own service management portal, then update the saved address in Shadowrocket. Clean up the local list and manage remote authorization separately.

Check subscription updates separately from rules and automatic connections

After organizing the node list, confirm which route the connection actually uses. Subscription updates determine “which connection entries are available”; Config determines “where a request is sent”; Settings → On Demand triggers connections under specified conditions. Enabling On Demand does not automatically deduplicate nodes or group subscriptions for you.

The rule syntax below illustrates the distinction between rules and subscription management; it is not a complete file to replace your current configuration with. Rules are matched in order, and policy names must match targets available in your active configuration.

DOMAIN-SUFFIX,example.com,PROXY
IP-CIDR,192.168.0.0/16,DIRECT,no-resolve
GEOIP,CN,DIRECT
FINAL,PROXY

DOMAIN-SUFFIX matches domain suffixes, IP-CIDR matches IP ranges, GEOIP matches based on IP geolocation data, and FINAL handles connections that did not match earlier rules. These rules are not rewritten when you reorder nodes in Home. If a site still connects directly after you select a node, check Global Routing and the matching rule before repeatedly deleting and re-importing subscriptions.

Frequently asked questions about managing multiple subscriptions

I imported the same subscription twice. Which one should I delete?

Compare the URLs in both subscription edit screens and confirm they are identical. Update each one separately and check the results. Keep the entry with a clear name and working content. Before deleting the other, check the selected node and any references in Config. Do not assume two subscriptions are the same just because their display names match.

Why did a node reappear after I deleted it and updated the subscription?

First check whether the remote subscription still returns the node. If it does, an update will bring it back; deleting it locally once is not a persistent filter. Then check for another subscription or a manual entry containing the same node. Remove duplicates by source instead of repeatedly deleting rows with the same name.

One subscription timed out, but the others work. Do I need to reinstall everything?

Keep the other working subscriptions. Check the URL in the affected subscription. If it needs an existing proxy to connect, confirm that the node works, then go to Settings → Subscribe and check Update via Proxy before retrying that subscription on its own. This setting changes the route used for update requests; it cannot fix expired credentials or a remote service error.

The order changed after an update. Does that mean a node is inactive?

No. An update may return new names or a different list order. Check the current sorting settings again and test any nodes you need to use. If you use manual ordering, update one subscription first and check whether the order is retained. Do not assume the remote subscription preserves your local order.

Can I merge two subscriptions by joining their URLs?

No. Joining two URLs does not merge subscriptions. Keep separate entries in Home with clear source names. If you want to use different sources for the same purpose, arrange that in a configuration and policy setup you understand. Do not submit links containing tokens to unfamiliar websites.

Download Shadowrocket