When migrating Shadowrocket, keep your connection details, the .conf file you currently use, and a record of key settings; use iCloud sync as an additional way to restore data. This guide is for users switching to a new iPhone or iPad, or reinstalling the app. It assumes you already have your own service provider and subscription. Remove data from your old device only after checking the connection, rules, and subscription updates on the new one.
Before you migrate: distinguish connection details, Config, and device settings
Exporting a .conf file does not back up the entire app. Servers and subscriptions in Home specify where to connect; Config files control how traffic is handled, including rules and DNS; Settings affect app behavior. These may be saved in different ways, so seeing a config file on the new device does not prove the migration is complete.
On the old device, open Home and note the selected server or policy group, the Global Routing mode, and the subscription name. Then open Config and check which file is actually enabled—not just the most recently downloaded file in the list. If you changed DNS, rule order, or local mappings, back up the modified local file; keeping only the original remote URL is not enough.
- Subscription users: Keep the original subscription URL and a name that identifies its purpose. The server list generated from a subscription is not a substitute for the original URL.
- Manual setup users: Save your connection details using the app's export or share feature. Check that the protocol, address, port, and authentication fields are all present.
- Custom rules users: Save the current .conf file and note any remote rule resources it references. Make sure those resources will still be accessible after restoration.
- Users with automatic connections: Note whether Settings → On Demand is enabled and record its conditions. Check these settings separately on the new device.
iCloud sync: check your account and permissions, and keep a separate backup
iCloud sync can help transfer data between devices using the same Apple Account, but it is not an independent archive with version history. Deletions and changes may also propagate to other devices, so avoid deleting large numbers of items on the old device while testing sync. For your first migration, export your files before changing sync settings.
- On the old iPhone, open Settings → Apple Account → iCloud and make sure iCloud Drive is available. Check that Shadowrocket has permission in the list of apps using iCloud. The menu names and locations may vary by system version.
- Open Shadowrocket → Settings and check the iCloud sync options. If the option is available in your installation, enable it in the app. The sync scope depends on the options provided by the app; don't assume that every setting is included.
- Keep the old device online. After checking its data, sign in to the same iCloud account on the new device and check that it has the same permissions.
- Open the app on the new device and compare the contents of Home and Config item by item. If there is no clear sync-complete message, check the entries and their contents directly; elapsed time alone does not indicate success.
Your iCloud account handles syncing; your App Store account handles access to purchased apps. They serve different purposes. Even if you successfully redownload the app, signing in to a different iCloud account will not automatically bring over data synced under the original account. Likewise, seeing files in iCloud does not mean the current App Store account has a purchase record for the app.
Export your .conf file and subscription URL separately; a rules file is not a connection backup
In Config, find the file you currently use, open its action menu, and choose Export or Share. Then save it to Files using the system share sheet. Menus can look different across system and app versions; long-press the file or open its actions, then use the export or share option that appears. After saving, make sure you can find the .conf file in Files—not just a screenshot of the app.
| Backup item | What to keep | What to check separately |
|---|---|---|
| Current .conf file | Complete text, including local changes | Check for [General], [Rule], and any other sections you actually use |
| Original subscription | Full URL and a note about its purpose | Check that query parameters and token are complete and still valid |
| Manual connection | Connection details exported from the app | Protocol, port, password or UUID, and any required TLS or transport settings |
| Device behavior | Written record of key options | Global Routing mode, selected item, and On Demand conditions |
Get the subscription URL from the existing subscription's edit or share options, or retrieve it from your own service provider account. After copying, make sure the URL hasn't been truncated, especially the parameters after the question mark. The example below is for format illustration only and is not a working subscription. Real URLs often contain access credentials; store them somewhere private and protected.
https://example.com/sub?token=xxxx
You can do a basic check of a config file by reviewing its text. The snippet below demonstrates what to look for; it is not a complete config to use in place of your original during migration. Finding rules under [Rule] only confirms that the rule text was saved. It does not prove that connection credentials from Home were saved too.
[Rule]
DOMAIN-SUFFIX,example.com,DIRECT
IP-CIDR,192.168.0.0/16,DIRECT
FINAL,PROXY
Bottom line: open the backup file separately before restoring
In Files, make sure the .conf file exists and can be opened. Also check that you saved the original subscription URL separately. Only after both checks should you consider moving on from the old device.
Restore on a new device: connection details first, then enable Config
Avoid importing the same subscription repeatedly, running a full sync, and replacing configs multiple times at once. First check what iCloud has already restored, then add anything that's missing. This helps prevent duplicate entries and accidentally selecting the wrong config. Keep On Demand off during restoration so you can see the effect of each step.
- Install and open the app: Choose your platform on the download page. After opening the app for the first time, check whether Home or Config already contains synced data.
- Restore connection details: If you have a subscription but it wasn't synced, use the add option in Home to restore the original subscription URL, then update it. For manual connections, use an import method supported by the app and check each authentication detail.
- Import the .conf file: Find the backup in Files and send it to Shadowrocket through the system share sheet, or use the file import option available in Config. Open the imported file and confirm it is the modified copy.
- Select the active config: Enable the target file in Config. Return to Home, set Global Routing to Config, and confirm the selected server or policy group.
- Set up the system connection: The first time you connect, follow the system prompt to allow a VPN configuration. This permission is part of the new device's system settings and must be approved there; don't assume it comes with the .conf file.
If you used Scene on the old device, check the selected scene and its associated conditions before deciding whether to restore it. For temporary diagnostics, Proxy can help test proxy connectivity, but it does not prove that your rules were restored correctly. Direct is not suitable for testing whether a proxy server works. Return to your intended mode before the final test.
Verify the restoration: a successful connection doesn't mean the rules are working
Check four things one by one: subscription updates, connection, request routing, and automatic connection. First, confirm that the updated list in Home isn't empty, then connect and visit a destination you normally use and know is reachable. To check traffic routing, review the matched rule and actual policy in the request log; don't rely solely on the top-level toggle being on.
- Check rule order: DOMAIN-SUFFIX matches domain suffixes, IP-CIDR matches IP address ranges, and GEOIP uses an IP geolocation database. Rules are evaluated in order; FINAL handles traffic not matched by any preceding rule.
- Check policy names: If the .conf file uses custom policy group names, make sure both their definitions and references were restored. Copying only the [Rule] section is not enough.
- Check DNS: Compare the [General] settings in your backup with the file that's actually enabled. If a domain fails to resolve, first check DNS reachability and your network environment rather than assuming the subscription credentials are invalid.
- Check network changes: Once a manual connection works, go to Settings → On Demand and restore your previous conditions. Check behavior on both Wi-Fi and cellular networks.
A common troubleshooting case: a destination works in Proxy but fails in Config. Check the matched rule, policy references, and DNS differences first instead of immediately deleting all connections and importing them again. If both modes fail, check the server address, port, authentication details, and whether the current network can reach the server.
After verification, export the final .conf file again and note its purpose and device in a private record. You can replace the old working copy, but keep a separate pre-migration copy for comparison in case of accidental changes. A subscription update is not a substitute for archiving your config file.
Restore a purchase: redownloading the app and restoring its data are separate steps
Shadowrocket for iPhone / iPad is a $2.99 one-time purchase on the App Store. Versions for Mac (Apple silicon and Intel), Windows, Android, and Linux are free. Check the App Store listing for iPhone / iPad system requirements, and verify the developer is Shadow Launch Technology Limited and the app ID is 932747118. Find download options for all platforms on this site's download page.
- On the new iPhone or iPad, check which account is used for Media & Purchases in the App Store. Make sure it is the account that originally bought the app.
- Open that account's purchased apps list, find Shadowrocket, and download it again. Depending on the current system interface, the entry may appear under “Apps” or “Purchased.”
- If the App Store still shows a price, check your purchase history, account, and storefront region before paying again. If you can't find the original order, contact support through the App Store.
- Once the app has downloaded, continue with the data restoration steps in this guide. Redownloading a purchased app will not recreate a lost subscription URL, password, or custom rules.
Common questions about moving to a new device
Why is Home still empty even though the new phone has a .conf file?
Config files and connection lists are different types of data. First check whether Home has a subscription group. If not, add the subscription again using your saved original URL and update it, or import your manual connection details. Reimporting the same .conf file won't create a server list.
Why isn't anything syncing, even though both devices use the same iCloud account?
Check iCloud Drive, Shadowrocket's iCloud permissions, and the relevant in-app options on both devices. Then check your network and available storage. If no data appears, restore from your separately exported files. Don't delete data from the old device or keep switching accounts before verifying the new device.
What should I do if the subscription is restored but an update fails authentication?
Open the subscription's edit option and compare the URL with your original. Check for a missing token or extra spaces, then check the link and service status in your own provider account. If you generated a new URL, replace the old one and try updating again. Don't post a URL containing a token publicly while troubleshooting.
Can I recover everything if I erased my old phone and only have the .conf file?
First check whether iCloud still has your connection data, then look for a privately saved subscription URL or check your original provider account. A .conf file can restore the settings it actually contains, but it can't recreate passwords, UUIDs, or subscription credentials that were never saved in the file. Retrieve any missing details, then import and verify everything as usual.