Official Guide · Glossary

Shadowrocket Glossary

Look up terms for the interface, protocols, and configurations. In the interface, Proxy is a routing mode; PROXY at the end of a rule is the policy applied to that individual rule.

Interface & Controls

First, distinguish server selection, connection status, and routing mode. These determine which connection to use, whether it is enabled, and which requests go through a proxy.

Home
View the server list, current selection, and connection toggle. A checkmark beside a server shows which entry is selected; it does not mean a connection has been established. If a webpage will not load, first confirm that the correct entry is selected, then check the toggle and test results.
Global Routing
Choose how traffic is handled: Config uses the active configuration, Proxy routes traffic through a proxy, and Direct sends traffic directly. To check whether a rule is taking effect, first make sure the mode is set to Config. Changing modes does not change the protocol of an existing server.
Config
In navigation, this refers to the screen for managing configuration files. In Global Routing, it refers to the mode that handles traffic according to the active configuration. If changed rules do not produce the expected result, check both the selected file and the mode in use.
On Demand
Starts a connection when specified conditions are met, such as when the device switches networks. It controls when to try connecting, not whether a domain uses a proxy or a direct connection after connecting. If the connection turns back on after you disable it, check the On Demand status and trigger conditions.
Add Server
Manually add a server when you already have its details. Select the protocol specified in those details, then check the address, port, and required authentication parameters. Saving an entry only completes setup; select it and test the connection separately.

Protocols

A protocol determines how the client communicates with a server. Choose a type based on the server details you have; matching addresses and ports do not make different protocols interchangeable.

Shadowsocks
A proxy protocol primarily used for encrypted forwarding. When entering settings manually, the address, port, encryption method, and password must match the server configuration. Checking only the address and port will not rule out an incorrect encryption method or authentication details.
VMess
A proxy protocol that uses UUID to identify the user. The UUID identifies the user for the connection; it is not the server address. If the server details specify a transport, path, or TLS parameters, check those as well rather than inferring them from the address and port.
VLESS
This protocol handles the proxy protocol and transport security separately; connection protection depends on the security layer actually configured. It and VMess may both use UUID, but similar fields do not mean they are compatible. When copying an existing entry, do not just change the protocol name and reuse the other settings.
Trojan
A proxy protocol carried over TLS, usually authenticated with a password. The server address identifies the connection endpoint; the TLS server name identifies the host expected in the certificate. They do not have to be the same. If the certificate name does not match, check the relevant fields against the server details.
HTTP / SOCKS5
Two different proxy interfaces: HTTP proxies can use CONNECT to establish a tunnel, while SOCKS5 has its own connection and authentication negotiation. Whether a username and password are required depends on the server settings. The interface name alone does not indicate whether the connection to the proxy server is encrypted.
WireGuard
An encrypted tunnel protocol that uses UDP and identifies the peer with keys. Connectivity also depends on the tunnel addresses and the address ranges allowed through it, as well as the endpoint address and port. Public and private keys serve different purposes; do not include a private key in logs or screenshots when troubleshooting.
Hysteria2
A QUIC-based proxy protocol that relies on a UDP path to the server. If the same configuration works on one network but times out on another, network conditions are one thing to investigate. A single test cannot establish the protocol's speed or battery use across all devices.

Rule Keywords

Rule keywords match requests; policies determine what happens to matched requests. When checking rules, first identify whether you need to match a full domain, a domain suffix, or a destination IP, then check the rule order.

DOMAIN
Matches an exact, full domain name. A condition of example.com does not also match www.example.com. Use an exact match when you want to target a specific hostname without affecting other subdomains on the same site.
DOMAIN-SUFFIX
Matches a specified domain and its subdomains; for example, one condition can cover both example.com and docs.example.com. It matches domain hierarchy, not arbitrary strings that happen to contain the text. Enter a domain in the rule condition, without a URL scheme or path.
GEOIP
Matches according to how a GeoIP database classifies the destination address, not the website's language or domain suffix. A service may resolve to multiple addresses, and the classification can change with the address. When checking a match, verify the destination address used for that connection.
IP-CIDR / IP-CIDR6
Matches IPv4 and IPv6 address ranges separately; the number after the slash is the prefix length. An IPv4 range alone does not cover the same service's IPv6 addresses. If a rule does not match, first confirm which address type the connection actually used.
FINAL
Specifies a fallback policy for requests that do not match earlier rules, usually at the end of the rule section. If a request uses the fallback, first check whether the preceding conditions cover the actual request destination. Changing the fallback directly also affects other unmatched requests.

Subscriptions & Configurations

Server entries are used to connect; configuration files store settings such as rules. Importing an existing subscription, enabling a configuration, and syncing app data between devices are three different actions.

Subscribe
Import a server list using a subscription URL you already have. When refreshed, the list may gain or lose entries as its source changes, but refreshing it does not change routing rules. Subscription URLs may contain access credentials; redact them before sharing troubleshooting details.
SERVER
An interface label for organizing or displaying server entries. An entry name is only for identification; the actual connection depends on settings such as the address, port, protocol, and authentication details. Two entries with the same displayed name are not necessarily connected to the same server.
Configuration file
A file that stores settings such as rules, for example, matching conditions and policies in a [Rule] section. Importing a file does not select it or switch Global Routing to Config. Keep a copy of the original before editing an existing file so you can compare or restore it.
iCloud Sync
Syncs app data between devices through iCloud when account and system settings allow. After switching devices, App Store purchase history refers to the app purchase, not a configuration backup. After syncing, check which configurations and server entries are actually available on the new device.

Policies & Diagnostics

A matched policy shows how a request is handled; a test result shows whether a particular check completed. An enabled toggle or a latency reading alone does not prove that a website is accessible.

PROXY
A rule policy that sends matching requests through a proxy. A rule match does not mean the selected server is available or that the destination service has responded. Check policy matching, server connectivity, and the destination service's response separately.
DIRECT
Sends matching requests directly over the device's current network, without a proxy. The spelling is similar to Direct mode in Global Routing, but a DIRECT rule affects only requests that match it. Direct connections are still subject to current network conditions and domain resolution.
REJECT
Rejects requests that match the condition; it does not try another policy for them. If a website uses a rejected domain for images, sign-in, or another feature, that feature may fail even if the main page loads. When troubleshooting, narrow the match first, then test the affected feature again.
DNS
Resolves domain names to records such as IP addresses, and the results affect rules that depend on destination IPs. A successful lookup only means a result was returned; it does not mean the destination service can be reached. If only some domains fail, check for resolution errors first, then review the matching rules.
Connectivity Test
Checks whether a specified test can complete under current network conditions. A successful test does not prove that every website is accessible or verify that a particular traffic rule matched. For a useful comparison, keep the server, test destination, and network conditions as consistent as possible.
Latency
The time recorded for a single measurement, which can vary with the network, test destination, and measurement method. Compare it under the same conditions; low latency does not mean high bandwidth or a stable long-running connection. If a test times out, first check whether it received a response before comparing timings.
Download Shadowrocket