This guide explains how to import a subscription into Shadowrocket and how teams can reduce the impact of node switching on account environments. Shadowrocket usually refers to the app for iPhone and iPad. Importing a subscription only retrieves a list of nodes; whether you can connect and whether the exit remains stable also depend on the subscription’s validity, node status, and client settings.
1. Before you import: the client and subscription link
First, get the official version of Shadowrocket from the App Store. Availability may vary by region, so check what is currently listed in your store. Prepare the subscription link provided by your service provider; it usually starts with HTTPS. Subscription links may contain personal credentials, so do not share the full link in public group chats, screenshots, or shared documents. Team members should use authorized subscriptions; do not assume that one subscription can be shared without limit.
The free nodes provided on this site can be used to test connectivity, but availability and exit addresses may change. They are not suitable as a long-term, fixed network environment for important business accounts.
2. How to import a subscription into Shadowrocket
- Copy the complete subscription link and check that it contains no extra spaces or line breaks and that no parameters are missing.
- Open Shadowrocket and tap “+” in the top-right corner of the home screen to open the add page.
- Under “Type,” select “Subscribe” or “Subscription,” then paste the link into the “URL” field. Enter a descriptive name in the remarks field, such as “Team authorized subscription.” Field names may vary slightly between versions.
- Tap Done or Save, then wait for the node list to download. If it does not download automatically, find the subscription on the home screen and use the update function.
- Expand the subscription, select a node, then turn on the connection switch on the home screen. The first time you connect, follow the system prompt to allow adding a VPN configuration and complete device verification.
- Open a browser and visit a frequently used website to confirm the connection works. Do not judge availability by the node’s latency number alone.
A subscription link is not the same as a link for a single node. If you have a single-node link such as vless:// or vmess://, import it from the clipboard or scan the corresponding QR code instead of trying to enter it as a subscription URL.
3. Why teams should pay attention to account environments
Importing a subscription does not directly make an account “more stable.” Platforms may assess security based on factors such as the exit IP, device, login location, and account activity. Sharing an account among multiple people or frequently switching countries or nodes may trigger additional verification, but using a fixed node cannot guarantee that you will avoid security checks.
Teams should prioritize using member permissions or subaccounts supported by the platform, and clearly assign responsibility for updating the subscription. When handling important accounts, try to keep the device, exit region, and usage habits consistent. Do not repeatedly switch nodes just to chase lower latency. After updating a subscription, some existing nodes may be replaced, so confirm the exit region before continuing. Choose rule-based or global mode as needed, but note that in rule-based mode, some traffic may connect directly. You cannot assume that every app uses the same exit.
4. How to troubleshoot import or connection failures
- Subscription download fails: Check that the link is complete and has not expired, and first confirm that your current network can access the subscription address. Do not submit links containing credentials to unfamiliar parsing websites.
- The list is empty: The returned format may be incompatible, or the subscription may contain no available content. Contact the provider to confirm that it supports Shadowrocket.
- Nodes appear but will not connect: Update the subscription, confirm that the device clock is set to sync automatically, then test another node. Avoid repeatedly importing the subscription.
- Connected, but webpages will not load: Check whether your rules are sending the target website through a direct connection, then review your DNS settings. You can first restore the client’s default settings and test each setting one at a time.
When troubleshooting, change only one setting at a time and record the node, time, and error message. When reporting the issue to an administrator, hide subscription tokens and account information. This helps diagnose the problem while protecting access credentials.