VMess and VLESS Share Links vs. Subscription URLs: Differences and Import Guide

Share Links vs. Subscription URLs

vmess:// and vless:// are typically share links for a single node. They contain the server address, port, user ID, and transport settings. When imported, the client reads these parameters and creates a local node entry. It does not visit the address to download a configuration from a webpage.

Subscription URLs usually start with https:// and point to an endpoint that provides a node list. The client sends a network request, then parses the response. A subscription can return one node or several; the number of nodes is not a reliable way to distinguish a share link from a subscription URL.

Link structure and fields to preserve

A common VMess share link consists of vmess:// followed by a Base64-encoded JSON object. Decoded, it commonly contains fields such as add, port, id, net, host, path, and tls. Base64 is an encoding, not encryption. These share-link fields are also not the same as the full runtime config.json structure.

A VLESS share link is closer to a URI: the user ID comes before @, followed by the server and port. Query parameters specify transport and security settings, and the text after # is usually the node label. The example below is for illustration only: the domain and UUID are sample data and cannot be used to connect.

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

• type=ws indicates WebSocket. Decoded, path=%2Fgateway becomes /gateway; the path must match the server configuration.
• security=tls enables TLS. sni is the server name used for the TLS handshake and should not be replaced with an arbitrary domain.
• encryption=none is a VLESS protocol field; it does not mean the connection has no TLS protection. Treat the protocol layer and transport security layer separately.
• REALITY nodes may also include parameters such as a public key, short ID, and flow. These must be parsed by a compatible client and core; do not apply the TLS example above to them.

v2rayN: Import from Clipboard or QR Code

These steps use the common Chinese-language interface; button locations may differ between desktop and classic versions. First make sure you copied the complete protocol share link, not the title of a subscription webpage. Importing a node adds it to the configuration list; it does not enable the system proxy.

1. Copy the link. Select the entire text, starting with vmess:// or vless://. For bulk imports, put one link on each line without numbering, quotation marks, or explanatory text.
2. Import from the clipboard. In the v2rayN main window, select “Servers” → “Import bulk URLs from clipboard.” In some versions, this option is under the Add Server menu. You can also try Ctrl+V in the main window; do not paste into the search box or a parameter field.
3. Check the entry. Verify the new node’s protocol, address, port, and label. Open its edit window to confirm the transport type, TLS, and server name are present. If the import succeeds but fields are blank, check the original link again.
4. Set the active server. Select the node you want to test, then use the context menu to set it as the active server. Configure the system proxy or another traffic mode for your use case. Test one node first to avoid changing routing and DNS at the same time.

A QR code is just a way to carry text, not a separate protocol. On desktop, display the full code on screen, then select “Servers” → “Scan QR code on screen.” In some versions, this option is under the Add menu. Close any windows covering the code, leave clear space around it, and adjust its display size if needed.

• If the scan result starts with vmess:// or vless://, import it as a node share link.
• If the scan result is an HTTPS URL, confirm what it is for, then save it to a subscription group. A successful scan does not mean the subscription has been updated.
• If the scan result is a webpage URL or plain text, ask the provider for a valid node QR code or subscription URL. Do not guess the parameters manually.

v2rayN: Add a Subscription and Update Nodes

Subscription setup involves two separate actions: saving the URL and fetching its contents. If you add a subscription group but do not update it, the node list may remain empty. Use an easy-to-recognize group name, such as “Primary subscription,” and do not put access tokens in the label.

1. Open “Subscription Group” → “Subscription Group Settings,” add a group, enter a name in the remarks field, paste the full subscription URL into the URL field, and save.
2. Return to the main window, select the relevant group, then choose “Subscription Group” → “Update current subscription (without proxy).” Menu wording varies slightly by version; make sure the selected group is the one you just saved.
3. Check the status or logs for download and parsing results. If the subscription endpoint is reachable only through an existing proxy, and you already have a working node, try “Update current subscription (through proxy).”
4. After updating, check the node count, group, and labels, then set a node as the active server. A successful subscription update does not prove that every node can connect.

v2rayNG: Import on Android and Subscription Groups

In v2rayNG, single-node imports usually start from the “+” in the top-right corner of the main screen. The first time you connect, Android asks you to approve VPN access. This system permission is part of connecting, not importing a node.

1. Clipboard: Copy the complete share link, open v2rayNG, and tap “+” → “Import from clipboard.” Return to the list, check the new entry, and select the node you want to use.
2. QR code: Tap “+” → “Scan QR code” and grant camera access if prompted. Scan a code displayed on another screen. If your version can scan an image, you can also select a QR code image saved on your device.
3. Subscription: Open “Subscription Group Settings” from the side menu, tap Add, enter a label and subscription URL, then save. Return to the main screen and choose “Update subscription” from the top-right menu. If the app lets you update the current group or all groups, select the appropriate option.
4. Connect: Once a node appears in the list, select it and tap the connect button. Approve the system permission, then test access. Battery-saving settings may affect background operation; if the connection keeps dropping, check your system’s battery and background restrictions.

Troubleshoot Import Failures and Empty Subscriptions

First identify which stage failed. Clipboard import problems usually involve the text or parser support. Subscription update failures usually involve the network request or response. If the node appears in the list but will not connect, check the server, transport settings, routing, and DNS.

Subscription Updates and Credential Safety

Treat share links, QR codes, and subscription URLs as connection credentials. Long strings in subscription URLs often identify an account, and a QR code may contain a UUID directly. Posting a QR code screenshot in a public forum is no safer than posting the link. When sharing diagnostic screenshots, hide credentials, the full subscription URL, and personal account details.

• Avoid duplicate groups: Creating multiple groups for the same URL can clutter the node list. Update the existing group when possible, and check which group an entry belongs to before removing duplicates.
• Update only when needed: Update after adding a subscription for the first time, when the provider announces a change, or when nodes stop working. Use scheduled updates only if the client supports them and the provider recommends them. Avoid repeatedly hitting the endpoint in a short period.
• Keep settings separate: A subscription provides nodes but does not necessarily include routing, DNS, or per-app settings suited to your device. Check these local settings separately when you change subscriptions.
• If a URL is exposed: Reset the subscription token or related credentials in your provider account, then replace the old URL saved on each device. Deleting a chat message does not invalidate credentials that have already been copied.

Once configured, follow a clear checklist: confirm the import type, check the node fields, select the active node, enable the traffic mode you need, and verify real-world access. This helps you distinguish a link entered in the wrong place from a failed subscription download or a node connection issue.