APP STORE · OFFICIAL MANUAL
A rule-based proxy client for iPhone and iPad. Start by verifying the App Store listing, then learn about the one-time purchase, importing existing subscriptions, and connection settings.
PURCHASE / INSTALL
Shadowrocket is a paid client for Apple platforms. This official manual is organized around purchasing, importing, modes, and verification. If you have not purchased it yet, check the App Store listing first. If it is already installed, go straight to the tutorials for step-by-step instructions.
Verify the app in the App Store, then purchase and install it. When you make your first connection, the system will ask to add a VPN configuration. Read the prompt and make sure the request comes from Shadowrocket before authorizing it.
See the iPhone setup steps →Check your purchase history using the Apple Account originally used to buy the app. Purchase availability on iPhone and iPad is subject to the App Store listing. After installation, verify the server selected on this device and its current configuration.
See the iPad setup steps →After purchasing the app, you will need your own subscription or server details. A subscription imports connection entries into the client; a configuration file describes rules and related settings. They are not the same thing. Identify which type of information you have before choosing an import method to avoid entering a subscription URL in a server address field.
For your first setup, import just one item with a known purpose. After importing, check Home to confirm the server entry appears, then verify the protocol and required fields. Avoid changing DNS, rules, and several advanced options all at once. A clear starting point makes it easier to identify which setting caused a problem.
Refer to the App Store listing for system requirements. Open the product page and first check whether you can purchase or redownload the app on this device, then review the compatibility section. Store availability depends on your account's storefront; being able to open the product page on the web does not mean your current account can complete a purchase.
Shadowrocket is also available through the same App Store on Mac and Apple TV; check the listing for compatibility.
If you have already purchased the app, first check the purchase history for the original account. See the download page for the steps to restore it. Purchase history restores the client; subscriptions, server details, and configurations must be checked separately. An installed app does not mean all your connection information is in place.
RULE / POLICY / CONFIG
Server parameters determine how a connection is established; Global Routing determines how requests are routed; and rules in Config define matching conditions. The examples below illustrate syntax or interface terms only. They do not include usable connection details or represent your device's actual configuration.
Rule-based routing uses domains, addresses, or other conditions to decide which policy applies to a request. In Home, set Global Routing to Config to have requests checked against the current configuration. Rules are usually matched from top to bottom, and the policy for the first match is applied. Put specific conditions before broader ones, and check where FINAL sends unmatched requests. If the result is unexpected, first confirm which configuration is active, then review rule order and the match log rather than relying on rule names. The domain on the right is a syntax example, not a recommended complete configuration.
# DOMAIN-SUFFIX,example.com,PROXYOn Demand starts connections when configured conditions are met. Set it up only after confirming that a manual connection works. Open On Demand in Settings, review each condition against the network environment you expect to use, then observe what happens when the network changes. On Demand controls when a connection starts; it does not fix server parameters or replace routing rules in Config. If a connection starts again after you turn it off manually, check these conditions instead of repeatedly deleting configurations. During troubleshooting, temporarily disable the relevant conditions so you can repeat the test reliably. Once manual connections work, restore the conditions one at a time.
# Settings / On DemandWhen adding a server, its Type must match the details of your existing service. Shadowsocks, VMess, VLESS, Trojan, HTTP, SOCKS5, WireGuard, and Hysteria2 use different fields and transport designs; changing the type name alone cannot convert a service. In Add Server, check the address, port, authentication, and transport fields against the information you were given, and keep any explicitly required options. A protocol name alone does not determine speed or battery use; network routes, server load, and connection methods all affect results. Read the field descriptions first, then test under the same conditions when comparing options.
# Add Server / TypeAn existing subscription can be used to import and update server details in one place. Before adding it, make sure the link is for a service you already use, and identify whether you have a subscription, a single server link, or a configuration file. Then choose the matching import method in the guide. After updating, check the entries in the group and confirm that the selected server is still available. If an update fails, distinguish between a network request failure, an unsupported content format, and a change in the service itself. Avoid adding the same subscription repeatedly. Subscription links may contain access credentials; hide the full URL before sharing logs or screenshots. The client purchase does not include subscription content.
# Subscribe / SERVERConfig manages configuration files. Importing a file does not automatically make it the active configuration. First check which item is selected, then review sections such as General and Rule. Keep a recoverable copy before making changes. Rules control routing, while DNS-related settings affect how domain names resolve; test these issues separately. For iCloud syncing, also check the account on each device, sync settings, and whether the file has arrived. Confirm the selected configuration and connection status on every device after syncing. Protect addresses and authentication details in configuration files; never share an entire file publicly when asking for help.
# [Rule]The connection toggle, Connectivity Test, Data, and Diagnostics each provide different kinds of information. A test response only confirms a result under that test's conditions; it does not guarantee that websites will load. Changes in Data usage alone do not prove that a rule matched correctly. Start by checking the underlying network, then verify the server connection, DNS resolution, and active policy, and finally review relevant logs. Change one setting at a time and record what happens before and after to narrow down the cause. When describing the issue to someone else, include the error type and steps taken, but hide subscription URLs, credentials, and personal browsing history.
# Settings / DiagnosticsConfig, Proxy, and Direct are three modes to distinguish while using the app. Config routes requests according to the active configuration; Proxy sends eligible requests through the selected proxy; Direct uses a direct route. PROXY, DIRECT, and REJECT in a rule file are policy keywords and should not be confused with the mode labels in the interface. Check Global Routing before editing rules, or you may repeatedly change rules while routing is not using the configuration.
When people refer to “global mode,” check the actual option in the interface rather than relying on the description alone. To compare connection results, keep the server and test target the same while checking each mode, then restore your intended setting. If a request fails in only one mode, review that mode's rules and DNS logs. This is more useful for pinpointing the cause than changing several servers and configurations at once.
Follow the interface to make your first connection →IDENTITY / PURCHASE / RESTORE
Verify the app using its App Store product page: check the developer, official icon, and app ID, then confirm the price and compatibility. This is the official Shadowrocket website and manual; the App Store is the sole place to get the app.
A name and icon in search results are not enough to verify an app. Open the product page, confirm the developer is Shadow Launch Technology Limited, and check that the app ID in the product page URL is 932747118. The icon should match the official icon shown in this site's header. Use all three details to confirm the app's identity; do not purchase based on a similar name alone.
Shadowrocket is a closed-source commercial app. Check the appropriate source for feature details, system requirements, and store transaction information: this manual covers usage and concepts, while the App Store lists current pricing, compatibility, and purchase details. Keep clear records of the account and transaction when purchasing to make it easier to switch devices, reinstall, or verify which account owns the purchase.
Whether the product appears, which currency is shown, and whether a purchase can be completed depend on the current App Store storefront and account status. If you cannot find the app in search, open its product page from the link on the download page, then check your account's storefront and any messages from the App Store. A missing search result does not necessarily mean your device is incompatible, and a web product page alone does not confirm that your account is eligible to purchase.
Before changing your account's storefront, check any restrictions related to your balance, subscriptions, and payment methods, and follow the requirements shown by Apple. Conditions may vary by account, so rely on the prompts on your account page before proceeding. System requirements are determined by the App Store listing; what appears on one device should not be treated as a universal requirement.
The US storefront price is about $2.99 as a one-time purchase. Other storefronts display local currency; the amount shown on the purchase confirmation screen is final. The purchase covers the Shadowrocket client. Check the same App Store product page for availability on iPhone and iPad and compatibility with other devices.
To use the app on another device, first confirm that you are signed in with the account used for the original purchase, then check purchase history and compatibility. App ownership and connection details on a device are separate: redownloading the client does not automatically transfer server passwords, subscription content, or the active configuration. Verify each item after installation.
After switching devices or deleting and reinstalling the app, look for Shadowrocket in your App Store purchase history. If the page shows a price again, do not confirm payment yet. Check that you are signed in with the original purchasing account, then verify the purchase history, storefront, and app identity. If the purchase record is still unclear, follow Apple's purchase history and billing support process.
Client updates are delivered through the App Store. Use automatic updates in your device settings or check for updates in the store. App updates, subscription updates, and configuration changes are managed separately. If connection behavior changes after an app update, first verify the selected server, Global Routing mode, and active configuration, then test again. Keep a copy of important configurations before making changes so you can review what changed.
App purchases and connection services are managed separately. Shadowrocket needs server details or subscription content you already have to establish the corresponding connection. Configuration files further define rules, DNS, and other settings. Identify the type of information you have, then follow the matching import steps. See the import and first-connection steps →
The toggle alone is not enough. Check server availability, the current mode, DNS resolution, and routing rules separately. Keep the test target the same and check each layer in order, changing only one setting at a time to identify where the problem occurs. See connection troubleshooting FAQs →
First, confirm in Config that the file is selected as the active configuration, then check that Global Routing is set to Config. Next, review rule order and match logs, especially whether a broad condition matched first and where FINAL routes unmatched requests. See FAQs about rules →
First, restore the client from the App Store using the original purchasing account. Then check that your existing subscription and configuration are in place, and finally verify the server selection and connection authorization on this device. Restoring the purchase does not restore your entire setup. See how to restore a purchase →
FIELD NOTES / REFERENCE
Choose a guide based on the issue and include the relevant context. If you are new to the app, start with the tutorial. If a connection works but the results are unexpected, choose a guide below based on what you observe. Rule examples explain how the system works; do not replace your entire configuration with them without checking first.
From specific domain conditions to the final policy, learn how rule order affects request routing. First check the current Global Routing mode, then compare match logs to see whether an earlier condition took effect. Understand the behavior before changing your own rules.
Read about rule order →Distinguish the connection toggle from actual access, then check server availability, Global Routing, DNS, and rule matches in order. Record what happens at each step before deciding what to check next. Avoid changing multiple settings at once, so the cause remains clear.
Read the connection troubleshooting checklist →Learn why test responses and domain name resolution are separate steps, and follow a check sequence for resolution failures. Start by verifying the underlying network and the observed error, then review DNS settings in the configuration to distinguish DNS, connection, and destination access issues.
Read the DNS troubleshooting guide →