How to Import vmess:// and vless:// Links: Single Nodes vs. Subscription URLs

First, know the difference: a share link is a configuration snapshot; a subscription URL is an update source

A single-node share link packages the server address, port, authentication details, and transport settings into one text string. The client parses it and saves a node locally. It reflects the configuration at the time it was exported. If the server later changes its domain, port, or credentials, the saved entry will not update automatically just because you imported the link earlier.

A subscription URL, on the other hand, lets the client retrieve a set of configurations and usually starts with HTTPS. When you update it, the client fetches the response and parses supported formats into nodes. A subscription may contain one node or many. The number of nodes does not define a subscription; the ability to fetch the configuration again is the key difference.

vmess:// format: Base64 encoding is not encryption

A common VMess share-link format consists of vmess:// followed by Base64-encoded JSON. The example below shows the decoded structure; it is not an importable share link or a complete core configuration. Export tools may use different conventions, so use a compatible link generated by your provider whenever possible.

{
  "v": "2",
  "ps": "Example node",
  "add": "node.example.com",
  "port": "443",
  "id": "7d9d2f80-52a1-4c8e-9c76-5c0d52dd7441",
  "aid": "0",
  "scy": "auto",
  "net": "ws",
  "type": "none",
  "host": "node.example.com",
  "path": "/proxy",
  "tls": "tls",
  "sni": "node.example.com"
}

• v: The 2 here is a version marker used in a common share-link format—not the client version or a declaration of the VMess protocol version.
• add, port, and id: These specify the server address, server port, and user ID, respectively. All three must match the server configuration.
• net, host, and path: This example uses WebSocket. The Host and path are part of the transport settings and must not be removed or changed arbitrarily.
• tls and sni: These describe TLS and the server name. WebSocket Host and TLS SNI are separate fields. Even if their values match, they are not interchangeable.
• aid: The example uses 0, a common value for modern VMess AEAD. Don’t follow outdated guides and increase it arbitrarily.

vless:// format: query parameters are part of the configuration

VLESS share links typically use a URI format: the user ID comes before @, followed by the server, port, query parameters, and a node label. The link below illustrates the fields only. The domain and credentials are examples, so it cannot be used to connect.

vless://[email protected]:443?encryption=none&security=tls&type=ws&host=node.example.com&path=%2Fproxy&sni=node.example.com#Example-WS

encryption=none does not mean the entire connection lacks transport protection. It describes this VLESS setting; the example separately specifies security=tls. type=ws means WebSocket, and path=%2Fproxy decodes to /proxy. The label after the hash, Example-WS, is just a remark and does not determine the server address.

• Keep every query parameter when copying the link, especially security, type, sni, and the transport path.
• Don’t treat & displayed by a chat app as a valid parameter separator. The raw URI should use a regular &.
• If you see flow or REALITY-related parameters, preserve the provider’s original values. Don’t apply the WebSocket example in this guide.
• A correctly formatted UUID only looks like a valid UUID. It does not prove that the credentials work or that the server is reachable.

Import from clipboard: desktop and Android instructions

Before importing, copy the entire link on a single line. Don’t include explanatory text, quotation marks, or ellipses from a chat message. Interface labels may vary by version; the steps below refer to common Chinese-language interfaces. If the wording differs, look for the equivalent command that mentions the clipboard and importing.

1. v2rayN desktop: Copy the link, return to the main window, then choose “Servers” → “Import bulk URLs from clipboard.” Some versions show “Import from clipboard” instead; you can also use Ctrl+V if supported. Check the import count and confirm the new entry appears in the list.
2. v2rayNG for Android: Copy the link, then tap “+” in the top-right corner of the main screen → “Import from clipboard.” If Android asks for clipboard access, verify the source and allow access for this operation.
3. Check the node settings: Open the new entry for editing and review the server, port, transport, and TLS settings. Verify the parameters before testing the connection; a successful import does not mean the connection works.
4. Start the proxy: Select a node and start it. In v2rayN, configure the system proxy or another traffic-routing mode for your use case. The first time you start v2rayNG, you’ll usually need to approve Android’s VPN permission prompt.

VMess and VLESS are protocol names; v2rayN and v2rayNG are client names. They are not interchangeable. v2rayNG uses the Xray core, while v2flyNG uses the v2fly core. Similar client names do not guarantee support for the same protocol and transport combinations. Check that the required server features are supported by the core you’re using.

Add a subscription: save the URL, then update it

Subscription management usually involves two steps: save the source and fetch its contents. If you save a subscription URL but don’t update it, the group may remain empty. Subscription links often contain tokens, and the query string is part of the authentication details. Don’t remove everything after the question mark to “clean up” the URL.

1. v2rayN: Go to “Subscription groups” → “Subscription group settings,” add a group, enter a name and the subscription URL, then save. Return to “Subscription groups” and choose the appropriate update command. Whether to fetch through the proxy depends on your current network.
2. v2rayNG: Open “Subscription group settings” from the top-right menu, add a subscription, and save it. Then return to the main screen and select “Update subscription.” Menu locations may change between versions; the important distinction is between editing a subscription and actually updating it.
3. Check the result: Review the update status, group, and number of added nodes. A URL opening in a browser does not guarantee that its response is a subscription format your client can parse.
4. Keep updates organized: Create separate groups for different sources. Back up important manual configurations before updating, and don’t assume that local changes such as renaming a node or changing its port will survive the next update.

Using multiple devices: sharing a subscription does not sync every setting

You can add the same subscription URL on each device allowed by your provider’s terms, but each client saves and updates it independently. Updating on Windows does not trigger an update on Android. Routing rules, system proxy settings, per-app proxy settings, and the currently selected node are not automatically matched just because both clients use the same subscription.

To send a temporary node to another device, share that node’s link or QR code instead of exposing the entire subscription. A QR code is just another way to encode text: import a single-node link as a node, or follow the subscription-management steps if it contains a subscription URL.

Troubleshooting: distinguish parsing errors from network failures

The decision process is simple: first identify whether you have a node link or a subscription, then confirm the import or update succeeded, and finally check the connection and traffic routing. Keeping these steps separate prevents mistakes like changing protocols to fix a copying issue or repeatedly importing a node when the system proxy is simply off.