Sync V2Ray Across Devices: Transfer Nodes Between Desktop and Android

Three ways to transfer V2Ray: nodes vs. client settings

“Sync” usually doesn’t mean real-time syncing between devices. Your computer and phone each store their own configuration and update their subscriptions separately. Renaming a node or switching servers on your computer generally won’t change anything on your phone. When your subscription provider updates its content, you still need to refresh it on each device to get the latest node list.

Before transferring, check your subscription provider’s device limit, concurrent connection limit, and data policy. Being able to import the same account on two devices doesn’t necessarily mean both can connect at the same time—or that any number of devices can. Those limits are set by the provider, not by the import features in v2rayN or v2rayNG.

Import the same subscription: create a group and update it on each device

A subscription URL is usually a complete URL starting with https://; its path or query parameters may contain an access token. It serves a different purpose from a single-node share link starting with vmess:// or vless://. Don’t paste a subscription URL into a single-node editor just because both can be copied.

1. Save the original URL

   Get the complete subscription URL for your client from your provider. Preserve its original capitalization, path, and query parameters. If several output formats are available, choose a format for V2Ray share links or for your specific client.

2. Create a group on desktop

   In the v2rayN main window, go to “Subscription Group” → “Subscription Group Settings” and add a group. Enter a recognizable device name in “Alias,” paste the subscription URL into “Optional address (Url)” or “Address,” then save. Field names may vary slightly by version.

3. Update the subscription on desktop

   Go back to “Subscription Group” and select “Update all subscriptions (without proxy).” If your current network can’t reach the subscription URL but an existing node can connect, try “Update all subscriptions (through proxy).” Confirm the update succeeds, then check the node list.

4. Add the URL on Android

   In v2rayNG, open the side menu and select “Subscription group settings.” Tap “+,” enter a “Remarks” label and the “Optional address (Url),” then save. This adds a subscription source; it doesn’t manually add a server.

5. Fetch nodes on Android

   Return to the v2rayNG main list, open the menu in the upper-right corner, and select “Update subscription.” Some versions show “Update current group subscription” or “Update all subscriptions.” After updating, switch to the right group, select a node, and start the connection.

When importing for the first time, note the node count and last update time on both devices. If the computer has 12 nodes but the phone has only 8, first check that you used the same URL, selected the same group, and haven’t applied filters. Then check whether the client skipped unsupported protocols or parameters. A difference in node count alone doesn’t mean the subscription is broken.

Share links and QR codes: transfer nodes from v2rayN to v2rayNG

A single-node transfer captures the parameters as they were when exported. Even if the original node came from a subscription, importing its export on your phone usually creates a standalone node without the subscription URL. If the server’s port or key changes later, import it again or manage it through a subscription instead.

1. Select the node to transfer

   Select the target row in the v2rayN server list and right-click. To copy a link, choose “Share server” → “Export share link to clipboard.” In some versions, the export option appears directly in the right-click menu.

2. Choose how to transfer it

   To send text, use a secure method to transfer the complete share link to your phone. For an in-person transfer, open the QR code option under “Share server.” To transfer multiple nodes, copy multiple links, one per line; don’t join them into a single line.

3. Import on your phone

   In v2rayNG, tap “+” → “Import from clipboard,” or choose “Scan QR code” and point your phone at the computer screen. Grant camera permission when prompted. After importing, confirm that the new entry appears before closing the QR code window.

4. Check the connection parameters

   Open the new node’s edit screen and check the server address, server port, user ID, transport, and TLS settings. For VLESS nodes using Reality, also check the public key, short ID, server name, Flow, and other original parameters.

If the QR code is too dense to scan, enlarge it, increase your screen brightness, and avoid glare. If it still won’t scan, use the complete text link instead. Don’t remove URL-encoded % characters, parameters after &, or the name after #. Matching node remarks alone don’t prove the parameters are identical on both devices.

• VMess: Share links are commonly Base64-encoded. Encoding changes how the data is represented; it does not make it private.
• VLESS: Parameters such as transport, TLS, and Reality may be in the query string. A truncated link can import successfully but fail to connect.
• Transfer back: In v2rayNG, long-press the node and use the share option to copy its link. On desktop, select “Servers” → “Import batch URLs from clipboard.”

Backup files: restore the same client, don’t copy folders across platforms

Share links are mainly for transferring nodes; backups preserve more app state. v2rayN internal configuration files, core runtime configuration JSON, and v2rayNG app backups are different file types. Even if they all use the .json extension, they aren’t interchangeable. The inbounds, outbounds, and routing sections in a core configuration are not the same as a client’s group database.

Before backing up on desktop, note the client version shown under “Help” → “About” and the core type in use. If the portable directory contains guiConfigs, it usually holds data worth keeping. But don’t assume that folder alone contains every setting: installation method, platform, and data location can vary, and external rule files may be stored elsewhere.

1. Exit the client and make sure its tray process has ended. Copy the original app directory and the actual data directory to a separate backup location. Label the backup with the date, operating system, and client version.
2. Before restoring, save the target device’s existing configuration so you don’t overwrite its nodes and groups. For cross-version restores, follow the client’s own migration guidance instead of mixing old and new configuration files.
3. If v2rayNG has no dedicated backup option, save the subscription URL, export manually added nodes, and record your routing and DNS settings. A node export is not a full app backup.
4. After restoring, select the core executable or relevant paths again. Absolute Windows paths won’t work on other desktop operating systems, and desktop client files can’t be copied into an Android app directory.

After the transfer: matching parameters don’t guarantee matching traffic routing

v2rayN is a desktop client, v2rayNG uses the Xray core on Android, and v2flyNG uses the v2fly core. A client accepting a link doesn’t guarantee that its core supports every protocol extension in it. For VLESS, Reality, or specific transport options, check the target core’s supported features rather than relying on the node appearing in the list.

For example, 127.0.0.1:10808 as a local desktop endpoint means the computer’s own loopback address and listening port; it is not the server address. If you enter 127.0.0.1:10808 on your phone, it points to the phone itself, not the computer. This port is only an example to explain what the address means; use the value shown in your settings. Syncing nodes usually doesn’t require exposing the computer’s local listener to your LAN.

• Test one device at a time: Verify the connection on each device separately before testing both at once, so account concurrency limits aren’t mistaken for incorrect settings.
• Change one thing at a time: Confirm the node connects before adjusting routing and DNS. Don’t change the core, proxy mode, and subscription source all at once.
• Latency isn’t a complete test: A latency result only shows that the test path responded. Routing rules, DNS resolution, or app proxy coverage can still prevent an app from working.

FAQ: Importing, updating, and restoring

Keep three clearly labeled items: the original subscription URL, exports of manually added nodes, and settings notes for each device. Use subscriptions to keep nodes up to date, links or QR codes to transfer a few nodes, and a backup from the same client to restore your setup after reinstalling. This makes issues easier to diagnose than repeatedly overwriting internal files across devices.