vmess:// and vless:// Share Links: Single-Node Links vs. Subscription URLs

First, distinguish single-node links from subscription URLs

Text beginning with vmess:// or vless:// is usually a single-node share link. It describes the address, port, user identifier, transport method, and security settings required to connect to one server. Importing it creates a configuration entry in the client; if the server settings change later, the original entry will not update automatically.

A subscription URL usually begins with https:// and is essentially a remotely accessible resource. After requesting the URL, the client receives one or more node records and saves them in a subscription group. When the provider adds or removes nodes, changes domains, or adjusts ports, you can update the subscription to resync the remote list locally.

What vmess:// and vless:// links contain

A typical VMess share link encodes a JSON configuration and appends it after vmess://. Encoding makes multi-field content easier to copy; it does not hide the settings. After decoding, the client still needs to read fields such as the server address, port, user ID, transport network, path, TLS, and server name.

The following VMess decoding example illustrates the structure. The example domain and user ID are for documentation only and cannot establish a real connection. add is the server address, port is the remote port, net and path together describe WebSocket transport, while tls and sni are used for the TLS connection.

{
  "v": "2",
  "ps": "Documentation example node",
  "add": "edge.example.com",
  "port": "443",
  "id": "00000000-0000-4000-8000-000000000000",
  "aid": "0",
  "scy": "auto",
  "net": "ws",
  "type": "none",
  "host": "edge.example.com",
  "path": "/ray",
  "tls": "tls",
  "sni": "edge.example.com"
}

A VLESS share link is closer to a standard URI. The user ID appears before @, the server address and port follow it, transport and security settings are written in the query string, and the text after the hash is used as the node name. Because the fields are visible directly, checking the port, transport type, and path is usually more straightforward.

vless://[email protected]:443?encryption=none&security=tls&type=ws&host=edge.example.com&path=%2Fray&sni=edge.example.com#Documentation example node

Import correctly in v2rayN and v2rayNG

Before importing, copy the complete original text rather than selecting only the portion visible in a chat message. Links may contain question marks, equal signs, percent signs, and hashes; truncating any part can cause parsing failures or create a configuration missing transport settings. The menu names below are based on the common interfaces of v2rayN 7.14.3 and v2rayNG 1.10.31.

Import a single-node link in v2rayN

1. Copy the complete vmess:// or vless:// link.
2. Open the v2rayN main window and choose “Servers” → “Import batch URLs from clipboard.”
3. Find the new entry in the server list and verify the protocol, address, remote port, and label.
4. Select the entry, set it as the active server, then check the log window at the bottom for configuration parsing or core startup errors.
5. To check local listeners, go to “Settings” → “Parameter settings” and confirm that the local port is not already used by another program.

Add a subscription URL in v2rayN

1. Open “Subscription groups” → “Subscription group settings.”
2. Add a group, enter an easy-to-recognize alias, and paste the complete HTTPS subscription URL into the address field.
3. After saving, open the “Subscription groups” menu and choose “Update subscription” for that group.
4. After the update, check the node count and update time; existing manual nodes normally do not become subscription nodes as a result.

Import links or subscriptions in v2rayNG

• Single-node link: copy the link, open the plus menu in the top-right corner, and choose “Import configuration from clipboard.”
• Subscription URL: open the menu in the top-left corner, go to “Subscription group settings,” add a group, and enter the subscription URL.
• Return to the main screen, update the subscription, wait for the node list to refresh, and then select an entry to start the connection.
• If the system asks whether to allow a local connection service, confirm it as prompted; otherwise, the client cannot take over traffic that needs forwarding.

When to use a share link and when to use a subscription

The deciding factor is not the number of nodes, but who maintains the settings and how often they change. If you manage the server yourself and its address is stable, a share link keeps a clearly defined configuration. If nodes are maintained remotely and their entry points may change, a subscription is better for long-term use.

If you only need to verify one new node, importing the share link directly is faster. During testing, keep the original label and check the server address, port, and transport settings. Once it works, you can edit the local label, but do not treat the label as a protocol setting. A node name that says “TLS” or “High Speed” cannot replace the actual fields in the configuration.

For multiple devices, a subscription avoids repeated manual entry. v2rayN and v2rayNG can each save the same subscription URL, but local routing, system proxy, and app traffic controls remain independent on each device. A subscription syncs the node list; it does not sync client settings such as “bypass LAN,” “per-app proxy,” or the local listening port.

Troubleshooting parse failures, empty lists, and duplicate nodes

Start with the original input instead of repeatedly switching cores. First confirm whether you copied a node link or a subscription URL, then check that the link is complete and that the client version supports the protocol and transport. A subscription opening in a browser does not guarantee that its response is a node list the client can parse; login pages, error pages, and expiration notices may all be returned as ordinary web pages.

• First verify the input type: protocol links use clipboard import, while HTTPS subscriptions use a subscription group.
• Then verify the parsed result: the protocol, address, port, user ID, and transport-layer fields must all be present.
• Next verify core startup: the logs should not report unsupported configuration fields or a local port conflict.
• Finally verify the connection path by distinguishing DNS resolution, TCP connection, TLS handshake, and application proxy settings.

Operational boundaries for saving, updating, and sharing

Share links and subscription URLs may contain access parameters that can be used to connect to a server, so handle them like account credentials. Do not include the complete content in public screenshots, log posts, or searchable documents. When asking others for help, keep the protocol name, transport type, and error message, but redact the user ID, domain, subscription URL, and other identifying fields.

Before updating a subscription, you can record the names, remote ports, and update times of currently working nodes. If many nodes disappear afterward, first check that the correct group is selected and that the remote response is normal; do not immediately add the same URL repeatedly. Before deleting a subscription group, confirm that it does not contain local entries you still need to keep.

1. After receiving the content, identify its prefix and confirm its source and purpose.
2. Use the matching import path; do not try to open protocol links in a web browser’s address bar.
3. After importing, verify the key fields, then start the core and review the logs.
4. Keep long-term nodes in a subscription group and temporary nodes as separate entries.
5. Update the client regularly to gain support for parsing newer protocol fields and transport settings.