When you first use Shadowrocket, distinguish between screen names, routing modes, and rule policies. Home is where you manage connections; Config is where you manage configurations; Data shows traffic information; and Settings controls app behavior. Proxy and Direct in Global Routing determine how traffic is handled overall, while PROXY and DIRECT in rules are rule targets. This guide focuses on the iPhone and iPad interface, explaining where to find settings and how to verify changes.
1. Identify the three types of interface labels
When following a tutorial, don’t assume an English label tells you where an action is. Config can refer to the Config tab or to a routing option in Home → Global Routing. The tab is where you manage files; the routing option applies the configuration’s rules to connections. Opening the tab does not change the routing mode.
| Category | Common labels | What to check |
|---|---|---|
| Screen or menu | Home、Config、Data、Settings | Whether you’re viewing connections, configurations, traffic, or app settings. |
| Overall routing mode | Global Routing → Config / Proxy / Direct / Scene | Which traffic-handling mode the app is currently using. |
| Rule target | PROXY、DIRECT | Which policy handles a connection when a rule matches. |
The interface may look different depending on the platform and layout. Identify options by their English labels and menu hierarchy—not by button color, screen position, or list order in a screenshot. Arrows below indicate menu navigation; they do not mean you should type the labels into a configuration file.
2. Home: Connection controls, nodes, and subscriptions
Home is the starting point for everyday tasks: checking connection status, selecting an existing node, and opening Global Routing. The connection switch starts or stops traffic handling, while the node list determines which connection target proxy traffic uses. Selecting a node does not mean every website will use it; the result also depends on the routing mode and configuration rules.
To add a connection manually, tap “+” in the top-right corner of Home to open the add screen. Type determines which fields appear next. Shadowsocks, VMess, VLESS, Trojan, Hysteria2, and WireGuard are protocol names, not quality ratings. Choose the protocol that matches your existing service details; don’t reuse a password, identifier, or transport setting from a different protocol.
-
Open Home
Check the current connection status and selected node first. Note the current Global Routing option before making changes so you can restore it after testing.
-
Add a subscription
If you already have a subscription, go to Home → “+” → Type → Subscribe, enter your subscription URL, and save. Don’t enter a subscription URL in the server address field for a single node.
-
Refresh the list
Return to Home and pull down to refresh the subscription. Check that the expected group and nodes appear. Refreshing a subscription updates service details; it does not automatically replace the routing rules in Config.
-
Check the connection
Select an existing node, choose a Global Routing mode as needed, and start the connection. If iOS asks for permission to add a VPN configuration for the first time, review the system prompt and confirm. Then visit the target page to check the result.
3. Global Routing: Config, Proxy, Direct, and Scene
The options in Home → Global Routing change the overall routing mode, not the tab you’re viewing. When troubleshooting, check this menu first, then inspect the node and rules. Otherwise, you may change a rule and see no difference in the result. The guidance below assumes you want to route traffic according to rules for everyday use.
Config
RecommendedRoutes connections according to the rules in the selected configuration. Rules can point to PROXY, DIRECT, or another policy defined in the configuration; they don’t automatically send every website in a particular category through a proxy.
Best for: Everyday routing based on conditions such as domains and IP addresses.
Proxy
Routes all connections handled by the app through the proxy, rather than applying Config rules one by one. This does not determine how system traffic or connections outside the app’s handling scope are routed.
Best for: Temporarily checking whether an existing proxy connection works and narrowing down rule-related issues.
Direct
Handles connections within the app’s scope as direct connections, without using a proxy exit. This does not remove the VPN configuration or turn off the Home connection switch.
Best for: Temporarily comparing results with a direct connection on your current network.
Scene
Applies routing based on configured scenes. What happens depends on the scenes and their matching conditions; the label Scene alone doesn’t tell you whether a proxy or a particular set of rules will be used.
Best for: When you’ve configured scenes and need different handling for different network conditions.
For example, if a destination works in Proxy but fails after switching back to Config, first check the rule matching that domain and the policy it points to. This narrows down the cause but doesn’t prove the node is working perfectly. Restore the original routing mode after testing so the temporary setting doesn’t continue to affect other apps.
4. Config: Configuration files and where rules take effect
The Config tab is where you manage configuration files and their contents. A configuration may include more than rules; it can also contain general settings, host mappings, and URL Rewrite entries. Importing a file, saving it, and selecting it for use are separate steps. Confirm that the edited file is selected, then check that Home → Global Routing is set to Config.
What the two Config options do
Config tab
- View and manage configuration files.
- Keep a copy of the original file before editing.
- Save your changes and confirm that the edited file is selected.
Global Routing → Config
- Determines whether connections follow the rules in the current configuration.
- Does not import subscription credentials for you.
- Does not guarantee that every connection uses the same exit.
Check which file is selected first, then confirm whether connections are being handled according to its rules. Both settings matter.
Keep rule keywords in English. The examples below explain syntax and order; they are not a complete configuration for users to copy over their own. They use a reserved example domain. In a real configuration, PROXY must refer to an available policy.
[Rule]
DOMAIN-SUFFIX,example.com,PROXY
IP-CIDR,192.168.0.0/16,DIRECT,no-resolve
GEOIP,CN,DIRECT
FINAL,DIRECT
DOMAIN-SUFFIX,example.com,PROXY: Matches example.com and its subdomains, but not other domains whose names merely happen to look similar at the end.IP-CIDR: Matches an IP address range. In the example,no-resolvemeans not to actively perform a domain lookup just for this rule; it does not disable DNS for the entire app.GEOIP,CN,DIRECT: Matches based on a category in the IP geolocation database. It does not check a webpage’s language or the text in a domain name.FINAL,DIRECT: A fallback for connections that don’t match earlier rules. It usually belongs at the end of the rule list; otherwise, later rules may never get a chance to match.
5. Data: Check traffic, but don’t treat the numbers as proof of connectivity
Data shows traffic statistics and related information. It serves a different purpose from the node list in Home: Home determines which connection target to use, while Data helps you see whether data is being transferred. Rising upload or download counts only show that traffic was generated. On their own, they don’t prove that a website opened successfully or that a DOMAIN-SUFFIX rule matched.
| What you observe | What you can conclude | What to check next |
|---|---|---|
| The count increases after visiting a page | Data was transferred within the observed scope. | Check request details, including the destination domain, matched policy, and page result. |
| A latency test returned a result | The test target responded according to that test’s method. | Open the website you need to use. A latency result does not prove that every service is reachable. |
| The connection switch is on, but the page still fails | System traffic handling and a successful connection to a specific service are not the same thing. | Check DNS, rules, node authentication, and the target service separately. |
| The result doesn’t change after editing a rule | The page’s behavior alone doesn’t confirm that the configuration is active. | Check the selected file and Global Routing; if needed, start a new test connection. |
Change one condition at a time when testing. Note the original settings, visit the same full URL, and check the corresponding request. Browser cache, existing long-lived connections, and multiple subdomains on a page can all affect the result. To test again, start a new connection rather than relying only on the accumulated traffic count.
6. Settings and On Demand: App settings and automatic connection triggers
Settings controls app behavior. To find automatic connection options, go to Settings → On Demand. On Demand triggers VPN connections based on configured conditions; it is not the same setting as the Config rule that determines which policy handles a domain. On Demand still requires usable service details and correct routing configuration.
- To change how a website is routed: Check Home → Global Routing first. If you’re using Config, also check the rule order in the selected configuration.
- To change when connections are triggered: Check whether On Demand is enabled under Settings → On Demand, and whether its conditions match the current network.
- If the connection comes back after you turn it off: Check On Demand and the relevant system VPN settings first, then determine whether the reconnection is unexpected.
- To refresh subscription nodes: Return to Home and refresh the subscription. Changing On Demand does not refresh a subscription.
7. Choose the right menu for the task: A complete check
For everyday troubleshooting, follow this order: service details → configuration file → routing mode → connection status → request result. This helps you distinguish authentication problems, rule issues, and automatic connection behavior, instead of changing settings across multiple screens without knowing which change affected the result.
- Start in Home: Confirm that your subscription or node is present and the correct target is selected. If you just refreshed a subscription, check that the list actually changed.
- Then check Config: Confirm that the correct file is selected and your edits have been saved. Importing a file alone doesn’t activate it.
- Return to Global Routing: Select Config when you want to route by rules. Restore Proxy or Direct if you selected either temporarily for testing.
- Check Settings → On Demand: Configure it only if you want connections to start automatically. Don’t use it to set routing rules for a destination website.
- Make a new request: Check the page and its connection details, then use traffic changes in Data as supporting information.
This guide covers menus on iPhone and iPad. Shadowrocket is also available for Mac (Apple silicon and Intel), Windows, Android, and Linux. Menu locations vary by platform, so don’t rely on the tab positions shown here. For installation and platform-specific acquisition details, visit the all-platform download page on this site.