How to Manage Multiple Shadowrocket Subscriptions: Organize, Sort, and Remove Duplicates

Imported several subscriptions? Learn how to organize sources, sort entries, remove outdated subscriptions, and prevent duplicate nodes after updates.

At a glance

This guide is for users who already have their own providers and subscriptions and want to organize their Shadowrocket list. Start by identifying each source, then name and sort it, and finally check for duplicates by comparing connection settings. Keep any necessary information before deleting entries. After an update, check the currently selected node, and don’t assume that matching display names mean the connections are identical.

1. Distinguish subscriptions, nodes, and Config

A subscription is an address used to retrieve a set of connection details. A node is one specific server entry in that set, while Config contains rules and related settings. These are different layers: updating a subscription in Home refreshes the node details from that source. Changing a configuration in Config may affect how requests match rules, but it does not organize subscription sources in Home.

It’s common for different sources to contain nodes with the same name. A name is just a label for identification; it doesn’t confirm that the address, port, protocol, and authentication details match. Conversely, the same connection can appear under different names. So don’t start by deleting entries in bulk. First identify which subscription each group of nodes came from and whether you also have manually imported copies.

3 types of data
Separate subscription sources, node entries, and Config settings
4 initial checks
Check protocol, address, port, and authentication—not just the name
1 update
Handle one source at a time to track changes

2. Group by source: give each subscription a stable name

Use a source label plus a purpose for each subscription note—for example, “Source A · Daily” and “Source B · Backup.” Avoid adding latency or temporary network conditions to the source name, or you’ll have to rename it after each test. Keep recognizable details in node names, and distinguish the source from the node’s purpose so it’s easier to identify which source failed to update.

  1. Open Home and find the group heading or subscription entry, then open its edit screen. Button locations may vary between mobile and desktop. Make sure you’re editing the subscription, not an individual node within the group.
  2. Check the subscription URL. If two entries have the same full address, mark them as possible duplicate imports rather than adding a third one. Compare query parameters too; matching domains alone aren’t enough.
  3. Enter a stable source name in an editable notes field, such as Remark. Save, return to Home, and confirm that the name makes the source easy to identify.
  4. If you need to add a subscription, choose Type: Subscribe in Add Server, then enter your own subscription address and a note. Don’t enter a subscription URL as the Address of a single server.
  5. After the first update, expand each source and check its nodes. If the list is displayed flat, use the grouping options available in the current interface. Don’t try to represent source relationships by renaming every node individually.

Source A organization notes

Remark
Source A · Daily
Type
Subscribe
Example URL
https://example.com/sub?token=xxxx
Retention rule
Keep one subscription entry for each unique full URL

This example address is not a usable subscription. Don’t import it. Keep real links only on your own devices or in a secure backup.

Source B organization notes

Remark
Source B · Backup
Check the source
Check whether it returns the same list as Source A
Manual copies
Label separately; don’t confuse them with subscription updates
When to delete
Confirm the source is inactive and you no longer rely on its nodes

Different addresses may still return some of the same nodes. Check the connection details before deleting anything.

3. Sort entries: handle source order and latency order separately

Source order determines which group you find first; node order determines which entry you see first within a group. Keep your everyday source somewhere easy to access and backup sources farther down, then sort within each group by name or test results. Don’t repeatedly import an entire subscription just to move one node to the top.

Open the edit or sort controls in Home and check what the current interface actually supports. If drag handles are available, reorder entries in edit mode. If sorting by name or latency is offered, check whether it applies to the current group or the entire list. Interfaces vary across platforms. Don’t use duplicate imports as a substitute for sorting features that aren’t available.

In short: organize by source first, then compare nodes within each group

After organizing one group, update just that source and see how the order changes. Check whether your sorting is retained before organizing other sources. This makes it easier to trace changes if something goes wrong.

Low latency doesn’t guarantee reliable access. A test may cover only part of the connection process, and may not check the target website, throughput, or every authentication step. A normal-looking latency result alone is not a reason to delete other nodes in bulk.

4. Remove duplicate nodes: compare settings, not names

Duplicates usually come from one of three situations: the same subscription was imported more than once; different sources returned the same entry; or a node from a subscription was imported separately, creating a manual copy. Identify which situation applies before deciding whether to remove a source or a single entry. If you delete just one node from a subscription group, it may return with the next update.

Identify the source Compare settings Keep the primary entry Remove the copy Review after updating
What you seeWhat to checkWhat to do
Same name, ports 443 and 8443Protocol, authentication, TLS, and transport settingsKeep them as separate entries for now; different ports may correspond to different service configurations
Two subscriptions have the same full URLWhether the same subscription was imported twice and whether either entry was edited manuallyKeep one source. Confirm the current connection works before removing the extra source
Same address and port, but different protocolsFor example, the authentication and transport requirements for Trojan and VLESSDon’t determine duplicates by address and port alone
Different names, identical connection settingsWhether authentication, SNI, TLS, and transport settings also matchKeep the primary entry once you’ve confirmed they serve the same purpose
A deleted entry returns after an updateWhether the entry is still included in the subscription responseAddress duplicate sources, or use a filtering feature if the interface provides one

When comparing entries in detail, check the fields required by each protocol. For Shadowsocks, compare the encryption method and password. For VMess and VLESS, check the UUID and their respective transport settings. For Trojan, check the password and TLS settings. The same address and port can still lead to different connections because of SNI or the transport path. Don’t keep an entry just because its details look shorter.

Don’t paste full passwords, UUIDs, or subscription tokens into public deduplication websites. Compare entries locally instead. If you can’t confirm whether they differ, keep them for now and mark them for review in your own list. Delete a few entries and test before moving on; this is easier to undo than clearing everything at once.

5. Update subscriptions and remove inactive sources: handle one at a time

Updating retrieves the latest content from a source; it doesn’t mean adding every retrieved list as a new subscription. Use the update action for an existing source. If your provider changes the address, edit the URL in the existing subscription entry first, then check the update result. This avoids keeping old and new addresses side by side indefinitely.

  1. Before updating: Note the source label, the currently selected node name, and whether you’ve manually changed any settings within the group. If needed, save your data using the app’s available backup or export options, and keep credentials secure.
  2. Update one group: In Home, update the relevant subscription and check whether it succeeds, times out, or returns content that can’t be parsed. Don’t keep adding the subscription again to fix an update failure.
  3. Check what changed: See whether existing nodes were renamed, replaced, or removed. If the list is empty, check the source response and account status before deleting other working sources.
  4. Confirm the current connection: After updating, make sure the selected entry is still there. If it was removed, choose a node that remains valid and verify the connection by visiting a site.
  5. Then remove inactive sources: Confirm the address is no longer active and there are no separate entries you need to keep, then remove it using the source’s delete option. Read confirmation prompts carefully and distinguish deleting a single node from deleting the entire subscription group.

If a request times out, first check that your regular network connection works. Then determine whether the subscription address needs to be accessed through an existing proxy. If Settings → Subscribe offers Update via Proxy, you can enable it when you already have a working connection. It changes the route used for update requests; it won’t fix an expired token, an inactive account, or an error in the server’s response.

6. FAQs about managing multiple subscriptions

I deleted a duplicate node. Why did it come back after refreshing?

First check which subscription the node belongs to. If it’s still included in the source’s list, an update may restore it. Check whether the same full URL was imported more than once. If it was, keep one source instead of repeatedly deleting nodes from the group.

Two nodes have the same name, but one connects and the other doesn’t. Can I just delete the one that failed?

Open each node’s details and compare the protocol, address, port, and authentication information. Retest on the same network to rule out a temporary issue. If the node belongs to an active subscription, update the source first, then decide whether to remove a manual copy.

My subscription has a new link. Should I add it again or edit the existing one?

If the same source has a new URL, edit and save the existing subscription first, then update it separately. Create a new entry only if you specifically need to keep two different lists side by side, and use notes to distinguish their purposes. Don’t share full old or new URLs publicly.

A website stopped loading after an update. Did sorting change my rules?

First confirm that the node currently selected in Home is still working, then check Global Routing. If you use Config, also check the active configuration and how its rules match. Sorting the list alone doesn’t modify rules or automatically switch requests to a new source.

After organizing, check that every source is identifiable, no full subscription URL was imported more than once by mistake, the current node works, and list changes after updates are understood. There’s no need to minimize the number of nodes. Keeping entries with distinct settings and a real purpose is more reliable than clearing the list based on names alone.

Get Shadowrocket and follow the setup guide

Shadowrocket for iPhone and iPad is a one-time $2.99 purchase on the App Store; check the App Store listing for system requirements. Versions for Mac (Apple silicon and Intel), Windows, Android, and Linux are free. Visit this site’s download page to choose your platform, then follow the quick-start guide to add your own connection details.

A one-time app purchase isn’t a service plan. Shadowrocket is closed-source commercial software; obtaining the app and maintaining your existing subscriptions are separate.

Download Shadowrocket