Shadowrocket Glossary
Look up terms as they appear in the interface. To determine how a request is routed, first check Global Routing, then whether configuration-based routing is enabled, and finally the matching conditions and policy.
Interface & Toggles
Check the current routing mode first
- Global Routing
- Choose how traffic handled by the client is routed. The three modes—configuration, proxy, and direct—correspond to Config, Proxy, and Direct. This setting is separate from the connection toggle.
- Config
- When selected in Global Routing, this means traffic is handled according to the currently enabled configuration. The same term is also used for the in-app configuration management page; seeing a file there does not mean it is active for the current connection.
- Proxy
- The proxy mode in Global Routing, which typically sends traffic handled by the client through the selected proxy server. To check whether rules are matching as expected, first make sure Config—not Proxy—is selected.
- Direct
- The direct mode in Global Routing, which routes traffic handled by the client without a proxy server. This is different from disconnecting: selecting Direct does not turn off the system VPN.
- On Demand
- Allows the system to start a VPN connection when the conditions you set are met. It controls when the connection starts; it does not replace routing rules. Once connected, traffic paths still depend on the current Global Routing mode and applicable configuration.
Protocols
Identify the protocol from the server details
The protocol determines how the client communicates with the server. When importing or entering details manually, use the type and fields specified in the existing server information; do not choose a protocol based on a similar name.
- Shadowsocks
- An encrypted proxy protocol for forwarding traffic between the client and server. If a connection fails, getting the address and port right is not enough—the encryption method and password must also match the server.
- VMess
- A proxy protocol with authentication and data protection; server details typically include a UUID. If transport settings and related parameters are provided, check those too. Matching identity fields do not guarantee that the transport settings are correct.
- VLESS
- A proxy protocol that separates the protocol from the security settings of its outer transport, typically using a UUID to identify the user. Do not select VMess just because the details also include a UUID; enter the outer transport settings as specified as well.
- Trojan
- Typically carries proxy connections over TLS and uses password authentication. The server address, TLS server name, and password each serve a different purpose. A reachable address does not mean authentication or certificate-name verification has succeeded.
- Hysteria2
- A QUIC-based proxy protocol that relies on UDP. The same connection may behave differently on Wi-Fi and cellular networks; checking that the destination's TCP port is reachable is not enough to confirm that this connection will work.
- WireGuard
- A tunneling protocol that carries data at the IP layer and uses UDP and keys to identify the peer. The peer address establishes communication; the allowed address range determines which IP traffic can be sent to that peer. They are separate parameters.
Rule Keywords & Policies
Separate matching conditions from outcomes
Rule keywords answer “which requests match?”; policies answer “what happens when they do?” Uppercase policy names in a configuration file and interface terms in Global Routing operate at different levels.
- DOMAIN-SUFFIX
- Matches the specified domain and its subdomains. For example,
DOMAIN-SUFFIX,example.com,PROXYmatchesexample.comandapi.example.com, but notnotexample.com.
- GEOIP
- Matches the destination IP based on its registered location in an IP geolocation database. This checks the destination address, not the device's location or a domain suffix. Database classifications may differ from the server's actual location.
- IP-CIDR
- Matches a destination IPv4 address by network prefix. For example,
192.168.0.0/16represents a network, not a single address. The corresponding IPv6 rule keyword isIP-CIDR6.
- FINAL
- Specifies where requests go if none of the preceding rules match. For example,
FINAL,PROXYsends the remaining traffic through a proxy. It is generally placed at the end of the rule list and does not override earlier matching rules.
- PROXY
- Sends traffic matching this rule through a proxy. This policy determines the route but does not provide server settings; a usable proxy connection is still required for requests matching PROXY to complete.
- DIRECT
- Routes matching traffic to its destination over the current network without a proxy server. This applies only to matching traffic; it does not switch the entire app to Direct mode or guarantee that the destination is reachable directly.
- REJECT
- Rejects connections or requests that match the rule. A domain-only condition cannot distinguish between different pages or resources on the same domain; an overly broad rule may also block requests you need.
Subscriptions & Configurations
Distinguish server details, server lists, and rule files
- Subscribe
- Import or update a server list using an existing subscription URL. Before switching to a new URL, confirm that it belongs to a service you already use. Links may contain access credentials, so don't include the full URL in public screenshots or feedback.
- Add Server
- The entry point for adding a record from existing server details. Select the protocol specified in those details, then enter the address, port, and applicable authentication information. Saving a record only adds the details; it does not confirm a successful connection.
- [Rule]
- The section of a configuration file where routing rules are defined. Rules are evaluated in order, so place specific conditions before broader ones that could take precedence. Also check that the final FINAL rule behaves as expected.
See how to import a configuration and connect for the first time →
Diagnostics & Data
Understand test results and traffic statistics
- Connectivity Test
- Tests whether a connection is available by sending a request to a test target. A successful test only confirms that the test request completed at that time. If an app still cannot connect, check the domain it uses and which policy matches it.
- Latency
- The time taken for a single probe, usually shown in milliseconds. For a meaningful comparison, keep the network, test target, and test method consistent. Lower latency does not necessarily mean faster large-file transfers.
- DNS
- Looks up records such as the IP addresses associated with a domain. Domain and IP rules use different matching criteria: a DNS response does not mean access succeeded or that the request went through a proxy.
- Data
- The page showing traffic statistics recorded by the client. Before comparing figures by server or app, check the statistics scope, upload and download directions, and time period. Client figures should not be treated as the provider's billing records.
Where to Get Shadowrocket
Two ways to get Shadowrocket: The iPhone and iPad app is a one-time $2.99 purchase on the App Store (see the store listing for system requirements). The Mac versions for Apple silicon and Intel, as well as the Windows, Android, and Linux versions, are free. Get installers from this site at /dl/shadowrocket/.
A one-time app purchase is not a service plan. Subscription and server terms assume you already have your own service details; this site does not provide, sell, or recommend routing services.
See downloads for all platforms and how to verify the official app →