How to Import Subscriptions in v2rayN and v2rayNG: Subscription Groups and Supported Formats

Learn where to add subscription groups in v2rayN and v2rayNG, how Base64 and plain-text link lists differ, and what to check when an update fails.

At a glance

For your first import, check whether you have a subscription URL or a node share link. Add subscription URLs to a subscription group, save, then run an update manually. Import share links from the clipboard. If an update fails, check in order whether the request succeeded, whether the response format is supported, and whether nodes appeared in the intended group.

Subscription URLs vs. node links

A subscription URL is an endpoint the client requests periodically and usually starts with https://. Share links starting with vmess:// or vless:// describe an individual node configuration. A https:// prefix alone doesn't prove that a URL is a valid subscription: login pages, account dashboards, and help pages can use it too. Copy the complete URL specifically labeled for client subscriptions.

Subscription URL

What to copy
The complete HTTP(S) subscription URL
Where to enter it
The URL field in subscription group settings
After saving
Run a subscription update, then check the node list
Ongoing updates
Refresh the group's list from the same URL

Keep any parameters after the question mark in the URL. Don't truncate it or paste the subscription response body into the URL field.

Node share link

What to copy
A complete line starting with vmess:// or vless://
Where to import
The client's clipboard import option
After importing
Check that the new configuration appears in the list
Ongoing updates
Re-import when the configuration changes, or edit the node manually

When copying, don't include bullets, quotation marks, or explanatory text. A node imported on its own won't be updated when you refresh a subscription.

Subscription URLs may contain access tokens, and node links may include connection credentials. When reporting an issue, note only the group label, error type, and time. Before sharing a screenshot, hide the full URL, node links, and any log lines containing them.

Import a subscription group in v2rayN

Use the desktop client's main window, not the tray's “System proxy” menu. For your first import, update just one group so you can match any error to a specific URL without searching through logs for multiple subscriptions.

  1. Open subscription group settings

    In the main window, select “Subscription group” → “Subscription group settings.” If a group list opens, click “Add” to create an entry; some versions use “+” for adding one.

  2. Enter a label and URL

    Enter a recognizable source name under “Remarks” and paste the complete subscription URL into “Address (url).” Don't put the label in the URL field. Check for leading or trailing spaces and line breaks, then click “OK.”

  3. Update the selected group

    Return to the main window and select the group you just created. If the subscription URL is directly accessible, choose “Subscription group” → “Update current subscription (without proxy).” If a direct connection times out and another working connection is already available on your device, try “Update current subscription (through proxy).” Some versions say “current group” instead of “current”; make sure you don't accidentally update all subscriptions.

  4. Check the node list

    Check the update log first, then view the node list for that group. A group name with no nodes after saving doesn't mean the import succeeded. If the log says nodes were imported but the list hasn't changed, clear the main window's search filter, confirm the selected group, then check the node names and protocols.

If you only have a share link, copy the entire line and choose “Server” → “Import bulk URLs from clipboard,” or press Ctrl+V in the main window. This adds a node directly; it doesn't create an updatable subscription URL.

Import a subscription group in v2rayNG

On Android, create a group first, then update it. In the layout used here, the main screen has a menu in the top-left and an overflow menu in the top-right. They serve different purposes: the left menu manages subscription URLs, while the right menu starts an update. Menu names may vary slightly by version or translation.

  1. Open subscription groups

    Tap the top-left menu on the main screen and open “Subscription group settings” (shown as “Subscription groups” in some versions). On the group management screen, tap “+” in the top-right. The “+” on the main screen isn't where you enter a subscription URL.

  2. Paste the subscription URL

    Enter a “Remarks” label and the “Address”; some versions call the address field “Optional address.” Tap the checkmark in the top-right to save. The group may still be created if you leave the address blank, but it won't have a source to update from.

  3. Update the subscription manually

    Return to the main screen, switch to the new group, then tap “Update subscription” in the top-right “⋮” menu. If the menu offers updates for the current group or all groups, choose the current group when troubleshooting for the first time. Wait for the result, then check that group's list.

  4. Test the connection separately

    Test the connection only after nodes appear in the list. Select a node, then tap the connect button at the bottom. When prompted the first time, approve the system's VPN connection request. If nodes are listed but none connect, don't delete the subscription yet. Try another node first to determine whether the issue affects one node or the whole group.

To import a single link, copy it, return to the main screen, and tap “+” → “Import from clipboard.” Opening the subscription URL in a browser and copying the page contents is not a substitute for entering the URL in subscription group settings.

Base64 vs. plain-text link lists

Being able to open a subscription URL doesn't mean the client can import it. The URL is the request endpoint; the response body determines whether the client can import it. Two common response formats can both contain VMess, VLESS, and other share links. The difference is whether the list is encoded as a whole.

Two response formats, one URL field

Base64-encoded list
  • The response often looks like a long string of characters. Plain Base64 text may end with = padding, but the absence of an equals sign doesn't rule out Base64.
  • The client decodes the list first, then parses the share links line by line. Base64 here is an outer encoding, not the node's encryption method.
Plain-text share link list
  • The response body contains share links directly, usually one per line. A one-line list only means the response contains one node; it doesn't mean the subscription URL is invalid.
  • A client may recognize the list format without supporting every entry. If the client doesn't support a particular protocol or parameter, only some entries may appear.

For either format, enter the original subscription URL. Don't paste the response body into the URL field or Base64-encode the entire URL.

If the two clients show different import results, first confirm that both use the same group URL and that you manually updated on both. The subscription service may return different content depending on the request source, and the clients may support different entries. If multiple formats are available, copy the subscription URL explicitly labeled for the client you're using. Don't guess or alter query parameters.

Troubleshooting subscription update failures

Check the update log or message first to decide whether to investigate the network or the response format. The numbers below are HTTP status codes, not latency or node counts. A status code appears only when an HTTP response is received; a connection timeout or DNS lookup failure may not show one.

200
Request succeeded; check the response format
401
Authentication failed; check the subscription credentials
403
Request denied; check access permissions
404
Resource not found; copy the URL again

The subscription was saved, but why are there no nodes?

Return to group settings and make sure the URL field isn't empty, then go back to the main list and run an update. If there's no error, check whether you're viewing a different group or have a search filter enabled. If the log explicitly says it parsed zero entries, investigate the response format instead of repeatedly creating the same group.

Updates keep timing out. Should I change the system proxy?

First, make sure you copied the complete subscription URL, then confirm the device has internet access by opening a regular webpage. In v2rayN, if a working proxy connection is already available, retry with “Update current subscription (through proxy).” Otherwise, try “without proxy” or switch to a working network. Change one thing at a time to determine whether the URL is unreachable or the update's network path is the problem.

The request returned 200. Why did parsing still fail?

The response may be a login page, an error page, or a configuration format the client doesn't accept. Go back to the original source and copy the subscription URL intended for your client. A URL opening in your browser doesn't prove the client receives the same content; your browser may already have an authenticated session.

The subscription updated successfully. Why won't webpages load?

A successful update only means the list was retrieved. Test a node on its own. On desktop, for a browser that follows the system proxy to use the connection, check that “Set system proxy” is selected under “System proxy” in the tray. On Android, first confirm the VPN is connected; if per-app proxying is enabled, check that the browser you're testing isn't excluded.

Why am I still getting a 403 after copying the URL from the source?

First confirm the subscription is still active and access permissions haven't changed. Check that you didn't miss any query parameters when copying. If the source offers a way to reset the link, follow its instructions to get a new URL, then edit the existing group and update it. Resetting may invalidate the old link, so replace it on your other devices too.

Download v2rayN