All platforms · Official guide
A rule-based proxy client for iPhone, iPad, Mac, Windows, Android, and Linux. iPhone and iPad are a one-time App Store purchase; Mac, Windows, Android, and Linux are free.
Current version v2.2.92 · Mac, Windows, Android, and Linux are free
Explore features
First, distinguish server details, configuration files, and routing modes; then inspect actual requests. The examples below show configuration syntax and settings, not a simulated app screen. Sample rules illustrate how matching works and are not a complete configuration to enable as-is.
DOMAIN-SUFFIX,example.com,PROXY
IP-CIDR,10.0.0.0/8,DIRECT
FINAL,PROXYRule-based routing lets you apply different policies to different requests. In Home > Global Routing, select Config to apply the rules in the active configuration. Proxy and Direct specify different routing behaviors; they are not speed settings. In Config, check the rule order and place specific matches before broader ones. FINAL sets the policy for requests that match no earlier rule. After making changes, send the request again and check which rule and policy matched. An active connection does not guarantee that a request uses PROXY.
On Demand uses network conditions to determine when to connect; it does not replace server credentials or fix rules. In Settings, find On Demand and first confirm that a manual connection works. Then configure conditions for your Wi-Fi, Cellular, or domain as needed. Add one condition at a time, switch networks, and check whether the expected connection behavior occurs before adding more. If the connection starts again after you disconnect manually, check these triggers too. On Demand controls when to connect, while Global Routing determines how requests are handled; test them separately.
Multiple protocol support lets you connect to different types of existing servers; it does not mean you can choose any Type. In Add Server, select the protocol used by the server, then check Host, Port, and the relevant authentication fields. Shadowsocks Method, transport settings for some protocols, and TLS parameters each have specific meanings; do not copy one protocol's fields into another. For an existing subscription, import the original details whenever possible and compare each field with its source if an error occurs. Speed and battery use also depend on the network, server, and workload, so the protocol name alone cannot predict performance. See the technical reference for more detail.
Subscribe · format example only
https://example.com/sub?token=xxxxUse your own existing subscription details. This example address cannot connect.
Subscribe reads server entries from an existing subscription and is useful for managing multiple connection details in one place. Before adding one, make sure the link was copied in full, without extra spaces, line breaks, or missing parameters. After importing, check the group and entries, then test one entry. Updating a subscription is different from updating the app: the former reloads subscription contents, while the latter updates the client through the App Store. If an update fails, first check whether your current network can reach the subscription URL, then verify that the subscription is still valid. Subscription links may contain access credentials; do not post the full link publicly when troubleshooting.
[General]
[Rule]
[Host]
[URL Rewrite]Configuration files organize global settings, rules, local mappings, and rewrite settings. They serve a different purpose from subscriptions, which provide server entries. In Config, confirm which file is active. Before editing, keep a recoverable copy, then check the syntax and policy names section by section. PROXY in a file still needs to correspond to an available server entry; importing a file alone does not make a connection possible. For iCloud-related settings, first check the account used on each device and the sync status, then verify what appears on the other device. Restoring an App Store purchase only restores access to the app; it does not confirm that configuration has synced.
Connectivity Test can help assess whether the selected entry is reachable, but its results do not replace testing actual access. In Settings, check Test Method and keep the test method and network conditions consistent when comparing results. If a connection fails, first determine whether the issue is subscription retrieval, connection to the server, or the target request. Then use Diagnostics and request records to narrow it down. Data shows traffic changes; it is not a subscription balance or billing statement. Before sharing diagnostic details, remove server addresses, authentication fields, and subscription parameters. Change one setting at a time so you can identify what affected the result.
If a field is unclear, check the glossary. For protocol parameters and configuration trade-offs, see the technical reference. English interface terms are retained so you can match them in the app.
Devices and availability
iPhone and iPad are purchased on the App Store. Mac, Windows, Android, and Linux are free from this site. Check device compatibility and the account used for the purchase, then confirm whether the listing shows a purchase option or that the app is already purchased. Always refer to the App Store listing for system requirements.
Verify the App Store listing, complete the purchase, and open the app. The first time you connect, the system may ask to add a VPN configuration. Check the app source shown in the prompt, then follow the system instructions. Return to Home to check the selected server and Global Routing, then verify the connection with an actual request.
See the iPhone setup and authorization steps →Use the same purchase account to find the app in your purchased items. App Store listing details determine whether the purchase covers both iPhone and iPad. A larger screen does not change how subscriptions, configurations, and routing modes work. After getting the app, check that your existing server details have been imported and the correct configuration is selected.
See iPad setup and configuration tips →The Mac desktop app is free on the download page. Apple TV follows that device’s App Store listing.
On the product page, verify the app name, developer, and app ID before purchasing. If the page is not currently visible, check your App Store region, age-rating restrictions, and account status first. Do not rely on similar search results to identify the app.
View setup steps →Quick-start preview
These steps assume you already have your own subscription or server details. For your first attempt, use one set of known-good details and keep the test conditions simple. After the connection works, add custom rules and on-demand triggers gradually.
01 / Add details
If you have details for a single server, open Add Server from Home, choose the Type that matches the source, and fill in the corresponding fields. If you already have a subscription, import it using the Subscribe type. Save and return to the list to check that the entry name, protocol, and group look right. If the list is empty, check the imported content and whether the link was read successfully; toggling the connection repeatedly will not fix missing details.
02 / Routing
To route traffic by rules, select Config and check which file is active in Config. Proxy and Direct can help distinguish access results under different routing behaviors, but they do not replace a complete rules check. Note the initial selection, then restore your usual mode after testing so temporary troubleshooting settings are not left in place.
03 / Verify
Select an existing server entry, turn on the connection, and authorize the system VPN configuration if prompted. Run Connectivity Test first, then open the page you need to access. A successful result means both that the connection was established and that the target request behaved as expected. If the test passes but the page does not load, check DNS, rule matches, and the target service rather than assuming all traffic is working.
View the complete guide → The guide covers importing, modes, authorization, verification, and troubleshooting. Pick up at the step where you are stuck.
Verifying the app and purchase details
Shadowrocket is a closed-source commercial app. This is the official site and guide. Before purchasing, use the App Store product page to verify the app's identity, price, and compatibility. Do not rely on the app name or search ranking alone.
The developer should be Shadow Launch Technology Limited, the app ID is 932747118, and the product page URL contains id932747118. Compare these details with the official icon shown here; a similar name alone is not enough to verify the app. Once all three details match, check the price and compatibility information on the listing.
If you cannot find the app in search, open the product page directly to verify it instead of repeatedly changing your search terms. Your current App Store region, age-rating restrictions, and Apple Account status can all affect whether the listing appears or a purchase is available. Check the account used for App Store purchases and its status, not just your device language. The current listing determines the price, currency, and purchase availability. See the download guide for troubleshooting steps.
The US reference price is $2.99 as a one-time purchase. Other storefronts show local currency, and the final amount appears at purchase confirmation. The purchase covers use of the client, not server connection time. Before buying, check two separate things: whether your device is compatible and whether you already have a usable subscription or server details. Neither condition replaces the other.
Use the same purchase account to access purchased apps on iPhone and iPad; see the App Store listing for the exact eligibility. After changing devices or reinstalling, look for the app in your purchased items and check which App Store account is active. Restoring access to the app and restoring personal configuration are separate tasks. Check subscriptions, rule files, and sync status from the original device separately. Seeing the purchased button does not mean your existing configuration has been restored to the new device.
Update the client through the App Store. You can check automatic update settings in the system's App Store settings. App updates, subscription updates, and switching configuration files each affect different content, so note the order of changes when troubleshooting. Keep a recoverable copy before editing rules, and check which entries changed after updating a subscription. Interface locations may change; follow the English labels shown in the current app.
Related reading
These three articles explain interface terms, on-demand connections, and configuration file structure. First identify which area your issue belongs to, then follow the relevant guide. This helps avoid changing server parameters, connection triggers, and routing rules all at once.
Learn what common English interface terms do and where to find them. Distinguish Home connection controls, Config files, and Settings options, then look up Proxy and Direct under Global Routing to avoid opening the wrong screen when labels seem similar.
Read the interface glossary →Start with manual connection working, then check Wi-Fi, Cellular, and domain triggers one at a time. Learn how to verify behavior after switching networks and which settings to check first when triggers overlap or the connection restarts after a manual disconnect.
Read the On Demand guide →Learn the role of each section, from global settings and rule matching to local mappings and rewrite configuration. Pay particular attention to the difference between server entries and configuration files, where FINAL belongs, and how to keep a recoverable copy before editing so you can compare actual request results before and after.
Read the configuration file guide →Browse all articles → For purchase and restoration questions, see the FAQ. To learn what each setting does, see Features.