Sync V2Ray Settings Across PC and Android: Subscriptions, QR Codes & Backups

1. Understand Subscriptions, Node Sharing, and Full Backups

V2Ray is a core project in the proxy ecosystem; v2rayN and v2rayNG are clients that manage nodes and run a core. Client databases, interface settings, and core runtime configurations are different kinds of data. A configuration file that works on a PC is not necessarily a backup that a phone can restore.

“Using the same configuration” usually means using the same server settings on both devices—not sharing local ports, system proxy settings, or Android app lists. Decide what you need to transfer before choosing a method to avoid unnecessary work.

2. Add the Same Subscription on Your PC and Phone

First, get a subscription link from your service provider that works with both clients. Subscription links often contain access tokens, so copy the entire URL and make sure chat apps haven’t inserted a line break or dropped any trailing characters. The steps below use common menu names in Chinese-language interfaces; if your version puts the option in a sidebar or overflow menu, look for the equivalent subscription group settings.

1. Add the Subscription on Your PC

   In v2rayN, open “Subscription Group” → “Subscription Group Settings,” create a group, and enter an “Alias” and “Optional Address (Url).” Save your changes. The alias is only for identifying the group on this device and doesn’t affect the other one.

2. Update the List on Your PC

   Return to the main window and select “Subscription Group” → “Update All Subscriptions (without proxy).” If the subscription URL can only be reached through an existing proxy, choose “Update All Subscriptions (through proxy)” instead; you’ll need a working node first.

3. Add the Subscription on Your Phone

   Open “Subscription Group Settings” from the v2rayNG side menu, tap “+,” and enter a “Remark” and “Optional Address (Url).” Paste in the same subscription link and save. Don’t enter it in the server address field for a manually added node.

4. Update the Group on Your Phone

   Return to the configuration list and select the subscription group. Open the overflow menu in the top-right corner and choose “Update current group subscription.” Once the nodes appear, select one and tap the connect button. On the first connection, follow Android’s prompts to authorize the VPN connection.

5. Test the Connection on Each Device

   On both devices, check the selected node and runtime logs, then open the same reachable HTTPS page. Confirm that it loads fully rather than relying only on the latency reading. Updating a subscription and connecting through a proxy are separate operations.

Automatic updates also need to be configured on each device. Don’t assume that updating the desktop client will immediately refresh your phone’s list. If the phone hasn’t been used for a while or Android has restricted its background activity, update manually before deciding the subscription has expired.

3. Move a Single Node with a Share Link or QR Code

If you only have one manually configured node, you don’t need to set up a subscription service just to move it. In v2rayN, right-click a node in the server list to find the share or export options. You can copy a share link to the clipboard or display a QR code. Menu labels vary by version; make sure you’re sharing the selected node, not the entire subscription URL.

• Transfer by text: Copy the node share link and send it to your phone through a trusted channel. In v2rayNG, tap “+” on the main screen → “Import from clipboard.” Check the node details after importing.
• Transfer by QR code: Display the node’s QR code on your PC. In v2rayNG, tap “+” → “Scan QR code” and grant camera access when prompted. If the QR code is dense, enlarge it and make sure the full border is visible.
• Transfer back to your PC: In v2rayNG, long-press a node and use the share option to get its link. Copy it on your PC, then in v2rayN open the “Servers” menu and select “Import batch URLs from clipboard.”
• Check for duplicates: Confirm the destination group before importing. Repeated taps can create duplicate entries, which won’t automatically become an updatable subscription.

vmess:// and vless:// are common protocol prefixes for node share links, not a standard format for subscription update URLs. A QR code may also contain a subscription URL, so check what the client detects after scanning; seeing content isn’t enough to confirm a successful transfer.

4. Use Backups to Restore; Use Share Links to Move Between Clients

Client backups and core JSON serve different purposes. A client backup restores client data, while core JSON describes the inbounds, outbounds, routing, and other settings needed for a core to run. Copying a JSON file to another client won’t restore subscription groups, update schedules, or interface preferences.

1. Record your setup first. Note the source client version, core, installation method, and backup date. Keep an older backup before upgrading; don’t rely solely on data rewritten by the new version.
2. Use the built-in backup option when available. If your version offers configuration backup, export, or restore under “Settings” or the overflow menu, use the matching options and check what they include. Similar names don’t mean the file formats are interchangeable.
3. Exit the desktop client before backing up files. If you’re backing up the data directory, exit v2rayN from the system tray first and make sure its process has stopped. Then copy the actual user data directory. Paths may differ between portable and installed versions; copying only the application itself isn’t enough.
4. Make another backup before restoring. Save the current data on the destination device and, if possible, test the restore with the same client version. Don’t overwrite another client’s directory with the source client’s database files.
5. Reauthorize after restoring. Check the core path, local ports, system proxy, and Android VPN permissions. Copying files between devices won’t grant system permissions for you.

When moving from v2rayN to v2rayNG, you’ll usually only need to transfer the subscription or node, then recreate routing and DNS settings manually. Android per-app proxy rules refer to apps installed on the phone; there’s no direct equivalent to desktop processes or system proxy settings to import. If an app isn’t installed on the new device, its old selection won’t work as-is.

5. Check Ports and Traffic Routing Separately, Even with the Same Node

Local listening ports don’t need to match across devices. On a PC, 127.0.0.1 means the PC itself; on a phone, it means the phone itself. Your phone can’t use that address to reach your PC’s proxy port, and everyday cross-device setups don’t require exposing the PC’s listener to your local network.

These numbers refer to ports at different levels; they aren’t recommended fixed values to change to. The server port must match the node settings. The local port is for apps on that device and can be configured in the client. Entering the remote port as the local port will usually make the connection fail.

• Works in your desktop browser, but not in other programs: Check whether the program uses the system proxy. Enabling the system proxy doesn’t send every network request through the core. If you need to route more traffic, review the permissions and routing requirements for TUN first.
• Only some apps work on your phone: Check v2rayNG’s per-app proxy settings and confirm whether it proxies only selected apps or bypasses them. It’s easy to reverse these options by mistake.
• The same node behaves differently on each device: First confirm that the updated address, port, and security settings match. Then check each device’s network, DNS, and routing. Your PC’s Wi-Fi and your phone’s mobile network may take different routes.
• One device stops working after an update on the other: Check whether the older device still has an outdated node, then see if the server limits simultaneous connections. Don’t start by deleting all your data or disabling certificate verification.

6. Treat Subscription Links and QR Codes as Credentials

A subscription URL may let anyone who has it download a full set of nodes, while a node QR code may contain the identity settings needed to connect. These aren’t ordinary product links. Screenshots, clipboard history, and device cloud sync can all retain information you meant to send only to another device.

• Copy these only between your own devices or through trusted channels. When you’re done, clear temporary text, screenshots, and clipboard history containing the full link.
• Store backups somewhere with access controls. For long-term storage, use encrypted storage and keep the unlock information separate from the files.
• When sharing troubleshooting screenshots, obscure the full subscription URL, user IDs, and QR codes. If you need to show the protocol, transport type, or error message, include only those non-sensitive details.
• If your subscription URL is exposed, reset its token using an option provided by your service provider, then replace the URL on both devices. Whether the old node credentials are also invalidated depends on the server’s rules.

A simple order of operations works well: use the same subscription source on both devices, select a working node on each, then configure traffic routing and local settings separately. Sharing is for moving a single node; full backups are mainly for restoring the same client. Keep these tasks separate so you know what will transfer—and what you’ll need to set up again—when changing devices.