Not sure where to paste a link? Check its prefix, then see how the source describes it. Import a single-node share link directly; save a URL labeled as a subscription to a group, then update it. This guide walks through both workflows in v2rayN and v2rayNG, and explains the difference between a successful import, a successful subscription update, and a working node.
How to tell a single-node link from a subscription URL
A string beginning with vmess:// or vless:// usually describes a single node. The client parses the link itself. A subscription URL usually starts with https://; the client must first fetch that URL, then parse the response. Regular login pages, dashboards, and download pages also use HTTPS, so the prefix alone doesn't prove a URL is a subscription.
Subscription URL
RecommendedIf you need to keep a node list from the same source up to date, save its subscription URL in a separate group. When you update the group, the client fetches the list again instead of making you edit previously copied links one by one.
Best for: keeping a changing set of nodes or parameters in sync
Single-node share link
Importing a link creates a local configuration based on its contents at that time. Even if the link was copied from a subscription group, importing it on its own doesn't preserve the group's update relationship.
Best for: adding one node or testing a configuration on its own
First, check where the node came from
When a node stops working, check whether it came from a subscription group. If so, update that group. If you imported a single link from the clipboard, ask the configuration provider for a new one; there's no need to keep refreshing unrelated groups.
What fields do VMess and VLESS share links contain?
A common VMess share link contains Base64-encoded JSON text with a vmess:// prefix. add is the server address, port is the server port, id is the connection credential, and ps is the display label. net specifies the transport; with WebSocket, for example, path and host may be part of the configuration. Base64 is an encoding, not encryption.
A typical VLESS link looks more like a regular URI: the user identifier comes before @, followed by the server address and port; connection parameters come after ?, and the display label follows #. The example below illustrates the field layout and uses a reserved domain and invalid credentials, so it cannot be used to connect.
vless://[email protected]:443?encryption=none&security=tls&type=ws&path=%2Fedge#Demo
In this example, type=ws means WebSocket, and path=%2Fedge decodes to /edge. security=tls specifies TLS; it is not the same setting as encryption=none in a VLESS link. To troubleshoot, check the fields in the client details, but don't remove query parameters just to shorten the link or manually rewrite percent-encoded values before importing it.
Import from the clipboard in v2rayN or scan a QR code in v2rayNG
A QR code is simply another way to transfer text, not a different protocol. If it contains a single-node link, import it as a node; if it contains a URL explicitly intended for subscriptions, add it to a subscription group. Menu labels may vary slightly by version; the steps below cover the usual options.
Choose the single-node import method for your device
Desktop: v2rayN
- Copy the entire link, from its protocol prefix to the end. Leave out any quotation marks or periods around it in the chat message.
- Open the main window and select “Server” → “Import bulk URLs from clipboard.” Despite the menu label, you can import just one link.
- If the QR code is displayed on your computer screen, look for the scan QR code from screen option in the “Server” menu, or import the original link instead.
Android: v2rayNG
- On the main screen, tap “+” in the upper-right corner, then choose “Import from clipboard” or “Scan QR code.”
- Use your camera to scan the QR code on another device's screen, and grant camera access when prompted. If the QR code is on this device, ask the sender to share the original link so you can use the clipboard option.
- Return to the configuration list, check the new entry's protocol and label, then select it to test the connection.
A new entry in the list only means the client recognized the configuration; it doesn't confirm that the server is reachable or the account is valid.
Add and update a subscription group
- Save the URL first. In v2rayN, open “Subscription Group” → “Subscription Group Settings,” add a group, and enter the URL in the address field. In v2rayNG, open the top-left menu → “Subscription Group Settings,” tap “+,” and enter a label and address. Give each source its own name so you can check the update results easily.
- Then run an update. In v2rayN, choose the option to update the current subscription from the “Subscription Group” menu, making sure the correct group is selected. In v2rayNG, return to the configuration list and tap “Update subscription” in the top-right overflow menu. Saving a URL creates a group; it doesn't fetch the list.
- Check the updated list. Switch to the relevant group and confirm the node count and labels look right. If the subscription removed your active node, select one that remains. Don't rely on edits made directly to subscription entries to persist; a refresh may overwrite them with the source's settings.
A subscription response commonly contains share links on separate lines, but it may also return the entire list encoded as Base64. That is different from the Base64 inside an individual VMess link: decoding the outer layer gives you a list of links, while decoding a VMess link's body reveals that node's fields. Being able to open a subscription URL in a browser also doesn't mean the client supports the format the server actually returns.
Import or update failed? Check these steps first
Why does the client say there’s nothing to import after I copy a link?
Check that you copied the protocol prefix, that no actual line breaks were inserted in the middle, and that no Chinese full stop was added at the end. If you have an HTTPS subscription URL, don't import it as a node from the clipboard; enter it in the subscription group's address field instead.
Do I need to reinstall the client if a subscription update returns 401 or 403?
Not yet. A 401 usually indicates an authentication issue; a 403 means the server denied access. Check the source page to see whether the subscription expired or its URL changed, then copy the full URL again. If access is restricted, ask the provider what conditions apply to your device.
Why are there no nodes even though the update returned 200?
A 200 response only means the HTTP request succeeded. The server may still have returned a login page, an empty list, or an incompatible configuration format. Make sure you copied the subscription URL rather than a management page, ask the provider to confirm the response format, and check whether your client version supports its protocols and transport settings.
What should I do if a node is listed but the connection times out?
First, make sure you're testing the entry you just imported. Check the server address, port, transport, and security settings, then look in the core logs to see whether it timed out or failed during the handshake. A subscription server returning a list only proves that the subscription request succeeded; it doesn't mean every node in that list is reachable.