V2Ray Config Sync Across Devices: Subscriptions, QR Codes, and Backups

Keep the same servers and routing on your PC and Android phone. Compare subscriptions, shared links and QR codes, and configuration backups.

At a Glance

For ongoing use on a PC and Android phone, add the same subscription on both. To transfer a single server, use a share link or QR code; to move to a new device with the same client, consider restoring a backup. Subscriptions don't sync the currently selected server, routing rules, or proxy toggle, so check connectivity and traffic routing separately.

Subscriptions, Shares, and Backups: What Gets Transferred

First, distinguish server settings from client settings. Server address, port, protocol, transport, and security are server settings. Group names, the selected server, outbound rules, and which apps are routed through the client are local settings. Seeing the same server name on both devices only confirms that the labels match—not that the server settings or routing are identical.

Add the Same Subscription on Both Devices

Recommended

Add the same subscription URL on desktop and mobile to get the server list on both. If the subscription provider changes a port, replaces a server, or removes an entry, update the subscription on each device to see the change. Renaming a server or switching servers on one device won't update the subscription itself.

Best for: Keeping the same set of regularly updated servers on a PC and phone.

Share Link or QR Code

Usually transfers only the selected server's current settings. Scanning a QR code and pasting a link are two ways to import it; neither preserves its original subscription group nor sets up future updates.

Best for: Adding one server temporarily or moving a manually added entry that's not in a subscription.

Configuration Backup and Restore

Useful when moving to a new device with the same client or rolling back settings. Whether subscriptions, routing, and local entries are retained depends on what's actually in the backup. A desktop configuration folder can't be imported into an Android client.

Best for: Moving to a new PC while keeping custom v2rayN settings.

Add the Same Subscription in v2rayN and v2rayNG

Use the full URL provided by the subscription page, including its query parameters. A subscription URL and a single-server link are different inputs: add the former as a subscription group, and import the latter from the server menu. Keep the old group during migration, then organize it after the new device has fetched the subscription successfully. This avoids mistaking an import failure for a removed server.

  1. Add a Group on Desktop

    In the v2rayN main window, open “Subscription Group” → “Subscription Group Settings,” add a group, and enter a remarks label and subscription URL. You can use the same label as on the old device for easy identification, but it isn't sent with the request or synced to your phone.

  2. Update the Group on Desktop

    Select the new group, then choose the option to update the current subscription from the “Subscription Group” menu. If the menu offers updates with or without a proxy and the URL is directly accessible, try “Update current subscription (without proxy)” first. If you need a proxy, make sure you already have a working connection. Updating one group at a time makes it easier to identify which URL is causing a problem.

  3. Save the URL on Your Phone

    In v2rayNG, open the top-left menu and go to “Subscription Group Settings” (called “Subscription Settings” in some older versions). Tap the plus icon in the top-right corner, enter a label and URL, then tap the save button. Return to the main list, open the top-right menu, and select “Update subscription.” Saving the URL alone won't fetch a usable server list.

  4. Compare Servers on Both Devices

    After refreshing, find the same server on each device and compare its address, port, protocol, and transport. If the entry counts differ, first check that you're viewing the corresponding group, then check whether a regex filter is configured for the desktop group and whether both devices received the same subscription format. If only a few entries are missing, compare their protocols and security settings.

When using v2flyNG, choose subscription content that works with its core. v2rayNG uses the Xray core, while v2flyNG uses the V2Fly core. A successful subscription fetch doesn't mean every server in it will run on the current core. For example, a VLESS server with REALITY security can't be judged compatible based on the “VLESS” protocol name alone.

Move a Single Server with a Share Link or QR Code

Move to a New PC: Back Up and Restore v2rayN

A full backup is useful when moving to a new PC if you want to keep manually added servers, multiple subscription groups, and custom routing. First note the old client's version and the actual location of its data. For v2rayN installations that use guiConfigs in the program directory, back up that folder. If a separate data directory is configured, back up the directory actually in use. Don't mistake a newly downloaded, empty folder for the old configuration.

  1. After making configuration changes, exit v2rayN on the old PC from the system tray—not just by closing the main window. Wait for the process to exit, then copy the entire configuration directory. Don't copy just one JSON file: servers and groups may also be stored in a database. Save any external files referenced by custom rules separately.
  2. On the new PC, first test the restore with the same v2rayN version as the backup. Confirm the data directory in use, exit the process, and keep a copy of the new PC's original directory. Then restore the full configuration to avoid mixing the old database with individual files from the new setup.
  3. After restarting, check that groups, manually added servers, and routing profiles are present, then test subscription updates and a single-server connection. Update the paths to rule files that point to absolute locations on the old PC. Recheck the system proxy and TUN settings on the new system, too. Once everything works, decide whether to upgrade.

If you're moving to an Android phone, rebuild the server list with a subscription or share link instead. If the app provides a backup and restore option, use only a backup format it explicitly supports. A core runtime configuration describes the outbounds, inbounds, and rules for a particular run; it isn't a full client backup of subscription groups and interface settings.

Check Routing on Both Devices: Matching Rules Don't Guarantee Matching Traffic Capture

Using Both Devices: Share a Subscription, Configure Traffic Capture Separately

Desktop (v2rayN)
  • Go to “Settings” → “Routing Settings” and check the active routing profile. When migrating custom rules, compare the match conditions, rule order, and corresponding outbound.
  • Check the system proxy status in the system tray. With only the system proxy configured, apps that don't use it may bypass the client. If you're using TUN, verify it separately based on its actual status and the apps' behavior.
Android (v2rayNG)
  • Check the routing options under “Settings” in the sidebar. Recreate the intended direct, proxy, or block behavior; don't copy desktop outbound labels or local file paths.
  • Check “Per-app proxy” and the app list. If an app isn't actually included in traffic capture, changing domain rules won't route its requests through the core.

First confirm that requests are reaching the client. Then test the same domain that should connect directly and the same domain that should use the proxy on both devices.

If you can't connect after importing, distinguish between two ports: the remote port in the server settings moves with the server configuration, while each device sets its own local listening port. They aren't interchangeable.

443
Example remote ports; use the values in the server settings
10808
Common v2rayN local listening ports; check the parameter settings

If both devices use the same server but only one connects, compare the server details and core compatibility first. If both connect but an app behaves differently, check whether it's included in traffic capture, then review rule order, domain resolution, and rule-set contents. This separates server migration issues from local routing issues without repeatedly importing the same subscription.

v2rayN ClientFind downloads by platform