September 30, 2026 · Platforms · About 8 min read

Share V2Ray Settings Across Devices: Subscription Links, QR Codes, and Backup Files

Compare three ways to sync nodes and rules between a PC and Android: use the same subscription, scan a QR code to import one node, or restore a backup. Learn when to use each method and what to check.

At a glance

For the same nodes on your PC and Android device, add the same subscription on both and update each one separately. To copy a single node temporarily, use the QR code generated by the client. When switching devices and keeping local groups or settings, check what the same client’s backup and restore features include. Verify routing rules and system proxy behavior separately: a successful import doesn’t guarantee both devices will behave the same way.

Choosing between subscriptions, QR codes, and backups

Use the same subscription

Recommended

Each device fetches its own copy of the node list from the subscription provider. Renaming a node, adding one manually, or enabling a routing profile on your PC won’t update the subscription URL. Even with automatic updates enabled, each device updates on its own.

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

Share a node by QR code

The QR code copies the connection details for the specific node selected when it was generated. If the source node’s address or port changes later, the imported copy won’t update. A node QR code is not the same as a subscription QR code, so make sure the share menu is for the selected node before generating one.

Best for: trying one node temporarily or moving a manually added configuration

Restore a client backup

A backup is a local snapshot. Whether it includes nodes, subscription groups, or app settings depends on the export feature. Even if two clients can both read a type of JSON, that doesn’t make their backups interchangeable.

Best for: moving to a new device or reinstalling the same client

Use one subscription on your PC and Android device

The steps below use common menus in desktop v2rayN and Android v2rayNG. Menu labels and button positions may vary by version. If you can’t find the option, make sure you’re in subscription management, not the screen for manually adding a server.

  1. Check the subscription URL

    Copy the full subscription URL from your provider, including its query parameters. Don’t paste a single-node vmess:// or vless:// share link into the subscription field, and don’t use the provider’s account login page URL as a subscription source.

  2. Add a subscription group on desktop

    In v2rayN, open “Subscription Group” → “Subscription Group Settings,” click “Add” or the plus button, enter a name and subscription URL, then save. Back on the main screen, select the group and use the corresponding “Update current subscription” option in the “Subscription Group” menu. If prompted to update through the proxy or directly, choose based on whether your current network can reach the subscription source.

  3. Save the subscription on Android

    In v2rayNG, open the top-left menu → “Subscription group settings” → the plus button in the top right. Enter a remark and URL, then tap the check mark in the top right to save. Return to the node list, select the group you just created, and choose “Update subscription” from the top-right menu. Saving the URL alone won’t add nodes to the list.

  4. Test the connection on each device

    Start by manually updating the subscription on both devices. Check that the target group has new entries, then compare a node with the same name on each device, including its protocol, server address, and port. Finally, connect on both devices and test the same destination site. Matching node counts don’t prove the connections work.

A successful update in v2flyNG doesn’t mean every node will connect. v2rayNG uses the Xray core, while v2flyNG uses the v2fly core; don’t assume protocol and feature support based on the client name. For example, if a node uses xtls-rprx-vision, check that the receiving client’s core supports it. Don’t remove or change the Flow field just to get the import to work.

Import one node with a QR code

  1. In v2rayN’s main list, select a node, right-click, open “Share server,” and display its QR code. If the menu offers a bulk export option, exit multi-select mode and leave only the node you want to share selected.
  2. In v2rayNG, tap “+” in the top right → “Scan QR code.” Grant camera access when prompted, then scan the code on your computer screen. After importing, look for the new entry in the current list or all configurations, and check its address, port, and transport settings in the edit screen.
  3. Give the test copy a remark that identifies its source, such as “Desktop QR test,” then select it and connect. If scanning fails, copy the single-node link from the desktop share menu and send it to your phone over a private channel. In v2rayNG, use the “+” menu to import from the clipboard. Don’t upload the link to an online decoder.

You can transfer a node the other way too: use the share option on an Android node to copy its link, then import it on desktop from the clipboard via the “Server” menu. QR codes and links may contain authentication details, so don’t post them in group chats or public screenshots. If they’re exposed, deleting the image won’t invalidate the credentials; ask your provider to replace them.

Restore backups and migrate routing rules

Use the backup and restore features provided by the same client whenever possible. If the menu only offers a share link or single-configuration export, treat it as a node export—not a way to restore all app settings. Before migrating, note the app versions on both devices. If the backup format has version requirements, follow the client’s instructions rather than overwriting newer data with an old file.

Back up the same client

What to save
The backup file exported from the original device
Before restoring
Back up the destination device’s existing data first
After restoring
Check the groups, nodes, and subscription URLs
Old device
Clean it up only after the new device passes testing

If you’re prompted to overwrite data, first check whether the destination device has local nodes you want to keep.

Rebuild settings in a different client

Node source
The same subscription or a single-node share link
Example LAN rule
Direct connection for 192.168.1.0/24
Rule order
Place specific exceptions before broader rules that could match them
Local port
Check the actual listening port on the destination device

Replace the example subnet with your actual network range. A local listening port is not the node’s server port.

In v2rayN, open “Settings” → “Routing Settings” on desktop to review the active rule set. Record each rule’s match criteria, outbound route, and order—not just the rule set’s name. On Android, recreate the rules using the options available in the receiving client. If a desktop rule matches by process, don’t use the desktop process name as an Android app rule. System proxy settings and Android VPN routing also cover different traffic. If an app behaves differently, first check whether its traffic is being routed through the proxy, then adjust the rules.

Test at least two kinds of traffic: one that should connect directly, such as a LAN service you’re authorized to access, and one that should use the proxy, such as a site you’ve chosen for comparison. If LAN traffic fails, check the address range and rule order, then confirm that the receiving device allows LAN traffic. Store backups containing private settings somewhere access-controlled, and delete temporary copies used during the transfer afterward.

Common issues after syncing

Why does my phone still show old nodes after I updated on my PC?

On your phone, switch to the target subscription group and manually choose “Update subscription.” If that fails, check that the full URL saved on both devices is identical, then review the update message on your phone. If the update succeeds but old entries remain, check the selected group. Don’t mistake a locally imported QR-code copy for a subscription entry.

Why can a node connect on my PC but not on my phone, even though they have the same name?

The same name doesn’t guarantee the settings match. Compare the protocol, server port, transport settings, and TLS options, then check the phone’s core log to see whether configuration parsing, the handshake, or the connection timed out. If the core won’t start, troubleshoot compatibility first instead of repeatedly changing routing rules.

Can both devices connect at the same time?

That depends on your subscription provider’s connection or device limits. First test each device on its own, then connect both at once and compare. If only simultaneous connections fail, check the service terms and account status rather than assuming the import is at fault.

Choose a client for your device

Choose a client for your device. After installation, import the subscription, then check routing and traffic interception settings separately.

Go to downloads View the guide
Download v2rayN and choose a platform