Official Manual · Features & Settings
Shadowrocket
Common Settings and When They Take Effect
First, confirm how requests are handled. Then adjust rules, DNS, or connection conditions. Change one setting at a time and test with the same request.
This guide follows common iPhone / iPad interface paths. Shadowrocket is also available for Mac, Windows, Android, and Linux, but menu locations and available settings may vary by platform. Follow what appears in your current interface. An existing subscription or server is required to establish a proxy connection; a configuration file alone does not provide a usable connection.
The iPhone / iPad version is a one-time $2.99 purchase on the App Store. The Mac (Apple silicon and Intel), Windows, Android, and Linux versions are free. See the download page for all platforms for availability and device details.
01 / GLOBAL ROUTING
Global Routing: Config, Proxy, and Direct
What it does: Global Routing determines how requests are handled overall. For everyday routing by domain and IP, use Config. To check whether a problem is caused by rules or the proxy server, compare Proxy and Direct. These options change the routing mode; they do not replace server credentials or restore an expired subscription.
Where to find it: On Home, locate Global Routing and check the selected option. This section covers the three common modes: Config / Proxy / Direct. If your interface also shows Scene, configure it according to its specific options; it is not simply another name for one of these three modes.
| Option | How it works | When to use it | What to check first |
|---|---|---|---|
| Config | Uses rules in the active configuration to determine how requests are handled. | Everyday rule-based routing; testing custom rules. | Active configuration, rule order, and policy references. |
| Proxy | Routes requests that can normally be handled through the current proxy path. | Temporarily rule out the effects of rule-based routing. | Selected server and its settings. |
| Direct | Routes requests directly. | Compare with the behavior of your regular network connection. | Whether the regular network works and the current DNS status. |
How to set it: Note the current option, select the mode you want, then return to Home and check the connection status. Retry the same website or app. If needed, end the existing connection before testing so an earlier session does not affect the result. If Proxy works but Config does not, check the rules and policies first rather than re-entering all server details.
Keep in mind: Direct does not disable the system VPN configuration, and Proxy does not guarantee that every app or system service will use the same route. Restore your usual mode after testing; do not leave a temporary troubleshooting setting in place just because one request worked.
02 / RULE MATCHING
Rule types, policies, and match order
What they do: A rule combines a matching condition with an action. DOMAIN matches an exact domain; DOMAIN-SUFFIX matches a domain and its subdomains; DOMAIN-KEYWORD matches a keyword in the domain. IP-CIDR and IP-CIDR6 match address ranges, while GEOIP relies on the corresponding IP data. Whether USER-AGENT applies depends on whether the request exposes that field; it cannot read every encrypted request.
Where to find them: In Config, confirm which file is active, then open that file’s rule editor. Global Routing must be set to Config for its rules to apply, so the rule text alone cannot tell you how traffic is routed. First confirm which file is active, then check what it contains.
[Rule]
DOMAIN-SUFFIX,ad.example.com,REJECT
DOMAIN-SUFFIX,example.com,PROXY
IP-CIDR,192.168.0.0/16,DIRECT
FINAL,PROXY
How to configure them: Rules are checked from top to bottom. The first match determines the action. PROXY sends the request through the proxy, DIRECT connects directly, and REJECT blocks it. In the example above, a specific subdomain is blocked before its parent domain is handled. Reverse those lines and the broader domain rule may match first. Put FINAL last to set a fallback action for requests that match no earlier rule. Example domains illustrate syntax only.
Keep in mind: A rule’s policy may refer to a policy group defined in the configuration; check the name and the group’s selected option. Domain matching, DNS resolution, and IP matching are separate steps, so the final IP alone does not show that a domain rule failed. Keep a copy of the original file, test with one narrowly scoped rule, then expand gradually. See Rule Order and FINAL Explained for examples.
03 / SERVER MANAGEMENT
Manage subscriptions and servers separately
What they do: Server entries store connection details such as protocol, address, port, and authentication. Subscriptions retrieve and refresh server entries in bulk. Config files define behavior such as routing and DNS. These are related but separate: updating one does not update the others. A successful subscription refresh means readable content was retrieved; it does not guarantee that every server can connect.
Where to find them: Existing servers usually appear in the Home list, where you can select one. Use Add Server to enter details manually or Scan QR Code to scan a code. Before importing a link, check whether it contains a server subscription or a configuration file, then use the matching option in your interface. Subscribe in Config is for the relevant configuration content; do not mix URLs with different purposes.
How to configure them: Get the original details from a service you already use. Before importing, check that the link is complete and has no extra spaces. For manual setup, select the correct protocol, then verify the address, port, password or ID, transport, and TLS settings. Shadowsocks, VMess, VLESS, Trojan, Hysteria2, and WireGuard each require different parameters; changing only the protocol name does not make the same settings work for all of them. Save your changes, select the entry, and test it.
Keep in mind: Refreshing a subscription may recreate server entries, and edits to subscription-provided entries may be overwritten by a later update. If you need to keep custom changes, first check whether your version offers a separate way to save them, and record what you changed. Before deleting a subscription, verify which group it belongs to so you do not remove other information by mistake. Links, QR codes, and connection logs may contain credentials; redact them before sharing screenshots or asking for help. This site does not provide, sell, or recommend servers or subscriptions.
04 / ON DEMAND
On Demand: Connect based on conditions
What it does: On Demand uses the system’s on-demand mechanism to start a connection when configured network conditions are met. It controls when a connection starts; Global Routing controls how requests are handled after it starts. They are not interchangeable. On Demand does not fill in missing server details or fix an unavailable network.
Where to find it: Check the On Demand conditions in Settings or wherever they appear in your version, and verify the VPN configuration saved by the system. Available conditions vary by system and interface, so do not assume another device’s screenshot will show the same controls.
How to configure it: Turn off On Demand first, then connect manually and confirm that an existing server works. Once it does, enable On Demand. If the settings offer conditions for Wi-Fi, cellular, or network names, start with one network. Save the setting, switch to the target network, and check the system connection status and actual browsing result. Add one condition at a time, noting which networks should connect and which should remain unchanged.
Keep in mind: If a connection returns automatically after you turn it off, an On Demand condition may have been met again; the toggle may be working as intended. To pause connections, turn off On Demand before disconnecting. When troubleshooting conflicts between VPN configurations, also check for on-demand rules in system settings. Network changes, sleep, and reconnection are managed by the system, so On Demand does not guarantee a continuous connection.
05 / DATA
Data: View traffic, not billing
What it shows: Data helps you monitor traffic handled by the app. Upload, download, totals, and current rate measure different things, so check each field’s name and reporting period. The app’s counters, system network statistics, and service provider billing may use different measurement methods; one figure cannot be used to calculate another directly.
Where to find it: Open Data to see the statistics available in your version. Check when the counters started and whether they cover a session or another period. For cellular data usage, also check system settings. For the allowance on a service you already use, refer to that service’s own records.
How to check it: Before investigating unexpectedly high usage, note the current counter, connection time, and network type. Temporarily pause known background tasks such as system updates and cloud sync, then repeat the same activity for comparison. If the interface offers a reset, save any records you need first. Keep the test duration and activity similar so you are not comparing different time windows.
Keep in mind: Requests, responses, retransmissions, and connection maintenance can all affect traffic totals. Traffic in Data does not mean the target page finished loading, and a low rate does not necessarily indicate a protocol problem. Traffic statistics do not measure connection latency; check reachability with Connectivity Test, a request to the target, and logs.
06 / SETTINGS
Recommended order for changing common Settings
Settings includes options for DNS, testing, shortcuts, and data sync. Before making changes, distinguish global settings from those inside the active Config file. When the same topic appears in both, check the active configuration and logs to confirm which setting takes effect; an old value left in a field does not establish its priority.
DNS: Check name resolution first
What it is and where to find it: DNS resolves domain names to IP addresses. Related options may appear in Settings and in the DNS section of Config. If a domain fails to load but a known IP address works, DNS is one thing to check; certificates, the destination service, and rules can cause similar symptoms.
How to configure it and what to watch for: Record the current DNS method first. Check whether your network requires a specific local DNS service, then adjust the setting to suit your needs. Names on a corporate or local network may depend on DNS provided by that network; replacing it can break access. Encrypted DNS also needs a working transport path. If DNS requests depend on a proxy connection that has not yet been established, this can create a connection dependency. After changing the setting, retry the request and check the resolution logs.
Test Method and Connectivity Test
What they are and where to find them: In Settings, choose a Test Method available in your version, then run Connectivity Test for a server from Home. Different methods test different layers: a reachable port confirms only part of the connection path, while a test against a target URL may also depend on TLS, the target’s response, and timeout settings.
How to configure them and what to watch for: To compare servers, use the same test method, target, and network, and look at multiple results rather than just one. If a test fails, check whether the method supports that protocol, especially for transports that rely on UDP. A successful test still does not confirm that a particular app or website works. Do not repeatedly switch test targets just to get a lower number; that makes results hard to compare.
Today Widget: System requirements for shortcuts
What it is and where to find it: Today Widget provides a quick way to view or control the app when supported by the system. Check Settings and the system’s widget or component picker to see what is actually available. It is not a separate proxy configuration and does not replace server selection in Home.
How to configure it and what to watch for: First, establish a normal connection in the app. Then add the widget where your system supports it and test its controls. If the widget is not listed, do not assume every device or system version offers the same option. Widget updates may also depend on background scheduling. If its status does not match, check the app and then the system VPN status; avoid rapidly tapping multiple connection controls.
iCloud: Back up before syncing
What it is and where to find it: iCloud-related options in Settings support the sync or import operations available in your version. Check the interface for the sync scope; do not assume that servers, subscriptions, logs, and every toggle are all copied.
How to configure it and what to watch for: Confirm that your devices use the intended iCloud account and that the required access is allowed in system settings. Before enabling sync, merging, or restoring for the first time, keep a copy of the configuration that currently works. Let one device finish, then check the other to avoid conflicts from editing both at once. The account used for app purchases and the iCloud account serve different purposes; restoring purchases does not restore configuration. Treat configurations that contain authentication details as sensitive data.
07 / DIAGNOSTICS
Diagnostics and restoring settings
What it does: Diagnostics collects and displays the connection information available in your version. Logs can help identify issues with DNS resolution, connections, authentication, or rule matching, but a single error rarely explains the whole problem. Relate it to the time the issue occurred and what you were doing.
Where to find it: Open Diagnostics from Settings or use the diagnostics option shown in your current interface. If temporary detailed logging is available, enable it only while reproducing the issue. Available diagnostics may vary by system and version.
How to use it: Note Global Routing, the selected server, the active Config, and the network type before enabling only the logs you need. Reproduce one clearly defined action, note the sequence, and review entries from around that time. Follow the steps below in order, moving on only after the previous one checks out:
- Disconnect temporarily and confirm that the current Wi-Fi or cellular network works on its own. Sign in to the network first if required.
- Disable automatic connection triggers from On Demand, select an existing server manually, and verify its protocol and authentication settings.
- Use the same Test Method for Connectivity Test, then confirm the result with a request to the actual destination.
- Compare Proxy and Config temporarily. If only Config has the issue, check the active file, rule order, and policy groups.
- If the symptoms point to DNS, check DNS settings. Also confirm that the device’s date and time are set automatically to avoid TLS validation issues.
- Revert any changes from this troubleshooting session that did not help, and restore your usual Global Routing mode and On Demand conditions.
Keep in mind: Diagnostics may contain server addresses, subscription URLs, authentication details, visited domains, and local network information. Review everything before exporting, keep only what is needed to investigate the issue, and redact sensitive data. After reproducing the issue, restore your usual logging level to avoid collecting unnecessary information. Do not delete all configurations or reinstall without a backup; you could lose useful evidence without fixing a network or server-side problem.