This guide explains how to import a subscription into Shadowrocket on an iPhone or iPad, update nodes, and check the connection. It also covers how node selection relates to account environment stability when used by a team. A successful import only means the configuration has been added—it does not guarantee that a node will work or that an account will avoid security checks.
1. Before you import: Check the app and subscription link
“Shadowrocket” usually refers to the iOS app Shadowrocket. Get it through the official App Store and verify the app name to avoid installing configuration profiles from unknown sources. Have the subscription link provided by your service provider ready. It is usually a full URL that may contain an authentication token; it is not the address of a tutorial page or the name of an individual node.
The subscription must be compatible with the client. Do not assume that a Clash configuration URL can be used directly as a Shadowrocket subscription. If the provider offers multiple formats, choose Shadowrocket or an option explicitly marked as compatible. If you use free nodes from this site or other sources, check their format and validity first.
2. How to import a subscription into Shadowrocket
- Copy the complete subscription link. Check that the beginning and end are included, and avoid copying any spaces or line breaks.
- Open Shadowrocket and tap “+” in the upper-right corner of the home screen to open the configuration screen.
- Tap “Type” and select “Subscribe.” The wording may vary slightly between app versions.
- Paste the subscription URL into “URL,” add a recognizable note such as “Work subscription,” then tap Done or Save in the upper-right corner.
- Return to the home screen and wait for the subscription to download. If it does not download automatically, find the subscription group and refresh it. Confirm that nodes appear below.
- Select a node and turn on the connection switch on the home screen. When connecting for the first time, follow the system prompt to allow the VPN configuration to be added, then complete device verification.
Once connected, test a frequently used website, then try the app you actually need. A latency test alone does not guarantee that a service will work; also check whether pages load and login works. For everyday use, start with the rules mode recommended by your provider. Global routing changes how traffic is routed, so switching modes should not be treated as a universal fix.
3. Troubleshooting import or connection issues
- Subscription download fails: First, confirm that your phone has internet access, then check whether the link has expired, been reset, or was copied incompletely. You can also switch between Wi-Fi and mobile data and try again.
- No nodes appear after updating: Check that the subscription format is correct and that the provider is returning valid content. Do not paste private links into unfamiliar online conversion tools.
- Nodes appear, but the connection fails: Refresh the subscription manually, try another node, and check that your device’s date and time are set automatically.
- Connected, but some apps are not working properly: Check whether the routing rules are sending traffic from the target app directly, and rule out problems with the app itself. Avoid repeated login attempts.
4. Team use and account environment stability
Each team member should import the authorized subscription on their own device. Do not share an Apple ID or post subscription links in group chats. Treat subscription links as sensitive credentials; if one is exposed, contact the provider to have it reset.
Account environment stability mainly depends on factors such as the exit IP, changes in region, the device, and the platform’s risk controls—not on the act of importing a subscription. When managing work accounts, try to keep the device and exit region consistent, and avoid switching nodes frequently in a short period. Even nodes with the same name are not guaranteed to keep the same exit IP. Teams can document who maintains the subscription, commonly used regions, and troubleshooting procedures, but should not record passwords or complete tokens. Follow the terms of service and local laws.