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

1. Single-node links vs. subscription URLs: the difference is how they update

A single-node share link contains one server configuration, usually including the address, port, user ID, and transport settings. After import, the client saves that configuration as it was at the time. If the provider later changes the port or certificate domain, the standalone node won’t update automatically. You can import multiple nodes by copying several share links at once, but that doesn’t create a subscription.

HTTPS is a transport protocol for a URL; it doesn’t mean the URL is a subscription. Account dashboards, login pages, and setup guides can also use HTTPS. Copy the URL the provider labels as a “subscription URL,” not the dashboard address in your browser. A subscription response may contain a Base64-encoded list of share links or use another format. Whether the client can read it depends on the formats it supports.

2. Understanding vmess:// and vless:// link parameters

A common VMess share link starts with vmess:// followed by a Base64-encoded JSON object. Encoding is not encryption; after decoding, you’ll typically see fields such as add, port, id, net, and tls. The example below shows the decoded structure. Don’t import this JSON directly as a vmess:// share link or use it as a complete core configuration.

{
  "v": "2",
  "ps": "VMess-WS-TLS example",
  "add": "node.example.com",
  "port": "443",
  "id": "d34db33f-1234-4abc-8def-0123456789ab",
  "aid": "0",
  "scy": "auto",
  "net": "ws",
  "type": "none",
  "host": "edge.example.com",
  "path": "/ws",
  "tls": "tls",
  "sni": "edge.example.com"
}

Here, add is the server address, host is the Host header used by the WebSocket request, and sni is the server name used during the TLS handshake. These values can differ, but must match the server setup. aid is the VMess alterId field, not a port. The example’s 0 is a common value in modern configurations; don’t change provider-supplied settings based on guesswork.

VLESS share links usually include their parameters directly in the URI. The example below shows a TCP connection with TLS only; the domain and UUID are illustrative and don’t provide a working service.

vless://[email protected]:443?encryption=none&security=tls&type=tcp&sni=edge.example.com#VLESS-TLS

• encryption=none refers to encryption at the VLESS protocol level. The example still uses TLS through security=tls, so it does have transport-layer protection.
• type=tcp specifies the transport type. Changing it to ws on your own won’t make the server support WebSocket.
• Text after # is usually the node name. It may be URL-encoded, with spaces often written as %20. Keep the entire query string when copying the link.
• Links using REALITY may also include parameters such as pbk, sid, and fp. Import the full link and make sure your client and core support the required features.

3. Import nodes into v2rayNG from the clipboard or a QR code

To use v2rayNG on Android, copy the complete link first, then return to the main screen. The steps below use common labels from the Chinese interface; menu wording can vary by version. Look for options such as “Import from clipboard” or “Scan QR code.”

1. Copy the link: Copy everything from vmess:// or vless:// to the end. Leave out quotation marks, explanatory text, and Markdown fences from chat messages. A long link wrapping on screen is fine, but actual spaces or line breaks inserted into a link can break it.
2. Import from clipboard: On the v2rayNG main screen, tap “＋” in the upper-right corner → “Import from clipboard.” Allow clipboard access if prompted, then check that the new node appears in the list. When importing multiple standalone links, they’re usually arranged one per line.
3. Check the configuration: Open the node editor and compare the address, port, user ID, transport, and TLS settings. Verify them first; don’t change values at random just to make a test pass.
4. Scan a QR code: Tap “＋” → “Scan QR code,” grant camera access, and scan the complete code displayed on another screen. Keep the full code and its quiet zone in view, avoid glare, and fit the entire pattern inside the camera frame.
5. Connect and test: Select the new node and tap the connect button on the main screen. Approve Android’s VPN connection request the first time, then open a known-working HTTPS page.

A QR code is just another way to represent text; it doesn’t determine what that text contains. Scanning a vless:// link will usually add a node. If the code contains an HTTPS URL, check whether it’s a subscription or an ordinary web page—“scan successful” doesn’t mean a usable node was added. If the QR code is on the same phone, use the provider’s copy-link option when possible. If the scanner can read images, you can also select one from your gallery.

The server port and local listening port refer to different things. In a share link, :443 is the remote server port. The local SOCKS port is for apps on your device. Don’t change the link’s port to 10808, or assume a node is invalid because your local port isn’t 10808.

4. Import into v2rayN and check both clients’ settings

In the desktop version of v2rayN, open the “Server” menu and select “Import bulk URLs from clipboard.” The common shortcut is Ctrl+V. Make sure the main window is focused before importing; if the cursor is in an edit field, the shortcut may paste text there instead. After import, select the node you want from the server list and set it as the active server.

A successful import only means the client recognized the configuration. In v2rayN, starting the core without setting the system proxy may leave a browser that relies on the system proxy outside the node. Some apps don’t use the system proxy and need to be configured separately. In v2rayNG, apps excluded by per-app proxy settings won’t use the proxy as expected. Before testing, check which route the target app uses.

5. Save the subscription URL before updating

A subscription connects a URL to a group of nodes. Pasting an HTTPS subscription URL into the single-node import option may result in an “unrecognized” message, though some versions may route it to subscription handling. To make it easier to verify, add subscriptions through the subscription settings instead.

1. v2rayNG: Open “Subscription group settings” in the side menu, tap Add, and enter an easy-to-recognize name and the subscription URL provided by your service. Save it, return to the main screen, and select “Update subscription” from the upper-right menu. If you have multiple groups, check whether you’re updating the current group or all groups.
2. v2rayN: Open “Subscription groups” → “Subscription group settings,” add a group, and enter the subscription URL. Save your changes, return to the “Subscription groups” menu, and choose the appropriate update option.
3. Choose how to update: Common v2rayN menus offer “Direct” and “Through proxy” options. Try a direct connection first if the subscription URL is accessible that way. If it times out and you already have a working node, try updating through the proxy. In v2rayNG, use whichever update options your current version provides.
4. Check the result: Review the update message, node count, and group. Then check whether the active node still works. If the provider removed or replaced a node, you may need to select a different one.

When an update fails, start by identifying the error. A timeout usually means the request didn’t finish in time. For HTTP 401 or 403 errors, check the token, account permissions, or access restrictions. If the response is a login page, make sure you copied the subscription endpoint, not the dashboard URL. Don’t keep retrying; first check whether the provider limits request frequency.

6. Common import errors and connection problems

7. What to check after importing

Don’t change DNS, routing, transport, and ports all at once. Tackle one issue at a time to tell whether the link is corrupted, the subscription failed to load, or the node imported but traffic isn’t going through the proxy. Follow the steps below; it’s usually easier to find the cause than by repeatedly deleting and reinstalling the client.

• Check the source first: Make sure you have the complete share link or a genuine subscription URL—not just a web page title.
• Check the contents: Verify the address, port, user ID, transport, and security settings. Keep the values supplied by the provider.
• Check that it’s running: Confirm the active node, core status, and system proxy or Android VPN status.
• Check a request last: Open an HTTPS page and review the relevant logs. A working node doesn’t mean every domain uses the same outbound route; check routing and DNS separately if needed.