At a Glance

To use the same nodes on a PC and Android phone, add the same subscription on both devices. To move just one node, share its QR code. Before reinstalling or switching devices, use a backup that the same client can restore to preserve groups and local settings. After migration, select a node on each device and check the proxy mode, routing, and DNS settings.

What Subscriptions, Backups, and QR Codes Transfer

Share a Subscription Link

Recommended

Each device requests the node list from the same URL. When the subscription provider changes the list, update it on both devices to get the latest nodes. Changes made on the PC—such as node names, the selected node, and routing settings—are not synced back to the subscription.

Best for: using the same nodes on a PC and Android phone

Export a Client Backup

A backup captures the client state at the time of export. What it includes depends on the client and version. Before restoring, distinguish an app backup from a node share link and a core runtime config; each has a different import method.

Best for: reinstalling the same client, switching devices, or reverting settings

Scan a Single-Node QR Code

A QR code contains the sharing data for the selected node. It imports the connection settings as they were when the code was created; it won't update with the original subscription or include the PC's system proxy settings. If the server address or credentials change, import the node again or update it manually.

Best for: moving a manually added node or testing one node first

Add the Same Subscription in v2rayN and v2rayNG

First, check that your subscription provider allows multiple devices, and confirm any simultaneous-connection limits and whether data usage is counted across the account. The menu steps below are based on common v2rayN 7.x and v2rayNG 1.9.x interfaces; icons and labels may vary by build. Use the full URL from the subscription settings—not a vmess:// or vless:// link exported from a node's context menu.

  1. Check the Subscription URL

    Copy the full URL from the subscription group settings on the original device, including its path and query parameters. Make sure both clients can read the same subscription format. Don't copy just the domain, or paste the URL into an online converter or QR code generator.

  2. Add a Group on Desktop

    In the v2rayN main window, open “Subscription Group” → “Subscription Group Settings” and click “Add.” Enter a group name and subscription URL, then save. Select the group and choose “Update Current Subscription” from the “Subscription Group” menu to fetch its nodes. Saving the group and fetching the node list are separate steps.

  3. Add a Group on Android

    In v2rayNG, open the menu in the upper-left corner and go to “Subscription Group Settings.” Tap “+” in the upper-right corner, enter a name and URL, then save. Return to the node list, select “Update Subscription” from the upper-right menu, and switch to the new group to check the results.

  4. Check the Node Settings

    Open the edit screen for the node with the same name on each device and compare the protocol, server address, remote port, and transport. Matching names don't guarantee matching settings; an older manually added node may have the same name as a subscription node. Select and test the node on each device—successful speed testing on the PC doesn't mean the phone is connected.

  5. Set Up Traffic Routing on Each Device

    To route apps that follow the system proxy through v2rayN, set the system proxy from the desktop tray menu. On Android, start the connection from the v2rayNG main screen and approve the system VPN prompt the first time. A subscription provides nodes only; configure traffic routing separately on each device.

Client Backups vs. Runtime Configs

Client Backup

Restores
Same client; use a compatible version where possible
Record
Client version, backup date, and export method
Check After Restore
Subscription groups, manual nodes, routing, and local ports

If your current version offers backup and restore, use its matching restore option and test the backup before wiping the old device.

Core Runtime Config

Common Settings
inbounds、outbounds、routing
Example of a Local Listener
127.0.0.1:10808; check the client settings for the actual value
Check Before Use
Core compatibility, local paths, and port conflicts

Even if the destination client can load JSON as a custom config, that doesn't restore subscription groups or interface settings.

In v2rayN's server list context menu, “Export Selected Server Config” exports a single node—not a client backup or the full desktop setup. When switching PCs, also note the local listening ports and active routing profile under “Settings” → “Parameter Settings.” When moving from a PC to Android, use these notes for reference; don't copy over listener addresses or file paths.

Transfer One Node by QR Code

  1. In the v2rayN server list, select just one node and open its share QR code from the context menu. Make sure it's a node QR code, not a QR code for the subscription URL: the former imports one node, while the latter must be handled as a subscription.
  2. In the v2rayNG main screen, tap “+” → “Scan QR code.” Allow camera access and point it at the PC screen. After importing, check that one new entry appears in the list. If a node with the same name already exists, give the new entry a distinctive name before testing it.
  3. If the connection fails, compare the original node with the imported entry. For a VMess node using WebSocket, check the transport type, path, and Host. For a VLESS node using REALITY, check the security type, server name, public key, and short ID. Don't disable TLS verification or switch REALITY to regular TLS just to troubleshoot.
  4. Select the new entry on your phone and start the connection, then test it with a site you know is reachable. Remove duplicate entries only after the test succeeds. QR codes contain connection credentials; close the QR code window after scanning and avoid saving it in screenshots, screen recordings, or shared photo albums.

Common Questions About Syncing Across Devices

The PC has updated, so why is the phone still showing the old list?

Open “Subscription Group Settings” in v2rayNG and check that the URL matches the PC's current group. Then choose “Update Subscription” from the menu in the top-right of the node list. If you see HTTP 401 or 403, check whether the subscription credentials have expired or been revoked. If the update succeeds but old nodes remain, make sure you're viewing the subscription group—not a manually added entry created by scanning a QR code.

Why are there different numbers of nodes on the same subscription?

First, check that both devices updated successfully and that you're comparing the same group. Then look for filters or node formats that one client may not recognize. If the provider offers multiple subscription formats, confirm both devices use the same one; matching group names alone aren't enough.

Why does a node work on the PC but not on the phone?

Check that the connection is running on the phone and VPN permission has been granted. Then check whether the target app is excluded from per-app proxy settings. If it still fails, test both devices on the same trusted network, then test the phone separately over mobile data. Change one condition at a time to tell node settings apart from network differences.

Do routing and DNS settings move with the node?

Standard subscriptions and single-node QR codes mainly transfer node details. After migrating, open the routing and DNS settings on both devices and check the fallback resolvers, direct-connection rules, and custom rule order. To verify, test one site expected to connect directly and another expected to use the proxy, then check the logs to confirm the outbound route—don't rely on whether a page loads.