App Store · Official Guide
A rule-based proxy client for iPhone and iPad. Learn about rule-based routing, importing existing configurations, and a one-time purchase.
Purchase and first launch
Shadowrocket is available to purchase and install only through the App Store. First check the store account on your device, then verify the product page, compatibility, and payment details. If you’ve purchased it before, check your purchases first rather than paying again. See the App Store page for system requirements and eligibility for use across devices.
Before purchasing, check the app icon, developer, and app ID. After installation, import your own server details before connecting. On your first connection, read the system prompt to add a VPN configuration and confirm as required by your device.
System permission allows the client to establish a connection; it does not confirm that the server is working. Return to Home to check the selected item and Global Routing, then verify by visiting a website.
View iPhone setup detailsIn the App Store, use the original purchasing account to find Shadowrocket and check whether it can be redownloaded. Purchase eligibility across iPhone and iPad is determined by the App Store listing. Check existing configurations on each device separately.
On wider screens, lists and editing areas may be arranged differently. Use interface labels such as Home, Config, and Settings to find the relevant controls. Restoring a purchase and syncing configurations are separate processes.
View iPad setup detailsBefore configuring the app for the first time, have your own subscription or server details ready. Make sure the address, port, authentication details, and protocol parameters come from the same set of instructions; don’t mix fields from different configurations. This site does not provide, sell, or recommend servers or subscriptions.
Shadowrocket is also available on Mac and Apple TV through the same App Store. See the App Store page for compatibility and system requirements.
View the setup steps →First, distinguish which server a connection uses, which mode handles traffic, and which rule matches a specific request. Each serves a different purpose, so the connection toggle alone can’t confirm that everything is set up correctly. The capabilities below are grouped by task; see the feature guide for details and requirements.
Set Global Routing to Config on Home to route requests according to the active configuration. Rules are generally checked in order: when a domain, address, or region condition matches, the corresponding policy is applied; unmatched requests fall through to FINAL. Save a copy of the original configuration before editing. Confirm that PROXY points to a working policy, then change one rule at a time and test the same destination. DIRECT means a direct connection; REJECT means the request is blocked. Check rule matching and server availability separately.
On Demand can trigger a connection when configured conditions are met; it does not replace server settings or routing rules. First connect manually from Home and confirm that websites load, then review the On Demand options and conditions in Settings. After setup, check what happens when the network changes and when the device wakes. If the connection starts again after you turn it off, check these conditions instead of repeatedly deleting the server. For troubleshooting, temporarily disable the relevant conditions, repeat the same test, then restore them. This avoids multiple settings affecting the result at once.
Shadowrocket supports protocols including Shadowsocks, VMess, VLESS, Trojan, Hysteria2, and WireGuard. In Add Server, make sure Type matches your existing server details, then check the address, port, and authentication fields. Transport, TLS, server name, and other parameters must also match as a set; changing only the protocol name while reusing all the old values may not work. Protocol support does not guarantee that every server can connect. Refer to the fields and features shown in the app, then confirm the imported configuration is complete and test access.
Use a subscription link from your own service provider. Select Subscribe in the add menu, then enter the address and a label as prompted by the current interface. After saving, check that the corresponding group appears on Home and contains entries, then select a server to test it. Updating a subscription fetches the remote list again; it won’t fix an expired account or incorrect parameters. Keep any important manual records before updating. If it fails, check the link, your network, and the service status in turn. Subscription URLs may contain access credentials, so hide them before sharing screenshots or logs.
Config manages routing rules and related settings. Importing a server list does not switch the active configuration file. Save a copy of the current file before making changes, review sections such as General, Rule, and Hosts, and confirm which file is active. To keep settings across devices, check the app’s iCloud sync options and account status, then verify what synced and the final result. Restoring a purchase does not restore configurations. After switching devices, check server selection, rule references, and sensitive details before connecting.
Connectivity Test on Home can help compare server responses, while Diagnostics in Settings provides more connection details. Results depend on the test method, destination, and current network; they don’t indicate webpage loading speed. If the connection is on but you can’t access a site, check the server, Global Routing, DNS, and matching rules in that order. Traffic statistics in Data show data usage but don’t prove that a request succeeded. Change one setting at a time and note the result. Hide addresses and authentication details before sharing diagnostic information.
Config routes traffic according to the active configuration file and is suitable for everyday use when your rules are ready. Proxy routes requests handled by the client through the current proxy path, which can help determine whether a problem is caused by routing settings. Direct uses a direct connection path for comparison. Changing modes won’t fix incorrect server parameters or restore an unavailable service. Remember to switch back to the mode you need after testing.
For example, if the same website works in Proxy but fails in Config, check the relevant rules and policy references next. If both modes fail, first check server status, authentication details, and your current network. If only certain domains have issues, don’t reset all settings right away. Retry the same destination on the same network, note which mode fails, then check how DNS and rules interact. This comparison makes it easier to isolate the cause than changing several options in a row.
On Home, first confirm that a working server is selected, then check Global Routing. If you’re using Config, make sure the active file is the one you expect. Turn on the connection and complete any system authorization prompts. Finally, visit a website you regularly use and check page resolution, content loading, and requests from within the app. The connection toggle is only one step; verify actual access as well.
If you use an existing subscription, distinguish between two things that can be updated: a server subscription manages connection entries, while a remote configuration manages rules and settings. Updating one does not update the other. Save a restorable copy of the configuration before making manual changes. After an update, check which entries were added or removed, then test a destination you previously used. Follow your provider’s instructions for each field; don’t guess the protocol from a name or label.
Shadowrocket is a closed-source commercial app. Verify the app by checking its developer, official icon, and app ID in the App Store. Refer to the App Store page for price, compatibility, system requirements, and purchase eligibility.
Open the product page and check that the app is named Shadowrocket and the developer is Shadow Launch Technology Limited; compare the icon with the official icon shown on this site. Then check the app ID in the product link and confirm it is 932747118. Search results may show similar names or icons, so don’t rely on a nickname alone. Once all three details match, review device compatibility and pricing on the store page before confirming your purchase.
Even when you open the App Store from this site, verify the product details. What appears in the store may vary with the account’s storefront. Use the final product page as your reference, not a search snippet, an old screenshot, or someone else’s description. Interface labels in this guide help you find features, but the app’s layout and available options may vary by device and change over time.
A one-time purchase gives you the right to use the client; it does not include servers, subscriptions, or data services. The client reads existing configurations, connects, and handles requests according to rules. Check with your own service provider to confirm that a remote service is active, an account hasn’t expired, and data is available. If Home has no usable connection entries after payment, that doesn’t mean the purchase failed; you still need to import your own details.
The reference price in the US storefront is $2.99. Other storefronts display local currencies; the actual amount is shown on the App Store payment screen. App pricing and service fees are separate, and paying for the app does not confirm that a server-side account is active. This is the Shadowrocket website and official guide, covering purchase verification, configuration, use, and troubleshooting. It does not provide servers or subscriptions.
When switching devices or reinstalling, first make sure the App Store account in use is the same one used for the original purchase, then find Shadowrocket in your purchases. The status of other accounts on the device doesn’t necessarily tell you which account the App Store is using. If the product page still shows a price, check the account, purchase history, and current storefront before paying again. The exact name of the restore option depends on the current interface on your device.
Check the App Store page to see whether the original purchase can be used across iPhone and iPad and which other devices are eligible. After restoring the app, check whether your configuration details are still there. Subscriptions, manually added servers, the active Config, and system connection permissions are separate parts of the setup. Restore the purchase first, check your configuration, then test access so missing settings aren’t mistaken for a failed app restore.
If you can’t find the app, check the region of your App Store account, age-rating restrictions on your device, and account status in turn. Then use the app ID listed on this site to verify the product. If the product page opens but you can’t purchase, read the reason shown by the store. App availability in a storefront and device eligibility are determined by the current App Store listing; this guide doesn’t infer purchase eligibility from search results.
See the App Store page for system requirements. App updates are delivered through the App Store. Check automatic update settings on your device or look for available updates in the store. Save important configurations before updating, then verify your existing connection before changing any newly available options. This guide doesn’t list version numbers or release dates. For current features, refer to the app’s interface and the App Store release notes.
Check them separately. A subscription usually provides server entries, while Config controls rules and related settings in Config mode. After importing, check the selected server, active configuration file, and Global Routing. Don’t assume everything is set up just because entries appear in the list. See definitions of subscription and configuration terms →
Connection status, server response, and successful requests are separate checks. Use Connectivity Test as a guide, then visit a consistent test destination. If it fails, check the server, mode, DNS, and rules in that order. See troubleshooting guidance →
Not directly. The test method and destination affect response results, while webpage loading also depends on bandwidth, the destination site, and the connection path. Compare real-world access under the same network and test conditions. See answers about testing →
First restore the app with the original purchasing account. Then check that your subscriptions, servers, and Config are intact, and verify connection permissions and access. Restoring a purchase doesn’t confirm that your configurations were restored. See the purchase restore steps →
Choose an article based on the issue you’re dealing with. For purchases and restores, start by checking the store account. For protocol fields, compare them with your own server details. Each article focuses on one issue and provides a clear set of checks, so you don’t have to change every setting at once.
A one-time purchase is linked to the original purchasing account. Learn how to verify the store account, find your purchases, and check app restoration separately from configuration restoration to avoid repeating purchase steps when switching devices.
If your search returns no results, first check the storefront, age-rating restrictions, and account status, then verify the app ID. Distinguish search visibility from device compatibility; a single search result isn’t the final word.
Understand the differences between the two protocols through authentication, encryption, and transport settings. Learn how fields such as UUID and TLS correspond to existing server details. Choose Type based on your server’s requirements, not just the protocol name.