For desktop, start with v2rayN. On Android, choose based on your existing configuration: use v2rayNG for Xray setups that need VLESS + REALITY, or consider v2flyNG to keep using a V2Fly configuration. For a first install or device migration, test one known-working configuration first: import it, connect, and confirm apps are routed as expected before moving the full subscription.
Choose by device first: v2rayN for desktop, then pick an Android core
A client imports subscriptions, edits nodes, and controls how traffic enters the proxy; the core establishes connections and applies routing. Similar names don't mean the apps, menus, or configuration files are interchangeable. On desktop, the main differences are how each client integrates with the operating system. On Android, check which core your configuration requires.
| Client | Platform | Core options | Common tasks |
|---|---|---|---|
| v2rayN | Windows、macOS、Linux | Supports multiple cores; check the build and configuration to see which core actually runs | Manage nodes and subscriptions in the main window. After enabling the system proxy, test with the app you want to use. |
| v2rayNG | Android | Xray | Choose a node from the configuration list, then grant VPN permission when prompted at startup. |
| v2flyNG | Android | V2Fly | Manage nodes in the configuration list. After connecting, check the system VPN status and which apps are covered. |
Before downloading v2rayN, check your operating system and processor architecture. If Windows offers desktop and WPF editions, choose based on your interface preferences and installation requirements; WPF is a UI technology, not a different proxy protocol. If Android offers ARM64 and universal packages, choose ARM64 if your device supports it; otherwise, the universal package is a safe option. Architecture determines whether an app can run, not whether it supports a node's protocol.
Xray vs. V2Fly: Check the full configuration, not just the protocol name
If your Android configuration comes as a vless:// link, check the security type, transport, and flow control in the local node details first. For example, if the security type is reality and the flow control is xtls-rprx-vision, choose an Xray build that supports those settings. Seeing VLESS alone isn't enough to determine compatibility. Don't remove flow control or change the security type to TLS just to accommodate a client; the altered configuration may no longer match the server.
v2rayNG: Check Xray configuration support
RecommendedA good first choice on Android when your configuration explicitly requires Xray. For VLESS + REALITY, check after importing that the security type, server name, public key, and short ID match the original configuration. Use the original flow control setting; don't add one unless specified.
Best for: Android users migrating Xray nodes or who specifically need VLESS + REALITY.
v2flyNG: Keep using V2Fly configurations
If you already have a configuration verified with V2Fly, start by testing it with a core from the same family. For example, with VMess + WebSocket + TLS, check the WebSocket path, Host, and TLS server name as well as the UUID. Host and TLS server name are separate fields; don't copy one into the other just because an example uses the same value for both.
Best for: Users whose server is configured for V2Fly or who want to keep their existing Android setup.
Test one node before moving your subscription
If you only have a subscription URL, open a frequently used node in your still-working client first. Note its protocol, transport, and security type, then test that same node in the new client. Change only the client, not the node or routing settings at the same time. This makes it easier to tell whether a failure comes from field parsing, core compatibility, or local proxy routing.
Using one subscription on desktop and Android: test app routing on each
Updating a subscription fetches and parses configuration; it doesn't test the connection. Even if both devices can update from the same URL, they may show different node lists because they support different link formats and fields or use different local filters. Desktop system proxy settings and Android per-app lists aren't transferred with the subscription either.
Test both devices: same subscription, same node
Desktop: v2rayN
- Open “Subscription Group” → “Subscription Group Settings,” add a group, and enter the URL. Save it, then update the group from the subscription menu. The wording of the update option may vary slightly by version.
- Select the test node. On Windows, check whether “Set system proxy automatically” is enabled under the tray menu’s “System Proxy” option. On macOS and Linux, check the proxy settings in the system network settings, then test with the app you want to use.
- If an app doesn't use the system proxy, configure the proxy type and port in the app. Check the actual listening port under “Settings” → “Parameter Settings.” Enter
127.0.0.1:10808only if the mixed port is set to10808.
Android: v2rayNG or v2flyNG
- Using v2rayNG as an example, open “Subscription Group Settings” from the side menu, add the URL, then return to the configuration list and update the subscription from the top-right menu. Menu names in v2flyNG depend on the installed version.
- Select the same node, tap Connect, and approve the system VPN request. Leave per-app filtering off at first and test the connection in a browser. Then check the apps you want routed, one by one.
- After enabling per-app settings, check whether the list is set to “Proxy selected apps only” or “Bypass selected apps.” Then test one app that should use the proxy and one that should connect directly to make sure the list works as intended.
Test the connection and apps on each device first. Enable automatic updates or custom routing only afterward, so you don't introduce multiple variables at once.
Client selection FAQs: Imported successfully but can't connect?
Why do two devices show different node counts for the same subscription?
Record the update time and target group on each device first, and check whether one is still showing an old cache. Then see whether the missing nodes all use one protocol or only a few individual entries are missing. If an entire protocol is missing, check the client's support for that protocol and subscription format. For individual entries, check for duplicate names, filtering settings, and whether each link imports on its own. When asking for help, share field names and error messages only; redact the full subscription URL and credentials.
A browser works on Windows, but another app doesn't?
Keep the current node and routing settings, then check whether the app uses the system proxy. If it requires manual setup, choose an HTTP or SOCKS proxy in the app's network settings and verify the local listening protocol and port. Even if the remote node is correctly configured for 443, that isn't the local listening port.
Android says connected, so why does another app still connect directly?
A VPN status only confirms that the system has established a local VPN session; it doesn't guarantee that a particular app is routed through the proxy. Turn off per-app filtering and test the same app again. If that fixes it, check whether the app list is set to include or bypass the selected apps. If the problem persists, check whether the client's routing rules send the destination directly. Change one setting at a time while troubleshooting.
A new client seems slower. Is one speed test enough to choose?
Use the same device, network, node, transport settings, and test target. Alternate between clients, record at least three results per client, and note any failures. Latency shown in a node list usually reflects a particular probe, not download throughput. Confirm both clients are actually routing traffic through the proxy before comparing medians. If the variation is greater than the difference between clients, favor the one with better configuration compatibility and a smoother everyday workflow.