· Getting Started · 8 min read

vmess:// and vless:// Links Explained: How to Import a Single Node or Subscription

Learn how vmess:// and vless:// links are structured, how single-node links differ from subscriptions, and how to import each via clipboard or subscription in v2rayN and v2rayNG.

At a glance

When you receive a link, first check whether it’s a single configuration you can import directly or a subscription URL you need to save and refresh. After importing, check the list and group, then test the connection. This makes it easier to tell whether the link wasn’t read, the subscription failed to load, or the node itself can’t connect.

Single nodes vs. subscription URLs

A share link beginning with vmess:// or vless:// contains a single node configuration. The client parses the link and saves the configuration to its local list. If the sender later changes the server address or port, your link won’t change with it; you’ll need to get the updated link and import it again.

Subscription URLs usually begin with https://. The client must request the URL to retrieve the current node list. Login and help pages can also begin with https://, so the prefix alone isn’t enough to identify a subscription. Copy the link the provider explicitly labels as a subscription URL, not the page address in your browser’s address bar.

Subscription URLNetwork requestResponse parsingGroup updatedNode list

VMess and VLESS share link fields

A common VMess share-link format Base64-encodes a JSON object and places it after vmess://. Base64 is an encoding, not encryption. A common VLESS share link puts the UUID, server, and port directly in the URL, with readable query parameters. You can check the fields in the client’s node editor for either format; there’s no need to decode the original link elsewhere.

36
Character count for a standard hyphenated UUID
443
Remote port in the example
0
alterId in common VMess AEAD configurations

VMess: decoded JSON fields

ps
Node label, such as “Example”
add / port
Server address and remote port, such as node.example.invalid and 443
id / aid
User UUID and alterId; for common AEAD configs, alterId is 0
net / path
Transport type and path, such as ws and /ws
tls / sni
Whether TLS is enabled and, if explicitly set, the TLS server name

You can rename the label; the address, port, and transport settings must match the server configuration.

VLESS: address and query parameters

Left of @
User UUID; an all-zero value is used below to show its position
Right of @ and before ?
Server and remote port, such as node.example.invalid:443
type / path
Transport type and path, such as ws and URL-encoded %2Fws
security / sni
Connection security type and server name; this example uses TLS
After #
Node label, not part of the connection path

In this example, encryption=none does not disable TLS; TLS is specified by security=tls.

Here’s a VLESS link for illustration only. The example domain won’t resolve, and 443 is not a fixed port for every node or a local listening port to enter in your system proxy settings.

vless://[email protected]:443?encryption=none&type=ws&security=tls&sni=node.example.invalid&path=%2Fws#demo

When checking a WebSocket node, make sure you distinguish the connection address, TLS server name, and WebSocket request Host. These can be the same or different. The connection address determines where to connect; the server name is used for the TLS handshake and certificate validation; and the request Host is an HTTP header. Don’t assume they should all match just because they look like domain names in the editor.

Import a single node from the clipboard in v2rayN or v2rayNG

Copy the entire line, including its vmess:// or vless:// prefix. Line wrapping in chat apps usually doesn’t affect copying, but actual line breaks, quotation marks, list numbers, or trailing punctuation can prevent the client from reading it. Don’t decode the link manually and paste the decoded text into the share-link import option.

  1. v2rayN (desktop): Switch to the main window and use the clipboard import command in the “Servers” menu. In many 7.x versions, it’s called “Import batch URLs from clipboard”; use it for a single link too. After importing, find the new entry by its label, open it to check the protocol, server, and port, then select it and test the connection.
  2. v2rayNG (Android): In the configuration list, tap the “+” in the upper-right corner and select “Import config from clipboard” rather than adding a configuration manually. Select the new entry and tap the connect button. The first time you connect, Android may ask you to confirm the VPN connection request.
  3. Import succeeded, but no entry appears: Clear the list’s search filter, switch to “All,” or check the current group. Then look for the entry by its label or server address. Avoid importing it repeatedly; that can leave duplicate-looking entries and make it easy to select the wrong one when testing.

Add and update subscriptions in v2rayN and v2rayNG

Subscriptions take two steps: save the URL, then update it. “Saved successfully” only means the client has stored the address; nodes may not have been loaded yet. Put each subscription in a different group so you can tell which URL returned an empty list or an error the next time you update.

  1. v2rayN (desktop): Open “Subscription Group” → “Subscription Group Settings,” add a group, enter a recognizable label and the full subscription URL, then save. Back in the main window, select the group and choose “Update current subscription” from the “Subscription Group” menu. If the menu offers updates with or without a proxy, try without a proxy first when the subscription server is directly accessible.
  2. v2rayNG (Android): Open “Subscription group settings” from the upper-left menu, tap “+,” enter a label and URL, then save. Return to the configuration list, switch to the relevant group, and choose “Update subscription” from the upper-right menu. Menu wording can vary slightly between versions; the important part is to save the URL to a subscription group first, then update it from the list.
  3. Check after updating: Confirm that entries appear in the intended group. Open one and check the server, port, and transport type, then select it and connect. If only one entry appears, the subscription may simply have returned one node. Check which group it belongs to rather than judging by the number of entries.

The full URL includes everything after the question mark. Don’t remove parameters, change their capitalization, or enter a subscription URL in a node’s server field. If the provider offers multiple subscription formats, choose the one explicitly intended for your client. A URL being reachable doesn’t guarantee that the client can parse its response.

Troubleshooting import failures, subscription timeouts, and connection issues

“No valid configuration” after pasting: what should you check first?

First, check that the clipboard content starts with vmess:// or vless://. Then look for line breaks in the middle or stray punctuation at the end. If you copied a https:// subscription URL, use the subscription group instead of repeatedly trying to import it as a node.

Subscription update timed out: should you try updating through the proxy?

First, make sure you’re connected to the network and retry without a proxy. If a direct connection to the subscription service times out but you already have a working node, select it and try the client’s update-through-proxy command. This option can’t establish a connection on its own if no usable node is available. You can also retry on a network you’re authorized to use that can reach the subscription URL.

The subscription says it updated, but why is the group still empty?

Switch to the group you just updated and clear any filters. If the log shows a parsing error, return to the provider’s page and copy the URL for your client again. If the log shows 401 or 403, check your account status, whether the token has expired, and whether you copied a login page URL by mistake.

The node imported successfully, so why won’t websites load?

First, make sure the newly imported node is selected, then check that traffic is routed through the client: on desktop, check whether the system proxy is enabled and your browser is using it; on Android, make sure the connection is active. If the connection log shows a TLS handshake or certificate error, compare the server name with the original configuration and check your device’s time. Don’t hide a configuration error by disabling certificate verification.

Download v2rayN