Shadowrocket Backup and Transfer Guide: iCloud Sync and Config Export

1. Separate your purchase record, subscription, and config files

Getting the app again from the App Store restores your eligibility to use the client; it does not restore all in-app data. Shadowrocket is a closed-source commercial app sold as a one-time purchase. Buying the client does not include a service plan. This site does not provide, sell, or recommend servers or subscriptions. Treat getting the app again and restoring your own connection details as separate tasks.

Home is primarily for viewing servers, subscriptions, and connection status. Config is where you manage and select rule configs, while Settings contains behavior options to check separately. A rule config may include General and Rule sections without including every subscription link in Home, passwords for servers added individually, or the currently selected setup. So don’t erase the old device just because you’ve exported a file.

• Purchase record: Linked to the Apple Account used for the purchase; it is not a config backup.
• Subscription URL: The source for retrieving the server list. Having the current list without its URL does not mean it can still be updated.
• Local config: Includes your own rule edits. Don’t save only the remote config URL and overlook local changes.
• Device state: VPN permission, current selections, and automatic connection conditions need to be checked again on the new device.

2. What iCloud sync and manual export each do

iCloud makes data supported by the app available across devices. It depends on the right Apple Account, iCloud Drive, app permissions, available storage, and a network connection. Sync is not a fixed-time archive: changes or deletions to shared data may also reach other devices. Keep a separate copy before moving to a new device.

Manual export saves a file as it exists at a particular moment. It’s useful for preserving local rule edits and comparing them after import. What gets exported depends on the selected item and export function; exporting one file from Config is not a full app backup. Saving a file to iCloud Drive only chooses where to store it—it does not enable the app’s own data sync.

3. Backup steps for your old iPhone

Before backing up, pause bulk edits and deletions. Confirm the current connection works, and note the Global Routing selection in Home and the file currently in use in Config. If you plan to update a subscription, save its original source details first. An update may change server names, counts, or order, so the updated list cannot tell you what was on the old device before the transfer.

1. Record the current setup

   Open Home and note the current server and Global Routing selection. Then open Config and note the name of the file in use. Go to Settings → On Demand and record whether it’s enabled and which conditions are set.

2. Save subscription sources

   In Home, open the details for each existing subscription and save its original URL somewhere safe. If the address is no longer visible, retrieve it from your own saved records. Don’t mistake a server’s share details for the whole subscription.

3. Export local files

   In Config, find the local file you want to back up. Use its action menu to share or export it, then save it to Files using the system share sheet. The gesture and label depend on the current interface. Don’t select Delete or copy only the remote URL by mistake.

4. Check the file contents

   Make sure the exported file is readable and still contains your Rule edits. If the config references external rules or remote configs, save those URLs separately; saving the main file does not save external content along with it.

5. Verify sync

   Check your iCloud permissions and available storage, then wait for the data to sync and verify it on another device. If you can’t verify it right away, keep the exported file, subscription sources, and old device. Don’t erase the old device yet.

Treat backup files as sensitive data

Tokens in subscription URLs, server passwords, and keys may grant connection access. Don’t post complete files in public forums or upload them to unfamiliar parsing sites. You can use a name combining the purpose and backup date to tell files apart, but never put passwords or tokens in the filename.

4. Restore on your new iPhone: app, data, rules, and permissions

Get Shadowrocket again from the App Store first. Sign in with the Apple Account used for the purchase and find it in your App Store purchase history; system menu names may change. Verify the developer is Shadow Launch Technology Limited, the app ID is 932747118, and the icon matches the official icon shown on this site. For iPhone, iPad, and other compatible devices, check the App Store listing for system requirements.

Don’t re-add every subscription as soon as you see an empty list. First check whether iCloud is still syncing, then decide which items need to be imported. Otherwise, synced data may arrive later and duplicate items you added manually, leaving duplicate groups and making their sources harder to identify.

1. Check synced content: Open Home and Config to review the server list and local configs separately. Compare names and key details, not just item counts.
2. Restore subscriptions: If a source is missing, tap “+” in the top-right corner of Home to open Add Server. Select Subscribe for Type, enter your saved URL, and save it. Then update that subscription. Don’t enter a subscription URL in a regular server address field.
3. Restore local configs: Find your backup in Files and send it to Shadowrocket from the share sheet. If that option isn’t available in your system, use the file import option in Config. After importing, make sure the file is readable in Config and select the config you want to use.
4. Check routing mode: To route traffic by rules, go to Home → Global Routing and select Config. Proxy and Direct do not apply the current Rule entries individually. If you use Scene, also check which policy that scene actually applies.
5. Grant device permission: The first time you connect, follow the system prompt to allow adding a VPN configuration. Permission on the old device does not grant it on the new one. Check the connection status after granting permission.
6. Restore automatic connection last: Test a manual connection first, then go to Settings → On Demand and restore the conditions you need. This makes troubleshooting easier.

5. Use two checklists to verify the transfer

Check connectivity and rule behavior separately. A successful subscription update means content was retrieved that time; it doesn’t mean every server in it can connect. A working server also doesn’t confirm that the right config is active. Start with a server you already know works, then verify both sets of details below.

For example, if the old config contains the rules below, make sure all three remain after restoration and that FINAL hasn’t been moved ahead of them. example.com is only there to illustrate the syntax; it is not a test site you need to visit. PROXY should point to a proxy policy available in the current config. When testing your own rules, use a destination with an outcome you already know.

[Rule]
DOMAIN-SUFFIX,example.com,PROXY
IP-CIDR,192.168.0.0/16,DIRECT,no-resolve
FINAL,DIRECT

• DOMAIN-SUFFIX matches the specified domain and its subdomains. Don’t judge whether it matched solely by whether a page loads.
• IP-CIDR matches an address range. In this example, no-resolve means the rule won’t trigger an extra domain lookup.
• FINAL handles traffic that didn’t match an earlier rule. Changing its position or policy can affect many connections.
• If the original config also has GEOIP or remote rule references, keep their original order and references. Don’t replace the full config with this shortened example.

6. Common transfer issues and what to check