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

At a glance

When you receive connection details, first determine whether they describe one node or point to a node list. This guide is for anyone importing a configuration for the first time, switching devices, or organizing subscriptions. Choose the right import option based on the link prefix, check the port, transport, and security settings, then confirm that a subscription update actually changed the node list.

Share Links vs. Subscription URLs: What Gets Imported

vmess:// and vless:// are URI prefixes that clients use to identify node configurations—not web addresses to open in a browser. A share link typically describes one server connection, including its address, port, credentials, transport, and security settings such as TLS. Importing it saves those details as a local configuration; it does not create a subscription.

Subscription URLs usually start with https://. The client fetches a node list from the URL and parses it into local entries. The provider can change server addresses or add and remove nodes; those changes appear only after you update the subscription. An HTTPS prefix alone does not tell you whether a URL is a subscription: account pages, help pages, and subscription endpoints can all use HTTPS.

Subscription URL

Recommended

If the provider offers both a subscription and individual share links, a subscription is usually easier to maintain over time. Save the URL in a subscription group and fetch the list again when you update it. Automatic updates depend on the client’s settings.

Best for: ongoing use, multiple nodes, and updates from the provider.

Single-node share link

Saves the current settings as a local node. If the provider later changes the port, credentials, or transport settings, the local entry will not update automatically. Import the link again or edit the entry manually.

Best for: temporary tests, a specific node, or troubleshooting one configuration.

How to choose: check the provider’s instructions first

If the provider labels it a “subscription URL,” add it as a subscription group. If you have a complete vmess:// or vless:// link, import it from the clipboard. Don’t paste a single-node link into the subscription URL field and repeatedly try to update it.

Link Structure: What Comes After the Prefix

A common VMess share-link format puts a Base64-encoded JSON object after vmess://. Typical fields include the server address add, port port, user ID id, transport type net, and TLS setting tls. Base64 is an encoding, not encryption. A hard-to-read link is not safe to share publicly.

VLESS share links usually look more like standard URIs: the identity appears before @, the server and port follow it, and parameters after the question mark describe transport and security settings. The example below illustrates the format only. The domain and identity are examples, not a working node.

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

example.org:443 is the remote server address and port, not the client’s local listening address.
encryption=none describes the encryption option at the VLESS protocol layer. In this example, security=tls means the transport layer still uses TLS; don’t confuse the two.
type=tcp indicates the transport type in this example. If the provider uses WebSocket, the link may also include path and host; keep all parameters intact.
sni is the server name used during the TLS handshake. It and the WebSocket Host belong to different layers, so don’t substitute one for the other based on guesswork.
The text after # is usually a node remark. Non-ASCII characters, spaces, and special characters may be percent-encoded. Don’t remove encoded characters just to “clean up” the link.

Not every VMess sharing implementation uses the same field conventions, and newer transport parameters require client support. If parsing fails, keep the original link, update the client, and check which formats the provider supports. Don’t start by randomly deleting parameters.

v2rayN: Import a Single Node from the Clipboard

The steps below use common menu labels from the Chinese-language interface. Wording and menu locations may vary slightly between versions, but importing nodes and managing subscription groups are separate workflows. Before you start, make sure you copied the link itself—not a page title, button label, or QR code image.

Copy the complete link. Copy everything starting with vmess:// or vless://. For bulk imports, put one link on each line and don’t add numbering or explanatory text.
Import the link. Open v2rayN and choose “Servers” → “Import bulk URLs from clipboard.” Many desktop versions also support Ctrl+V; make sure the main window is focused first.
Check the entry. Find the new node in the server list, open its edit window, and check the address, port, user ID, transport, and TLS settings. Matching remarks don’t guarantee matching configurations.
Set it as the active server. Select the node and choose “Set as active server.” Confirm that the core starts successfully, then test the connection.
Choose how traffic is routed. To route traffic from apps that follow the system proxy through this node, choose “System proxy” → “Automatically configure system proxy.” TUN is a separate routing method and doesn’t need to be enabled just to import a node.

v2rayNG: Import from Clipboard and Update Subscriptions

On Android, v2rayNG also distinguishes between local nodes and subscription nodes. Importing a configuration does not require a VPN connection. When you tap Connect, Android may ask you to authorize the VPN connection. That authorization lets the client route the relevant traffic; it does not mean the remote server has connected successfully.

Import a Single Node

Copy the complete share link and open the v2rayNG main screen.
Tap “＋” in the upper-right corner → “Import config from clipboard.” If Android asks whether v2rayNG can access the clipboard, grant access for this operation as needed.
Select the new node in the list, open its edit screen, and check the server port, user ID, transport protocol, and TLS settings.
Tap Connect. If prompted, authorize the VPN connection, then check the connection status and logs.

Add a Subscription

Open “Subscription group settings” from the menu, tap the add option, and enter a recognizable remark, such as “Daily subscription.”
Paste the complete HTTPS subscription URL from the provider into the address field and save it. Make sure there are no extra spaces at the beginning or end.
Return to the main screen and choose “Update subscription” from the menu. If the app lets you update the selected group, make sure the newly added group is selected.
Check the update result and node list. If you saved the URL but haven’t updated the subscription, an empty list is expected.

To move to another device, get the same subscription URL from the original provider and add it on each device. Exporting only the current nodes gives you a snapshot of their settings; it does not transfer the subscription, per-app rules, or connection authorization.

Manage Both Clients: Subscription Groups and Port Checks

In v2rayN, subscriptions are usually added through “Subscription group” → “Subscription group settings”: create a group, enter a remark and URL, save, then go back to the “Subscription group” menu and update it. The menu may offer updates “without proxy” or “through proxy.” Use the first option if your current network can reach the subscription endpoint directly. The second requires a working proxy connection.

Setup: Save the Same Subscription on Both Devices

Desktop: v2rayN

Save the provider’s URL in “Subscription group settings.”
After updating, confirm that the nodes belong to the right group.
If you need to preserve manual changes, copy the node to a separate local group first.

Android: v2rayNG

Add the same provider in “Subscription group settings.”
Update it separately; this doesn’t depend on the desktop client.
Configure per-app proxy settings to suit this device.

Using the same provider doesn’t mean the lists stay in sync. Differences in update timing, filters, and supported formats can produce different results. The account may also limit how many devices can connect at once.

One of the most common configuration mistakes is confusing the remote server port with the local proxy port. The numbers below are examples to help identify each port; they aren’t required values for every node. Use the port specified by the provider for the remote server and the client’s settings for local ports.

443

Common HTTPS port; TLS nodes may use other ports

Common HTTP port; this alone doesn’t tell you whether a node works

10808

Common local proxy port in v2rayN; check your current settings

For example, if an app requires a manually configured local proxy, the address is usually 127.0.0.1. Find the port in v2rayN under “Settings” → “Parameter settings,” in the local listening configuration. The app’s HTTP or SOCKS option must match the listener type. Don’t enter these local proxy details as the node’s server address and port.

Troubleshooting: Parse Errors, Empty Updates, and Connection Failures

Why does the app say there’s nothing to import after I copy a link?

Paste the text into a local editor and check that it starts with vmess:// or vless://, has no quotation marks or bullet points, and wasn’t truncated by a messaging app. Copy the original text again and use “Import from clipboard.” Don’t copy the entire message if it includes extra instructions around the link.

Why does a subscription URL open in my browser but show no nodes in the client?

The browser may be showing a sign-in page, account page, or error—not a node list. Check that you’re using the subscription URL specified by the provider, that the token is complete, and that your plan is active. The subscription must also use a format the client can read; a regular webpage or incompatible configuration file won’t automatically become a node list.

My subscription update times out. Should I update through a proxy instead?

First check whether the URL is unreachable directly or no longer valid. In v2rayN, choose the appropriate update method from the “Subscription group” menu. If you already have a working active node, try updating through the proxy. If you have no working connection, this option won’t help you fetch the subscription for the first time. Contact the provider to check whether its endpoint is reachable.

Why does the connection fail even though the node imported successfully?

Open the edit window and check the address, port, user ID, transport, TLS, and SNI against the source. For REALITY, also check parameters such as the public key and short ID. Then look in the logs for connection timeouts, authentication errors, or certificate errors. If there’s a certificate issue, check the device time and server name first; don’t disable certificate verification outright.

Why did my custom remarks and settings revert after updating the subscription?

A subscription update may rebuild the nodes in a group and overwrite local changes, depending on the client. To keep edits long-term, copy the node to a separate local entry before changing it. Keep the subscription group for provider updates so manual and subscription-managed configurations stay separate.

Before Sharing: Protect Credentials and Subscription Tokens

User IDs and password-like fields in node links, as well as tokens in subscription URLs, may let someone else access the service. Be especially careful with subscription URLs: one URL may return multiple nodes on your account, not just the one currently selected. A QR code usually contains the same text in visual form; it does not hide the credentials.

Before sharing a screenshot: Hide the full subscription URL, user ID, QR code, and account details. Show only the menus, field names, and error type needed for troubleshooting.
When asking for help: Share the client name, steps you took, and redacted logs. Never post a complete, unredacted link in a public forum or paste it into an online decoder.
If you shared a link by mistake: Reset the subscription token or connection credentials in the provider’s account settings, then replace the URL on each device and update it. Deleting the message won’t invalidate a URL that someone has already copied.
After importing: Clear clipboard contents you no longer need. Check your system settings for clipboard history and cross-device sync, which may retain copies.

Remember the two import options: a share link imports the current node settings, while a subscription group saves the source for fetching a node list. Identify what you have before importing, updating, or testing. Check parsing, the core connection, and traffic routing separately to narrow down problems.