Already using v2rayN on your PC and want the same nodes on Android? Add the same subscription in v2rayNG. For just a few nodes, use share links or QR codes; when replacing a device, restore a backup in the same client. Set routing, DNS, and traffic handling separately on each device—they don’t transfer with the nodes.
Choose a sync method: shared subscription, node sharing, or backup restore
Sharing nodes between two devices usually means each connects to the same remote server—not that your phone connects to your PC’s local proxy. A subscription provides the node list; group names, the selected node, routing, and DNS are generally stored in each client. Changes to local labels or the selected node on your PC won’t carry over to your phone.
- For ongoing use of the same nodes: Save the same subscription URL on both devices and update each client separately. If the provider changes server addresses or removes nodes, there’s no need to resend them one by one. Check the provider’s limits for simultaneous devices, connections, and data usage first.
- To move just one or two nodes: Use a share link or QR code. It captures the settings at the time of export. If the server address, credentials, or transport settings change later, export the node again and replace the old entry.
- When replacing a device or reinstalling: Restore a backup using the same client. Don’t try to import a desktop app’s data directory into an Android client. Even if both use Xray, they may store settings in different formats.
Import the same subscription in v2rayN and v2rayNG
The steps below use the v2rayN 7.x desktop interface and the commonly used Simplified Chinese interface in v2rayNG. Menu labels, button icons, and punctuation may vary slightly by version. Paste the full URL provided by your subscription service, usually starting with https://. Don’t use a node share link copied from the context menu, such as vmess:// or vless://.
Check the subscription URL
If the subscription is already set up on your PC, open v2rayN and go to “Subscription Group” → “Subscription Group Settings.” Find the relevant entry and check its URL. Copy the entire address, including the question mark and everything after it—not just the domain.
Refresh the desktop group
To add it for the first time, go to “Subscription Group” → “Subscription Group Settings,” enter a name and URL, and save. Back on the main screen, select the group, then choose “Subscription Group” → “Update Current Subscription (without proxy).” Update just this group first so it’s easier to identify which subscription has an issue.
Add the subscription on Android
In v2rayNG, open the top-left menu → “Subscription Group Settings” → tap “+” in the top-right corner. Enter a label and the same URL, then tap Save in the top-right corner. Return to the node list, select the group you just added, then open the top-right menu → “Update subscription.”
Test each client separately
Select the same node on both devices and check its protocol, server address, and port. On desktop, choose “Set as active server,” then, if needed, select “Automatically configure system proxy” from the tray’s “System proxy” menu. On Android, tap Connect and approve the system VPN prompt the first time. Then open the same test page on each device.
Even when both clients have fetched the latest subscription, their lists may differ. The server may return different formats to different clients, or one client may not recognize a particular config. Compare update times and the protocol of any missing nodes, then check whether the provider supplies different URLs for desktop and Android. Don’t clear a working group just to make the node counts match.
Move an individual node with a share link or QR code
To move a node from your PC to your phone, right-click it in the v2rayN node list and choose “Share server” to display a QR code. To send it as text, choose “Export selected server share link to clipboard” from the same menu. In v2rayNG, tap “+” in the top-right corner and choose “Scan QR code” or “Import from clipboard,” depending on what you have. To move a node back to your PC, copy its share link from the phone, then press Ctrl + V in the v2rayN main window to import it.
VLESS node checklist
- Server address
- Use the domain or IP address provided by the source
- Authentication
- Use the UUID provided by the source
- Transport
- For example, TCP or WebSocket; match the original config
- Security settings
- Match the original TLS or REALITY settings, and keep any existing custom parameters
If the original node uses REALITY, check the server name, public key, short ID, and other existing fields after import, as well as the address and port.
VMess node checklist
- Server address
- Use the domain or IP address provided by the source
- Authentication
- Use the UUID provided by the source
- Transport
- For WebSocket, check the original path and Host
- Transport security
- If the original node uses TLS, retain settings such as the server name
Don’t copy a sample path, hostname, or port from another node. Using the same protocol doesn’t mean the settings are interchangeable.
Back up config files: restore in the same client, migrate separately across devices
Before replacing a PC, check where v2rayN stores its data. In a common v2rayN 7.x portable setup, the program’s guiConfigs folder may contain both interface settings and the node database; copying just one JSON file may not include your nodes. Don’t overwrite the new device’s data with a single database file copied while the app is running.
- Restore on desktop: Exit v2rayN on the old PC from the system tray. Back up the actual config directory and any separately referenced custom files. On the new PC, test the restore with the same version first. Exit the app before making changes, and keep a copy of the new PC’s original config. After reopening, check the node count, groups, and routing mode before upgrading.
- Restore on Android: If your version of v2rayNG supports exporting and restoring local configs, use that feature to create a backup and import it into the same client on your new device. Check the export instructions to see whether it saves just the node list or all settings. If it exports nodes only, save your per-app proxy list, rules, and DNS settings separately.
- Move between platforms: Use a subscription or share links to transfer nodes, and separately note your domains, subnets, rule order, and expected routing. Re-create the settings on the other device using its supported format. File paths, network interface names, and outbound tags referenced in desktop custom configs may not exist on Android.
Set up routing, DNS, and traffic handling separately
A successful node connection only means a connection can be established; it doesn’t mean the same app’s traffic will take the same route. With the standard system proxy mode on desktop, first check whether the app uses the system proxy. On Android, check that the VPN is running and whether the app is included in or excluded from per-app proxying. Confirm that traffic reaches the client before troubleshooting routing rules.
Set up the same routing requirements on each device
Desktop (v2rayN)
- Go to “Settings” → “Routing Settings” to check the current profile. Note the domains, subnets, and rule order that should go direct or through the proxy.
- If you have a “Bypass LAN” rule, check that it comes before the catch-all rule. Test with an app confirmed to use the system proxy.
Android (v2rayNG)
- Open “Settings” from the top-left menu and check routing, DNS, and “Per-app proxy.” If your version doesn’t let you edit individual rules, don’t paste desktop rules into an unrelated settings field.
- Open one site expected to connect directly and another expected to use the proxy. During troubleshooting, stay on Wi-Fi and avoid switching to mobile data while changing rules.
Test how the rules behave before fine-tuning them. If a rule uses GeoIP or GeoSite data, make sure both clients have the relevant categories. Matching category names alone don’t guarantee the same results.
Local proxy ports and remote node ports are not interchangeable. To troubleshoot desktop ports, open “Settings” → “Parameter Settings” and check the actual listening port, then look in the logs for port conflicts. When importing a node on your phone, keep its remote port—don’t replace it with your PC’s local port.
Common questions about sharing nodes across devices
Why does the subscription update on my PC but time out on my phone?
First check that the URL has no extra spaces and that none of its parameters were truncated. Try again on the same Wi-Fi network. If the network can’t reach the subscription service directly and your phone already has a working node, try updating through the proxy if your version offers that option. If it still fails, check whether the error is a timeout, a certificate issue, or a server rejection. Don’t share full logs containing tokens.
Why can’t my phone connect after importing a node?
Check that you selected the newly imported node and that Android allows the VPN to start. Then compare the address, port, protocol, and transport security settings on both devices. If it only fails on mobile data, test again on the same Wi-Fi network to distinguish a network issue from an import problem. When testing VMess, also check whether automatic date and time are enabled.
Will changes I make to a node on my PC sync to my phone?
No. Both devices update from the same subscription source; they don’t share a local database. To keep manual changes, save the node as a separate entry and share the modified version with the other device. Don’t rely on manually edited fields in a subscription group, as an update may overwrite them.