Moving Shadowrocket to a new device involves handling the app, config files, subscriptions, and device settings separately. This guide is for anyone who can still use their old device and is preparing to switch iPhones or iPads. Save a local copy first, check iCloud sync, then verify Config, Global Routing, and On Demand on the new device. Seeing nodes does not mean your rules and auto-connect settings have been restored. Keep the old device until you have verified the new one can connect.
1. Separate configs, subscriptions, and device settings before you transfer
Shadowrocket configs and the service details in Home are separate data. Exporting a .conf file does not guarantee that node passwords, subscription URLs, the currently selected node, or system VPN authorization have been saved. Before transferring, make an inventory of each item by its source rather than simply checking that a file exists.
| What to transfer | Where to check on the old device | What to save |
|---|---|---|
| Local config | Config | The file currently in use, manually edited rules, DNS, Host, and other settings |
| Subscription | The relevant subscription’s edit screen in Home | Your complete subscription URL, group name, and any requirements for updating it |
| Manual node | The relevant node’s edit screen in Home | Type, server address, port, authentication details, and protocol-specific settings |
| Runtime state | Home → Global Routing;Settings → On Demand | The original routing mode, selected node, and auto-connect conditions |
This guide assumes you already have your own service provider and subscription. This site does not provide, sell, or recommend nodes, subscriptions, or connection services. Subscription URLs often contain access credentials; treat them like passwords when backing them up. Do not store them in public photo libraries, shared documents, or screenshots sent with support requests.
2. Back up the old device: export first, then check iCloud
Sync makes the same data available across devices, but it is not an immutable historical backup. Deletions and incorrect edits can also sync. Save a separate copy before organizing, deleting, or reimporting anything. If the old and new devices have different configs, export each one so you do not end up with only the most recently synced copy.
-
Record the current state
In Home, note the selected node and Global Routing value. In Config, note the currently selected file, then go to Settings → On Demand and record the enabled conditions. Keep screenshots for your own records only; hide addresses, passwords, and subscription credentials before sharing them.
-
Export the config
In Config, find the local file you actually use. Use that file’s action menu to export it or open the system share sheet, then save it in the Files app. Menus vary by interface; make sure you use the export action for the file itself. Copying the filename is not an export.
-
Check the file contents
In the Files app, confirm that the file opens and has a
.confextension. Check that the sections you use, such as[General]and[Rule], are present. If you changed Host or URL Rewrite, check those sections too instead of relying on the file size. -
Save service details separately
Save the complete URL for each existing subscription and the details for each manual node. For manually added nodes, check Type, port, and authentication fields one by one. A server address alone is usually not enough to restore a connection on the new device.
-
Check iCloud settings
On iOS, go to Settings → Apple Account → iCloud and check iCloud Drive and Shadowrocket’s access permissions. Then check the iCloud-related options in Shadowrocket’s Settings. Include only sync items that are actually available in the app and enabled on your device.
3. Install Shadowrocket on your new iPhone and restore from iCloud
Redownloading the app and restoring its data are separate steps. The App Store handles purchase eligibility; iCloud handles synced data. They may use different accounts. Successfully installing the app does not confirm that you are signed in to the right iCloud account.
-
Check the purchase account
In the App Store account page, open Purchased or your purchase history and look for Shadowrocket. Labels vary by iOS version; use the list of purchased apps as your reference. If the app still shows a price, first check the Apple Account used for Media & Purchases and your purchase history. Do not buy it again straight away.
-
Install and verify
Check that the app is named Shadowrocket and the developer is Shadow Launch Technology Limited, then redownload it. The iPhone/iPad version is a one-time $2.99 purchase on the App Store. The Mac (Apple silicon and Intel), Windows, Android, and Linux versions are free. See the download page for details; iPhone/iPad system requirements are as listed on the App Store page.
-
Restore the sync setup
On the new device, sign in to the iCloud account that holds your old data. Check iCloud Drive and the app’s access permissions, then open Shadowrocket and review the iCloud sync options actually available in Settings. Keep the network connection stable, and do not create multiple configs with the same name while the list is empty.
-
Compare items one by one
Check Home and Config separately. Confirm that subscription groups, manual nodes, and local configs are present. Open the config and check key rules; matching names do not guarantee matching contents. Restore only what is missing from your manual backup to avoid importing everything twice.
-
Allow the VPN configuration
When you connect for the first time, follow the iOS prompt to allow adding a VPN configuration and complete device authentication. Authorization must be confirmed on the new device; approving it on the old one does not authorize the new one. Test the connection manually first, without enabling auto-connect.
If iCloud restores only some of your data, do not delete anything from the old device or repeatedly switch accounts to force a refresh. Check the network, iCloud storage, and account first, then use the file recovery steps in the next section to restore anything missing. Sync time depends on the device and network; there is no fixed wait time that can be guaranteed.
4. Manually restore .conf files, subscriptions, and standalone nodes
For a manual transfer, work in this order: config file → service details → runtime settings. This lets you confirm the rules are intact before checking connection credentials and restoring automatic behavior. Keep the original file unchanged and edit only a copy after receiving it.
Restore a Config file
- Source
- The
.conffile exported from the old device - Import method
- Use the Files app’s system share sheet or Open In menu and choose Shadowrocket
- Confirm the location
- Find the imported file in Config and select the config you intend to use
- Check the contents
- Rule order, target policies, and
FINALin[Rule]
After the file appears in Config, confirm that it is selected. Do not rely only on an “Import successful” message.
Restore a Subscribe entry
- Import method
- Home → “+” in the top-right corner → Type → Subscribe
- URL
- Paste your complete subscription URL, including all query parameters
- Refresh
- After saving, pull down in Home to refresh and check the nodes returned by the subscription
- Avoid duplicates
- If sync has restored the subscription, check its URL before adding it again
The example URL https://example.com/sub?token=xxxx is for illustration only and cannot be used to connect.
If Shadowrocket does not appear in the Files app’s Open In options, first make sure you downloaded an actual config file—not a webpage, archive, or shortcut that only has a filename. For remote configs, save the original URL and a local copy of your edits. Fetching the remote file again may overwrite local changes, so redownloading it is not a complete restore.
- For Shadowsocks nodes, check the encryption method and password. An address and port alone are not enough.
- For VMess and VLESS nodes, check the UUID and original transport settings. Do not reuse another node’s settings just because the addresses match.
- For Trojan and Hysteria2, use the original service details for authentication and TLS settings. Do not disable certificate verification as a troubleshooting shortcut.
- WireGuard also requires keys, addresses, and peer settings. Do not treat it as a simple server address and password when transferring it.
5. Verify rules and On Demand after restoring
Test the connection manually before restoring auto-connect. The options under Home → Global Routing—Proxy, Direct, Config, and Scene—represent different routing modes: Proxy routes traffic through the proxy, Direct connects directly, Config follows the selected config, and Scene follows the configured scene. Restore the mode you actually used before the transfer; do not switch everything to Proxy by default.
| What to verify | Action | What to check |
|---|---|---|
| Node connectivity | In Home, select a restored node and run Connectivity Test | Check for timeouts. The result only reflects the test target; it does not mean every website is reachable. |
| Selected config | In Config, check the selected local file. Then go to Home → Global Routing and select Config. | Seeing the file is not enough; confirm that requests are actually being handled by it. |
| Rule matching | Visit a domain covered by your proxy rules and one covered by your direct rules, then check the connection log. | Check that each destination uses the expected policy and that the original DOMAIN-SUFFIX rule still appears before the fallback rule. |
| Auto-connect | In Settings → On Demand, check the conditions and test switching between Wi-Fi and cellular. | Check that it connects or disconnects under the original conditions, rather than reconnecting immediately after you disconnect manually. |
In a rule file, DOMAIN-SUFFIX matches domain suffixes, while GEOIP and IP-CIDR match the relevant IP conditions. FINAL is the fallback when no earlier rule matches. When checking a transfer, focus on preserving the original contents and order. Do not add an overly broad rule just for testing.
- Keep On Demand from triggering automatic actions for now. Connect manually once and visit a site you normally use.
- Confirm that Global Routing, the selected node, and Config are correct. Then check DNS, Host, and the target names in your rules.
- Restore the original conditions in Settings → On Demand, then test the network changes covered by each condition.
- When testing is done, reopen the app to confirm the settings are still there. Then decide whether to erase the old device.
6. Common questions about restoring on a new device
Why is Home still empty after installing on the new device?
First check the iCloud account and the app’s sync permissions, then check whether Config is empty too. Installing the app does not restore its data. If iCloud has no service details available, add your own subscription again via Home → “+” → Type → Subscribe. Restore manual nodes from a separate backup.
Why are there no nodes after importing a config?
A .conf file can contain rules and other config, but do not assume it includes all the service details from Home. Open the file and check what it actually contains, then compare it with the groups in Home on your old device. Do not enter a remote rule-file URL under Subscribe or save a subscription URL as ordinary config text.
Why does subscription refresh fail on the new device when it worked on the old one?
Check that the URL is complete, the credentials are valid, and the current network can reach the subscription address. Cached nodes on the old device do not mean the subscription URL is still accessible. Keep the cache and backups, then check device limits or credential status with your own provider. Do not repeatedly delete and recreate the same subscription.
Why does the connection come back after I turn it off?
Go to Settings → On Demand and check the auto-connect conditions. Temporarily disable them while troubleshooting, then test disconnecting manually again. If the issue stops when auto-connect is disabled, adjust the trigger conditions instead of deleting nodes or overwriting Config.
Can I recover anything after erasing the old device?
First check what is available in iCloud, any previously saved .conf files, and subscription or service details in your personal secure storage. Purchase history lets you redownload the app; it is not a backup of node passwords. Data that was neither saved nor synced cannot be recovered by reinstalling. Re-enter it from your own original service details.
7. Final checks before retiring the old device
Move on to clearing the old device only after checking files, refreshing subscriptions, and testing both manual and automatic connections on the new device. In particular, do not retire a device by deleting synced data from the app one item at a time. If deletions sync too, they could affect data already restored to the new device.
- The file selected in Config on the new device is the one you verified, and your manually added rules and
FINALare intact. - Subscriptions in Home refresh successfully; manual nodes have complete authentication details; and duplicate groups have not been created by repeated imports.
- Global Routing and the selected node suit your normal use, and you have tested On Demand conditions in the new device’s environment.
- Keep at least one readable, separate config backup and store subscription credentials securely. Do not keep the only backup on the old device you are about to clear.
- When retiring the old device, follow the iOS device handoff process for its account and data. If your service has device management, handle authorization for the old device according to your service terms.
After any substantial rule changes or service updates, export the config again and update your separate records. A useful backup is a clearly identified set of settings you can restore—not a pile of same-named files you cannot distinguish and have never opened to verify.