Shadowrocket Subscription Import: Subscribe, Add Server, QR Codes & Clipboard

Learn where to find Subscribe, Add Server, QR code scanning, and clipboard import, and how Shadowrocket recognizes common link formats.

At a glance

The right way to import into Shadowrocket depends on what you have: a node subscription, a single protocol link, a QR code, or a remote configuration file. This guide assumes you already have a service and subscription. It explains the difference between Subscribe and Config, how to fill in Add Server, how to check QR code and clipboard imports, and how to verify imports and troubleshoot common issues.

Identify the subscription URL, protocol link, or config file

Before importing, check whether you have a URL that returns a set of connection details or a link that describes a single connection. Subscription URLs usually start with https://; the app retrieves the content by requesting that address. A single protocol link often starts with a protocol identifier such as ss://, vmess://, or trojan://. The file extension alone does not identify the format: a URL without a .conf suffix may still return a configuration file.

Type of dataHow to identify itWhere to import it
Node subscriptionUsually an HTTPS URL with authentication parameters that returns multiple connection entries.Use the subscription import option in Home and set Type to Subscribe.
Single connectionStarts with a protocol identifier and includes a server, port, and authentication details.Import by scanning a QR code or using the clipboard, or enter the details manually in Add Server.
Remote configurationThe content may include sections such as [General] and [Rule].Manage remote configurations in Config, then check which one is enabled after downloading.
Web page URLOpens to a login page, help page, or other HTML content.It cannot be used as a subscription directly. Ask your existing service provider for the correct import URL.

This guide covers three areas: Home, Config, and Settings. Home manages connections and the selected connection; Config manages configuration files; Settings controls app behavior. Button placement may vary by platform and window layout. The steps below use the common English labels on mobile; on desktop, look for the same functions rather than matching screen positions exactly.

4 methods
Import options: Subscribe, Add Server, QR code, and clipboard
3 areas
Find them in: Home / Config / Settings
2 ways to get the app
iPhone / iPad: $2.99 one-time purchase; Mac / Windows / Android / Linux: free

Subscribe vs. Config: use the right import path

When looking for “Subscribe” in Config, first identify what you are importing. Subscribe or remote URL options in Config are for managing configuration files; they are not a place to enter every node subscription. A common path for a node subscription is Home → “+” in the top-right corner (Add Server) → Type → Subscribe. Both may use an HTTPS URL, but they import different things: Config imports a configuration file, while Subscribe imports a list of selectable connections.

  1. Check the URL

    Copy the complete subscription URL from your service management page. Make sure you have not included surrounding instructions, spaces, or line breaks, and keep all parameters after the question mark.

  2. Open the import option

    Go to Home, tap “+” in the top-right corner to open Add Server, then select Subscribe under Type. Don’t paste the full subscription URL while a regular single-server protocol type is selected.

  3. Enter the URL

    Paste the complete URL into URL, add a label you’ll recognize, and save. Don’t split the token out as a separate password or enter the HTTPS URL in the server hostname field.

  4. Refresh the list

    Return to Home and check whether the subscription group appears. If the content was not fetched automatically, use the subscription’s update option. In lists that support pull-to-refresh, pull down to start an update, then check any error message and the number of entries.

  5. Verify the results

    Expand the group and check that at least one connection’s protocol, server, and port match the information you have. Saving a subscription name does not mean the connection list was retrieved successfully.

If you have a remote .conf file, go to Config and use the option for adding a remote URL to retrieve it. Then check which configuration is currently enabled. The file may define routing and DNS behavior, so a successful download does not mean every setting is suitable for your network. Check subscription updates and configuration file updates separately: the former refreshes connection details, while the latter refreshes configuration content.

Add Server: enter a single connection manually

If your details are provided as separate fields such as server address, port, password, or UUID, use Home → “+” → Add Server to check them one by one. Select Type first, then enter the fields, because authentication and transport settings vary by protocol. Avoid filling everything in and then switching protocols at random: old fields may remain, or required fields may change without being noticed.

For example, if the server details specify port 8443, enter 8443; don’t change it to 443 just because TLS is enabled. The server field usually takes a hostname or IP address, not a web URL beginning with https://. Enter the path in the appropriate transport setting. Checking each field before saving is usually easier than finding mistakes by toggling settings afterward.

Choose an import method based on the details you have

You have details for one connection
  • In Add Server, select the correct Type.
  • Enter the server, port, and authentication details field by field.
  • If the server settings change, update the local settings manually.
You have an updateable subscription
  • Use Subscribe to save the original subscription URL.
  • After updating, check whether the connections in the group have changed.
  • Back up separately first if you need to keep local changes.

These methods differ in how connection details are organized and maintained; they do not imply any fixed difference in connection speed or service quality.

Importing a QR code: check what it contains first

A QR code encodes text. It might contain a protocol link, a subscription URL, or just a regular web page. Go to Home and tap the QR code icon at the top to open the scanner. If prompted, grant camera access. Review the detected type and fields before saving; recognizing a QR code does not guarantee that its connection details are valid.

  1. Display the QR code you already have on another screen. Keep the full code visible and avoid glare, obstruction, or excessive zoom.
  2. Open the QR code scanner in Shadowrocket and point it at the code. If the screen offers an option to import an image from your photo library, use the original image rather than a repeatedly compressed chat thumbnail.
  3. Check the result. A single protocol link should import one connection; a subscription URL should be handled as a subscription; a regular login page cannot be turned directly into a connection.
  4. After saving, return to Home, check for the new entry or group, and then run a connectivity test.

If the camera view is blank, check Shadowrocket’s camera permission in system settings. If the camera can see the code but never recognizes it, make sure the image is complete and its text uses a format the app supports. QR code screenshots may contain passwords or tokens; don’t post the original image in a public discussion when reporting an issue.

Clipboard import: keep the full link and its original encoding

For text already on your device, importing from the clipboard is usually quicker than scanning again. Copy only the link, then return to Home and follow the import prompt that appears when the app recognizes it. If needed, look for a clipboard import option in the add menu. If the system asks whether to allow pasting, the app can read that content only after you allow it. If no import prompt appears, paste the HTTPS subscription URL manually into the URL field with Type set to Subscribe.

Subscription URL format example:
https://example.com/sub?token=xxxx

Common prefixes for single-connection links:
ss://
vmess://
vless://
trojan://

These prefixes identify the type of content; they are not complete, usable connections. Links may contain percent-encoding, Base64 text, and a label after #. Manually “cleaning up” these characters can change the meaning. Don’t mistake an ellipsis shown by a messaging app for part of the original text, and don’t copy an entire message containing instructions such as “tap to import.”

After import: check the selected connection and Global Routing separately

Importing saves connection details; it does not establish a connection. First select the imported connection in Home and run a latency or connectivity test, then turn on the connection. When creating a system VPN configuration for the first time, follow the system prompt to authorize it. A successful latency test only confirms that the specific test worked; it does not guarantee that DNS, TLS, UDP, or every website will work.

Then check Home → Global Routing. Proxy, Direct, Config, and Scene are different routing modes, not four types of protocol. To isolate the source of an issue, you can temporarily compare routing behavior, but restore your original settings when finished.

Config

Recommended

Routing follows the rules in the current configuration. Whether traffic connects directly depends on the matching rule and final policy; unmatched traffic does not necessarily go direct.

Use when: You have checked the configuration and need rule-based routing.

Proxy

Set the routing mode to Proxy to check whether rule selection is preventing the target traffic from using the proxy as expected.

Use when: Briefly comparing the selected connection with the routing rules.

Direct

Uses a direct connection. If a website works in this mode, that does not prove the newly imported proxy connection is working.

Use when: Checking reachability on your local network for comparison.

Scene

Routing behavior follows the configured scene conditions. Check the scene’s contents to see which settings are actually in effect.

Use when: You have set up and checked scene conditions for switching between networks.

If a site works in Proxy but not in Config, check DOMAIN-SUFFIX, IP-CIDR, GEOIP, and FINAL in the active configuration. Rules are generally matched from top to bottom; traffic follows the policy for the first match, while FINAL determines the handling of traffic that did not match earlier rules. Reimporting a subscription repeatedly will not fix a rule issue.

Troubleshooting import failures: check the result, then the network and format

Keep the exact error message and note whether the failure occurred while saving the URL, fetching content, parsing content, or testing the connection. Each stage points to a different issue. A subscription URL opening in a browser only means the browser received a response; if that response is a login page, Shadowrocket still cannot parse it as a subscription.

What you seeCheck firstNext step
Request timed outWhether the current network can reach the subscription host and whether DNS is working.Compare Wi-Fi and mobile data without changing connection settings at the same time.
HTTP 401 / 403Token, access permissions, and server restrictions.Check the URL and authorization in your existing service management page; a status code alone does not prove the subscription has expired.
HTTP 404Whether the path is complete and the URL has changed.Copy the actual subscription URL again; don’t guess the path.
Certificate errorSystem date and time, and the server name.Correct the system time first, then check the remote certificate. Don’t hide the cause by disabling verification.
Update succeeds, but no entries appearAn empty response, an incompatible format, or the wrong import option.Confirm that the response is a node subscription, not a configuration file or web page.
Entries appear, but connections failProtocol, port, authentication, TLS, and service status.Check the individual connection fields; there’s no need to delete the entire subscription group first.

A subscription update may replace entries managed by that subscription. Whether local name or parameter changes are preserved depends on how they are managed. Back up first if you need to retain separate settings. When sharing screenshots for troubleshooting, hide sensitive server details, passwords, UUIDs, and tokens. Include only the import screen, error text, and protocol type needed to diagnose the issue without exposing full credentials.

Download Shadowrocket