Import subscriptions and configure rules on iPhone and iPad with this rules-based proxy client. The app is a one-time purchase; you’ll need your own existing subscription or server details to use it.
ROUTING / Connections and paths
CAPABILITIES / Settings overview
First, distinguish server details, subscription lists, and configuration files; then adjust connection behavior. The six items below serve different purposes: servers provide connection parameters, configurations determine how requests are routed, and diagnostics help you verify the results. An import succeeding, a test returning a response, and a service working normally are three different things.
Global Routing determines how requests are handled. Config applies the rules in the selected configuration, Proxy sends requests through the selected proxy policy, and Direct connects without a proxy. Before relying on a setup, check which configuration is selected in Config, then review the order of rules under Rule. Rules are generally evaluated from top to bottom, and the first match determines the policy. DOMAIN-SUFFIX matches domain suffixes; FINAL is the fallback when no earlier rule matches. After making changes, visit the relevant destination and check the connection logs to confirm the result. An enabled switch alone does not prove that a rule is working.
On Demand starts a connection when its configured conditions are met; it does not fix server parameters or fill in missing rules. First connect manually and confirm your own server works and the destination loads. Then check the On Demand conditions in Settings. Decide which network environments should trigger a connection and which should keep their usual connection behavior. After changing the conditions, switch networks to verify the result in each case. If the connection drops and reconnects repeatedly, check On Demand and the system VPN status before deleting configurations. To temporarily stop automatic connections, check both the On Demand conditions and the main connection switch.
A protocol name identifies the technology used for a connection; it does not tell you whether a particular server is available. After importing your own details, compare Type, Host, Port, and the relevant authentication fields in Add Server, then check additional settings such as TLS and transport. Shadowsocks, VMess, VLESS, Trojan, and Hysteria2 use different fields, so do not apply one protocol’s parameters to another. For VLESS in particular, verify the server’s required settings even after importing a share link. Available fields depend on the app’s actual interface. If a connection times out, check the address and port first, then authentication and transport settings.
A subscription keeps a list of server details up to date; you’ll need your own valid subscription URL. Choose Subscribe or the appropriate server import option for the link type. After saving, check that the expected entries appear in the list, then test a server. If an update fails, verify that the URL is complete and still valid, and that your current network can reach it. Updating a subscription is not the same as updating a configuration file; refreshing the list does not rewrite all routing rules. Subscription URLs may contain personal access credentials. When troubleshooting, share only the error message and the conditions in which it occurred—not the full URL.
A configuration in Config describes how rules, DNS, and other behavior are handled; the server list in Home has a separate purpose. After importing a file, confirm that it is selected, then review the sections in use, such as General, Rule, and Hosts. Global Routing must be set to Config for that configuration to control routing. Keep a recoverable copy before making changes, and change only one category of settings at a time. If you use iCloud to sync related content, check the sync status on both devices and which item is selected locally. A file appearing in the list does not mean it is enabled. If the devices differ, compare the local files and test the connection behavior again.
Connectivity Test, Diagnostics, and Data show different kinds of information. A test response only confirms that the chosen test method returned a result; it does not guarantee that every destination will load. Changes in Data traffic do not prove that a particular rule matched. When troubleshooting, note the current network, selected server, Global Routing mode, and destination that failed, then review the available diagnostics. Narrow down the cause in this order: server connectivity, DNS resolution, rule policy, and destination access. Change one variable at a time. Before sharing diagnostic results, hide subscription credentials, authentication details, and any access logs you do not need to disclose.
RULE / Top-to-bottom matching
DOMAIN-SUFFIX,example.com,PROXY
GEOIP,CN,DIRECT
FINAL,DIRECTexample.com is shown for syntax illustration only. Before using a rule, confirm the policy names in your configuration. This example is not a complete configuration for every network.
Read about features and settings →ON DEMAND / Verification steps
Test the connection manually first, then configure the trigger conditions. Check behavior after switching networks separately.
Read the On Demand guide →ADD SERVER / Check parameters
Fields vary by Type. Use your own server details; example values are not valid connection parameters.
Browse protocol terms →SUBSCRIBE / Example URL
https://example.com/sub?token=xxxxThis sample value is for demonstration only and cannot be used to connect. Use your own valid subscription details; this site does not provide subscriptions.
See the import steps →CONFIG / Configuration sections
Confirm which file is selected, then check the sections you need. Keep a copy before editing so you can isolate issues if something goes wrong.
Troubleshoot configuration issues →DIAGNOSTICS / Check each layer
Record test results separately from actual access to the destination. Identify which layer is causing the problem before changing settings.
Open the troubleshooting guide →QUICKSTART / Three checks
These steps are for users who have purchased Shadowrocket through the App Store and already have their own subscription or server details. Start with a basic connection test, then add rules and automatic connection conditions as needed. This makes it easier to troubleshoot without multiple settings affecting one another.
01 / IMPORT
In Home, use Add Server with your existing details or subscription URL. For QR codes or clipboard imports, use complete, valid content. A server share link and a subscription URL are different.
Check: The imported item appears in the list, and its Type, Host, and Port match the original details. A successful import only means the content was read; you still need to test the connection.
02 / ROUTING
Choose Config to apply the selected configuration’s rules. Proxy and Direct test proxy and direct connections. The configuration chooses the policy; the selected server supplies connection details.
Check: The selected mode matches what you’re testing; FINAL is at the end of the rules, and policy names match the active configuration. Keep a copy of the original configuration before making changes.
03 / VERIFY
Approve the system VPN prompt only when it comes from Shadowrocket. Turn on the connection, run Connectivity Test, visit your destination, and check the connection logs for the policy used.
Check the connection switch, test result, and actual access separately. If something fails, note the network and error message. Check the parameters and DNS first; don’t change everything at once.
DEVICES / App Store
Shadowrocket is available only through the App Store. Before purchasing, open the product page and verify the app, your account’s storefront, and compatibility. Check the App Store listing for system requirements and supported devices. Whether the app appears in the store depends on the storefront and device; search results are not a substitute for checking the product page.
Use this guide to check each step, from purchase and first launch to connection authorization. After installing, prepare your own existing subscription or server details. System VPN authorization allows the app to establish a connection; it does not provide a working server. Read each prompt before proceeding.
Read the iPhone guide →If you’ve already purchased the app, check your purchase history using the original Apple Account. App availability across iPhone and iPad depends on the App Store listing. Getting the app and migrating its configuration are separate steps; check the local server list, selected configuration, and connection permissions independently.
Read the iPad guide →Get the app and install updates through the App Store. Use the product page to verify the price, compatibility, and purchase options. This guide does not list fixed system requirements.
See how to get the app →VERIFY / App identity and purchase
This is the official Shadowrocket website and manual. Verify the App Store listing by the product name Shadowrocket. Confirm the app’s identity using all three: the developer, official app icon, and App ID. Don’t rely on the search result title or a similar-looking icon alone.
On the product page, confirm that the developer is Shadow Launch Technology Limited, then check the page URL for id932747118. The App ID is a fixed identifier; a similar page title is not enough to confirm the app’s identity. The official app icon should match the one in this site’s header. Proceed with the purchase only after all three details match.
If search results show several apps with similar names, return to the specified product page to verify the listing instead of relying on rank, similar wording, or placement. See how to verify the official listing for the full checklist.
Shadowrocket is a paid, closed-source commercial app. The US storefront price is approximately $2.99 as a one-time purchase; other storefronts show local pricing. Check the App Store listing for the current price. The purchase grants use of the app; it does not include server details or a remote connection service.
Check the App Store listing for availability across iPhone and iPad, compatibility with other devices, and any related conditions. Before purchasing, check the price and button shown for your account. Don’t rely on a price shown in a screenshot.
Whether the app appears in the store may depend on your Apple Account’s storefront, device compatibility, and purchase conditions. If the product page won’t open or the app doesn’t appear in search, first confirm your account’s current storefront, then check the specific message from the system. System requirements are always as listed on the App Store page; don’t use old screenshots in this guide to determine whether a device is supported.
Account settings and connection settings in the app are separate steps. If you haven’t completed the App Store purchase, you don’t need to change DNS, routing rules, or server parameters first. Resolve any questions about the product page and purchase status before adjusting connection settings.
When switching devices or reinstalling, use the original Apple Account in the App Store to find your purchases, then download Shadowrocket again. Normally, you don’t need to purchase the app again to restore it with the original account. If a price still appears, check that you’re using the account used for the purchase and that the storefront and purchase history match.
Getting the app again does not restore all local configuration. After opening it, check the server list, the selected item in Config, and system VPN authorization separately. Updates are delivered through the App Store. Keep important configuration before updating, then test the connection to your usual destinations afterward.
Subscription updated, but the list hasn’t changed: Check the update result and whether the URL is valid, then make sure you’re viewing the right group. Updating a configuration file does not refresh the server list. See the subscription import guide for the steps.
The test succeeds, but webpages won’t load: A latency test does not verify full access. Also check DNS, rule matching, and the connection log for the destination request. Follow the steps in the troubleshooting guide, changing one setting at a time.
Not sure how Config differs from Proxy? First decide whether you’re checking rules or the server. Config relies on the selected configuration; Proxy is for checking proxy behavior. See the glossary for terminology and FAQs for purchase and first-launch questions.
TECHNICAL NOTES / Troubleshooting notes
Once the basic connection works, read about import methods, restoring purchases, or DNS troubleshooting as needed. Each note addresses one issue, so you can compare the steps with the current interface without changing every setting at once.
Compare when to use each import method, and distinguish a single server entry from a subscription list that can be refreshed. Before importing an existing link, check its type and make sure it’s complete, then choose the matching method.
Read the guide →Learn how the original purchase account, purchase history, and redownloading work, and how restoring the app differs from transferring its configuration. If a price appears, check the account and purchase history first.
Read the guide →Start with the roles of DNS resolution, connectivity, and rule policies, then check domain-specific failures and webpage loading issues in order. Record the test conditions and compare results after each change.
Read the guide →