Shadowrocket Subscription Setup: 4 Ways to Import Links

Learn how to use Subscribe, Add Server, QR code scanning, and clipboard import, and how to tell subscription URLs from individual server links.

At a glance

If you already have a service provider and subscription details, first identify whether you have a node subscription, an individual server link, or a remote configuration. This guide uses the Home, Config, and Settings screens on iPhone and iPad to explain four ways to add details, how to check what was saved, and what to troubleshoot if something goes wrong. Mac, Windows, Android, and Linux users can look for the same features; button locations vary by platform.

Identify the link type first

“Add subscription” is often used as a catch-all for adding connection details in Shadowrocket, but a node subscription and a rule configuration are different things. Home manages connection entries and node subscriptions; Config manages configuration files; Settings contains app preferences. Pasting a node subscription into the remote configuration field won’t create a usable configuration, even if the URL is reachable.

Get subscription URLs from your service provider. A one-time app purchase does not include a service plan, and installing the app does not create a subscription or connection credentials. This guide only explains how to add details you already have. All examples show formats only; they are not usable connections.

4 ways
to add details: Subscribe, manual entry, QR code, or clipboard
2 types
of remote content to distinguish: node subscriptions and configuration files
1–65535
The valid numeric range for server ports does not mean every port is usable
What you haveHow to identify itWhere to add it
Node subscription URLUsually an HTTPS URL that returns one or more connection entriesHome → + → Type → Subscribe
Remote configuration URLContains configuration sections such as [General] and [Rule]Use the remote configuration option in Config; Subscribe manages updates for the corresponding remote configuration
Individual server linkCommon prefixes include ss://, vmess://, vless://, trojan://, and hysteria2://Import from the clipboard or scan the corresponding QR code
Connection details listed separatelyProtocol, server address, port, and authentication details are listed individuallyHome → + → Add Server form

A URL starting with https:// does not tell you what kind of subscription it is, and the file extension is not a reliable indicator. Check how your provider says to use the URL. If it opens an account sign-in page or an error message, it is not the connection data the app needs.

Method 1: Subscribe

First, distinguish between two uses: Subscribe in Config manages subscriptions to remote configurations and their updates; it does not add a list of nodes to Home. To see nodes from your provider in Home, set Type to Subscribe in Add Server. If you have a complete rule configuration, use the remote configuration feature in Config.

  1. Copy the URL

    Get the node subscription URL from your service provider and copy it in full, including any query parameters after the question mark. Don’t include labels such as “Subscription URL:” or omit any trailing characters.

  2. Choose the type

    Go to Home → + in the top-right corner, open Add Server, and set Type to Subscribe. Don’t leave the default protocol selected and paste the entire subscription URL into the server address field.

  3. Paste and save

    Paste the URL into URL, enter a name you’ll recognize, and save. The name is for local identification only; it does not change the nodes returned by the subscription.

  4. Check for updates

    Return to Home and check that the subscription group and its entries appear. If no entries appear after saving, update the subscription and check the error returned instead of repeatedly adding the same URL.

What Config is for

To add a remote configuration in Config, use a confirmed configuration file URL, then manage updates with the Subscribe option for that remote item. Updating a node subscription and updating a configuration file are separate operations; updating one does not update the other.

For example, https://example.com/sub?token=xxxx is an obviously fake value used to illustrate URL structure. A token in a real URL often grants account access. Don’t upload an unredacted screenshot or post the URL in a public forum. When asking for help, share the error message but redact the URL path, query parameters, and account identifiers.

Method 2: Enter connection details manually

Manual entry in Add Server is useful when your provider gives you connection details separately or when you need to check the fields for a single connection. It creates one connection entry, not a node subscription. If the server address or password changes, you’ll usually need to edit the entry yourself.

  1. Open the form

    Go to Home → + → Add Server. Select the protocol that matches the server under Type, then fill in the remaining fields. Recheck the fields whenever you change Type.

  2. Enter the address

    Enter the domain name or IP in the server address field and the port separately. For example, if your details specify port 443, enter 443. Don’t include https://, a path, or “:443” in the address field.

  3. Check authentication

    For Shadowsocks, check the encryption method and password. For VMess and VLESS, check the UUID and relevant transport settings. For Trojan and Hysteria2, check the password and TLS settings. The fields shown depend on the selected Type.

  4. Save and test

    After saving, return to Home, select the entry, and check connectivity. If it fails, compare each field with the original details, paying particular attention to extra spaces in the password, the domain spelling, and the port number.

Using port 443 does not make different protocols interchangeable. The TLS Server Name, transport-layer Host, and server address may also be different; enter the values provided for your server. Don’t disable certificate verification just to clear an error: that changes connection security and may not fix incorrect settings.

Method 3: Scan a QR code

A QR code is just a way to carry data. It may contain an individual server link, a subscription URL, or an ordinary webpage address. Scanning it won’t turn a webpage into a subscription. Before importing, review the scan result and confirm that its content type and source are what you expect.

  1. Get the original image

    Display the full QR code on another device, or save the original image to the device you’re using. Avoid cropped edges, glare, and heavy compression; the black and white modules should be easy to distinguish.

  2. Open the scanner

    Open the scanner from Home. Allow camera access if you’re scanning with the camera; if you’re scanning from your photo library, select the original image. If you denied system permission, change it in the device’s app permission settings.

  3. Check the result

    Check whether the result is a node or a subscription. If it’s just an account webpage URL, return to your provider’s site and look for a QR code clearly labeled for connection details. Don’t mistake a sign-in page for connection data.

  4. Confirm and save

    After confirming, return to Home and check the entry count and names. If you imported an individual server, check it as a standalone entry; don’t expect it to change automatically with a remote subscription.

A QR code may contain complete authentication details and is as sensitive as the original link. Covering visible text in a screenshot isn’t enough; cover the QR code itself too. If scanning keeps failing, ask for the original text and import it from the clipboard rather than repeatedly copying a low-resolution image.

Method 4: Import from the clipboard

Clipboard import is useful when the details are already on your device. Copy a complete link or connection data the app can recognize, not an entire chat message containing the link. If the system asks for permission to paste, the app can read the clipboard only after you allow it.

  1. Copy only the link

    Select the complete connection text and remove any surrounding quotation marks, bullets, or explanatory text. Don’t manually alter percent-encoding, plus signs, or equals signs in the URL.

  2. Return to the app

    Open Shadowrocket and use the clipboard detection prompt if it appears. If it doesn’t, check whether the add menu offers clipboard import and make sure the system allows pasting.

  3. Confirm the type

    Check the parsed Type, address, and port. If you copied an HTTPS node subscription URL and it wasn’t detected automatically, go to Home → + → Type → Subscribe → URL and paste it manually.

  4. Clear the copied data

    After saving and checking the entry in Home, you can copy ordinary text to replace the clipboard and reduce the chance of pasting credentials somewhere else later.

Choose an import method based on where your details are

Details are on this device
  • You have a complete server link: use clipboard detection.
  • You have a node subscription URL: create a Subscribe entry.
  • You only have a screenshot: use the scanner’s photo library option.
Details are on another device
  • You have a QR code: scan it with the current device’s camera.
  • You only have separate connection details: enter them manually in Add Server.
  • You need ongoing updates: get a node subscription URL instead of importing a single node.

The import method only affects how data enters the app; it does not change the server protocol, account permissions, or service status.

Check routing after import

Seeing an entry only means the data was saved; it doesn’t mean traffic is going through it. First select the node you want to use in Home, then check the connection switch and Global Routing. The first time you create a system network connection, confirm network configuration access when prompted by your device.

Config

Recommended

With a suitable configuration prepared and selected, let rule matches determine the policy. Not all unmatched requests go direct; the final behavior depends on the actual rules, including FINAL.

Use when: You have a rule configuration and need to route traffic by domain or address.

Proxy

Route traffic handled by the app through Proxy for comparison testing and to check node connectivity. Special exclusions in the system or configuration still need to be considered separately.

Use when: You need a short comparison test to distinguish a node issue from a rule-matching issue.

Direct

Connect directly using Direct. If a webpage opens after switching to this option, that alone doesn’t prove the imported node works—the request may not have gone through it.

Use when: You want to check whether the local network can reach a destination directly.

Validate rule files and subscriptions separately. For example, the snippet below describes rule matching; it is not a node subscription and contains no server connection details. Rules are matched from top to bottom, with FINAL at the end as a fallback. PROXY, DIRECT, and REJECT are policy keywords.

[Rule]
DOMAIN-SUFFIX,example.com,PROXY
IP-CIDR,192.168.0.0/16,DIRECT
FINAL,PROXY

A latency test returning a result doesn’t guarantee that webpage requests will succeed. DNS, TLS, the destination site’s status, and rule matches can all affect access. Change one variable at a time: keep the node and destination fixed, then compare routing modes or configurations. Changing the node, DNS, and rules all at once makes it hard to find the cause.

Troubleshoot by failure type

Classifying the problem as “not recognized,” “update failed,” or “imported but won’t connect” makes it easier to find the cause than reinstalling. Keep the original error text. Check the input and response first, then the network and account status. Don’t hide an update failure by repeatedly creating the same subscription.

SymptomCheck firstNext step
No result detected from clipboardPaste permission, whether the text is complete, and whether you copied explanatory text by mistakeFor a node subscription, paste the URL manually into Subscribe
A webpage opens after scanningCheck whether the QR code points to an account or help pageGet the relevant connection details from your service provider
Update returns 401 or 403Authorization details, URL validity, and server-side access restrictionsCheck with your provider; don’t remove token parameters yourself
Update returns 404URL path, whether it was copied in full, and whether the old URL has expiredCopy the current valid URL again; don’t build the path manually
Update times outCan the current network reach the subscription server? Is DNS resolution working?Try again on another working network and note when the error occurs
Import succeeds, but the connection failsSelected entry, Global Routing, account status, port, and authentication fieldsKeep one node selected and check each item to distinguish a connection failure from a routing issue
Download Shadowrocket