Interface terms and toggles, protocols, rule keywords, subscriptions and configuration, and app-store and purchase information.
Look up a term by name, then use its location in the app to understand its role. Interface terms and rule keywords are shown in their original English. Each card has a direct link via its address-bar anchor. If you are setting up Shadowrocket for the first time, start with the setup tutorial. You do not need to read the entries in order.
01 / CONTROLS
Interface & Toggles
Start with where the term appears. Config has a different role in the routing mode selector than it does on the file management page.
Interface & Toggles / Routing selector
Global Routing
The Global Routing mode selector offers three common modes: Config, Proxy, and Direct. Config handles requests according to the rules in your configuration; Proxy and Direct set the overall routing direction. Selecting a mode and enabling the connection are separate actions. After choosing a mode, check the default server and confirm that the connection is active.
In Global Routing, Config means requests are routed according to the active configuration, rather than all being sent in one fixed direction. On a page name, Config refers to configuration file management. To troubleshoot, check that Config mode is selected, the intended file is enabled, and its rules are in the right order. The label alone does not confirm that routing is working.
Interface & Toggles / Routing modes
Proxy / Direct
These two capitalized interface terms refer to proxy and direct connection modes. Use them to compare how traffic behaves under different routing choices. They are not the same as the uppercase rule policies PROXY and DIRECT. Switching to Proxy will not fix a password, port, or TLS setting. If Direct works, that alone does not prove the rules file is wrong.
Interface & Toggles / Automatic triggers
On Demand
On Demand triggers connection behavior based on conditions such as the network environment—for example, applying different behavior on a specific Wi-Fi network. It controls when to connect; it does not replace server authentication details. Confirm that a manual connection works before adding conditions one at a time. If several conditions are configured, check their order and whether the current network meets the intended criteria.
Interface & Toggles / Entering settings
Add Server
Use Add Server to create a server entry. Choose a protocol first, then enter the address, port, and required authentication details. Follow the information from your service provider; fields do not mean the same thing across protocols. Saving creates an entry but does not connect to it. In Home, select the default server, turn on the connection, and confirm that it connects successfully.
Interface & Toggles / Diagnostics
Connectivity Test
Use Connectivity Test to check reachability and response time, especially after the first connection or after changing servers. A latency result reflects only the conditions of that test; it is not a download-speed measurement and does not confirm that every domain is routed as expected. If a test fails, note the test method and error, then check server settings, the current network, and DNS separately.
02 / PROTOCOLS
Protocols
A protocol defines how the client and server exchange data. Matching protocol names is only the first step; authentication, transport, TLS, and other settings must also match.
Protocol / Encryption method and password
Shadowsocks
A protocol that uses an agreed encryption method and password to carry proxy traffic. In addition to the server address and port, set the encryption method to match the server. Do not reuse authentication fields from another protocol. Check any additional details provided by your service provider. An address can be reachable while authentication still fails, preventing requests from being forwarded.
Protocol / Identity and transport
VMess
An authenticated proxy protocol whose configuration typically includes a UUID and may also specify a transport method, path, and TLS settings. The UUID is an important authentication field, but it is not the whole configuration. If the connection fails after import, compare the transport and certificate requirements with the original details instead of repeatedly changing the server name.
Protocol / Parameter combinations
VLESS
An authenticated proxy protocol that uses a user identifier. Its name alone does not reveal the transport security setup. Check the UUID, transport method, TLS, and all other options against the server requirements. A successful import only means the text was parsed into an entry; it does not guarantee compatible settings or network access to the server.
Protocol / TLS
Trojan
Carries proxy traffic over TLS and typically uses password authentication. SNI indicates the server name during the TLS handshake and may differ from the connection address; follow the server details when setting it. If a certificate error occurs, check the domain name, device time, and certificate requirements first. Allow Insecure lowers the certificate verification requirements and should not be used as a routine fix.
Protocol / QUIC and UDP
Hysteria2
A QUIC-based proxy protocol that depends on UDP connectivity. In addition to authentication and TLS settings, check whether the network allows the required UDP traffic. Direct access to ordinary websites does not guarantee that this protocol connection will work. Consider the server address, port, and current network conditions rather than relying on latency alone.
Protocol / Peer and address ranges
WireGuard
A protocol that creates a tunnel using public and private keys and Peer settings. It uses details such as Private Key, public key, Endpoint, local addresses, and Allowed IPs. Private Key is sensitive information and should not appear in diagnostic screenshots. Allowed IPs describes IP address ranges for the tunnel, not a domain routing list; domain suffixes are not a substitute.
03 / MATCH → POLICY
Rule Keywords
A rule typically contains a match type, a value to match, and a policy. First identify what the rule matches, then determine what happens when it matches.
Rule Keywords / Exact domain
DOMAIN
Matches an exact domain, for example DOMAIN,example.com,DIRECT. This does not include every subdomain. To match subdomains, check whether DOMAIN-SUFFIX is needed. Do not include a protocol prefix, port, or page path in the domain field. Pasting a full URL here will not match by page path.
Rule Keywords / Domain suffix
DOMAIN-SUFFIX
Matches a target domain and its subdomains by domain suffix, making it useful for applying a policy to an entire domain. For example, DOMAIN-SUFFIX,example.com,PROXY expresses this type of condition. Put more specific exceptions before broader rules. After making changes, check request logs to confirm which rule matched; whether a page loads is not enough to verify the result.
Rule Keywords / IP geolocation
GEOIP
Matches a request's destination using an IP geolocation database, for example GEOIP,CN,DIRECT. Database records do not indicate a site's interface language, operator location, or visitor location. This is especially important for destinations using distributed services. If the result is unexpected, check the actual destination IP, resolution results, and database criteria—not just the site name.
Rule Keywords / Address ranges
IP-CIDR / IP-CIDR6
Matches IPv4 and IPv6 address ranges. The prefix length after the slash determines the size of the range. 192.168.0.0/16 is an IP subnet, not a server port. An IPv4-only condition does not automatically cover IPv6. If a destination provides both address types, check which one the connection actually uses.
Rule Keywords / Final policy
FINAL
Specifies the policy for requests that did not match any earlier rule and is usually placed at the end of the rule list. The difference between FINAL,DIRECT and FINAL,PROXY is the routing direction for remaining traffic, not whether rules are enabled. If many requests fall through to FINAL, review the match fields and order of earlier rules, along with the actual request domains.
Rule Policies / Proxy
PROXY
The uppercase PROXY is a rule policy that sends matching requests through a proxy; it is not a server protocol. Matching a rule and connecting to a server are separate stages. Even with the correct policy, incorrect server settings or network conditions can cause failure. Check the matched rule, selected server, and connection error details.
Rule Policies / Direct connection
DIRECT
Connects directly to the destination without forwarding the request through a proxy server. DIRECT does not bypass the current network, DNS, or restrictions imposed by the destination service, and it does not turn off the entire client. If a domain fails over a direct connection, first check its resolved address and local network, then consider whether the rule needs adjustment.
Rule Policies / Reject
REJECT
Rejects requests that match the rule and can be used to control access to specific destinations. Overly broad conditions can disrupt sign-in, resource loading, and other normal functions. Confirm the exact request before adding a reject rule. If part of an app stops working, check the logs for REJECT matches instead of deleting the entire configuration.
04 / SUBSCRIBE & CONFIG
Subscriptions & Configuration
A subscription updates connection details; a configuration file organizes behavior. Importing one does not mean the other is ready.
Subscriptions & Configuration / Bulk import
Subscribe
Use a subscription URL to import and update a set of server entries. Get subscriptions from your service provider. The URL may contain account credentials, so hide the full address before sharing logs or screenshots. A failed update does not necessarily mean all existing servers have stopped working. Check the subscription URL, whether the update request can reach it, and whether existing entries still connect.
Subscriptions & Configuration / Server entry
Server
A connection entry stores a server address, port, protocol, and authentication settings. Its display name is just a label for identification; it does not determine how the connection works or reveal its actual location or performance. An entry being imported, selected as the default, and connected are three different states. Check them in that order.
A file for organizing rules, DNS, and related behavior settings; it is not the same as a server subscription. Keep the current file before switching configurations, and check the new file's rule order and final policy. After enabling it, confirm that Global Routing is set to Config. Repeatedly overwriting files from different sources without keeping track makes it difficult to tell which change affected behavior.
Subscriptions & Configuration / Domain resolution
DNS
DNS resolves domain names to IP addresses. The results affect the actual connection destination and can also affect rules that depend on destination IP. If a server connects but a particular domain does not load, check DNS separately. Record the current settings before changing them, then retest the same destination so you can compare results without changing multiple variables at once.
Subscriptions & Configuration / Request handling
URL Rewrite
URL rewriting and other actions applied under specified conditions are separate from server selection and domain-based routing. HTTPS behavior is also limited by encryption, certificates, and the app itself; do not assume that all request contents can be modified. Change these entries only when you understand their matching scope and effect. If something goes wrong, disable the relevant entry temporarily for comparison.
05 / STORE & IDENTITY
App Store & Purchases
Shadowrocket is available for iPhone, iPad, Mac, Windows, Android, and Linux. Keep acquisition options, purchase history, and client configuration separate.
App Store & Purchases / Getting the app
App Store
The iPhone and iPad version is a one-time $2.99 purchase on the App Store; local currency and pricing are shown by the store. The Mac (Apple Silicon and Intel), Windows, Android, and Linux versions are free and available from this site's download page. Check the App Store listing for iPhone and iPad system requirements. Store region affects whether a listing appears, so do not identify an app by search results alone.
The App Store section for finding apps you previously purchased. When changing devices or reinstalling, check that you are using the original purchase account and that the app is available in your current store. Redownloading the app does not restore servers or rule files; purchase history is not a configuration backup. For computers and Android devices, use the download page instead of this App Store feature.
For iPhone and iPad, check the official icon, developer Shadow Launch Technology Limited, and app ID 932747118; the name alone is not enough to identify the app. Get the Mac, Windows, Android, and Linux versions from this site's download page. Installers use this site's /dl/shadowrocket/ path. If the system displays a warning the first time you open the app, follow the installation approval steps for your platform on the download page.