This guide is for users who have already added multiple subscriptions of their own to Shadowrocket and want to organize the Home list. First, back up your data and label each source. Then group and sort subscriptions, update them one at a time, and remove only entries confirmed to be inactive or imported more than once. Don’t assume entries with the same name are duplicates, or that a single update timeout means a subscription is inactive. The steps use the iPhone / iPad interface; menu locations may vary on other platforms.
First, distinguish subscriptions, server entries, and Config
A subscription is an address used to retrieve server entries, usually with access credentials tied to an account. A server entry contains the protocol, address, port, and authentication details for a specific connection. Home can show multiple server entries under the same source. Config manages settings such as rules; changing the display order on Home does not change the policy order in Config.
Before you start, note the currently selected server, the Global Routing mode, and the active Config. Back up any configuration and subscription URLs you may need to restore, and make sure the backup actually includes them—don’t rely on the filename alone. Keep subscription URLs private; don’t share them in public screenshots or troubleshooting posts.
Group by source, then choose the display order
When managing multiple subscriptions, start by asking “Where did this group come from?” before deciding “Which one do I use most?” Keep one clearly identified subscription entry for each source, and use consistent remarks such as “Personal—Primary” or “Personal—Backup.” Avoid permanent labels like “Fastest” or “Working”: availability changes, but source labels should remain tied to the original record.
-
Review existing entries
Open Home and review each subscription and its servers. Open an existing subscription’s edit screen and check its URL and Remarks. If the same URL is already there, mark it for review instead of adding it again with “+”.
-
Add a clear source name
In the subscription’s Remarks field, enter a name that identifies its source. Remarks are for identification only. Don’t add notes, spaces, or custom parameters to the URL, as that could change the subscription request.
-
Add new sources separately
To add another subscription of your own, tap “+” in the top-right corner of Home → Type → Subscribe. Enter the address in URL, identify the source in Remarks, save, and then update the subscription.
-
Set the display order
If the current Home editing screen has drag handles, move frequently used sources to the top and backups below. If it only lets you sort entries within a group, organize them there. Don’t delete and re-add subscriptions just to force a different order.
-
Review the current selection
After leaving edit mode, check the currently selected server again. Collapse subscription groups you don’t use and expand the ones you use often to confirm the remarks make each source easy to identify. Collapsing a group does not delete its subscription.
Drag, collapse, and sort controls may vary by platform; use the controls available in your interface. Automatic sorting by name or latency is different from manual sorting: if automatic sorting is enabled, an update or a new test may change the order again. If the list gets rearranged after you sort it, check the sort setting before importing anything again.
Separate primary and backup sources without confusing them with policy groups
Subscription groups on Home help you identify and select servers; policy groups in Config determine how traffic is handled. Even if they have similar names, they are different things. Before renaming anything in a Config that uses fixed server names, name filters, or policy group references, check those references so rules don’t continue pointing to an old name.
A cleanup plan: keep sources separate and sort by use
Primary source
- Keep one subscription entry that updates successfully.
- Label its source and purpose in Remarks, and place frequently used groups first.
- After updating, check that the previously selected server is still there.
Backup source
- Keep its original URL separate; don’t combine it with the primary URL.
- Place it below primary sources or collapse it to prevent accidental selection.
- Update it separately on a regular basis, and verify the connection before switching to it.
Display order does not determine where traffic goes. The result also depends on Global Routing, the current selection, and matching rules in Config.
Keep test conditions consistent when checking the results. Traffic is handled differently in Global Routing modes such as Proxy, Direct, Config, or Scene. A webpage loading in Direct mode does not prove that the newly selected server works. You don’t need to change routing for this guide; record the original mode and compare results under the same conditions before and after cleanup.
Before deleting, confirm the subscription is actually inactive
A failed update and a failed server connection are two different troubleshooting paths. The first asks whether the list can be retrieved and parsed; the second asks whether a particular connection in that list works. One unavailable server does not mean the entire subscription URL is inactive. Conversely, seeing a list does not prove the latest update succeeded—the app may still be showing previously retrieved entries.
| What you see | What to check first | Delete it right away? |
|---|---|---|
| The update request timed out | Check whether the current network can reach the subscription domain; switch networks and retry that subscription on its own. | No. One timeout is not enough to show that the URL is inactive. |
| HTTP 401 or 403 | Check the access credentials, account status, and whether the subscription URL was reset in the original service account. | Check authorization first; a status code alone doesn’t prove permanent inactivity. |
| HTTP 404 | Check that you copied the full path, aren’t using an old URL, and that the original URL hasn’t moved. | Handle the old entry only after confirming the new URL and a successful update. |
| The response can’t be parsed | Check whether the URL leads to a login, information, or error page instead of supported subscription content. | Fix the URL or content format first; don’t keep adding the same entry. |
| The list updated, but one connection failed | Check that entry’s protocol, authentication details, and network reachability; see whether other entries in the same group work. | Don’t delete the entire subscription based on this alone. |
Update one source at a time and note whether it succeeded, timed out, or returned a specific error. Updating all subscriptions at once may be convenient, but it makes it harder to pinpoint the URL causing the problem. If the account has issued a new token, edit the URL of the existing subscription instead of keeping both old and new entries. Confirm the new list appears before continuing.
Compare server parameters—not just names—to find duplicates
Duplicates often result from adding the same subscription twice, manually adding a server that was later imported through a subscription, or receiving the same server from two different sources. Matching names only mean the display text is the same; different names don’t prove the connection parameters differ. Identify the source first, then compare the actual fields.
- Protocol: Shadowsocks, VMess, VLESS, Trojan, Hysteria2, and WireGuard use different connection parameters. Don’t identify duplicates by address alone across protocols.
- Destination address and port: For example, ports 443 and 8443 on the same domain are different endpoints. Don’t merge them just because the domain matches.
- Authentication details: The same address and port may still use different passwords, UUIDs, or keys, and may belong to different accounts or have different permissions.
- Transport and security settings: Compare the fields actually in use, such as TLS, Server Name, transport type, and path. Differences in these settings can affect the connection.
- Source: Even if all parameters match, confirm whether you intend to keep the entries as separate sources and whether Config references one of them by name.
If you confirm that the same URL was added twice, keep the subscription entry with clear remarks that updates successfully, and remove the extra entry—not individual servers within the group. If a manual entry duplicates one from a subscription, it’s usually best to keep the one that updates with its source. If you deliberately changed parameters in the manual entry, note the differences before making changes; don’t overwrite it blindly.
Source: Personal—Primary
Type:Trojan
Address:edge.example.com
Port:443
Source: Personal—Backup
Type:Trojan
Address:edge.example.com
Port:8443
The example above uses reserved example domains to show how to compare entries; it is not a working connection. The two entries have the same Address but different Ports, so they are not duplicates on that basis. Even if the Port also matches, check authentication and TLS settings too. Never copy passwords or other sensitive values into a public comparison table.
After removing old entries, check updates and rule references
Once you’re sure you no longer need a subscription, return to Home and delete the record for that subscription group. Confirm its name and the scope of the change in the confirmation prompt. If the interface offers Delete after a swipe, make sure you’re swiping the subscription record, not an individual server in the group. Deleting a local entry does not cancel the original service account or remove copies on other devices.
- Keep a way to restore it first: Make sure the original URL is saved securely and note the current selection. If you’re replacing a subscription, verify that the new URL updates successfully first.
- Remove one entry at a time: Start with a subscription entry confirmed to be duplicated or inactive. Return to Home and check that the other sources are still there before removing anything else.
- Review Config: Check whether policy groups or rules reference a deleted or renamed server. Policy targets for rules such as DOMAIN-SUFFIX, GEOIP, IP-CIDR, and FINAL should resolve to valid policies.
- Select and test again: Confirm the current server is still present. Keep the original Global Routing mode and test a destination you normally use; don’t rely on latency alone.
- Update the remaining subscription: Update it on its own and see whether the removed entry returns. This can help determine whether it came from the remote list or a duplicate import.
If you manually delete a server from a subscription group, it may be recreated on the next update from the remote content. If it reappears, the update probably worked—the remote list still includes that entry. To keep it excluded, check whether the subscription’s edit screen offers options such as name filters, and verify the filter’s scope. If there’s no suitable option, keep the original list and collapse the group instead of repeatedly deleting the server by hand.
Name filters also need maintenance. If a filter depends on a region abbreviation or fixed prefix, a change upstream could accidentally exclude valid entries. Compare the list before and after applying the filter, make sure frequently used entries are still there, and then save a copy of the configuration.
Common questions about organizing multiple subscriptions
I imported the same subscription twice. Which entry is safe to delete?
Open each subscription’s edit screen and compare its full URL and remarks. If the URLs match and there are no differences you need to keep, retain the entry that updates successfully and has a clear source label. Before deleting the other, switch to a server in the group you’re keeping and check Config for references to the old name.
The update failed, but the old servers still work. Should I delete the subscription?
Not yet. A connection from the old list only shows that its existing parameters still work; it doesn’t prove the subscription request succeeded. Retry that subscription separately and check the network and original account status. If the URL has been replaced, update it in the existing subscription to avoid adding another duplicate source.
Why did a server come back after I deleted it and updated the subscription?
First check which subscription group it reappeared in. If it’s the same group, the remote list still includes that entry; if it’s in another group, another source includes it too. Check for duplicate subscription entries or review the subscription’s filter settings instead of deleting only the individual server shown.
Two servers have the same name, but one works and the other doesn’t. How should I clean them up?
Compare the protocol, Address, Port, authentication and TLS settings, then check the source. Don’t remove duplicates based on name alone. Keep the original subscription remarks to identify the source and note the specific entry during testing. If you rename a server locally, remember that an update may overwrite the name with the one from the remote list.
It still connects automatically after cleanup. Does that mean I didn’t delete everything?
Not necessarily. Open Settings → On Demand and check the existing on-demand connection conditions, then confirm the current Home selection and Global Routing mode. Automatic connection behavior and the number of subscriptions are separate settings; don’t clear all subscriptions instead of checking On Demand.
Get Shadowrocket and set it up
Shadowrocket for iPhone / iPad costs $2.99 as a one-time App Store purchase. The Mac (Apple Silicon / Intel), Windows, Android, and Linux versions are free. Check the App Store listing for iPhone / iPad system requirements. The developer is Shadow Launch Technology Limited. See the Download page for platform-specific options, then follow the setup guide to review your first connection, subscription import, and Config settings.