A rule-based proxy client for iPhone and iPad, available as a one-time purchase through the App Store. Follow the instructions in order, from verifying the official listing and importing an existing subscription to rule-based routing.
Shadowrocket manages server details, connection methods, and request-handling rules separately. Before you get started, prepare your existing subscription or server details. Then check whether the connection works, and adjust routing behavior last. Each stage has its own checks: a rule configuration error, a failed subscription update, and a local network issue are different problems.
The five topics below cover common tasks. Start with the one that matches your issue, then open the full guide. Interface labels remain in English so you can match them to Home, Config, and Settings on your device. The location and availability of specific options may vary; check the app’s current interface.
Manage configuration files in Config and set Global Routing to Config to process requests using the active configuration’s rules. Rules are generally checked from top to bottom, and the first match determines the policy. Put more specific domain rules before broader ones, and place FINAL at the end as a fallback. PROXY, DIRECT, and REJECT specify proxy, direct, and reject actions. After making changes, test a request to the intended destination instead of relying only on the connection toggle. The syntax below is an example, not a complete configuration or a recommended routing setup.
DOMAIN-SUFFIX,example.com,PROXYFINAL,DIRECTOn Demand controls connection behavior when specified conditions are met. Look for the relevant options in Settings. First disable automatic triggers and connect manually to confirm that your existing server and configuration work. Then set conditions one at a time. After switching networks, check both the connection status and whether requests succeed; a trigger firing does not guarantee a working route. To troubleshoot repeated connections, temporarily turn off On Demand and compare results on a stable network before restoring the conditions you need. Available conditions and system behavior depend on the options in the app.
Shadowrocket supports protocols including Shadowsocks, VMess, VLESS, Trojan, and WireGuard. To add a server manually, choose the matching type under Type in Add Server, then fill in the corresponding fields. Host, Port, authentication details, and transport settings must work together; the protocol name alone cannot confirm that the settings are correct. Use the complete import details from your own service provider where possible, and verify key fields after importing. A protocol is only one part of the connection; results also depend on the server, local network, and route conditions.
Get subscription details from your service provider. If you already have a subscription, follow the Subscribe import flow in the guide and check that the server list updates when the import is complete. A subscription generally maintains server entries; it does not necessarily include a suitable routing configuration. If an update fails, first check that the link is complete, authorization is valid, and your current network can reach the subscription URL. Then check whether the response contains data the app can read. Subscription links may contain personal credentials, so hide the full URL and authentication parameters in screenshots or logs.
Use Config to manage configuration files and Diagnostics in Settings to help investigate connection issues. Keep a copy of the original configuration before making changes. When reproducing an issue, note the network, selected server, and Global Routing mode, then compare results using the same request. Traffic records in Data can help you understand usage, but traffic appearing there does not mean the request reached its destination. If you use iCloud sync, check the sync conditions on each device and confirm what actually synced. Purchase records, configuration sync, and server access credentials are separate and should be checked independently.
Config routes requests according to the active configuration file. Proxy sends requests through the selected proxy, subject to the protocol and network working correctly. Direct connects without a proxy. When testing for the first time, confirm which mode is active; Proxy does not prove that rules are working. To route differently by domain, address, or region, switch back to Config and check the active configuration file and rule order.
Latency tests, Connectivity Test, and real-world requests answer different questions. Test results can help with initial checks, but they do not replace a complete request to the service you want to use. If a connection appears active but a service will not load, first confirm that the device itself is online, then check the server, routing mode, and rules. Change one thing at a time to see what affects the result. For policy names and rule keywords, see the glossary.
Devices / App Store
Shadowrocket is available exclusively on Apple platforms, and the App Store is the only place to get it. First check your App Store account and the product listing, then complete the purchase and installation. System requirements are as listed on the App Store page; do not infer device eligibility from a device name on this website alone.
After getting the app from its product page, prepare your existing server details. When you connect for the first time, review the system prompt to authorize the VPN configuration. This authorization allows the connection profile to be created; it does not confirm that the server is working.
See the iPhone setup steps →Use the same Apple ID to check your purchase history and get the app again if it appears there. The layout may differ in landscape, but you can still find options under Home, Config, and Settings. Restoring a purchase and transferring a configuration are separate steps.
See how to get your previously purchased app on iPad →Shadowrocket is also available through the same App Store on Mac and Apple TV. Check the App Store page for system requirements, compatibility, and whether it is a universal purchase.
Quickstart / Step by step
This simplified first-use sequence does not replace the full guide. Before you begin, make sure your device is online, Shadowrocket is installed from the App Store, and you already have usable server details or a subscription. If any of these are missing, address that first rather than repeatedly changing settings with an empty server list.
To add a server manually, choose Type first, then enter Host, Port, and the required authentication fields using your existing details. If you already have a subscription, add the complete link through the Subscribe import flow. Get subscription details from your service provider. When finished, check that the expected entry appears in Home. Matching names do not guarantee matching settings, so verify the protocol and address too. QR codes and links may contain access credentials; do not share them publicly as-is.
Select an existing server, then confirm the Global Routing mode. For rule-based routing, choose Config and check which file is active in Config. If you temporarily switch to Proxy or Direct to troubleshoot, note the original setting. The server list and routing configuration serve different purposes: the former provides connection destinations, while the latter determines how requests are handled. Importing a subscription alone does not mean you have rules suited to your needs.
Turn on the connection, approve the VPN configuration when prompted, and check the connection status. Then use Connectivity Test as an additional check and try accessing the service you need. If it fails, first distinguish between “the connection cannot be established” and “requests fail after the connection is established,” then check the local network, server settings, DNS, and rules. Reproducing the issue under consistent test conditions makes it easier to identify the cause than changing the server, protocol, and configuration all at once.
Verification / Before you buy
Shadowrocket is a closed-source commercial app. This is the official Shadowrocket website and manual; refer to the App Store product page for details on getting the app. Search results may show apps with similar names. The nickname “Little Rocket” or a description alone is not enough to identify the app; check the developer, App ID, and official artwork together.
id932747118In the App Store, first confirm the title is Shadowrocket, then check the developer name and the App ID in the product page URL. The artwork can help you identify the app quickly, but it does not replace the other two checks. The amount and currency on the purchase confirmation screen depend on your storefront; a reference price on a webpage is not the amount you will necessarily be charged. The US storefront reference price is $2.99. Check the App Store listing for the final price.
If you cannot find the app, first check the account you use for App Store purchases and its storefront region—not just your device’s language or region settings. Being able to open the product page on the web does not mean the app is available for purchase in your account’s storefront. If the store says the app is unavailable, follow its guidance to check your region, payment requirements, and device compatibility. Before changing regions, review the store’s information about balances, subscriptions, and purchase history. For the full checklist, see the App Store availability guide.
A one-time app purchase is not a service plan. Buying Shadowrocket gives you the right to use the app; it does not provide a server or subscription. This site does not provide, sell, or recommend nodes or subscriptions. If you already have a subscription, get its link from your service provider. If you have a server, configure it with your own details. App purchase status and server access are separate: being able to open the app does not prove that a subscription is still valid or that a server can currently connect.
On iPhone and iPad, you can get the app using the purchase history linked to the same Apple ID, subject to availability in the store. When changing devices or reinstalling, first look for Shadowrocket in the App Store purchase history and confirm that you are signed in to the original purchasing account. After restoring the app, check your server details, configuration files, and sync results too; purchase history does not restore every connection detail automatically. For Family Sharing, check the product page, family settings, and purchase-sharing requirements rather than assuming every family member is eligible.
App updates come through the App Store. Depending on your device settings, you can use automatic updates or check for updates in the store. Subscription updates retrieve data from your subscription URL, while editing a configuration file is a separate task. If something goes wrong after an update, first identify which layer changed, then check its relevant fields and records. This page does not list specific app or OS versions; compatibility and system requirements are always as stated on the App Store page.
Reading / Use cases
After your first connection works, browse the topic guides that match your situation. The rules guide explains how matching works; the device guide distinguishes purchase history from configuration migration; and the connection guide covers comparison tests. Identifying which layer is causing the issue can save you from repeatedly changing unrelated settings.
Check the original purchasing account, get the app from purchase history, then review the landscape layout and configuration migration. Keep app purchase eligibility separate from connection details saved on the device; getting the app again does not restore every configuration.
Understand REJECT at the request-matching stage and how rule order relates to rejection policies. A single domain can serve different types of content, so a simple domain rule may not distinguish every request. Before changing rules, be clear about the intended result and its limits.
Choose a server from a subscription you already have, and understand how latency figures differ from real request performance. Compare regions, protocols, and connection stability using the same network and test destination; do not rely on a single test result.