Check three details in the store
Before getting the iPhone / iPad version, open the Shadowrocket App Store product page and confirm that the developer is Shadow Launch Technology Limited, the app ID is 932747118, and the icon matches the official icon used in this site's header. Check the name, icon, developer, and product page together; do not identify the app by a similar name in search results alone. The app ID in the product page URL distinguishes listings with the same name; store search ranking does not establish product identity.
Before purchasing, also review compatibility and the local price shown in the store. System requirements for iPhone / iPad are as listed on the App Store page; do not rely on system version numbers in older guides. For Mac, Windows, Android, and Linux, use the matching installer on this site's download page rather than selecting a desktop version from mobile store search results. Keep a record of the download source. If an installation prompt appears, verify the source first, then follow the approval steps for that platform.
Understand store region and device region
App Store availability depends on the store region for your purchasing account, not directly on the device's current language. If Shadowrocket does not appear in your store, check the country or region for “Media & Purchases” in your account settings, then review the region change requirements shown by the system. Conditions such as account balance, active subscriptions, and payment methods may affect the process; follow the guidance on your account page. Repeatedly changing the device language or restarting the phone will not resolve a store-region mismatch.
Confirm the product page before purchasing. You do not need to enter purchasing account details in Shadowrocket's server fields. The app store account is used to get the client; server credentials are used to connect. If the store reports a payment or account restriction, resolve it in the store account. If the app reports a server connection failure, troubleshoot the network and connection details instead; do not confuse the two types of errors.
Understand one-time purchases and restoring downloads
The iPhone / iPad version costs $2.99 one-time on the App Store; other storefronts may display prices in local currency. Mac, Windows, Android, and Linux versions are free. iPhone and iPad can share a purchase under the same purchasing account, and downloads can be restored from purchased items on compatible devices. After changing devices, first confirm you are signed in with the original purchasing account, then check your purchase history. If the app appears with a new price, verify the account and product identity before purchasing again.
Restoring the client and restoring its configuration are separate tasks. Reinstalling the app does not automatically restore your subscription URL, manual servers, or local changes. Before changing devices, save configurations you want to keep and check sync status. Afterward, check the server list, current Config, and connection permissions one by one. Mac, Windows, Android, and Linux users can get the appropriate version again from the download page; preserve existing configurations before updating instead of treating an app update as a data backup.
Prepare your own server or subscription
Before configuring the app, have your own subscription URL or server details ready. A single share link, QR code, subscription URL, and Config file each contain different information; do not assume they use the same import method just because they are all links or files. A single server entry establishes one connection, a subscription maintains a list of servers, and a configuration file controls rules and related settings. After importing, check which item was added before choosing a server and routing mode.
An app purchase is not a network service plan. The app purchase record does not include a server address, connection credentials, or service validity period; free versions for other platforms also require service details you already have. This site only explains how to import and use that information. Subscription links, QR codes, and exported configuration files may contain credentials. Before sharing a troubleshooting screenshot, hide access parameters, passwords, and other authentication details in the URL; the error and setting names are usually enough.
Check each connection stage, not just the switch
On iPhone / iPad, for example, select a server from Home, check Global Routing, then turn on the connection switch. The first time you connect, the system may ask for permission to add a VPN configuration. After allowing it, return to the app and check the status. A system message that the connection is established only confirms that the local connection process reached that stage; it does not by itself prove that a website is accessible or that a destination matched the expected rule.
To verify, first confirm the regular network is working, then run Connectivity Test and visit the destination you want to test. If only some destinations fail, check DNS, rule order, and which rule matched the destination. If all destinations fail, first check the server status and parameters. Traffic in Data can be a useful clue, but should be considered alongside actual access results. Note the current settings and change one item at a time; this makes it easier to identify the cause than changing the server, rules, and DNS simultaneously.
Handle updates and configuration maintenance separately
Manage iPhone / iPad app updates through the App Store; get new installers for Mac, Windows, Android, and Linux from this site's download page. Before updating the client, save your current configuration. Afterward, check the selected server, Global Routing, and required permissions. A subscription update rereads your existing remote server list; an app update does not confirm that the list was retrieved successfully, nor does it automatically maintain the rules in Config.
For routine maintenance, track changes to the app, subscription, and configuration separately. If entries disappear after a subscription update, check the remote list and service status first. If access changes after editing a configuration, check the rules first. If the connection fails after a system update, check permissions and the network environment. For more detailed steps, follow the chapters in the full manual in order. Avoid deleting all settings and losing the original information needed to troubleshoot.
Frequently asked questions
I just installed the app. Why are there no available servers?
The client and network service are set up separately. First get your own subscription URL or server details, then import them using the appropriate type. After entries appear in the list, select a server and check Global Routing. Installation alone does not complete connection setup. See the first-import steps.
What is the difference between Config and Subscribe?
Subscribe reads and updates a server list; Config stores rules and related settings. A successful subscription update does not mean the rules have changed, and selecting a configuration file does not mean a usable server is available. Before troubleshooting, determine whether you need to change the server source or the traffic route. See interface terms and configuration terminology.
How do I get the computer, Android, and Linux versions?
Mac, Windows, Android, and Linux versions are free. Choose the system and architecture on this site's download page. The iPhone / iPad version costs $2.99 one-time on the App Store. For Mac, check whether you need Apple Silicon or Intel; for Linux, choose the package format for your distribution. Follow each platform's system prompts the first time you open the app. See installation approval instructions.
The switch is on. Why are some destinations still inaccessible?
Check Global Routing first, then confirm which rule matches the destination and review DNS results. A successful server test and access to a destination are not the same thing. Test methods and destinations can also affect results. Keep a record of failed destinations, error messages, and network type, then troubleshoot in order. See connection troubleshooting Q&A.