Official manual

Shadowrocket Glossary

First identify the action associated with an interface term, then distinguish protocols, matching conditions, and handling policies. Use this page to look up terms while reading a Shadowrocket configuration; available options may vary by app interface.

PlatformiPhone / iPad Available onApp Store Import your existing configuration

Browse by task

Five term categories, organized by function

Interface terms help you find controls, protocols describe connection types, and rules determine how requests are matched. Subscriptions and configurations organize content you already have; DNS and network terms explain name resolution and request handling.

01 / INTERFACE

Interface and controls

These English terms are used in the app interface. When looking for a control, match its English label and distinguish routing options from rule policies.

Home: The main screen shows existing server entries and connection status. Before using Shadowrocket for the first time, import your own configuration and select the entry you want to use.

Global Routing: Choose the default routing mode for connections. Common options are Config, Proxy, and Direct. Before switching, decide whether you want rules to handle requests or prefer a consistent routing mode.

Config: In Global Routing, Config handles requests according to the rules in the current configuration file. Rules are generally checked from top to bottom, and processing stops at the first match, so their order matters.

On Demand: Choose when to try connecting based on preset network conditions. Review Wi-Fi, Cellular, and Domain conditions separately to avoid unexpected behavior when multiple conditions apply at once.

Add Server: Use this entry point to add server details you already have. After selecting the relevant protocol, enter the address, port, and authentication parameters exactly as provided.

Connectivity Test: This feature checks whether the selected connection is reachable. Results depend on your current network and the destination; a single test result is not a reliable measure of actual loading speed.

02 / PROTOCOL

Protocols

Protocol names identify the type of server details you already have. Use the original parameters when importing; a protocol name alone cannot fill in missing settings.

Shadowsocks: A proxy protocol that establishes a connection using client and server parameters. Check that the server address, port, encryption method, and authentication details match the information you have.

VMess: A connection protocol that requires corresponding server parameters. If the connection fails after importing, check the credentials, transport settings, and any other requirements provided by the server.

VLESS: A connection protocol whose name alone does not define a complete configuration. The transport method, security parameters, and server settings must correspond; do not substitute them arbitrarily.

Trojan: A protocol that establishes a connection using a server address, port, and authentication details. Also check any secure-connection requirements in the information you have.

Hysteria2: A QUIC-based connection protocol. Authentication and other connection parameters must match the server configuration you already have.

WireGuard: A network protocol that establishes a connection using keys and peer parameters. Distinguish local interface settings from peer settings, and enter address ranges as specified in the information you have.

03 / MATCH & ACTION

Rule keywords and policies

The left side of a rule defines its matching condition; the final policy specifies what happens when it matches. Check the order, condition, and policy. FINAL handles requests that matched no earlier rule and belongs at the end.

DOMAIN-SUFFIX: Matches a domain suffix and its subdomains. For example, DOMAIN-SUFFIX,example.com,PROXY applies the PROXY policy to domains matching that suffix.

DOMAIN-KEYWORD: Checks whether a domain contains specified text. This can match more domains than an exact domain rule, so consider which other domains may contain the same text before adding it.

GEOIP: Matches based on IP address location information. GEOIP,CN,DIRECT is one example of this rule syntax; actual matches also depend on the resolved address and current configuration.

IP-CIDR: Matches IPv4 addresses or ranges. The prefix length defines the range. Check the address and mask before adding a rule to avoid including unrelated addresses.

IP-CIDR6: Matches IPv6 addresses or ranges. It covers a different address format from IP-CIDR; check separate rules for each address type you need to match.

FINAL: Handles requests that did not match any earlier rule and is usually placed at the end of the rule list. FINAL,PROXY is a fallback example; requests matched by an earlier rule never reach it.

PROXY / DIRECT / REJECT: These are policies applied when a rule matches: PROXY routes the request through a proxy, DIRECT connects directly, and REJECT denies the request. PROXY and DIRECT are rule policy terms; Proxy and Direct in Global Routing are interface options.

Rule order example

Put specific conditions first and the fallback rule last. This example illustrates syntax and matching order only; it is not a complete configuration to use as-is.

DOMAIN-SUFFIX,example.com,PROXY
GEOIP,CN,DIRECT
FINAL,PROXY

04 / INPUT

Subscriptions and configuration

These terms assume you already have your own subscription or server details. Importing is a configuration step; it does not provide the information needed to connect.

Subscription link: An update URL for configuration content you already have. After importing, check that the entries were parsed correctly. If the content changes later, update the subscription as needed.

Server details: Typically includes an address, port, protocol, and corresponding authentication parameters. When adding a server manually, identify the protocol first, then check each field against the information you have rather than guessing from its name.

Configuration file: Organizes rules, policies, and related settings. After editing, check the rule order and the position of FINAL, and confirm that the file suits your current connection scenario.

Scan QR Code: Use this entry point to scan a QR code containing configuration details you already have. Review the detected protocol and parameters before saving and testing; the QR code does not replace checking the source information.

05 / NETWORK

DNS and networking

If a connection is established but results are unexpected, check domain resolution, request rules, and connection data separately rather than relying on the toggle status alone.

DNS: The process of resolving domain names to network addresses, as well as related settings in the app. When troubleshooting a domain, first check whether it resolves as expected, then review the connection and applicable rules.

URL Rewrite: A configuration feature that handles request addresses according to matching conditions. A rule’s scope depends on how it is written, so check which requests it will affect before making changes.

Data: An in-app view of connection data. The exact information depends on the app interface. This data can help identify connection activity, but cannot by itself confirm that a rule matched as expected.

Where to go next

From terminology to practical steps

To import content you already have, read the setup guide. To investigate connection issues step by step, see the troubleshooting manual. Shadowrocket is a one-time purchase—not a service plan—and buying the app does not provide server details or a subscription. Check the App Store listing for system requirements.

Read the setup guide Read the troubleshooting manual How to verify the official App Store listing →