For ongoing use on a PC and Android phone, add the same subscription URL to v2rayN and v2rayNG separately. To transfer a single node temporarily, use a share link or QR code. When switching devices, use the client’s backup feature to move its local settings. A subscription provides nodes; it does not sync system proxy settings, per-app proxy rules, DNS, or routing rules. Follow the steps below to import, update, migrate, and verify your setup.
Subscription Sync vs. Local Settings
A subscription URL lets a client retrieve a list of nodes. When two devices use the same URL, they usually receive configurations from the same source, but each keeps its own copy. Updating on your PC does not update your phone. Providers may also return different content based on subscription parameters or client type, so matching node counts alone do not prove that the devices are in sync.
v2rayN is a desktop client, while v2rayNG is an Android client that uses the Xray core. Both can handle compatible node-sharing formats, but their settings files are not interchangeable. Copying the entire desktop configuration folder to your phone will not recreate the same proxy setup.
| Configuration item | Usually included in the subscription? | What to do on each device |
|---|---|---|
| Server, port, and user credentials | Yes | Update the subscription separately and check for the same node |
| Transport, TLS, SNI, and related parameters | Usually, depending on the format | Check that key fields were parsed correctly |
| Currently selected node | Not synced between devices | Select a node on each device; do not rely on list order |
| System proxy and Android VPN permission | No | Enable the appropriate traffic entry point on each device |
| Routing, DNS, and per-app settings | Usually not included in standard node subscriptions | Configure separately and test the actual behavior |
Choosing a Sync Method
First decide whether you need to transfer an updateable source of nodes, a single node, or a client’s local settings. Each requires a different method; importing a QR code once does not provide ongoing sync.
Add the Same Subscription on Both Devices
RecommendedSave the same subscription URL in both clients and update them separately. When the provider changes the nodes, each client can fetch the latest content again. Routing and proxy modes remain managed locally on each device.
Best for: using the same subscription source on a PC and phone over time
Share Links and QR Codes
Export a share link for a selected node, or scan a node’s QR code displayed on your PC with your phone. The import captures the node settings as they are now; it will not follow later changes to the original subscription.
Best for: temporarily transferring one node or troubleshooting differences in subscription parsing
Back Up and Restore Configuration
Use the current client’s backup feature to transfer groups and any local settings it supports. Backup contents and restore formats vary by client, so backups cannot be used interchangeably across clients.
Best for: moving to a new device or saving settings before reinstalling the same client
Import the Same Subscription on Your PC and Phone
The steps below use the “Subscription Group” menu in v2rayN and “Subscription Group Settings” in v2rayNG. Button locations may vary between versions. If the labels differ, look for the page used to manage subscription URLs—not the page for manually entering a server address. Keep any working groups in place until the import is verified; do not delete all existing nodes first.
-
Get the Original URL
Copy the full subscription URL from the subscription management page. Do not copy the browser’s login page URL or remove any parameters after the question mark. Send it to your other device through a private channel you control. When pasting, check that there are no extra spaces or line breaks at either end.
-
Add a Group on Your PC
In v2rayN, open “Subscription Group” → “Subscription Group Settings.” Add a group, paste the URL into “Address,” and give it a recognizable name. Save, return to “Subscription Group,” and choose the relevant update option. For the first update, try “Update all subscriptions (without proxy).”
-
Add the Subscription on Your Phone
In v2rayNG, open “Subscription Group Settings” from the side menu, tap “+,” enter a note and the subscription URL, then save. Return to the main screen, open the top-right menu, and select “Update subscription.” Check that the expected nodes appear in the group.
-
Check Node Parameters
Select a node with the same name on both devices and open its edit screen to compare the protocol, server, port, and transport. For TLS nodes, also check the server name. For VLESS + Reality, retain the required public key, Short ID, Flow, and other fields; do not guess values based on the node name.
-
Enable the Proxy Separately on Each Device
On your PC, configure “System Proxy” in v2rayN as needed. On your phone, select a node and tap Connect; grant VPN permission when prompted the first time. Open the same test page on both devices and check the client logs for connection errors.
If an update without a proxy times out but an existing node still works, connect through that node and try “Update all subscriptions (through proxy)” in v2rayN. Whether v2rayNG can route subscription requests through a proxy, and where to find that option, depends on the current version’s settings. Do not force all update requests through a proxy when no working node is available, or you may get stuck unable to retrieve new nodes.
QR Codes and Share Links: Transfer a Snapshot of a Node
If your PC is connected and you only need one node temporarily on your phone, select the node in v2rayN and look for an option to share the link or display a QR code in the right-click menu. In v2rayNG, tap “+” → “Scan QR code.” For text, use “+” → “Import from clipboard.” Check the node after scanning, then connect.
- Check the QR code type first: Node QR codes usually encode a share link such as
vmess://orvless://. A regular webpage QR code is not a node. A QR code for a subscription URL should be handled through the subscription screen; scanning it does not necessarily create a subscription group. - Transfer one node at a time: A single-node entry is easier to check. If a QR code is too dense, blurry when enlarged, or affected by screen glare, use the full text link instead. Do not try to reconstruct it by joining fragments manually.
- Keep track of the source: Put temporary nodes in a separate group or add a clear note. If the server changes its port or credentials, export the node again. Updating the original subscription will not update this separate node.
- Check the sharing parameters: If the imported node appears but will not connect, compare TLS, SNI, the WebSocket path, or Reality parameters one by one. Sharing formats and parser support vary, so checking only the server address is not enough.
Same Nodes, Separate Proxy and Routing Settings
On a PC, apps that follow system proxy settings typically send their traffic through v2rayN. On a phone, traffic is routed through the VPN interface, with per-app settings determining which apps are covered. These are different entry points. “System proxy enabled” and “global routing rules” are also not the same: the former determines whether traffic enters the client, while the latter determines where traffic goes afterward.
Share the Subscription; Manage Local Rules Separately
Desktop: v2rayN
- Save the same subscription URL and check the update results before use.
- Check the system proxy status and the actual listening port.
- Check direct and proxy rules under “Settings” → “Routing Settings.”
- Apps that do not follow system proxy settings need a separately configured traffic entry point.
Android: v2rayNG
- Update the subscription separately and select the node to use manually.
- Confirm the VPN is connected and has not been replaced by another VPN connection.
- Check routing options and the per-app proxy scope under “Settings.”
- Check whether the system restricts the client’s background activity.
What the devices share is the source of their nodes, not their live status. Update and verify each device separately to confirm its current configuration works.
Do not copy your PC’s loopback address to your phone and use it as the PC’s proxy. 127.0.0.1 always refers to the current device: on a phone, it points to the phone itself, not a PC on the same Wi-Fi network. The values below are examples for recording settings, not universal defaults. Check the client’s current settings and listening logs for the actual port.
Example: Recording the PC’s Local Proxy
- Listen address
127.0.0.1- Local port
10808, example for reference only- App entry point
- System proxy or manually configured app proxy
- Routing checks
- Direct domains, proxied domains, and fallback rules
The port is a local entry point. It is not the server port of a subscription node and does not need to match the port on your phone.
Example: Recording How Phone Traffic Is Routed
- Main entry point
- Android VPN interface
- Local address
127.0.0.1refers to the phone itself- App scope
- All apps or explicitly selected apps
- Routing checks
- Domain rules, IP rules, and DNS behavior
Do not enter the PC’s local port on the phone’s node edit screen. Node parameters should come from the subscription.
To get similar traffic-splitting behavior on both devices, record the same rule targets and order rather than blindly copying configuration text. For example, handle domains that should connect directly first, then proxied domains, and finally check the fallback route. The actual matches still depend on the core and the configuration generated by each client. Check DNS separately too: using the same node does not guarantee that both devices use the same DNS resolution path.
Back Up, Migrate, and Verify a New Device
A full backup is best for moving between installations of the same client. v2rayN’s app settings, node database, and runtime configuration generated for the core serve different purposes. A file named config.json may contain only runtime settings; its presence does not mean it includes every subscription, group, and interface setting. Prefer the backup and restore options explicitly provided by the current client, and check what they include.
- Before backing up: Record the subscription source, group names, current node, routing choices, and DNS settings. Note whether automatic updates are enabled so you do not assume they ran after restoring.
- Use a supported export: If the current client offers a backup feature, export to storage you control. If it does not, save the subscription URL and the settings you need separately. Do not guess what database files or private directories are for.
- Verify the new device first: After restoring, update one group, test one node, then check the routing rules and proxy entry point. Do not immediately overwrite or wipe the old device.
- Remove old copies last: Once the new device is confirmed to work, clean up subscriptions and temporary backups on the old device. Backup files may contain subscription tokens and node credentials, so store them as sensitive data.
For migration between v2rayN and v2rayNG, the safest approach is to add the subscription URL again, import compatible node share links as needed, and rebuild routing and DNS settings from your notes. v2flyNG uses the V2Fly core; being another Android client does not mean it can use v2rayNG backup files or supports every protocol feature in the same way.
| Check | Action | Pass condition |
|---|---|---|
| Subscription source | Open the group settings on both devices and privately compare the full URLs | Both URLs match the expected source and both updates succeed |
| Node parameters | Choose a corresponding node on each device and compare the protocol, port, and security layer | All key parameters are present; matching names alone are not enough |
| Proxy entry point | Check the system proxy on the PC and VPN status on the phone | A test app’s traffic actually passes through the client |
| Traffic routing | Visit sites expected to connect directly and through the proxy on each device, then check the logs | The logged routes match each device’s rules |
| Future updates | Close and reopen the client, then run a subscription update again | The group remains available and the update can be repeated |
FAQs: Syncing Subscriptions Across Devices
Why does my phone still show old nodes after I updated on my PC?
Each device stores its subscription cache separately. In v2rayNG, select “Update subscription” on the main screen and confirm that the update succeeded, then return to the intended group. If the nodes still differ, check that the URLs and query parameters match, and make sure your phone is not using a standalone node imported earlier from a QR code.
Why does the same node work on my PC but not my phone?
First connect both devices to the same network and select the same node to reduce network differences. On your phone, check VPN permission, per-app scope, and the node’s security parameters, then test again on mobile data. If it fails only on one network, look for timeouts or handshake errors in the logs. Do not change the subscription’s port or credentials without checking first.
Will a manual node edit on my phone remain after the next update?
Do not rely on manual edits to subscription nodes being preserved. An update may recreate the node entry. For a temporary test, save the node in a separate local group and note why you changed it. Ask the subscription provider to correct the official parameters so the devices do not drift apart over time.
Can I share a subscription to automatically sync routing rules?
Standard node subscriptions cannot do that. Open the routing settings on each device and compare the rules, their order, and the fallback policy. Use an import feature only if the current client explicitly supports that rule format. Do not treat a client’s full runtime configuration as a universal routing file.