Shadowrocket for MacAll-platform access and rule configuration
Rule-based proxy client for all platforms with rule-based routing using your existing configuration. iPhone / iPad: $2.99 one-time through the App Store; Mac, Windows, Android, and Linux versions are free.
iPhone / iPad $2.99 one-time·Free on other platforms
Config / Proxy / DirectDOMAIN-SUFFIX → PROXYFINAL → DIRECTTwo ways to get the app
Two ways to get the app
Choose Shadowrocket for your device
iPhone / iPad: $2.99 one-time through the App Store; Mac (Apple Silicon / Intel), Windows, Android, and Linux versions are free. Get desktop and Android installers from this site's download page.
iPhone / iPad
$2.99 one-time through the App Store; Mac, Windows, Android, and Linux versions are free. iPhone and iPad can use the same purchase record. Check the App Store page for system requirements.
Check the product page in the store, then confirm which account made the purchase. After installation, prepare your own subscription or server details and import them from Home.
Free · Apple Silicon / Intel. iPhone / iPad: $2.99 one-time through the App Store; Windows, Android, and Linux versions are also free.
Check the chip information in About This Mac, then choose the matching dmg. If you see a warning that the developer cannot be verified on first launch, confirm the source, then go to Privacy & Security and select Open Anyway. See the installation approval guide for full steps.
Free. Mac, Android, and Linux versions are also free; iPhone / iPad: $2.99 one-time through the App Store.
Use the 64-bit installer. If SmartScreen appears, first confirm the file came from this site's download page, then select More info → Run anyway. Follow administrator policies on managed devices.
Free. Mac, Windows, and Linux versions are also free; iPhone / iPad: $2.99 one-time through the App Store.
The download page provides an arm64 installer. If Android requests permission, allow the browser or file manager currently in use to install unknown apps; you can turn this permission off after installation. System VPN permission is also required before connecting.
Free · deb / rpm / AppImage. Mac, Windows, and Android versions are also free; iPhone / iPad: $2.99 one-time through the App Store.
Choose a format based on your distribution and package manager rather than installing formats one after another. AppImage needs execute permission before first launch; handle deb and rpm with the corresponding package manager. See the download page for commands.
After getting the client, keep your existing configuration before importing anything. Server address, port, protocol type, and authentication details are a set of related parameters; copying only the address leaves out essential fields. When changing devices, check both local connection permissions and the configuration in use. A purchase record or configuration file alone does not establish a connection.
Desktop and Android installers are distributed through this site's /dl/shadowrocket/ path. The download page reads the current manifest and provides the matching format. Before updating, back up Config and custom rules. If the system blocks installation, verify the download source first, then follow the platform-specific approval steps rather than disabling system protection.
Check Global Routing first, then review Config and server parameters. The snippets below explain configuration syntax only; example.com is a sample domain, not working service information.
Home / Global Routing / Config
Global Routing determines how connections are handled: Config mode routes traffic according to the Rule entries in the active configuration; Proxy mode sends applicable connections through the current proxy; Direct mode connects directly. For domain-specific policies, choose Config and confirm the intended configuration is enabled. During troubleshooting, you can switch modes temporarily for comparison, but note the original setting and restore it after testing. The snippet below applies only when the relevant rules match; changing modes does not fix server parameters.
Rule entries are checked in order, and the first match determines the policy for a connection. Put specific domains near the top and broad network ranges and FINAL later. When editing, understand the scope differences between DOMAIN, DOMAIN-SUFFIX, and DOMAIN-KEYWORD, then confirm the policy name is valid. Use IP-CIDR to specify a range when local network addresses should connect directly. Add or move one rule at a time, then repeat the target request to check the result. Reused connections can otherwise make test results misleading.
On Demand triggers connections based on conditions such as the network, and is best configured after you have a stable setup. Check On Demand in Settings, configure Wi-Fi, cellular, or domain conditions as needed, and review the order of multiple conditions. Automatic connection does not select a working server or replace Config rule evaluation. To test, switch to the target network, observe whether a connection is triggered, then check which rule matches the request. The snippet below shows Rule entries used after a connection is established; it is not On Demand condition syntax.
[Rule]
DOMAIN,example.com,PROXY
FINAL,DIRECT
Home / Add Server / Subscribe
Subscribe imports and updates a server list you already have. Get your subscription details from your own provider, select the appropriate type under Add Server, paste the details, save, and update. Seeing entries in the list only means the content was parsed; you still need to select a server and test the connection. If an update fails, check that the link is complete, the network can reach it, and the response format is valid. Avoid deleting existing working entries and recreating them repeatedly. Subscription links may contain private credentials, so redact them before sharing screenshots or diagnostics. The snippet below shows domain-rule syntax only.
Config manages request-handling settings and serves a different purpose from the server list. After importing a file, confirm which configuration is selected, then review General and Rule. Do not assume a file being edited is already active. Save a copy before changing DNS or rule order so you can return to the last working state. On devices and setups that support iCloud sync, also check sync status and the selection on each device. A synced file does not ensure that the connection switch, system permission, and server selection are all consistent. The snippet below is a basic General section.
[General]
bypass-system = true
dns-server = system
Settings / Diagnostics · Home / Connectivity Test
Diagnostics helps narrow down the cause of a problem; Connectivity Test provides a reference for connectivity under current conditions. First confirm the device itself can access the internet, then test the selected server, and finally reproduce the issue in the specific app or domain. A latency reading is not the same as download speed, and one failed test alone does not prove that a protocol is unsupported. Check changes in Data upload and download readings to see whether requests are being made, but increasing totals do not mean a request succeeded. When preparing logs, note the network type and reproduction steps, and redact addresses, passwords, and subscription links.
[Rule]
DOMAIN,example.com,DIRECT
FINAL,DIRECT
Distinguish the server list from Config
The server list answers “which server handles the connection?” Config answers “which policy applies to each request?” After importing a subscription, check Global Routing; after importing a rules file, confirm the selected server as well. Missing either part can leave a populated list unable to connect, or an active connection routing traffic differently than expected. For first use, verify one existing server connection before adding rules and automatic triggers.
Match the protocol to your existing details
Shadowrocket supports scenarios using protocols such as Shadowsocks, VMess, VLESS, Trojan, HTTP, SOCKS5, WireGuard, and Hysteria2. Protocol names are not speed settings; switching Type at random is not a reliable way to fix a connection. Check Host, Port, authentication fields, and related transport parameters against your own server details. For configurations that use TLS, also check the server name and system time. Fields vary by protocol, and leaving them blank or copying values from another type can cause a handshake to fail.
Narrow rule checks to one target
When checking rules, choose a problem domain you can reproduce consistently and decide whether it should use PROXY or DIRECT. Then scan from the top of Rule and find the first matching entry instead of looking only at FINAL. DOMAIN-SUFFIX covers the domain and its subdomains; DOMAIN-KEYWORD can have a broader scope. If multiple conditions match the same target, adjust their order or narrow their scope. Sample private network ranges also need to reflect your own LAN; they are not a complete configuration for every network.
What Data and test results indicate
Data readings help show whether data is being sent or received during a connection and how traffic changes across different statistics. They do not replace the target service's response or directly correspond to billing data from a provider. If Connectivity Test returns a result but a page still will not load, continue checking DNS, rule matches, and the specific request. If only one app has an issue, first rule out its cache, connection reuse, or local network permissions. Changing one variable at a time makes the cause easier to identify than switching servers, protocols, and rules all at once.
Separate routine setup from troubleshooting
Configure On Demand and sync after the connection is stable to reduce variables during initial setup. When a problem occurs, record the current Global Routing mode, Config filename, server type, and network, then compare against the most recent working state. If changing networks resolves it, investigate the original network conditions first. If the same configuration fails on several networks, check the server parameters. When sharing diagnostic details, include the action sequence and symptoms, but never provide full passwords, authentication data, or subscription links containing private information.
iPhone / iPad: $2.99 one-time through the App Store; Mac, Windows, Android, and Linux versions are free. The client manages subscriptions or server details you already have. This site does not provide, sell, or recommend servers or subscriptions.
Product page verification
Developer, official icon, and app ID
On the iPhone / iPad App Store product page, check the developer, Shadow Launch Technology Limited, the official icon, and app ID 932747118. A similar name is not a substitute for these details. The app ID in the store link should match the product page. Use the official icon shown in this site's header and in the store; do not complete a purchase based only on the word “Shadowrocket” in search results.
Shadowrocket is a closed-source commercial application. Get it according to platform: use the specified App Store product page for iPhone / iPad, and use installers from this site's download page for desktop and Android. If a downloaded file has an unclear source, return to the relevant download page to verify it rather than relying on the filename.
Store and account
Check your account region and system requirements
If the app is not available in the mainland China App Store storefront, check the region of the account currently used for Media & Purchases instead of repeatedly changing search terms. Account region and device language are separate settings; changing the language does not switch storefronts. To change a region, follow Apple's prompts in the account's Country/Region settings, including any requirements related to balance, existing subscriptions, and payment information.
Check the App Store page for iPhone / iPad system requirements. Before purchasing, confirm that your device meets them and review the currency and price shown on the product page. The US storefront lists a $2.99 one-time purchase; other storefronts show local currency. Mac, Windows, Android, and Linux versions are free. The account holder should manage account changes.
Purchase record
Use the same purchase record on iPhone and iPad
Using the account that made the purchase, you can download the app again from Purchased on iPhone or iPad. After changing devices or reinstalling, first confirm the account signed in to Media & Purchases, then check the purchase history. If the product page still shows a price, do not pay again immediately. First verify the account, storefront region, and order history for the same app.
Restoring the app and restoring configuration are separate tasks. A purchase record lets you download the client again; whether existing server details, custom Rule entries, and Config are retained depends on the old device's backup and actual sync settings. Keep a working configuration before changing devices. On the new device, check the selected file, connection permissions, and server status before use.
Scope of use
Getting the client and connectivity services are separate
The one-time iPhone / iPad payment covers the client, not servers, subscription content, or connectivity services. Mac, Windows, Android, and Linux versions are free and also require server details or a subscription that you already have. Check subscription validity, available entries, and authentication status with your own provider; buying the client again will not fix them.
A successful import means the app received and parsed the information; it does not mean the remote server is currently reachable. If the list is empty, check the subscription response. If entries are present but a test fails, check the network, port, and protocol. If the test succeeds but some destinations do not, continue with Config and DNS. Troubleshooting by symptom helps avoid attributing unrelated issues to purchase status.
Update methods
Updating the client does not update subscriptions
Update the iPhone / iPad app through the App Store; get current Mac, Windows, Android, and Linux installers from this site's download page. Before updating the client, keep a copy of your configuration and custom rules. If the system blocks installation, follow the download page's installation approval steps. After reinstalling, confirm the selected item and system connection permissions.
Subscribe updates your existing server list, Config updates request-handling rules, and an app update changes the client itself. These are separate operations, not one general “update.” If a connection problem starts after a change, note which layer changed and compare by restoring only that content. Do not reset all settings at once.
Continue reading
Open the guide for your specific question
If you have not installed the client, start with the all-platform download guide. If it is installed but you have not imported details, follow the setup guide for Add Server and Subscribe. If only a specific destination has a problem, start by checking Global Routing and Rule. For protocol settings, read the field explanations in the protocol reference rather than changing Type at random.
Installation blocks, store searches, restoring purchases, and connection failures require different steps. The official manual documents each process so you can preserve working settings and verify issues one by one. If you need to share configuration while troubleshooting, include only the smallest rule snippet needed to reproduce the problem and replace private addresses with sample domains.
Subscription updates and connection troubleshooting
Each guide explains prerequisites, steps, and expected results for a specific task. Record the current state first, then follow the checks in order to avoid changing multiple settings at once.
Learn the difference between refreshing manually, updating automatically when opening the app, and scheduled updates. If an existing subscription will not refresh, check link completeness, network access, and whether the content can be parsed, keeping the current list before making changes.
Learn what upload and download readings mean, how statistics by server and app differ, and when to reset them. Separate traffic observed by the client from remote usage records instead of treating a change in numbers alone as proof of a connection or billing problem.
Check the local network first, then latency test results, protocol settings and port, and finally the system time. Record each result and follow the same sequence to distinguish an unreachable network, authentication failure, and an issue with the target request.