Shadowrocket
FAQ

Check the spelling first, then open the App Store product page from this site's App Store page rather than relying on search ranking alone. If the store says the app isn't available in your region, check the country or region of the Apple Account used for purchases—not just your device language. Find it in Settings under Apple Account → Media & Purchases → View Account → Country/Region. If you need to change it, follow Apple's prompts about your balance, subscriptions, and other requirements. App Store availability is the final reference.

Verify all three details: the app name is Shadowrocket, the developer is Shadow Launch Technology Limited, and the product page URL includes app ID 932747118. Then compare the store icon with the official icon in this site's header. Don't rely on a similar name or icon color alone. Check the price, compatibility, and update history on the same product page, and confirm the app name and account details before purchasing. Shadowrocket is available only through the App Store.

Sign in to the Apple Account used for the original purchase, find your purchased apps in the App Store account page, then open the Shadowrocket product page and check for a redownload option. Your iCloud sign-in and Media & Purchases account may differ, so check both. If you still see a price, review your purchase history and the current storefront before paying again. Redownloading the app does not restore server details, subscriptions, or configuration files stored in the app; back up and restore those separately.

A one-time app purchase is not a service plan. Your App Store payment buys the Shadowrocket client; connecting still requires your own subscription or server details. The US price is a one-time purchase of $2.99; the actual price and billing currency depend on the App Store storefront. Before importing, ask your service provider to confirm that the server address, authentication details, and protocol settings are valid. This site covers how to check, import, and use the client; it does not provide connection services.

Refer to the compatibility and purchase information on the App Store product page. Shadowrocket is primarily used on iPhone and iPad; check the same page's compatibility section for Mac, Apple TV, and Apple Vision. System requirements and whether the purchase is universal are as listed on the App Store page. Don't assume that in-app configurations sync automatically as part of the purchase. On a new device, check your subscription, Config, and system VPN authorization.

This is the system authorization required for a client to establish a VPN connection. Confirm that the prompt was triggered by the Shadowrocket you're using, then allow it and complete device authentication as requested. Authorization creates a system configuration; it won't supply a server address or fix invalid settings. If you canceled the prompt, return to the app and turn the connection on again to see if it reappears. If you still can't proceed, search for VPN in Settings and check the relevant configuration's status. Avoid deleting configurations used for other purposes.

Open the Shadowrocket product page in the iPad App Store; refer to that page for system requirements. If you've already purchased the app, check that the Media & Purchases account matches the one used for the original purchase, then look for the redownload option. After installation, check Home, Config, and Settings in the actual interface; the layout may vary by device and app version. An iPhone's connection toggle and system authorization do not authorize the iPad. Confirm the VPN configuration on the iPad when connecting for the first time.

Start with Home, Config, Settings, and Global Routing. Home lets you view and select existing connection profiles; Config manages configuration files; Settings is where you review settings. Global Routing determines the current routing mode. Add Server is where you add a server, Subscribe relates to subscriptions, and Data shows data-related information. Match the English labels in the current interface; don't mistake explanatory text in this guide for button names.

First, make sure a usable connection profile exists and is selected, then check that system VPN authorization is complete. Next, look for another VPN connection, device management restrictions, or On Demand rules that may be changing the connection state. Change one setting at a time and test again, noting system prompts and when the toggle changes. Try turning the connection off, then reopening the app. Before removing a VPN configuration, back up the app's data and only remove an item you can clearly identify as belonging to Shadowrocket.

Updates are delivered through the App Store; refer to the product page for release notes. Before updating, keep your subscription source, necessary server details, and configuration file backups. After updating, check the selected profile, Global Routing, and Config. A layout change alone doesn't mean you need to import everything again. If an issue starts after an update, note the steps that triggered it and the exact error text, then troubleshoot based on the symptoms. Deleting the app can affect local data, so don't make it your first step without a backup.

First, confirm that you pasted the complete subscription link you already have. Remove any accidentally included spaces, line breaks, or punctuation, and make sure it isn't the URL of an information page. Check that your current network can reach the subscription service and whether your provider requires a particular subscription format. A parsing error may mean the response doesn't match the import method; a request error points first to link validity or network access. When reporting an error to your provider, redact authentication details in the link.

Open Add Server, select the Type that matches your existing details, then enter the address, port, and relevant authentication fields. Shadowsocks, VMess, VLESS, Trojan, and WireGuard use different fields; don't enter settings for one protocol under another type. Check any additional requirements in your service details, such as TLS, transport, or Server Name, and use the fields available in the current interface. After saving, reopen the profile and verify the entries rather than relying on its label.

First, check that the system allows Shadowrocket to use the camera. Make sure the QR code is complete and clear, and that it contains your connection details rather than a webpage link. A successful Scan QR Code scan doesn't guarantee that the settings are valid; after saving, check Type, address, port, and authentication fields. If the code's format isn't recognized, ask your provider which import method to use. You can also enter the complete details in Add Server, rather than repeatedly scanning an image from an unknown source.

First, run a manual update from the subscription's management screen and confirm that the request succeeds. Then check the subscription settings available in your current app version for the option to update automatically when the app opens. Both manual and automatic updates require a valid link, network access, and a correctly formatted response. If an update fails, keep existing usable profiles, check the error message, and ask your provider whether the link has changed. App updates, subscription updates, and Config updates affect different things—don't confuse them.

A subscription update replaces or adjusts profiles based on the content returned by the remote service, so names, order, and available profiles may change. After updating, check the subscription group and confirm that the selected profile is still the one you intend to use. Check whether the previous profile was removed from the subscription. A matching label alone doesn't prove that a profile is unchanged. Record any custom details you need to keep, and check which fields are subscription-managed before editing them, so a later update doesn't overwrite local changes.

Choose Config for routing based on a configuration file, and confirm that the relevant configuration is enabled. Choose Proxy to send requests through the current proxy, or Direct to connect to the destination directly. These are the configuration, proxy, and direct connection modes; the explanation here doesn't replace the English interface labels. When troubleshooting rules, check Global Routing first. In Proxy or Direct mode, you can't infer the actual result from a rule in Config alone. After changing modes, test the same destination again.

First turn off the connection and check that Wi-Fi or cellular data can reach services that were previously accessible. Turn the connection back on, then check the selected profile, Global Routing, and Config. A system VPN status of Connected confirms that the connection is established, not that every request can reach its destination. Next, check server reachability, DNS resolution, and rule matches separately, using a small set of consistent test destinations. Change one thing at a time and note which step restores access; changing several settings at once makes the results hard to interpret.

No—don't draw conclusions from a single test. Check the test method and destination used by Connectivity Test, then verify the device's network, selected server, and authentication settings. An unreachable test destination, DNS issue, or temporary network fluctuation can affect the result. A successful test also doesn't prove that every website is accessible. Repeat the check on the same network, then test a destination you actually need to access. If you contact your provider, share the test result and error text, but hide passwords and subscription credentials.

First confirm that Global Routing is set to Config, then check whether an earlier rule matches the destination. Rules are evaluated from top to bottom. Check conditions such as DOMAIN, DOMAIN-SUFFIX, and IP-CIDR, along with PROXY, DIRECT, and REJECT policies; then check the FINAL fallback. If a domain fails while other access to the same service works, review DNS alongside the app's logs. Don't enter an unfamiliar DNS server at random. Keep the existing configuration and test your hypothesis with one reversible change.

Compare battery usage for similar time periods in system settings, then check for heavy data transfers, frequent subscription refreshes, detailed logging, or network changes. On Demand can affect connection state based on its conditions; verify that its Wi-Fi, cellular, and domain triggers match your actual environment. Temporarily disable On Demand and compare whether the connection still changes repeatedly. Keep other conditions as consistent as possible, and don't rely on the VPN status icon alone to identify the source of battery use.