Sync v2rayN and v2rayNG Across Devices: Subscription Links, QR Codes, and Backups

Compare subscription updates, QR code and share-link transfers, and backup imports to keep nodes and routing consistent between your computer and phone.

At a Glance

For a computer and Android phone sharing nodes long term, add the same subscription on both devices. To transfer a single node, use a QR code or share link. To restore after switching devices, use a backup the same client can read. Subscriptions don't sync settings: check routing rules, DNS, and traffic handling separately.

Choosing a Sync Method

Same Subscription Link

Recommended

Both devices fetch their node lists from the same source. When the server changes addresses or adds or removes nodes, update each device separately. The selected node and local rules won't sync.

Best for: Sharing the same node source across a desktop, laptop, and phone.

Node QR Codes and Share Links

These import the node settings as they were when shared. If the server address or credentials change, share the node again. Scanning the same code more than once may also create duplicate entries.

Best for: Moving a single manually added node or checking a connection on another device.

Client Backups

What a backup restores depends on its format. A list of share links, a core configuration file, and a client backup are different file types; the extension alone doesn't tell you what a file is for.

Best for: Moving to a new device with the same client, saving a copy before reinstalling, or rolling back after an update.

Add the Same Subscription on Your Computer and Phone

First, make sure you have a subscription URL, not a link for a single node starting with vmess:// or vless://. Subscription URLs often contain access tokens, so protect them like passwords. The steps below use common Chinese interface labels; menu names and locations may vary slightly by version.

  1. Add a Subscription Group on Desktop

    In v2rayN, open “Subscription Group” → “Subscription Group Settings,” add a group, enter a label and subscription URL, then save. The label helps identify the source; it doesn't affect the nodes returned by the server.

  2. Fetch Nodes on Desktop

    Select the group you just created, then choose “Update Current Subscription” from “Subscription Group.” If the menu offers updates through or without a proxy, choose based on whether your current network can reach the subscription URL. An update through a proxy may fail if no usable node is available.

  3. Add the Subscription on Android

    In v2rayNG, open the top-left menu → “Subscription Group Settings” → “+”, enter the same subscription URL, and save. Return to the node list, open the top-right menu, and select “Update Subscription.” Then switch to the relevant group to check the results.

  4. Compare and Test

    Note the update time on each device. Select the same node and compare its protocol, server port, transport, and security settings, then test a known-working address on each. Matching node names only confirm that the labels are the same, not that the connection settings match.

If the node counts differ after an update, first check that both devices have the same group selected and that each update succeeded. The subscription service may return different results depending on the request, and a client may skip entries it doesn't support. If the list is empty or missing nodes, check the update log, then compare the protocols and transport settings of the missing nodes. Don't repeatedly overwrite an existing group just to make the counts match.

Transfer Nodes with QR Codes and Share Links

  1. Computer to phone: In the v2rayN node list, select the node and use the right-click menu to display its QR code. In v2rayNG, tap “+” on the main screen → “Scan QR Code,” grant camera access, and point the phone at the computer screen. After scanning, open the new entry's details and make sure you didn't scan a subscription URL or a different node by mistake.
  2. Phone to computer: In v2rayNG, use the share option on the node and copy its link. Copy the complete link on your computer, then use the clipboard import option in v2rayN's “Servers” menu. If the clipboard contains multiple lines, keep only the node link first to avoid including chat text or cutting off the link at a line break.
  3. Verify the imported node before removing duplicates. Compare the address, port, transport type, and security settings. For TLS, check the server name too. A successful import only means the format was recognized; it doesn't guarantee that the receiving client's core supports every setting.

Backup and Restore: What to Expect

Before making a backup, decide what you need to restore: the node list, subscription URLs, routing rules, or all client preferences. If backing up the desktop configuration directory, fully exit v2rayN first, then copy the directory used by the current instance. Don't mistake the program installation directory for the configuration directory, or overwrite files while the program is still writing to them.

Align and Verify Routing on Both Devices

Use the Same Routing Intent, Configure Traffic Handling Separately

v2rayN on Desktop
  • First, check whether you're using the system proxy or TUN. The system proxy mainly covers apps that honor system proxy settings; a successful browser test doesn't mean all desktop processes are covered.
  • Keep direct connections to your local network. When editing custom rules, check that broad matches don't come before more specific ones.
v2rayNG on Android
  • After starting the VPN, check the per-app proxy list. Confirm the app you're testing is included in the VPN, then check which routing rule its traffic matches.
  • Recreate the domain rules to match the expected desktop behavior, and check the DNS settings. Don't enter the desktop system proxy port on your phone as a substitute for its local VPN.

Verify that the same destination gets the expected outbound route; don't compare the number of enabled toggles on each device's settings screen.

10808
Common v2rayN Local Proxy Ports (Check Settings)
443
Common Remote Ports for TLS Nodes (Check Node Details)
3 checks
Verify: direct access to your local network, proxying for a specified domain, and default handling for a regular domain

On desktop, check the local listening port under “Settings” → “Parameter Settings.” This is separate from the server port in a subscription entry: the local port is for apps on your computer, while the server port is the remote destination the client connects to. When moving a node, copy its remote settings; the local listening port doesn't need to match across devices.

For testing, put both devices on the same network, then visit a local network service, a domain explicitly routed through the proxy, and a domain that uses the default rule. Check the connection logs for the expected outbound route. If only one app on your phone behaves incorrectly, check the per-app list first. If the devices differ only in domain tests, compare where DNS is resolved, domain rule order, and the rule data.

Download v2rayNChoose a platform and installer