This article explains how to import a subscription into Shadowrocket and why the same subscription may have varying levels of stability across accounts and network environments when used by a team. It’s for users who already have a subscription link and want to import it quickly into Shadowrocket on an iPhone or iPad, distribute it consistently, and reduce disconnections.
1. What to prepare before importing a subscription
Shadowrocket is just a client; it cannot provide internet access on its own. You need working nodes or a subscription link. A subscription is usually a URL starting with http or https and containing node information for protocols such as VLESS, VMess, Trojan, and Shadowsocks. You can use a subscription you already have, or temporarily test availability with the free nodes on this site. However, free nodes are more susceptible to network fluctuations, so teams are advised not to rely on a single source for work.
Before using a subscription as a team, check three things: whether the link is still valid, whether concurrent use is allowed, and whether the system clocks on members’ devices are accurate. Many connection failures are not caused by incorrect Shadowrocket settings, but by expired subscriptions, restricted nodes, or local network blocking.
2. How to import a subscription into Shadowrocket
- Open Shadowrocket, go to the home screen, and tap “+” in the top-right corner.
- Select “Subscribe” or “订阅” as the type. Do not select an individual protocol type.
- Paste the subscription link into the URL field. Add a name, such as the team name, project name, or date, to make it easier to identify later.
- Tap “Done” to save. Return to the home screen and pull down to refresh, then wait for the node list to appear.
- Select a node with low latency and a clear name, then turn on the connection switch at the top.
- When connecting for the first time, follow the system prompt to allow adding a VPN configuration.
If no nodes appear after importing, first check that you copied the entire link, especially any parameters at the end. If you get a format error, try opening the subscription link in a browser. If it displays a list of node details or automatically downloads a configuration, the link is usually accessible.
3. How account and network environments affect stability for teams
Many teams share the same subscription with multiple members, but stability depends on accounts, devices, and network environments. For example, company Wi-Fi, campus networks, and mobile carrier networks can differ in how much they interfere with proxy traffic. If multiple people connect to the same node at once, this may also trigger server-side speed or concurrency limits.
- Don’t share the same account with too many people: Excessive simultaneous connections can cause issues where the subscription imports successfully but won’t connect.
- Group subscriptions by purpose: Keep testing, everyday browsing, and remote collaboration separate to make troubleshooting easier.
- Assign fixed nodes to individual members so everyone doesn’t crowd onto a single node.
- Keep a backup subscription or client, such as Clash or sing-box, to help determine whether the issue is specific to Shadowrocket.
The more disorganized the account setup, the more likely you are to encounter “it works for everyone else but not for me” situations. Team administrators can use consistent subscription names, such as “Team A-Daily-2026,” and remind members to refresh their subscriptions regularly rather than repeatedly reinstalling the client.
4. Troubleshooting connection failures
If you can’t connect after importing a subscription into Shadowrocket, troubleshoot in this order: switch between 4G/5G and Wi-Fi; update the subscription; try a different node; then restart Shadowrocket or your phone. If all nodes fail, the subscription may have expired or the network may be restricting connections. If only one node fails, it’s most likely temporarily unavailable.
Also check Shadowrocket’s “Global Routing” mode. Most users should select “Config” or “Rule” mode to access sites that require a proxy while avoiding unnecessary detours for domestic apps. If team members report problems with certain apps, ask them to send screenshots showing the current node, routing mode, and error message so the administrator can assess the issue.
In short, importing a subscription into Shadowrocket is straightforward. The key is to use a valid source, copy the link in full, and connect over a stable network. Teams should also pay close attention to account concurrency, node assignments, and regular subscription refreshes to reduce disconnections and connection failures.