For keeping computer and Android nodes aligned over time, use the same subscription in v2rayN and v2rayNG. For a few static nodes, export share links or scan QR codes. When replacing a computer and preserving routing, groups, and local ports, use a complete configuration backup. This guide covers the steps, sync boundaries, and post-migration checks for all three methods.
Define What Needs to Be Synced First
“Syncing a V2Ray configuration” can mean different things. Server address, port, user ID, transport, and TLS parameters are connection details. Subscription groups, node labels, routing rules, DNS, system proxy settings, and local listening ports belong to the client. Each migration method carries different information.
VMess and VLESS share links are suited to moving individual nodes. Subscription links are better for maintaining a changing node set. A complete v2rayN backup targets a similar desktop environment and preserves more local state, but it should not be copied directly to v2rayNG.
Shared Subscription
RecommendedAdd the same subscription address on the computer and Android device. After updating, both receive the same server entries. New, removed, or changed nodes only require a subscription update on each device.
Best for: Long-term use on two devices and frequently changing node lists
Config Export and Import
Export share links for selected servers, or back up the v2rayN data directory. Share links work across clients; a full backup is better when replacing a computer and preserving local settings.
Best for: Batch migration of static nodes and replacing a desktop device
QR Code Migration
Display a QR code for one node on the computer, then scan it with v2rayNG. The process is quick, but the imported node will not continue updating with the original device.
Best for: Temporarily moving one or two nodes when copying text is inconvenient
Bottom Line: Separate Node Sync from Client Backup
If only the server list must match across devices, use a subscription or share links. To preserve routing, DNS, groups, and interface settings, create a complete v2rayN backup. Separating these needs prevents a situation where the node is present but proxy behavior differs after import.
Option 1: Use the Same Subscription on Both Devices
A subscription has the lowest maintenance cost. Server-provided subscription content typically contains multiple VMess or VLESS entries, which the client parses into its local list. Updating a subscription on the computer does not automatically refresh the phone, so sharing one subscription means using the same data source, not real-time communication between devices.
In v2rayN, open 「Subscription Groups」 → 「Subscription Group Settings」, create a group, and enter the subscription address and a label. Save it, then choose 「Subscription Groups」 → 「Update All Subscriptions」 to retrieve the nodes. If the subscription address can only be reached through an existing proxy, choose the corresponding proxied update method; on a regular network, start with the direct update method.
In v2rayNG, open 「Subscription Group Settings」 from the side menu, add the same address, and save it. Return to the server list and choose 「Update Subscription」. Menu wording may vary slightly by version, but the sequence remains the same: save the subscription source first, then refresh the server list manually.
- Update the subscription on the computer first, and note the group name, node labels, and number of entries after the update.
- Enter or paste the same complete subscription address on Android, taking care not to omit trailing parameters.
- Update both devices separately, then spot-check the address, port, protocol, and transport of nodes with the same name.
- Test a connection with one node on each device. Do not treat latency figures as a substitute for an actual access test.
- After confirming that updates work normally, set a refresh interval that suits you, such as once every 24 hours.
Option 2: v2rayN Export and Configuration Backup
Export according to what needs to move. To give several nodes to another device, select them in the v2rayN server list and choose 「Server」 → 「Export Selected Servers as Share Links」 to copy VMess or VLESS links. On the other v2rayN installation, choose 「Server」 → 「Import Batch URLs from Clipboard」 to import them in one go.
Menu wording may differ slightly between v2rayN versions, with labels such as “share link” or “batch URL.” To verify that you chose the right function, inspect the export: node migration should produce share text beginning with the protocol name, not a complete JSON file used to run the core.
When replacing a computer while preserving subscription groups, custom routing, DNS, node labels, and local settings, fully exit v2rayN before backing up its data directory. Portable installations usually keep configuration in the user-data location within the program directory; for installed versions, use the configuration or data directory shown under 「Settings」 → 「Parameter Settings」. Restore by installing a similar version, replacing the corresponding data, and restarting the client for verification.
Recommended Approach: Split the Process by Sync Target
Node Migration
- Select the servers to migrate
- Export VMess or VLESS share links
- Import from the clipboard in the target client
- Verify the address, port, and transport parameters one by one
Complete Desktop Backup
- Exit v2rayN, then copy the data directory
- Preserve subscription, routing, and DNS settings
- Restore in a similar client version
- Recheck the system proxy and local ports
Share links transfer server parameters across clients; a complete data directory restores a similar desktop environment. Neither can replace the other.
| Configuration Item | Share Link | Complete v2rayN Backup |
|---|---|---|
| Server address, port, and user parameters | Typically included | Included |
| Subscription groups and update addresses | Not included | Usually preserved |
| Custom routing and DNS | Not included | Usually preserved |
| System proxy toggle state | Not included | Requires manual confirmation after restoration |
| Per-app proxy on Android | Not included | Not applicable |
Option 3: Migrate to v2rayNG with a QR Code
QR migration encodes a share link as an image. It works well when the computer and Android device are both available and only a few nodes need to be moved. In v2rayN, select the target server and display its QR code through the server-sharing function. In v2rayNG, tap the add button in the upper-right corner, choose QR code scanning, and complete the import.
A successful scan only means that the client recognized the QR content; it does not confirm that every field meets the server’s requirements. For VLESS configurations, carefully verify the transport, TLS, server name, fingerprint, Reality public key, and Short ID. For VMess nodes, focus on the user ID, encryption setting, WebSocket path, and Host.
- In v2rayN, confirm that the target node connects successfully before generating its QR code.
- Display the QR code only on a local screen; do not keep it long-term in a publicly accessible image.
- In v2rayNG, choose QR code scanning, grant camera access, and align the full code within the frame.
- After importing, open the node editor and verify the address, port, protocol, transport, and TLS fields.
- Save and select the node, start the connection, then test domain access and app connectivity.
- When migration is complete, close the QR window on the computer and delete screenshots you no longer need.
Bottom Line: Use QR Codes for One-Time Transfers, Not Ongoing Maintenance
When moving three or more nodes, or when node parameters change every month, setting up a shared subscription takes fewer steps. QR codes are a better option only for fixed nodes when passing text between devices is inconvenient.
Why Do Identical Nodes Produce Different Results After Migration?
Matching node parameters only shows that both devices connect to the same server. Actual proxy behavior is also affected by local DNS, routing mode, app proxy scope, system time, and network conditions. If the computer uses a global proxy while Android uses per-app proxying, an unselected app connects directly, making it appear that the node is not working.
Local listening ports must not be assumed to work the same way everywhere. Common v2rayN ports are SOCKS 10808 and HTTP 10809, but installed versions and personal settings may differ. If a browser extension or other program still points to an old port, the proxy may appear unresponsive even when v2rayN is connected. Use the actual local ports shown under 「Settings」 → 「Parameter Settings」.
Routing rules are also local configuration. domain, ip, geosite, and geoip rules added in v2rayN do not travel with a single-node share link into v2rayNG. Configure routing separately on both devices, and because rules are matched from top to bottom, avoid placing broad rules before precise ones.
| Symptom | Check First | What to Do |
|---|---|---|
| Works on the computer but will not connect on Android | System time, network permissions, and complete node parameters | Sync the clock, import again, and verify the TLS and transport fields |
| Different node counts on the two devices | Subscription group, update time, and filter settings | Confirm that the subscription addresses are identical, then update both devices manually |
| The browser cannot use the desktop proxy | 10808, 10809, and the browser proxy type | Match the SOCKS or HTTP type to the actual listening port |
| Some Android apps bypass the proxy | Per-app proxy list | Check include/exclude mode and select the target apps again |
| Different results for domain and IP access | DNS and routing rule order | Check domain resolution and the first matching rule separately |
A Repeatable Multi-Device Sync Workflow
A reliable sync workflow should have one clear source of truth. For long-term use, make the subscription the node source instead of maintaining two hand-edited lists on the computer and Android. Keep temporary test nodes in a separate group and decide whether to retain them after they are confirmed to work.
Back up desktop routing and DNS separately because these settings do not sync through a subscription. Before replacing a computer, record the v2rayN version, data directory location, local ports, system proxy mode, and current routing setup. After restoration, verify each item against the record; this is more reliable than checking only whether the nodes appear.
- Step 1:Use the subscription as the sole source for the server list, with the same group name on both devices.
- Step 2:Set a defined automatic update interval, such as 24 hours, while keeping a manual update option available.
- Step 3:Put temporary share links in a separate group so they do not mix with production nodes when the subscription updates.
- Step 4:Back up the v2rayN data directory once a month, and create an extra backup after changing routing or DNS.
- Step 5:After migration, test websites, apps that require a proxy, and direct-connect targets separately to confirm consistent routing behavior.
- Step 6:Remove invalid nodes and duplicates so same-named nodes do not obscure the one actually selected.
Sync record example
Data source: shared subscription
Desktop client: v2rayN
Android client: v2rayNG
Update interval: 24 hours
SOCKS port: 10808
HTTP port: 10809
Desktop extras: custom routing, DNS, system proxy mode
Android extras: per-app proxy, bypass local networkFrequently Asked Questions
Can the same subscription be added to both v2rayN and v2rayNG?
Yes. Each client downloads and stores its own copy of the subscription, so neither overwrites the other. Updates must also be run separately. If the provider limits the number of simultaneous connections, use the devices according to its service rules.
Can I copy the v2rayN data directory to v2rayNG and use it directly?
No. The two clients use different data structures and platform settings. For cross-client migration, use a subscription, VMess or VLESS share link, or QR code. A complete data directory is only for restoring a similar v2rayN version.
Why did manually added nodes disappear after updating the subscription?
If a manual node is placed in a subscription-managed group, the update process may rebuild that group’s list. Put manual nodes in a separate group and maintain subscription nodes separately from temporary ones.
Can v2flyNG use the same subscription or share links?
Supported protocols and fields depend on the subscription content and the v2fly core’s capabilities. Compatible configurations such as VMess can be imported using the same general approach. If the subscription contains specific Xray parameters, verify every field in v2rayNG using the Xray core first.
Do I need to keep the original QR code after importing it?
No. Once the node is saved in the client, the QR code is no longer involved in the connection. If parameters change later, obtain the latest share content instead of scanning the old image again.