Shadowrocket is available across platforms: get it for iPhone and iPad from the App Store for a one-time $2.99 purchase; check the App Store listing for system requirements. The Mac (Apple Silicon and Intel), Windows, Android and Linux versions are free. This guide is for anyone verifying the app before installation, getting it again on another device, or investigating an issue after installation. Start by identifying the right source for your platform, then cross-check the developer, official icon and app ID. Finally, distinguish app identity checks from connection and configuration issues.
Know where to get the app—and what verifies it
Start with the source, not an icon’s size, search ranking or description. On iPhone and iPad, verify the app on its actual App Store product page. For desktop and Android, choose your platform on this site’s download page. Search results, forwarded images and home screen icons can help you find the app, but they do not verify its source.
The App Store app ID identifies a product listing in that store. It is not the filename of a desktop installer or a subscription account. Don’t expect Mac, Windows, Android or Linux installation files to contain this number. Verify each platform using its own source-checking steps; App Store listing details do not apply to every operating system.
iPhone / iPad: verify the App Store listing step by step
Start from the iPhone / iPad App Store link on the Get the app page, then verify the product listing—not just a name in the search results. You don’t need to import a subscription or turn on a connection to follow these steps.
-
Open the product page
Open this site’s Get the app page and select the App Store option for iPhone / iPad. Make sure you’re on the Shadowrocket product page, not another product with a similar name or an informational page.
-
Check the developer
Check the developer name on the product page. If needed, expand the information section to verify the provider details. The full name should be Shadow Launch Technology Limited. Don’t treat a name quoted in a search snippet as the developer field.
-
Compare the official icon
Compare the product page icon with the official icon below: a rocket with blue-purple outlines on a white background. Don’t rely on a similar color alone, and don’t mistake decorative artwork in an app screenshot for the app icon.
-
Check the app ID
Use the product page’s share option to copy the link, then check that its URL path includes
id932747118. Also make sure the link opens an App Store product page, rather than a regular webpage that merely includes the number in its title. -
Get the app once verified
Once all three checks match, get the app from that product page. Check the App Store listing for system requirements. If you’ve obtained it before, check the purchase history for your current Apple Account before trying again.
When checking a link, focus on the domain and path, not the page title. The product page URL used on this site is https://apps.apple.com/us/app/shadowrocket/id932747118. The store may show a different regional page based on your device or account. If the regional path changes, verify the app ID and developer; don’t judge the app’s identity by the region code alone.
The official icon can help identify the app, but it isn’t proof on its own
An icon is useful for quick recognition, but the image can be copied to websites, file covers or promotional materials. Verify it in the context of the product page: check the source first, compare the artwork, then cross-check the developer and app ID. Home screen names can also be changed, so they are not conclusive evidence either.
- Check the full image: Compare the rocket shape and background. Don’t identify the app by the word “Shadowrocket” or a color match alone.
- Check where it appears: An icon on the App Store product page is more useful for verification than the same image in a chat or download description.
- Check the source of each detail: Get the developer name from the product page and the app ID from the actual product link—not from promotional copy.
- Check the download path: Don’t skip the platform selection and installation instructions on this site’s download page just because a file uses the same icon.
If anything doesn’t match, stop
If the developer or app ID on the product page doesn’t match, stop before getting the app and return to this site’s download page to start again. A similar icon does not outweigh mismatched identity details.
Mac, Windows, Android and Linux: verify the site and system architecture
Get desktop and Android versions from this site’s download page. Before opening it, check your browser’s address bar and confirm the domain is shadow-start.com. Seeing the domain in page text, a button label or the path of a different domain does not mean you’re on this site. Installers on the download page are served from the site’s /dl/shadowrocket/ path.
- Mac: Open the Apple menu → About This Mac and check the “Chip” or “Processor” details. Then choose the Apple Silicon or Intel download. This is an architecture choice, not a choice between different app identities.
- Windows: Select Windows on the download page and follow the platform’s download and installation instructions. The mobile App Store link is not a Windows installer.
- Android: Use the Android option on the download page. If an in-app browser interferes with the download, follow the page instructions to continue in your system browser. Don’t infer a file’s source from a forwarded copy.
- Linux: Choose deb, rpm or AppImage according to your distribution and the page instructions. Different package formats mean different installation methods, not a different developer identity.
If a downloaded file won’t run, first check your operating system, processor architecture and package format. Selecting the wrong Mac version (Apple Silicon or Intel), or using a Linux package that doesn’t match your distribution, is an installation compatibility issue. Note the exact system message and compare it with the download page instructions. That’s more reliable than judging the app by whether the file opens immediately.
Connection trouble after installation: separate app identity from routing behavior
“Installed, but webpages won’t load” does not by itself mean the app is not genuine. Once you’ve verified the source, check the configuration: see which server is selected in Home, which profile is selected in Config, and the current Global Routing mode. The comparisons below explain Shadowrocket’s routing behavior; they are not a way to verify app identity.
Config
RecommendedHandle connections according to the rules in the current configuration file. If the configuration is known to be correct, check whether the domain matches the expected policy and how the FINAL rule handles other connections.
Best for: Checking everyday rules and routing with a known, working configuration.
Proxy
Handle connections covered by the client according to the proxy mode. This can help distinguish rule-matching issues from proxy connection issues temporarily, but results still depend on server status and network conditions.
Best for: Briefly troubleshooting a proxy connection, then restoring the previous setting.
Direct
Handle connections in direct mode. A webpage loading does not mean the proxy server is working; a webpage failing to load does not, by itself, indicate a problem with the app’s source.
Best for: Checking direct connectivity as a baseline; don’t treat a direct connection as a proxy test.
Scene in Global Routing is a scene-specific mode; don’t confuse it with Config while troubleshooting. Also check whether Settings → On Demand is enabled with conditions that match your current network. Automatically triggering a connection is a settings behavior, not an identity check. Don’t enable every condition just to test whether the app is genuine.
Assess subscription imports and updates separately. If a subscription you already have times out, fails authentication or returns an empty list, check that the link is valid and review the service and network status. Subscription links contain access credentials. Blur the full URL, password and token in troubleshooting screenshots; you don’t need to share them with anyone to prove the client’s identity.
Genuine App Check: frequently asked questions
The icon matches. Is it safe to install?
An icon alone is not enough. On iPhone and iPad, return to the App Store product page and verify Shadow Launch Technology Limited and id932747118. For other platforms, choose your operating system again on this site’s download page. Don’t treat a forwarded image as a download source.
Can I still use the app ID if it doesn’t appear in App Store search?
Yes. Open the product page from this site’s download page and check for any region, content restriction or account notices. Then follow the prompts to check your Apple Account and device settings. Not appearing in search and having a mismatched product identity are different issues; don’t decide based on missing search results alone.
The page shows a cloud download icon. Should I still verify it?
Yes. Check the developer and app ID on the current product page. The cloud icon is usually related to the current account’s download history; it does not replace the app’s identity details. If the history doesn’t look right, check which account is signed in to the App Store and review its purchase history before trying to get the app again.
It’s already installed, but I can’t remember where I downloaded it. What should I do?
Save any configuration details you need and protect your credentials. On iPhone and iPad, check the App Store download history and product page. On desktop and Android, confirm the platform entry on this site’s download page. Before reinstalling, check how your operating system preserves app data so you don’t lose local configuration by deleting the app.
After verification, keep a record without credentials: the platform used, the product’s app ID or this site’s download entry, and your operating system and architecture. If installation fails, a subscription update fails or routing behaves unexpectedly later, troubleshoot in this order: source → system requirements → configuration → network. Don’t repeatedly use connection results to guess the app’s identity.