August 27, 2026 · Advanced · About 10 min read

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

Imported multiple subscriptions? Learn how to label sources, sort by latency, remove stale entries, and prevent duplicate servers in Shadowrocket.

At a glance

To manage multiple subscriptions, identify each source before updating, testing, or cleaning up entries. Don’t delete entries in bulk based on their names. This guide focuses on using Shadowrocket on iPhone and iPad and is intended for users who already have their own provider and subscriptions. The same source-tracking and deduplication principles apply to other platforms; check the app for the available editing options. By the end, you should be able to spot duplicate imports, keep the original links for recovery, and manage your subscription list separately from routing settings in Config.

1. Distinguish subscription sources, server entries, and routing settings

Server entries in Home, subscription sources, and configuration files in Config are separate things. A subscription provides a set of server parameters; Config handles routing settings such as rules and policies. Deleting a duplicate subscription doesn’t delete Config, and importing more subscriptions won’t automatically assign connections to different sources based on how you use them.

Here, “subscription groups” means organizing entries in Home by source—not creating an automatic selection policy. Proxy, Direct, Config, and Scene under Global Routing are different routing modes, not subscription categories. Keep your existing routing settings unchanged while cleaning up the list so you don’t change several variables at once.

Home
Check servers, subscription sources, and the current selection
Config
Manage configuration files and rules—not a place to deduplicate subscriptions
Settings
Check settings related to testing and updates

Before you start, save the full links for your subscriptions, notes about their sources, and the names of the servers you currently use. Parameters such as tokens in a link are usually access credentials. Store them securely; don’t include them in public screenshots, group chats, or public notes. This site does not provide, sell, or recommend servers or subscriptions. The steps below apply only to content you already have.

2. Name subscriptions by source to avoid importing the same one twice

Use names that identify the source rather than piling on locations, latency, and temporary status. One option is a source label followed by its purpose, such as “Personal A - Daily” or “Personal B - Backup.” Don’t add test results to a subscription name: the number may no longer be useful after a network change or update.

  1. In Home, open each existing subscription’s edit screen and check its URL and Remarks. First check whether the exact same full link is already in the list, then decide whether to add it.
  2. To add a subscription, open the add option in Home, set Type to Subscribe, enter the URL you already have, and give Remarks a recognizable source name.
  3. Save it and wait for the content to load, then check that the entries appear under that source. Handle one source at a time and confirm it before importing the next, so you can tell which link caused any duplicates.
  4. If you need to change a link for an existing source, edit and update the original subscription instead of adding another copy. Keep the old link before editing in case you need to troubleshoot a typo.

Example: existing source A

Type
Subscribe
Remarks
Personal A - Daily
URL
https://example.com/sub?token=xxxx
What to do
Update the existing subscription instead of adding a duplicate

The URL is an example of the format only; it cannot be used to retrieve servers.

Example: existing source B

Type
Subscribe
Remarks
Personal B - Backup
URL
https://example.com/sub?token=yyyy
What to do
Keep this source separate and check its update results individually

The same domain doesn’t mean the subscriptions are identical; query parameters may return different content.

These names are a suggested organizational convention, not a required Shadowrocket format. If an entry name comes from the subscription, a local edit may be overwritten on the next update. To keep source information over time, add it to Remarks at the subscription level rather than renaming individual servers.

3. Update first, then test, and sort by latency last

Updating and testing answer different questions. An update checks which parameters the subscription currently returns; a test checks how those entries respond on your current network. Sorting an old list may leave entries that the source has already removed in the running. If an update fails, deleting the entire group right away could remove local entries that still work.

Keep the original records Update each source Check for changes Test under consistent conditions Sort by latency
  1. Update the first subscription and note whether it succeeds. Compare the number of entries before and after. If the update fails, keep the existing list for now; a failed fetch doesn’t mean every server is invalid.
  2. Repeat the same steps for each source. If one group has far fewer entries than expected, check that the URL is complete and whether the source content has changed. Don’t rush to clear and re-import it.
  3. Run Connectivity Test in Home using the same Wi-Fi or cellular network and the same test method. Don’t test half the entries on Wi-Fi and the rest after switching to cellular.
  4. When testing is complete, use the sorting option available in the current interface to sort by latency. The menu location may vary by platform. Compare entries within the same source first, then compare candidates across sources.
  5. After choosing a candidate, open the page or service you need to use and check whether the connection works and stays up. Test results alone don’t tell you whether an entry suits your needs.

Latency is not download speed or a record of long-term stability. Results vary with the test target and method, local network congestion, and server load. If an entry times out once, it only means the test didn’t finish within the time limit; it doesn’t prove the entry is permanently unavailable. The lowest number doesn’t guarantee access to every site.

4. Identify duplicates by connection details, not names

The easiest case is when the exact same subscription link has been added twice. It’s harder to judge when two sources return similar servers: the same name can point to different addresses, and the same address can use different ports, protocols, accounts, or transport settings. Before removing anything, open the details and compare each field. Don’t rely only on location words in the name.

What you seeWhat to checkWhat to do
Two subscription URLs are identicalFull path, query parameters, and whether either has local-only entriesKeep one subscription that updates successfully, then remove the duplicate after confirming
Same name, different addressServer address, protocol, and portDon’t assume they’re duplicates based on the name; keep both and test them separately
Same address, ports 443 and 8443Port, protocol, transport settings, and authentication detailsTreat them as different connection configurations; don’t merge them outright
Same address and port, different protocolsFor example, the specific parameters for Shadowsocks and TrojanDon’t deduplicate by IP alone; confirm what each connection is for first
Matching connection details from two separate subscriptionsCheck whether authentication, TLS, and transport parameters also matchAfter confirming, keep the primary source. Note that the other source may bring the entry back on its next update.

Bottom line: remove duplicate sources before duplicate server entries

If the exact same link was imported twice, remove the redundant subscription first. Only remove duplicate server entries after confirming their connection details match. This reduces the chance that a later update will bring back duplicates.

Ports 443 and 8443 are examples of a port difference, not ports required by the app. Don’t copy passwords, UUIDs, or keys into public text tools while comparing entries; check them locally in the details screen. If different domains resolve to the same IP, that alone doesn’t prove the entries are equivalent: the domain and TLS settings may be part of the connection.

5. Keep a recovery path before deleting stale entries

Confirm an entry is “stale” by updating, testing it more than once, and checking an actual connection. One Connectivity Test timeout, or a failure on a single Wi-Fi network, isn’t enough reason to delete entries in bulk. If an entire group is affected, check your network and subscription fetch status first instead of deleting entries one by one.

Don’t delete DOMAIN-SUFFIX, GEOIP, IP-CIDR, or FINAL rules in Config just to clean up the server list. These keywords are used for connection matching and fallback handling; they don’t remove duplicate subscriptions. For help checking rules, see the subscription manual and glossary. Treat list management and routing troubleshooting as separate tasks.

Settings → On Demand controls on-demand connections; it isn’t where you deduplicate or sort entries. If the connection comes back automatically while you’re cleaning up, check that setting instead of assuming the subscription was imported again. When troubleshooting, change one setting at a time and note its original value. Restore the settings you need for everyday use when you’re done.

6. Frequently asked questions about managing multiple subscriptions

Why does a deleted server come back after an update?

Because the subscription still includes it in the content it returns. First identify the source, then decide whether you still need that subscription. A local deletion doesn’t change remote content. If the same URL was imported twice, remove the duplicate subscription record instead of repeatedly deleting the servers it generates.

Two subscriptions have the same name. Can I merge them?

A name doesn’t prove the content is identical. Open each subscription’s edit screen, compare the full URLs, and check the server parameters. If you need to keep both sources, add a source label to Remarks. Don’t replace subscription management by copying all the servers; you could lose track of where future updates come from.

Why does the order change after I sort by latency?

First check whether you ran a new test or update. A test changes the measured results; an update may change the entries and their source order. A single sort isn’t a permanent priority. To choose again, test under the same network and conditions, then verify actual access.

A subscription update failed. Should I delete it and add it again?

Keep the existing entries and check the URL first, especially for missing query parameters. Then check your local connection, whether the link currently returns content, and update-related settings under Settings → Subscribe. Delete the subscription only after confirming it’s a duplicate or incorrect record, so you don’t lose local parameters that still work.

7. Follow a consistent cleanup routine

The goal of managing multiple subscriptions isn’t to minimize the number of entries. It’s to make sure every entry you keep has a clear source and a reason to keep it. Use a small number of tested candidates day to day, and leave the rest under clearly named sources. Test again when you need to switch; there’s no need to rename or delete everything each time.

  1. Check for duplicates before adding: Compare the full URL and make sure it isn’t already in the list.
  2. Review after updating: Check for unexpected drops in entry count, name changes, and whether the current selection is still there.
  3. Filter after testing: Use consistent test conditions and consider actual access, not just the latency number.
  4. Review after deleting: Check the current selection, Config references, and results of the next update to make sure you can recover if needed.

To move to another device, get the client for that device first, then import your existing subscriptions one source at a time. Shadowrocket is a closed-source commercial app. Getting the client and having your own service connections are separate things; a one-time app purchase doesn’t include a service plan. For iPhone and iPad, check the App Store page for system requirements. See the download page for installation instructions on other devices.

Download Shadowrocket