932747118
Check for id932747118 in the App Store product page URL. If an app has a similar name, verify the developer and official icon as well.
App Store · Official Handbook
ShadowrocketSetup Guide
A practical guide to the iPhone / iPad app: verify the official listing, import an existing setup, and understand rule-based routing and the one-time purchase.
Shadowsocks
WireGuard
Global Routing
APP STORE FACTS
Three things to know before you buy
Understand the difference between the app, connection settings, and update source before getting started.
One-time purchase
The US storefront lists it at $2.99; confirm the price at checkout. Buying the client does not include a server plan. You’ll need your own subscription or server details to connect.
App Store
Automatic updates
Updates are distributed through the App Store. Automatic installation depends on your device settings; you can also check for updates manually in the store.
Shadowrocket is a paid, closed-source rules-based proxy client for Apple platforms. This is the official site and handbook, covering information you can verify in the App Store and the settings available in the app. Purchasing the app grants the right to use the client; connection details, authentication parameters, and rule files must be prepared separately. None can replace the others.
For your first setup, verify one existing server configuration before adding subscriptions, rules, or automatic connection conditions. This gives you a clear baseline if something goes wrong: check whether server details are incomplete, rules aren’t matching as expected, or the network itself is at fault. Note the original value before making changes, and change one setting at a time to make results easier to assess.
SETTINGS / THREE TOPICS
Rules, connections & configuration
Choose a section based on what you want to do. If a default hasn’t been verified, use the value currently shown in the app; don’t assume an example is the default.
Global Routing
Global Routing determines whether requests use the configuration, a proxy, or a direct connection. The options are Config, Proxy, and Direct. Config applies the rules in the currently enabled configuration file; Proxy sends eligible requests through the selected proxy; Direct connects without a proxy. Use the selection currently shown in the app as the reference. If you have explicit routing rules, Config is a good starting point. To troubleshoot, temporarily compare the options on the same network and with the same destination, then restore the original selection. Changing the routing mode doesn’t switch servers or fix incorrect authentication details.
Config · Rule
In Config, check which file is enabled and review its Rule contents. DOMAIN-SUFFIX matches domain suffixes, GEOIP matches by IP address location, and FINAL handles requests not matched earlier. PROXY, DIRECT, and REJECT are different actions. First check rule order and whether the referenced policies exist, then add exceptions if needed. example.com is shown only to illustrate syntax; don’t replace your entire existing file with the example. Default rules depend on the active configuration, so one file’s behavior should not be treated as the app’s default for everyone.
DNS
DNS resolves domain names to addresses, but successful resolution doesn’t guarantee a successful connection. When troubleshooting, check name resolution, rule matching, and server connectivity separately. DNS values may depend on the active configuration file, so use the app and enabled file as the source of truth for current defaults. Keep settings from a verified configuration unless you’ve confirmed a DNS issue; then adjust one value at a time and record the results. Stacking DNS settings without a clear reason can change request routing and make rule behavior harder to reproduce.
RULE SYNTAX
Match condition → Policy
DOMAIN-SUFFIX,example.com,PROXY
GEOIP,CN,DIRECT
FINAL,PROXYThis shows rule syntax only. Actual results depend on the full configuration, rule order, and available policies.
On Demand
On Demand triggers connections based on conditions. Set it up after you’ve confirmed that manual connections work reliably. Open Settings and review the conditions currently available under On Demand. Decide which network conditions should trigger a connection, then configure them one at a time. Use the current app display to check defaults and enabled conditions. During initial testing, use the manual switch to avoid automatic triggers affecting your observations. If the connection drops and then reconnects automatically, check these conditions and the system VPN status before deleting configurations. Automatic triggers can’t replace a working server or correct authentication details.
Add Server
Add Server lets you enter details for an existing server. Select the appropriate Type, then fill in Host, Port, and authentication fields using the supplied details; required fields vary by protocol. Don’t reuse parameters across Shadowsocks, VMess, VLESS, Trojan, Hysteria2, and WireGuard. Enter values exactly as provided—don’t guess the port, password, or transport settings. There are no universal recommended values for every server; use the current interface as the reference for defaults. After saving, select the entry and test an actual request.
Connectivity Test · Ping
Connectivity Test and Ping can help assess reachability, but results vary by test method and don’t represent real download speeds. Use the same method and network conditions for comparisons, and consider how pages actually load. Check the current Test Method value in Settings rather than assuming a default. If a test responds but a page won’t load, check Global Routing, DNS, and Log. If a test fails, determine whether the destination simply doesn’t respond to that test or the connection itself is failing; one result alone doesn’t show that every configuration is unusable.
CHECK IN ORDER
Test one layer at a time
- Can the current network reach a destination known to be available?
- Do Type, Host, Port, and authentication details match the supplied information?
- Are the selected server and Global Routing mode behaving as expected?
- Do DNS, rule matches, and Log provide relevant clues?
For more detail, check each setting in the handbook. Don’t keep changing everything based on a single test result.
Read the settings handbook →Subscribe
Subscribe manages sources for subscriptions you already have. Subscription URLs often contain access credentials, so keep them as secure as passwords. Make sure the link is complete, import it using the subscription option currently available in the app, and check the resulting server group. Use recognizable names for different sources, then confirm the expected entries are still there after an update. Check the current app display for defaults such as automatic updates. An update refreshes content from the source; it doesn’t guarantee every server will remain available or update your active rule file.
Config
Config primarily manages configuration files and rules; server subscriptions primarily manage connection entries. They serve different purposes. After importing a subscription, if you choose Config, check which configuration file is enabled. Before editing, keep a recoverable copy and review General, Rule, and referenced policy names to avoid overwriting existing exceptions. Use the app display to check the active file and its current contents. Remote updates may replace manual edits, so keep track of where the file is saved and how it updates.
iCloud · Data
iCloud options manage data across devices, while Data shows traffic recorded by the app; neither confirms that a connection works. Use the app to check sync scope, default switch states, and how traffic is counted. Before editing or deleting data, confirm what actually synced to another device and keep a recoverable copy of important configurations. Traffic shown in Data only indicates that data was transferred; it doesn’t prove that all destinations were routed as intended. To verify a connection, also check the actual results, current routing mode, and relevant logs.
KEEP THE ROLES SEPARATE
A subscription isn’t a rule file
- Server details
- Specify the destination and the protocol and authentication method to use.
- Subscribe
- Get and update server entries from a subscription source you already have.
- Config
- Determine which policies handle requests that match each rule.
Understand what each component does before deciding what to update. A successful import doesn’t mean the connection has been verified.
When reviewing settings, distinguish between three layers: interface options, configuration file contents, and system authorization. Global Routing is the app’s current routing mode; Rule contains matching conditions in a file; system VPN authorization allows the app to create the corresponding network configuration. One layer working as expected doesn’t mean the others have been checked. Troubleshoot in order rather than relying only on the main switch.
This handbook doesn’t present unverified settings as fixed defaults. Existing configurations, device state, and the current app interface can all affect what you see. Start with parameters you’ve verified, then adjust them for a specific need. If you don’t have a clear reason to change DNS, Proxy ports, or On Demand, note the current values and leave them as they are. For details on individual settings and how to check them, see Settings reference.
DEVICES / STORE
Getting Shadowrocket on iPhone & iPad
Use the same App Store product page to check the purchase and compatibility details. Refer to the system requirements listed on the App Store page.
iPhone
A good place to start is manually importing one existing configuration. Before buying, check device compatibility. On your first connection, review the system prompt to add a VPN configuration and approve it if you wish to proceed. After authorization, return to Home, select a server, check Global Routing, and test access.
View instructions →iPad
Use the same Apple Account to check purchase history and whether the purchase is available across devices; refer to the App Store listing. Layouts may differ, but server parameters and rules work the same way. After installing on another device, check its configuration, system authorization, and actual connection separately.
View instructions →Shadowrocket is also available in the App Store for Mac and Apple TV. Check the listing for compatibility, system requirements, and whether the purchase works across devices.
App purchase history and connection details stored on a device are separate things. Purchases under the same Apple Account can help restore the app, but don’t mean every device has the same servers, subscriptions, or rules saved. After switching devices, check the currently selected items rather than assuming everything is ready just because the app is installed. If you use iCloud features, confirm what actually synced.
When the system first prompts you to add a VPN configuration, make sure the request was initiated by Shadowrocket, which you just opened. After allowing the system configuration, return to the app and check the connection status. If no prompt appears, authorization was canceled, or the system status looks unusual, follow the first-connection steps in the guide. Other network settings on the device may also affect the result. Keep a record of the current setup and check one variable at a time.
QUICKSTART / 01—03
Three steps to get started with an existing setup
First establish a repeatable manual connection, then add routing exceptions and automatic triggers.
-
Add Server / Subscribe: import existing details
Have your existing server details or subscription URL ready. In Add Server, enter the fields for the relevant protocol, or use the subscription import option currently available in the app. After saving, check that the expected entries appear in Home, the labels are recognizable, and Host, Port, and Type match. Don’t share subscription URL credentials in public screenshots, comments, or shared documents.
A completed import only means the information was read; it doesn’t prove the server works. If the list is empty, check that the link is complete, the source can be read, and its format is supported. If only some entries have issues, start by checking those entries rather than immediately deleting the entire subscription. Use the details in your existing configuration as the source when filling in fields manually.
-
Global Routing: choose a routing mode
Choose Config, Proxy, or Direct based on what you want to test. To use existing rules, select Config and check the enabled file. To temporarily test the selected proxy connection, use Proxy for comparison. Direct lets you observe the result without a proxy. These are routing modes, not separate servers or protocols. Note the original selection before switching so you can restore it after testing.
If a destination behaves differently than expected, first check which rule it matched and which policy was applied, then decide whether to add an exception. Rules are processed in order; an earlier match can prevent later entries from taking effect. Understand the match scope before copying in a new rule. In particular, don’t place a broad rule near the top of the file without considering its impact.
-
Home: connect and test a request
Select the server you want to use and start the connection, then follow the system prompts to authorize the VPN configuration. Visit a destination known to be available and check Connectivity Test, Log, and the actual loading result. A connected status at the top shows the client is running, but only actual request results can confirm that a page is accessible and rules are working as intended.
If a connection fails, first check whether the current local network can access the destination normally, then review server details, rules, and DNS. Keep the network, destination, and test method consistent, changing just one setting at a time. A Ping response or an increase in Data alone doesn’t prove that all app traffic uses the same policy. Record the specific destination that failed to make troubleshooting more focused.
VERIFY / PURCHASE / RESTORE
Verify the app & understand the purchase
The name is only a starting point. Check the developer, official icon, and app ID together.
LISTING CHECK
Developer and app ID
On the App Store product page, check that the developer is Shadow Launch Technology Limited, then verify id932747118 in the page URL. Compare the store icon with the official icon in this site’s header as well. Proceed with your purchase only when all three match.
Similar names in search results can be confusing. Don’t rely on one word in the title, the screenshot style, or the description alone. The app ID identifies the specific product, the developer name verifies who published it, and the icon offers a visual comparison. Checking all three is more reliable than relying on any one alone. See the App Store verification guide for the full process.
STORE REGION
Store availability and your account
After opening the product page, check what’s shown in the storefront associated with your current Apple Account. Purchase availability, local currency pricing, and compatibility requirements all need to be confirmed in the store. If the app doesn’t appear in search, check your account’s storefront region, age restrictions, and account status first; no search result doesn’t necessarily mean the app has changed its name.
A web link and the storefront account used on your device aren’t the same thing. Before checkout, confirm the account and product page details. Always refer to the App Store page for system requirements. This homepage doesn’t list a specific version or update date. To see what has changed, check the store’s update history and consult the handbook alongside the current app interface.
PURCHASE RECORD
Purchases, restores, and using multiple devices
Shadowrocket is a one-time purchase. The US storefront lists it at $2.99, while other storefronts show local currency; the checkout page is final. Check purchase history under the same Apple Account for iPhone and iPad. Refer to the App Store listing for availability across devices and compatibility with other devices. When changing or restoring a device, look for the original app in your purchased items and check which account is signed in.
Restoring the app doesn’t restore all connection details. Before deleting it, save your existing subscription URLs and necessary parameters, and note which configuration file is enabled. If you use iCloud, confirm the data has actually synced. If the store still shows a purchase prompt, check your account and purchase history instead of assuming you’ll be charged again because the app was previously installed. See the guide to restoring a purchase for details.
SCOPE
The client and connection service are separate
Buying the client doesn’t include a server plan. Purchasing the app grants the right to use the client; it doesn’t create a server, subscription URL, or authentication details. This site doesn’t provide, sell, or recommend servers or subscriptions. It explains how to add your existing configuration to Shadowrocket and check rules, connections, and diagnostic results. If you don’t have the necessary details yet, you can read about the interface first; don’t enter parameters you don’t know.
Server availability and connection performance depend on the actual connection conditions; they can’t be inferred from whether the app has been purchased. Subscription updates refresh content from a source, while App Store updates update the app—these are separate processes. If something goes wrong, first determine whether the issue concerns a purchase or restore, configuration import, or connection test. Then follow the relevant section rather than repeating steps at the wrong level.
ARTICLES / RECENT TOPICS
Configuration & troubleshooting articles
Once the basic connection works, review subscription management, request blocking, and App Store availability.
Manage multiple Shadowrocket subscriptions: label, sort, remove, and clean up duplicate servers
When importing multiple existing subscriptions, use labels to identify their sources, confirm the group before updating, and check which source an entry belongs to before deleting it. This article explains how to find duplicates and keep Home organized, so similarly named entries aren’t mistaken for the same server.
Read the article →How to write Shadowrocket REJECT rules: request blocking, syntax, and limitations
Learn how REJECT works during rule matching and check where DOMAIN-SUFFIX and IP-CIDR apply. Request blocking depends on matchable conditions and can’t handle every kind of page content. If legitimate requests are blocked, check match records and rule order to find the cause.
Read the article →Can’t find Shadowrocket in the App Store? Check storefront region, age rating, and account status
If search returns no results, check the storefront region, Screen Time restrictions, and account status one by one. First identify the specific restriction, then return to the same product page to verify availability. Don’t rely on repeatedly changing search terms to determine whether the app is available.
Read the article →