How to Manage Multiple Shadowrocket Subscriptions: Naming, Sorting, and Removing Duplicate Servers

First, distinguish subscriptions, servers, and Config

In Shadowrocket, a subscription provides a set of server parameters. One subscription can contain multiple servers, and different subscriptions can include the same server. Two entries with the same name in Home do not prove that a subscription was imported twice—and are no reason to delete an entire subscription.

Config manages configurations and rules. Adding source remarks in Home does not change the rules in Config, and moving an entry to the top does not mean all traffic will use it. Routing also depends on Global Routing, the selected server, and the policies in your configuration.

This guide assumes you already have a service provider and subscription. This site does not provide, sell, or recommend servers or subscriptions. Shadowrocket is a paid commercial app with a one-time purchase; buying the app does not include a service plan. Organizing your local list does not change your service's expiration date or data allowance.

Name by source, then import one at a time

Start by naming each group after where it came from, then distinguish how you use it. Use brief remarks such as “Provider A – Daily” or “Provider B – Backup.” Choose your own labels; don't put your email address, order number, or actual subscription credentials in a name.

1. Note the current setup

   In Home, review your subscriptions and their servers. Note which source and server are currently in use. Keep the original subscription links somewhere secure so you can restore them if needed.

2. Open the add screen

   In Home, tap “+” in the upper-right corner to open Add Server, then select Subscribe under Type. Check your existing sources first to make sure you aren't adding the same link again.

3. Add a remark

   Enter your existing subscription link in URL and a source label in Remarks. Before saving, check that the link is complete, especially for spaces, line breaks, or missing query parameters introduced during copying.

4. Check the result

   After saving and updating the subscription, return to Home and check the servers listed under that source. Confirm the remark matches the contents before moving on. Don't rename, re-import, and delete multiple sources at the same time.

A subscription URL might look like https://example.com/sub?token=xxxx. This is a dummy example and cannot be used to connect. Parameters in a real link may contain access credentials. Don't remove them to “standardize” the URL, and don't post the full link in a public support request.

Sort servers by purpose, then check test results

“Server sorting” involves two separate things: how the list is displayed and which connection you actually choose. Sorting by name can make locations easier to find; sorting by test results can help check current reachability. Neither tells you the actual speed of a webpage. Results can vary with the test method, your network, and the time of the test.

In Home, use Connectivity Test to check candidate entries, then visit the pages you use. Note whether they load successfully or repeatedly stall, and retest under the same network conditions if needed. Don't compare a result on mobile data directly with another server tested over Wi-Fi.

• First, group by source: Identify “Provider A” or “Provider B” so identical location names don't obscure different subscriptions.
• Next, group by purpose: Keep daily-use and backup options separate. You don't need to test every visible entry.
• Then check reachability: Rule out candidates that repeatedly fail tests, then compare the response of those that succeed.
• Finally, check what's selected: After changing the display order, return to Home and check the current selection. The first entry in the list is not necessarily the one in use.

Sorting options can vary by list type. If the current list offers sorting, review the available options before using one. If it doesn't, consistent source remarks and a fixed record of candidates are enough to keep things organized. A “01” in a server name does not mean the app will automatically prioritize it.

Protocol names aren't performance scores. Shadowsocks, VMess, VLESS, Trojan, Hysteria2, and WireGuard refer to different connection protocols; the name alone can't tell you which server is faster. Provider status, network routing, and correct parameters can all affect the result.

Removing duplicate servers: check their identity before deleting a source

Duplicates generally fall into two categories: the same subscription link added twice, or similar-looking servers supplied by different subscriptions. For the first, remove the duplicate subscription record. For the second, compare the connection parameters. Deleting just one server under a subscription may not help—it can reappear at the next update.

The domain and ports above are examples for comparison, not working services. Even if Type, Address, and Port all match, different authentication details may grant different access. Don't merge entries just to shorten the list. If you're unsure, keeping the original records is easier to recover from than deleting everything at once.

1. If you're about to delete the source used by your current connection, disconnect in Home first so you don't rely on it during cleanup.
2. Make sure you can retrieve the original link, then delete the target entry. Confirm whether it's a single server or an entire subscription, and read the confirmation prompt.
3. Return to Home and check that the other sources are still there. Update each subscription you keep individually.
4. Select a server from a source you're keeping, connect, and check the pages you use. Continue with the next source only after verifying the result.

Updating multiple subscriptions: verify manually before automating

After organizing the list, update each subscription manually once. Check that source remarks, server counts, and the current selection are as expected. A successful update only means the subscription content was retrieved or processed; it doesn't guarantee every server can connect. Conversely, one timed-out request doesn't prove the subscription is no longer valid.

If only one subscription fails to update, first check that its URL is complete, the service is still active, and the current network can reach the address. Don't delete other sources that update successfully. If the subscription URL requires a proxy to access, check Update via Proxy in Settings → Subscribe using an existing working connection. This setting can't fix an incorrect URL or restore expired credentials.

Check list organization separately from Global Routing

If your traffic still takes the same route after cleanup, check Global Routing before importing subscriptions again. Config handles connections according to the current configuration, and specific traffic may follow policies in that configuration. Proxy and Direct set the overall routing mode; Scene relates to scene settings. Source remarks don't change any of this.

• When using Config: Check the current configuration and the policies targeted by the relevant rules. DOMAIN-SUFFIX, GEOIP, and IP-CIDR in rules are matching conditions; FINAL is used as the last-resort fallback, not as a subscription source label.
• When using Proxy: Check which option is currently selected for proxy connections. Don't infer it from the order of source groups.
• When using Direct: Don't treat the result of a direct connection as a test of a proxy server.
• When using Scene: Check the settings for that scene first, then investigate why the current connection isn't following your manual selection.

If your device automatically reconnects, also check On Demand in Settings. On Demand controls connection triggers; it doesn't remove duplicates or infer your intentions from a subscription remark like “Backup.” When troubleshooting, check when the connection starts, which routing mode is in use, and which server is selected. This is more effective than repeatedly switching every setting.

Common questions about organizing multiple subscriptions