Official Manual · Glossary

Shadowrocket Glossary

Look up terms by interface location and configuration purpose. First identify where a setting lives, then determine what it matches and how it handles traffic. English names are kept as they appear in the interface and rule files.

This page explains general Shadowrocket concepts; menu locations may vary by platform. If you already have a subscription or server details, follow the Getting Started guide. For full syntax, see the rule reference.

Getting Shadowrocket: The iPhone / iPad app 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 guide for platform links.

Interface & switches

Interface options determine the current operating mode. Don’t confuse title-case option names with uppercase rule policies.

Interface & switches

Global Routing

The control for how traffic is handled overall. The three common options are Config, Proxy, and Direct. With Config selected, the active configuration rules determine where traffic goes; Proxy and Direct switch the overall handling mode. If rules aren’t taking effect, first check that this is still set to Config.

Interface & switches

Config

Depending on where it appears, Config can mean the configuration management screen or the Config mode in Global Routing. Viewing a file on the configuration screen does not mean it is selected for use. In Config mode, also check which configuration is active and review its Rule section.

Interface & switches

Proxy

The proxy mode in Global Routing routes traffic through a proxy, subject to the platform’s networking behavior and the active configuration. It is not a protocol and does not fill in server details. The interface option Proxy and PROXY at the end of a rule belong to different layers.

Interface & switches

Direct

The direct mode in Global Routing, useful for checking whether a problem is related to the proxy route. Selecting Direct does not turn off the client connection switch; the client may still be handling network traffic. To compare against a fully disconnected state, turn off the connection separately and test the same destination again.

Interface & switches

On Demand

A mechanism that starts a connection when preset conditions are met, reducing the need for repeated manual actions. It controls when a connection starts; Rule controls how each request is handled after the connection is up. When troubleshooting automatic reconnections, check both the On Demand conditions and the system VPN status.

Interface & switches

Connectivity Test

Checks whether the selected route can connect under specific test conditions. Results depend on the test method, destination, and current network; they are not a measure of sustained download speed. If the test gets a response but webpages won’t load, continue by checking DNS, rule matches, and the destination service.

Protocols

A protocol defines how a client and server communicate. Similar names or a shared port do not mean their settings are interchangeable.

Protocols

Shadowsocks

A protocol that uses symmetric encryption to protect proxy traffic between a client and server. Match the server address, port, password, and encryption method; checking just one field is not enough. UDP support also depends on the server configuration and current network conditions.

Protocols

VMess

A proxy protocol with authentication. Connection details typically include a user ID and transport settings. Protocol parameters, transport type, and TLS settings are separate layers and must each match the server configuration. If authentication fails, check the connection details and device time rather than changing encryption options at random.

Protocols

VLESS

A proxy protocol that separates authentication from underlying transport security. The protocol name alone does not mean the connection is encrypted; actual protection depends on the security settings of the transport in use. Check the user ID, transport type, and security parameters provided by the server.

Protocols

Trojan

A proxy protocol that typically runs over TLS. Both authentication details and certificate validation affect whether a connection can be established. The server address and the name used for TLS validation may serve different purposes; use the connection details you have. If you get a certificate error, check the name, certificate validity period, and device time first.

Protocols

Hysteria2

A QUIC-based proxy protocol that relies on UDP. Packet loss, bandwidth, and network restrictions can all affect performance. High latency does not necessarily mean it will be faster; compare it on the same network. If the handshake times out, first check whether the required UDP traffic can get through, then verify the authentication and TLS settings.

Protocols

WireGuard

A UDP-based tunneling protocol that identifies peers using key pairs. In addition to the server endpoint, configure the local address, peer public key, and allowed routes correctly. If the handshake succeeds but traffic does not, check routing and DNS. Keep private keys confidential; don’t include them in public screenshots.

Protocols

HTTP / SOCKS5

Two common proxy protocol names, not simply choices for a website address prefix. The base protocols do not guarantee encryption between the client and proxy server; protection depends on any additional security encapsulation. SOCKS5 UDP forwarding also requires support in both the server and client configuration.

Rule keywords & policies

The beginning of a rule specifies its match condition; the end specifies what to do. The domains and address ranges below illustrate syntax only; they are not connection details.

Rule keywords & policies

Rule

The configuration section that defines match conditions and actions is typically named [Rule]. More rules do not mean higher priority: rules are checked from top to bottom, and the first match applies. Put specific conditions before broader ones, then use FINAL as a fallback at the end.

Rule keywords & policies

DOMAIN

Matches one exact domain, for example DOMAIN,example.com,DIRECT. This rule does not automatically include subdomains such as www.example.com. Exact matching is easier to verify when you want to change the route for just one hostname.

Rule keywords & policies

DOMAIN-SUFFIX

Matches a domain and its subdomains, for example DOMAIN-SUFFIX,example.com,PROXY. It matches based on the domain suffix, not on an arbitrary string appearing anywhere. Use it to send requests across a domain family to the same policy without repeating rules.

Rule keywords & policies

DOMAIN-KEYWORD

Checks whether a domain contains a specified keyword, for example DOMAIN-KEYWORD,ads,REJECT. Short keywords may match unrelated domains, so this example is not a complete blocking solution. If it matches too broadly, narrow the condition or add a more specific exception above it.

Rule keywords & policies

GEOIP

Selects a policy based on how the destination IP is classified in the geolocation database in use, not on the webpage language or device region. Database classifications may differ from where a service is actually hosted, and the result can also depend on the IP address returned by DNS. For services with specific routing requirements, check more precise domain rules as well.

Rule keywords & policies

IP-CIDR / IP-CIDR6

Matches IPv4 and IPv6 address ranges. The number after the slash is the network prefix length. For example, IP-CIDR,192.168.0.0/16,DIRECT describes a private IPv4 range. An IPv4 rule alone does not mean the same service’s IPv6 address will also match.

Rule keywords & policies

FINAL

The policy used when none of the preceding rules match, for example FINAL,PROXY. It usually goes at the end of the Rule section; placing it earlier prevents later conditions from being checked. Choose PROXY or DIRECT as the fallback based on your configuration goals.

Rule keywords & policies

PROXY

When a rule matches, the request is handled by the currently selected proxy or the proxy policy defined in the configuration. This is an action, not a server address, and it does not specify a protocol such as Shadowsocks. To find out which connection will actually be used, check the selected server and how the configuration maps its policies.

Rule keywords & policies

DIRECT

Routes the matching request directly instead of forwarding it through a proxy server. It only sets the route for requests that match this rule; it does not switch every other request in the configuration to a direct connection. If the destination is unreachable, using DIRECT is no guarantee that access will be restored.

Rule keywords & policies

REJECT

Rejects matching requests, typically for connections you do not want to make. Rejecting a domain may also affect images, sign-in, or other features that rely on the same domain. If page content is missing, check the match logs before changing the condition.

Subscriptions & configuration

Server details, server lists, and rule files serve different purposes. Before importing, check what kind of content you have; after an update succeeds, verify which item is actually selected.

Subscriptions & configuration

Subscribe

An entry point for importing or managing subscription content. Get subscription links from your service provider. A subscription may return a server list or configuration content, so you can’t tell what it contains just from how the link looks. Updating rereads the remote content; it does not extend a service’s validity period.

Subscriptions & configuration

Add Server

An entry point for manually entering the details of a single server connection. A server is a remote endpoint for proxy connections, often called a node. Choose the right protocol first, then enter the address, port, and authentication details from the information you already have. The display name is only a local label; changing it does not change the server.

Subscriptions & configuration

Configuration file

A text file that organizes settings such as General, Rule, and Host to define network behavior. A server list tells you which connections are available; a configuration file may specify how requests are resolved, matched, and handled. They are not interchangeable. Keep a copy of the original before changing configurations so you can compare or restore it.

Subscriptions & configuration

URL Rewrite

A configuration section for URL rewriting or redirects, with a different purpose from Rule-based request routing. Whether a rule takes effect depends on its match expression, request format, and visibility; a matching domain alone is not enough. For HTTPS traffic, keep TLS boundaries in mind. Ordinary route selection does not require changing certificate settings.

Networking & DNS

Name resolution, connection establishment, and data transfer are separate stages. Passing a test at one stage does not verify the others.

Networking & DNS

DNS

The mechanism that resolves domain names to IP addresses and other records, and a prerequisite for accessing most domains. A DNS response does not mean the destination port is reachable; likewise, normal server latency does not mean the service domain is resolving correctly. When troubleshooting, check whether the lookup succeeded, which address it returned, and how subsequent rules handle that address.

Networking & DNS

Latency

The time taken for a request and response in a particular test, usually measured in milliseconds. What the value means depends on the test method. Low latency does not mean high available bandwidth or guarantee fast responses from every destination. For a useful comparison, keep the test target, network, and method consistent, then check performance in the actual app or service.

Networking & DNS

TCP

A transport protocol that provides an ordered, reliable byte stream, handling network changes with acknowledgments, retransmission, and congestion control. Even after a connection succeeds, packet loss or competing bandwidth can slow data transfer. If an app uses TCP, a test using another transport is only a clue, not a direct measure of the app’s performance.

Networking & DNS

UDP

A datagram-based transport protocol that does not guarantee delivery or ordering on its own; higher-level protocols can add their own reliability mechanisms. QUIC and WireGuard both rely on UDP, so UDP is not simply for unreliable applications. If TCP works but UDP connections time out, check the network path and server listener separately.

Want to turn these concepts into steps? Read Getting Started. Need the configuration structure and rule order? See the rule reference.