Official Guide · Features and Settings
Shadowrocket Features and Settings
Choose how traffic is routed in Global Routing, and set when to connect in On Demand. This page covers the iPhone / iPad interface; options on other platforms may differ.
- ConfigConfiguration · Choose a policy by rule
- ProxyProxy · Use the selected server
- DirectDirect · Bypass proxy servers
01 Routing modes
Global Routing: Config, Proxy, and Direct
Open Global Routing from Home, then select Config, Proxy, or Direct. This setting determines how traffic entering Shadowrocket is routed; it does not turn the connection on or off. Changing modes does not establish a connection. After selecting a mode, return to Home and check the connection status.
| Interface option | How traffic is handled | When to use it | Check before switching |
|---|---|---|---|
Config (configuration) |
Selects a policy based on the rules in the active configuration. | Different sites or addresses need different routes. | In Config, check which file is active and the order of its rules. |
Proxy (proxy) |
Routes traffic entering the client through the selected proxy, without applying routing rules. | Temporarily bypass rules to check whether the current server can handle a test request. | In Home, confirm that the server you want to test is selected. |
Direct (direct) |
Traffic entering the client bypasses proxy servers. | Establish a direct-connection baseline for the same request to see whether the issue occurs only over the proxy route. | This does not disconnect the client. To disconnect, use the connection switch on Home. |
If a site works in Proxy but fails in Config, first check which rule it matched and which policy that rule specifies, then decide whether to change the configuration. If it fails in both modes, do not start by reordering the entire ruleset. First check the current network, selected server, and exact test destination. When comparing modes, change only the mode and keep all other conditions the same.
02 Matching and policies
Rules: matching conditions, order, and fallback
In Config, open the configuration you plan to use and check its Rule section. The first part of each rule defines the match condition; the end specifies the policy to apply, such as PROXY to use a proxy, DIRECT to connect directly, or REJECT to deny the request. After applying the configuration, select Config in Global Routing; otherwise, the rules will not affect routing in the current mode.
Choose a rule type based on request details
DOMAINmatches an exact hostname, useful when routing a single specific domain.DOMAIN-SUFFIXmatches a domain suffix, useful when the same policy should apply to a root domain and its subdomains.DOMAIN-KEYWORDmatches a string in the domain name. Short strings are more likely to cause false positives, so check for unrelated domains that could match before using this rule.IP-CIDRandIP-CIDR6match IPv4 and IPv6 ranges, respectively.GEOIPmatches based on the geographic classification of an address. For domain-based requests that need to be matched by destination IP, also check the DNS results.USER-AGENTmatches an available request identifier; it does not identify traffic by app name. Do not rely on this rule for routing if the client cannot access the relevant field.
Put specific rules first and FINAL last
Rules are checked in order, and the first match determines the policy. This example uses placeholder domains to illustrate an exception: the first line sends only static.example.com direct; the second sends other requests with the same domain suffix through a proxy. If you swap the first two lines, the broader suffix rule matches first and the specific exception no longer applies.
DOMAIN,static.example.com,DIRECT
DOMAIN-SUFFIX,example.com,PROXY
FINAL,DIRECT
This illustrates rule order; it is not a complete configuration. FINAL applies only to requests that did not match any earlier rule. Whether to use DIRECT as the fallback depends on how you want unlisted destinations handled. Save a copy of the original configuration before making changes. When testing, check at least one destination that should match a specific rule and one that should reach the fallback. If using REJECT to block requests, start with clearly defined domains to avoid blocking dependencies such as login services or static assets.
03 Connection details
Subscribe, Add Server, and choosing a server
Manage existing server details in Home. If you have a subscription URL, open Add Server from the add menu, select Subscribe, enter the complete URL, and save. If the interface offers an update option, refresh the subscription and check that its entries appear in the SERVER list. Subscription URLs may contain access credentials; do not share the full URL in public posts, screenshots, or diagnostic logs.
If you have details for a single server, select the protocol specified in those details in Add Server, then enter the address, port, and authentication and transport settings required by that protocol. The fields for Shadowsocks, VMess, VLESS, Trojan, Hysteria2, and WireGuard differ; do not reuse one protocol's settings for another. After saving, return to Home, select the entry you want under SERVER, then run a Connectivity Test and verify access to an actual destination.
Updating a subscription and updating a configuration file are different: the first refreshes server entries; the second changes the rules used for matching. After a subscription update, check the current selection if an existing entry was replaced. If the configuration refers to servers or policy groups by name, verify that the names still match. If a subscription refresh fails, first check the update status to see whether the list was retrieved. Do not confuse connection problems with existing entries with subscription update failures.
04 Connection conditions
On Demand: Connect based on network conditions
On Demand controls when the system triggers a connection based on conditions; it does not decide whether an individual request uses a proxy or a direct route. First connect manually from Home to confirm that system connection authorization is complete and the server is available. Then open On Demand in Settings and configure the network conditions shown in the interface. Enable and test one required condition first, then add exceptions; this makes it easier to identify which setting changed the connection behavior.
For example, if you want an automatic connection only after switching to cellular, start by setting only the relevant network condition. After saving, switch between Wi-Fi and cellular using the same test destination, and record the connection status before and after the switch and when returning to the original network. Seeing the switch enabled in Settings alone does not confirm that the condition was triggered.
After a manual disconnect, the system may reconnect if the device still meets the automatic connection conditions. To verify the effect of disconnecting manually, temporarily turn off On Demand before testing. If the connection status is as expected but traffic takes the wrong route, check Global Routing and the rules instead of repeatedly changing On Demand conditions.
05 Usage checks
Data: Check traffic usage
Data shows traffic recorded by the client. Open Data and check the current measurement period and units, then distinguish sent from received traffic. To estimate the usage for one action, note the current reading, perform the action once, and compare the readings after they update. Avoid downloading, syncing, or streaming media at the same time, so other requests are not included.
Client statistics, the system's cellular data usage, and provider bills may cover different traffic and time periods, so subtracting one from another is not a reliable way to detect missing usage. If the reading does not seem to change, first confirm that the connection is active, then check whether the request passed through the client and whether the display precision can show the difference. To determine whether an individual request matched a rule, check the request log; total traffic alone cannot identify the policy used.
06 Common settings
Settings: DNS, testing, sync, and diagnostics
Before troubleshooting, note the current configuration, server, and routing mode. Change one setting at a time and retest using the same destination. This makes it easy to restore the original value if the change does not help, without reconfiguring the entire connection.
DNS: Check the current configuration's DNS settings first
DNS determines how domain names are resolved to addresses. If the active configuration specifies DNS servers, first check the file's General section in Config, including whether dns-server is set. Do not attribute the results to the system network before checking the configuration. If there is a DNS resolution issue, note the original settings, change the DNS option, and retest the same domain. A custom DNS server must be reachable on the current network; being able to connect to a server does not guarantee that the destination domain will resolve.
Test Method: Keep connectivity tests consistent
In Settings, check Test Method and choose an available method, then return to Home and run a Connectivity Test. When comparing entries, keep the test method, network, and destination the same. A successful test means only that this probe met the selected method's success criteria; it does not guarantee access to every site. Likewise, a failed probe to one destination does not mean the server is unreachable for all destinations.
Today Widget: Check status and use quick actions
Find Today Widget in Settings and configure its features using the options available in the app. Then check the system's widget screen to see whether your device supports adding it. After using a widget action, return to Home to check the connection status and current server. Widgets provide shortcuts; if the client reconnects shortly after you disconnect it, first check the On Demand conditions.
iCloud: Check what syncs before switching devices
Find the iCloud-related options in Settings. Before syncing, check that both devices use the same Apple Account, that the relevant iCloud features are enabled in the system, and which items the client actually lists for syncing. Keep a copy of important configurations before switching devices. Afterward, check the server list, active configuration, and connection authorization one by one. Restoring purchases and syncing app data are separate processes; reinstalling successfully does not mean the original settings have been restored.
Diagnostics: Find issues by timestamp
Open Diagnostics in Settings or use the diagnostic option shown in the interface. Note when the issue occurs, then reproduce the failed action once. Review nearby entries to distinguish a DNS resolution failure, an incorrect rule policy, or a connection timeout, then adjust the relevant setting. If you need to share diagnostic information, include only the relevant excerpts and remove subscription URLs, authentication fields, and private addresses. After troubleshooting, restore the original logging level if you raised it temporarily.
Read the setting-by-setting guide · Look up interface and rule terminology