A rule-based proxy client for iPhone / iPad, with rule-based routing and a one-time purchase through the App Store.
Verify the app before you buy
Shadowrocket
App Store listing
Enter the protocol and fields provided by your service provider
Understand rules, proxying, and direct connections
A list explaining settings, not an app screenshot. Config uses rules in the current configuration; Proxy routes traffic through a proxy; Direct connects directly.
Examples illustrate rule structure only
# Domain suffix
DOMAIN-SUFFIX,example.com,PROXY
# Local address range
IP-CIDR,192.168.0.0/16,DIRECT
# Final match
FINAL,PROXYTest manual connections first, then set trigger conditions
Network condition names
Understand the roles of servers, configuration files, and the connection toggle before changing individual settings. These six topics can be read separately; the official handbook covers the full setup sequence.
Global Routing determines how requests are handled. Config applies the rules in the current configuration to choose a policy; Proxy routes requests through a proxy; Direct connects without a proxy. For everyday rule-based routing, first confirm which configuration is active, then select Config. Rules are generally evaluated in order, so earlier matches can affect later results. Save a copy of the original configuration before making changes. If a website does not follow the expected route, check the matching rule and its policy rather than relying on the connection toggle alone.
Read the handbook →Interface terms: these three modes change how traffic is handled; they do not supply missing server details.
On Demand uses specified network conditions to trigger a connection. Set it up only after confirming that manual connections work. Find On Demand in Settings and review the Wi-Fi and Cellular conditions you need; also confirm that the system VPN configuration is still present. On Demand controls when a connection starts, while Global Routing controls how requests are handled after it connects. They are separate settings. To troubleshoot unexpected reconnections or network-switching issues, temporarily disable On Demand, compare results with a manual connection, and then restore conditions one at a time.
Read the handbook →Whether a connection is triggered also depends on the system’s network state; a trigger does not mean the destination website is reachable.
Before adding a server, check the protocol type in the information you already have. Protocols such as Shadowsocks, VMess, VLESS, Trojan, and Hysteria2 use different authentication and transport fields; do not reuse one protocol’s settings for another. In Add Server, select Type first, then check the address, port, authentication details, and TLS or transport settings field by field. A successful import only means the entry was saved; missing or mismatched settings can still prevent a connection. Use the original details rather than guessing based on the protocol name.
Read the handbook →Protocol names help identify the right parameter type; use the fields shown in the app as your reference.
Import a subscription only if you already have its URL. Select the matching Subscribe type, paste the full URL, and check for spaces, line breaks, or truncated query parameters. After importing, confirm that the expected entries appear in the group before testing the connection. Updating a subscription fetches server details again; it does not extend the service or guarantee that existing entries will remain usable. If an update fails, check your network, the URL, and the response from your provider. Avoid repeatedly deleting configurations that still work.
Read the handbook →Subscription URLs may contain access credentials. Do not share the full URL or QR code when asking for help.
Configuration files store rules and related network settings; server entries store connection destinations. Check both separately. In Config, confirm which file is active and save a recoverable copy before editing. Understand the purpose of sections such as General, Rule, and Hosts. Place rule snippets in the correct section and make sure they refer to policies that exist. Before using iCloud sync features, check your system account and sync status; syncing is not a substitute for a separate backup. Store files containing sensitive settings securely, and change one item at a time when troubleshooting.
Read the handbook →DOMAIN-SUFFIX,example.com,PROXY
IP-CIDR,192.168.0.0/16,DIRECT
FINAL,PROXYSyntax example only; not a complete configuration to replace an existing file.
Connectivity Test checks reachability using the selected test method; it does not replace testing a website in a browser. Data can help track traffic changes, but the app and your provider may use different reporting methods. If something goes wrong, check the diagnostic tools under Settings, then note the network, routing mode, and symptoms. Troubleshoot the local network, server settings, DNS, and rules in turn. Redact authentication details before sharing diagnostics. A single latency result is rarely enough to identify the cause.
Read the handbook →Keep a complete record: network conditions → test method → actual results.
The server determines where to connect; the configuration determines which route requests take; system VPN permission allows the client to establish the connection. Completing just one of these steps does not mean everything is set up. For your first connection, test a single existing server before importing a large set of rules. That way, you can tell whether a problem stems from adding the server, routing, or connecting.
The official handbook keeps interface labels, protocol names, and rule keywords in English so you can match them to the app. If you see an unfamiliar term such as DOMAIN-SUFFIX, IP-CIDR, or FINAL, check the glossary before returning to the current step. For an overview of what each option does, see Features. There is no need to change every advanced setting before your first connection.
Shadowrocket is available only through the App Store. Before purchasing, verify the listing and check compatibility and your purchase status for the current device.
Start from Home to import settings and make your first connection. After purchasing through the App Store, open the app and add an existing server or subscription. The first time you connect, review the system prompt to add a VPN configuration. Allow it, then return to the app to check the connection toggle and visit the destination website. Opening the app alone does not establish a connection.
Check the App Store listing for system requirements. If the expected purchase or redownload option is not shown, first verify the current store account and purchase history before trying again.
See iPhone access and permission steps →On iPhone and iPad, check your purchased apps under the same Apple ID to confirm the purchase or redownload the app. The larger display can make it easier to compare Config with parameter details, but changes to the layout do not alter how servers, rules, and connection permissions work. Use the labels shown on the current screen.
Restoring a purchase does not restore server details. When opening the app on another device for the first time, check the configuration, subscription, and system VPN permission separately. Verify the connection even if content was restored through sync.
See iPad purchase and setup guide →Shadowrocket is also available on Mac / Apple TV through the same App Store. Check the App Store listing for compatibility, system requirements, and whether Universal Purchase applies.
See how to get the app →Have your existing subscription or server details ready, then follow these steps in order. Get a result you can reproduce before adding automatic connections or custom rules.
Go to Home and select the matching Type in Add Server. If entering details manually, check each field against the original information. If importing a subscription, make sure the URL is complete and check the server group after import. QR codes and subscription URLs may contain access credentials; treat them as sensitive information when storing or sharing them.
First confirm that the expected entries are available to select. If the list is empty, the type is wrong, or required settings are missing, fix that before changing DNS or routing rules. This site explains how to import and use existing details; it does not provide servers or subscriptions.
To use the rules in your configuration, select Config and confirm which configuration file is active. For troubleshooting comparisons, you can temporarily use Proxy or Direct if you understand the effect, then compare access to the same destination. Restore the original setting after testing so later results remain comparable.
Seeing PROXY in a configuration does not mean every request will use a proxy. The result depends on rule order, matching conditions, and the final policy. If only one website is affected, check its matching rule first instead of immediately rebuilding all server entries.
Select a server and turn on the connection toggle. The first time you connect, follow the system prompt to add a VPN configuration. Then run Connectivity Test and open the website you need to access to check that it loads. System connection status, test results, and actual access are separate checks; verify each one.
If the connection fails, note what happened before checking the current network and server settings. If latency looks normal but websites do not load, check DNS and rules. If the problem occurs after switching networks, compare the same configuration on each network. Change one condition at a time to see whether it helps.
Shadowrocket is a closed-source commercial app. Use its App Store listing and your account’s purchase history to verify availability, payment, and updates. This is the official site and handbook.
On the App Store listing, confirm the app name is Shadowrocket and the developer is Shadow Launch Technology Limited. The app icon should match the official icon used on this site. The App ID in the listing URL is 932747118. Similar names do not mean it is the same app: check all three details rather than relying on search-result order or icon color alone.
After verifying the listing, check the price and compatibility. The download guide explains where to find these details; payment takes place in the App Store. Links to the app from different sections of this site all lead to the same listing—there is no need to look for another way to get it.
See how to verify the official listing →App Store availability, billing currency, and payment methods can vary by storefront. If you cannot find the app, first make sure you opened the specified listing, then check the account and storefront currently shown in the App Store. Always refer to the App Store listing for system requirements; do not assume your device is compatible just because the listing opens on another device.
Your account region is an App Store account setting and is unrelated to the server address entered in Add Server. Importing a configuration does not change purchase eligibility, and changing network rules is no substitute for checking your account. If you see a purchase prompt, read the App Store information and follow the relevant account process.
See App Store listing guidance →The app purchase is not a service plan. The one-time payment covers use of the Shadowrocket client; it does not create server entries or include a subscription for connecting. The US storefront reference price is $2.99. Prices are shown in local currency by storefront; check the App Store listing for the current price.
To connect, you need your own existing subscription or server details. Check with your original provider for service validity, usage limits, and changes to settings. Buying the app and having an active connection service are separate matters. This site does not provide, sell, or recommend servers or subscriptions; it explains how to import existing details, choose rules, test connections, and troubleshoot issues.
Read about pricing and the one-time purchase →On a new device, use the original purchase account to check your App Store purchases, then redownload the app. Keep purchase history and locally stored settings separate: redownloading the client does not restore subscription URLs, server credentials, or custom rules. Save anything you need before reinstalling, then verify each item after restoring it.
App updates are delivered through the App Store; refer to the store for release details. If you use iCloud sync, check your system account and sync settings first, and keep a separate copy of your configuration. If something changes after an update, confirm that the server and Config selection are still correct before checking automatic triggers such as On Demand.
See how to restore purchases →Restoring a purchase restores eligibility to use the app; servers must be added separately using information you already have. Check whether the import through Add Server or Subscribe is complete and whether the expected entries appear in the group. Verify purchase history and service details separately. See the Getting Started guide for the import steps.
The test reflects only the selected test method. Website access can also depend on DNS, TLS, rule matches, and the destination service. Note the affected website and network conditions, confirm Global Routing, then check DNS and configuration rules. See Troubleshooting for a step-by-step approach.
No. A subscription usually retrieves server details; Config manages rules and related settings. Updating one does not mean the other has changed. First determine whether you need to update server information or change how requests are routed, then choose the relevant action. See the glossary for definitions.
Not directly. The app and your provider’s dashboard may differ in their starting points, coverage, and calculation methods. Data is more useful for tracking traffic changes; check with your provider for your remaining service allowance. If you need a record, note the reporting scope and observation time so you are not comparing figures measured differently.
Start with the specific symptom: confirm how the data is measured, then check name resolution and the network path. Each article focuses on one issue, so you can choose the troubleshooting steps that match your situation.
Slow speeds can have more than one cause. Compare your existing server, local network, and protocol settings one layer at a time, keeping the destination and conditions consistent to avoid misleading results.
Read the troubleshooting steps →Test server connectivity and domain resolution separately to find where requests get stuck. Check the current DNS and routing configuration first, then make changes in order instead of rebuilding all entries at the outset.
Read the DNS troubleshooting guide →Compare upload and download traffic and understand the scope of each view. Learn why app readings may not match your provider’s dashboard, and use traffic changes as one clue when assessing connection activity.
Read about traffic reporting methods →