Shadowrocket Rule Types Explained: How to Write DOMAIN-SUFFIX, GEOIP, IP-CIDR and FINAL

Compare the right things

App Store descriptions often place protocol names, automation, and rule features side by side, but a feature list alone does not tell you whether an app fits your routine. Start with the tasks you actually need: for example, importing an existing configuration, sending selected domains through a proxy, keeping other traffic direct, or switching between a few known routing choices. A feature that you will not use should not outweigh a clear interface or a dependable workflow.

Separate app cost from the cost of a proxy service. Shadowrocket for iPhone and iPad is a one-time $2.99 App Store purchase; its Mac (Apple silicon and Intel), Windows, Android, and Linux versions are free. The purchase price covers the app, not a connection service, subscription, or traffic allowance. This guide assumes you already have your own service. It does not provide, sell, or recommend nodes, subscriptions, or invitations.

Before comparing any paid or free option, check how it handles the configuration you already use. Look for the specific protocol names and fields supplied by your service rather than assuming that a broad claim such as “supports proxy protocols” covers every transport, authentication method, or option you need. Also check whether rules can distinguish exact domains, domain suffixes, IP addresses, and a final fallback policy if those controls matter to your setup.

Consider ongoing effort as well as the initial setup. Can you tell which configuration is active? Is it clear whether a request is being routed by rules or by a global mode? Can you update an existing subscription without replacing unrelated settings? These practical questions often matter more than an especially long protocol list. Review the current App Store product page for iPhone and iPad requirements, and consult the app’s current documentation for platform-specific feature details rather than relying on an old feature comparison.

Understand Shadowrocket’s routing options

In Shadowrocket, the choice under Global Routing changes how traffic is handled. It is useful to understand this distinction before testing rules: a routing rule cannot explain the result if the app is currently using a different global mode. For routine rule-based use, first confirm that the intended Config is active and that Global Routing is set to Config.

Config is the sensible starting point when the goal is rule-based behavior, but the “best” mode depends on the task. For example, if a site fails only when a particular rule is active, switching briefly to Proxy or Direct can help isolate whether the issue is related to the rule path or to the underlying connection. Return to the intended mode after the test; otherwise, later observations may describe the temporary setting rather than your normal setup.

In Config, rules are evaluated in configuration order. A request that matches an earlier rule may not reach a later, more specific exception. Keep exceptions above broad rules and place FINAL at the end as the fallback. A simple example is DOMAIN-SUFFIX,example.com,PROXY; it should be interpreted in the context of the full configuration and its policies, not copied as a complete working configuration. When a route is unexpected, check the active Config, Global Routing, rule order, and the result for a new request before changing several entries at once.

Check protocols and rules in practice

Protocol support should be checked against the exact connection details supplied by your existing service. Names such as Shadowsocks, VMess, VLESS, Trojan, Hysteria2, and WireGuard identify different protocol families; a name appearing in a feature list does not guarantee that every server-side option or transport variation is supported in the way you need. Compare the relevant fields—such as address, port, authentication, and any transport-specific settings—with the provider’s instructions. Do not guess values from a server label.

For a subscription, use its complete URL and follow the service’s instructions for adding it. A subscription is a credential-bearing link, so do not paste it into public troubleshooting posts or screenshots. After import, check that the expected entries appear and that the selected entry is available. If a profile is empty or an update fails, resolve that import problem before editing routing rules; a rule cannot repair missing connection details.

Use a small, reversible test when comparing rule behavior. Choose a destination for which you understand the intended policy, note the current Global Routing mode, and make one change. Then create a fresh request—an already-open connection may continue on its existing route—and inspect the result. Record whether the connection itself succeeds separately from whether the expected rule matched. This distinction prevents an unreachable service from being misdiagnosed as a rule-order problem.

Evaluate battery use and usability fairly

Battery impact cannot be reduced to a universal number for a proxy app. It depends on the phone, iOS version, signal quality, connection protocol, traffic volume, background activity, and how long the connection remains active. A weak cellular signal can keep the radio working harder regardless of which app you choose. A busy sync or streaming session also consumes more energy than an idle connection. Treat any battery estimate that does not describe its test conditions as an incomplete comparison.

For a practical test, compare similar periods on the same iPhone, with the same network, destination, workload, and approximate signal conditions. Begin each session with a similar battery level, avoid charging during the test, and keep background activity as consistent as possible. Record the time window and the iOS Battery screen’s app usage after each session. Repeat the observation on more than one occasion; a single short run is easily affected by background tasks or changing reception. Do not interpret a small difference as a dependable result.

• Keep the test workload consistent: compare the same browsing, messaging, or media activity rather than an idle period against active streaming.
• Use the same network conditions where possible. If switching between Wi-Fi and cellular, record the change instead of treating the sessions as equivalent.
• Check whether the connection is intentionally kept active in the background and whether On Demand conditions are triggering reconnects.
• Look at both battery use and the behavior you need. A marginal battery difference may matter less than reliable rule handling or a simpler routine for your particular use.

Usability is similarly personal, but it can be assessed with concrete tasks. Time how long it takes to import your existing configuration, identify the active connection, select the intended Global Routing mode, and restore your normal setup after a test. Notice whether labels make the current state obvious and whether recovery steps are understandable when a subscription update or connection fails. If you are new to proxy configuration, fewer decisions per task may be more valuable than advanced controls you do not yet need.

More experienced users may value detailed Rule control, multiple configuration choices, and the ability to diagnose route behavior. Those features also introduce responsibilities: protect subscription credentials, preserve a copy before substantial edits, and avoid changing several policies at once. The right balance is the one that lets you explain what a setting does and reverse it safely. A feature is not automatically useful simply because it is available.

Make a practical choice

Before paying for an iPhone or iPad app, check the current store listing for its developer, requirements, supported protocols, and purchase terms. For Shadowrocket, the App Store listing identifies the iPhone / iPad app; confirm the developer name Shadow Launch Technology Limited and App Store ID 932747118. The iPhone / iPad version costs $2.99 as a one-time purchase, while Shadowrocket for Mac (Apple silicon and Intel), Windows, Android, and Linux is free. Download desktop and Android versions through the site’s Get the app page; do not infer that mobile pricing applies to those platforms.

Use the following decision sequence rather than choosing from a feature count alone. First, rule out any option that does not handle the protocol and configuration format your existing service requires. Next, decide whether you need rule-based routing or only a simpler global choice. Then assess whether the setup steps and current connection state are clear to you. Finally, evaluate battery behavior under your own workload instead of relying on an unqualified claim. This sequence helps avoid paying for a feature set that does not solve your actual problem.

1. Write down your must-haves. List the protocol, rule behavior, and import method you already rely on. Separate requirements from features you might explore later.
2. Check costs by platform. Verify the current purchase terms for iPhone / iPad and distinguish them from the free Mac, Windows, Android, and Linux versions of Shadowrocket.
3. Test a basic connection first. Use your own service, confirm the selected entry works, and avoid changing routing rules until the connection is available.
4. Test one routing scenario. Set Global Routing to Config, use a destination with a known expected policy, and make a fresh request after each change.
5. Review effort and battery. Repeat ordinary tasks and comparable battery observations before deciding whether the app fits your day-to-day use.

The most useful comparison is one you can reproduce: same device, same network conditions, same task, and one setting changed at a time. If Shadowrocket’s protocol support matches your existing configuration and its routing controls fit your needs, its Config mode offers a practical foundation for rule-based use. If you mainly need a simpler workflow, prioritize clear setup and predictable behavior over advanced options you will not use. Either way, keep the connection service, app price, routing policy, and battery result as separate parts of the decision.