A rule-based proxy client for iOS / iPadOS, purchased through the official App Store as a one-time purchase. Verify the listing first, then import your existing server details or subscription.
Verify the purchase details before configuring the app. Shadowrocket is a closed-source commercial app available exclusively on the App Store. Buying the client and entering server details are separate: the App Store provides the app, while users supply their own connection information.
Verify the developer and app ID on the App Store before purchasing. On first launch, make sure you already have a subscription or server details. Then go to Home and tap Add Server to add them. When you connect, iOS may ask to add a VPN configuration; review the prompt before confirming. Refer to the App Store listing for system requirements.
View guideOne purchase covers iPhone and iPad. Check your purchase status under Purchased using the Apple Account used for the original purchase. Check server selection, the connection toggle, and the active configuration separately on each device; having the app installed does not mean it is configured. Refer to the App Store listing for system requirements and purchase eligibility.
View guideAlso available on Mac / Apple TV through the same App Store; check the listing for compatibility details.
After installing, first verify a connection using one of your existing servers. Then configure rules and On Demand step by step. This makes it easier to tell whether an issue comes from the server details, routing mode, or automatic connection conditions. See how to get the app →
Use the app’s interface to work through settings one at a time, making issues easier to troubleshoot. First check the server in Home, then choose a Global Routing mode. To route traffic by destination, check which file is enabled in Config. These six features cover routing, connection conditions, rules, protocols, subscriptions, and configuration management.
Open Global Routing in Home and choose Config, Proxy, or Direct for your needs. Config routes requests according to the currently enabled configuration; Proxy handles traffic through a proxy; Direct connects directly. To check whether rules are working, first select Config, then verify the enabled file and its matching policies. Changing the routing mode does not verify server details; proxy policies still depend on a working server you already have.
[Rule]
DOMAIN-SUFFIX,example.com,PROXY
FINAL,DIRECTOn Demand triggers connections based on conditions you configure. Find the relevant options in Settings. First disable automatic triggers and confirm that your existing server works with a manual connection. Then add conditions one at a time and test them on the network you actually use. On Demand controls when a connection starts; it does not fix server addresses, authentication details, or rules. If the connection turns back on after you disconnect, check these conditions and the system VPN status instead of repeatedly changing configuration files.
[Rule]
FINAL,DIRECTManage routing rules in the Rule section of Config. Rules are typically checked from top to bottom, and the matching policy is applied. DOMAIN-SUFFIX matches a specified domain suffix; DOMAIN-KEYWORD matches a keyword in the domain; FINAL handles requests not matched by earlier rules. To send only specific sites through PROXY, place their rules first, then use FINAL,DIRECT as the fallback. Keep a copy of the original file before editing. When testing, check the actual request domain and avoid using a URL path as a domain rule.
[Rule]
DOMAIN-SUFFIX,example.com,PROXY
DOMAIN-KEYWORD,example,PROXY
FINAL,DIRECTIn Add Server, select Type first, then enter the details from your existing server. Protocols such as Shadowsocks, VMess, VLESS, and Trojan use different authentication fields; the same Host and Port do not make them interchangeable. After importing from a link or QR code, check the protocol type, address, port, and other options. A PROXY rule selects a proxy policy; it does not specify a protocol. Check rules and server details separately.
[Rule]
DOMAIN-SUFFIX,example.com,PROXY
FINAL,DIRECTIf you already have a subscription link, choose Subscribe in Add Server and enter the complete link. After importing, check that the list appears, then select a server and test it. Refreshing a subscription retrieves the list again; it does not extend the service period. If an update fails, check in order that the link is complete and still valid, the network can reach it, and the device date and time are correct. Subscription links may contain credentials; do not share them publicly. A server list and a Config rules file serve different purposes: importing one does not enable the other.
[Rule]
DOMAIN-SUFFIX,example.com,PROXY
FINAL,DIRECTConfig manages rules and related settings. After importing a file, check which item is enabled, then set Global Routing to Config to test the rules as intended. You can review sections such as General, Rule, and Hosts. Change and test one type of setting at a time to make issues easier to isolate. Adding a server and enabling a configuration are separate steps; do not overwrite the original file with content you do not understand. The snippet below illustrates rule syntax only. Its example domains are for demonstration and are not a substitute for your own destination list.
[Rule]
DOMAIN-SUFFIX,example.com,PROXY
GEOIP,CN,DIRECT
FINAL,DIRECTAfter importing, first make sure the expected server is selected in Home, then check Global Routing and the connection toggle. Connectivity Test can help you check reachability, but one test result does not replace testing access in an actual website or app. If the test responds but the destination is unreachable, check the domain, DNS resolution, rule matching, and server capabilities. If all requests fail, check the underlying network and authentication details before adding more rules.
Use Data to review traffic logs and changes in statistics. Interpret them in context: check the reporting period, connection status, and actual requests. A cumulative reading alone cannot confirm that a rule is working. To verify PROXY or DIRECT, check the policy shown for the relevant request. If you use iCloud sync, check what actually synced and what is enabled on the other device. A synced configuration does not mean both devices selected the same server; check the connection toggle on each device separately.
When troubleshooting, note three things: the selected server, the current Global Routing mode, and the enabled Config file. Change one item at a time, then test the same destination again. This keeps results comparable and helps preserve clues that can be lost when changing protocols, DNS, and rules all at once. For the complete workflow, see the Shadowrocket setup guide.
Purchase, redownload, and update Shadowrocket through the App Store. This official website and guide bases its instructions on details you can verify on the App Store listing. Check the developer, official icon, and app ID together; do not rely on the name alone.
On the product page, verify that the developer is Shadow Launch Technology Limited, that the icon matches the official icon shown here, and that the app ID in the product page URL is id932747118. Search results may include apps with similar names, so do not decide based only on keywords or icon colors. Confirm all three details match before checking the price and compatibility.
The app name identifies the product, the developer name identifies its publisher, and the app ID points to the specific App Store listing. If search results do not match the product page you opened directly, recheck all three details. Do not treat search ranking, promotional copy, or a similar name as proof that an app is genuine or that the purchase is eligible for your device.
See the App Verification Steps →Whether Shadowrocket appears in the App Store depends on the region of the Apple Account used for App Store purchases. If you cannot find it in search, first check the store region in your account settings, then see whether the product page is available. Your device’s location, system language, and store region are separate settings. A Chinese-language interface alone does not tell you which storefront you are using.
If the product page opens but you cannot complete the purchase, check the specific message from the App Store and review your payment method, account status, and device compatibility separately. Store region affects payment details and existing purchases, so read the account page guidance before making changes. This site does not provide accounts; the guide explains how to check your own store information and does not determine purchase eligibility.
Read the App Store Guide →The US storefront lists the price at around $2.99 as a one-time purchase; other storefronts show local currency. The price on the App Store at the time of purchase is the one that applies. A one-time purchase covers the client, not usage by connection. One purchase covers iPhone and iPad; check the App Store listing for system requirements and purchase eligibility on other devices.
When switching devices or reinstalling after deletion, first make sure you are signed in to the App Store with the original purchasing Apple Account, then find Shadowrocket under Purchased. If you have already bought it but see a price button, check the account and purchase history before paying again. For Family Sharing, check the App Store listing’s support details and your family purchase settings. Being signed in to an app on a device does not mean that account owns the purchase.
See How to Restore After Switching or Reinstalling →Get client updates through the App Store; you can manage automatic updates in your device’s store settings. App updates, subscription refreshes, and Config file changes affect different things: app updates change the client, subscription refreshes retrieve your existing server list, and configuration changes affect rules and related settings. When something goes wrong, identify which layer needs attention rather than treating a redownload as a fix for every issue.
Before reinstalling, check that important configurations have a usable backup and keep your own server details. Purchase history can restore your eligibility to get the app, but does not restore all local settings. Check on your device whether sync or backup includes what you need. If an update moves an option, look for it under the English interface labels Home, Config, or Settings.
See App Access and Troubleshooting →A subscription retrieves a server list; Config manages rules and related settings. Having a list does not mean a rules file is enabled. To route by rules, also check that Global Routing is set to Config and which file is currently enabled. See the configuration and connection steps →
Direct connects directly; it is not the mode to use when testing Config rules. To test whether a specific domain matches PROXY, first select Config, then check rule order and the selected server. Keep other settings unchanged during the test. Learn about routing modes →
First check that your existing subscription link is complete, valid, correctly formatted, and reachable over the network. Also check the device date and time. The app purchase and subscription content are separate; buying the client again will not fix an expired link or server authentication error. Troubleshoot subscription update failures →
First confirm that you started the connection in Shadowrocket, then read the app and configuration details in the system prompt. Allowing a configuration lets the system establish a connection; it does not confirm that your server details are correct. After granting permission, check the selected server and test actual access. See how to make your first connection →
Choose a topic based on the issue you are having. For app access, check the purchasing account and Purchased items. For subscription issues, check the link and refresh results. To interpret traffic, consider the Data reporting period and actual policy records. Use these topic guides alongside the main tutorial; there is no need to change every setting at once.
Understand how statistics differ between the server and app views, and interpret changes alongside actual requests. Cumulative traffic helps track usage; to determine whether traffic used PROXY or DIRECT, also check the corresponding rule and policy.
Read the guide →Check manual refresh results, automatic update settings, and link validity in order. Check formatting, network timeouts, and device time separately to distinguish a list that has not refreshed from a failed connection to the selected server.
Read the guide →Check the original purchasing account and purchase history, then get the app again from Purchased. Learn how app purchase eligibility differs from local configuration data, so you can check the servers and rules you need after restoring the app on a new device.
Read the guide →