v2rayN vs. v2rayNG vs. v2flyNG: How to Choose a V2Ray Client

Compare v2rayN, v2rayNG, and v2flyNG by platform, core, subscription management, routing, and TUN support—with picks for desktop and Android.

At a glance

For desktop, use v2rayN. On Android, choose a core based on your node settings: use v2rayNG for configurations requiring REALITY or XTLS Vision; if your setup specifically targets V2Fly, check v2flyNG first. You can use the same subscription URL on both platforms, but proxy routing, traffic rules, and app lists must be configured separately. When switching clients, test one node before moving your subscriptions and rules.

Platform: v2rayN for desktop, Android based on your configuration

The three clients have similar names, but their supported platforms and cores don't map one-to-one. For example, the v2rayN 7.x series runs on Windows, macOS, and Linux, and offers multiple core options. The two Android clients use Xray and V2Fly, respectively. The recommendation below is for Android users who haven't settled on a core and need support for common node types.

v2rayN

Desktop client. Choose a supported core based on the node type and the options available in your build. Route traffic through the system proxy or TUN.

Best for: Managing nodes and desktop app proxy settings on Windows, macOS, or Linux.

v2rayNG

Recommended

An Android client powered by Xray. Handles common VMess configurations and supports setups that require REALITY or XTLS Vision.

Best for: Using Xray nodes on Android or routing traffic by app.

v2flyNG

An Android client powered by V2Fly. If your configuration is maintained against V2Fly documentation, you can verify it with the corresponding core.

Best for: Using an existing V2Fly configuration or checking whether nodes such as VMess work on Android.

Core compatibility: Check the protocol, transport, and security settings first

The client imports, selects, and manages configurations; the core handles connections and traffic forwarding. A successful import only means the client accepted the input—it doesn't confirm that the core can use those settings. If both clients show a node but only one connects, open the node editor and compare the fields below. Don't rely on the node name alone.

How to tell if a node will work in another client
SettingWhat to checkHow to choose
Protocol and destination portFor example, VMess or VLESS. Use the remote port specified in the node configuration.VMess is available across both core families. A VLESS label alone doesn't tell you whether the full configuration is compatible.
Transport and pathFor example, the WebSocket path and Host header. Check whether the path starts with a slash.The same protocol doesn't guarantee the same transport. If the original node uses WebSocket, don't switch to TCP and retry.
Security type and flow controlFor example, reality and xtls-rprx-vision. Check the security type and flow control separately.For these settings, use the Xray core in v2rayN on desktop or v2rayNG on Android. Don't remove fields just because another core doesn't recognize them.

Bottom line: Test one fully configured node first

Try the same node on the old and new clients to reach the same destination. If it works on the old client but fails on the new one, check the new client's core logs and imported settings before migrating everything.

Keep the remote port separate from the local listening port. For example, a node might use remote port 443, while the desktop client's local mixed listener uses 10808. The first connects to the server; the second accepts requests from apps on your device. These are examples, not universal defaults for all three clients. When configuring a desktop app to use a proxy manually, enter the local address and port the client is actually listening on—not the node's remote port.

Subscription management: Share the URL, not local settings

In v2rayN, open Subscription Groups > Subscription Group Settings, add a group, and save the subscription URL. Then return to the Subscription menu and update it. In v2rayNG, open Subscription Group Settings from the top-left menu, tap the plus button to save the URL, then return to the node list and choose Update Subscription from the top-right menu. v2flyNG also lets you save and update subscriptions by group. Menu locations vary by version; if you can't find an option, check whether you're on the node list or the group editor.

Use one subscription on both platforms, with separate settings

Desktop (v2rayN)
  • Create a group and update only that group, so you can distinguish newly imported nodes from existing manual entries.
  • Choose a node you know works. Test a webpage through the system proxy before deciding whether to enable TUN.
Android (v2rayNG or v2flyNG)
  • Add the same subscription URL. Find a node whose settings match the desktop node; don't rely on its position in the list.
  • Approve the system VPN connection request. If per-app proxy is enabled, make sure the browser you're testing is included.

Using the same URL makes maintenance easier, but the returned content may vary by time or client. The selected node, routing rules, and app list aren't synced by the subscription.

Track two kinds of errors separately. If an update fails, check whether the subscription request returns valid content. If the update succeeds but nodes won't connect, check the import format, core, and handshake logs. Before switching devices, save manual configurations separately and note your routing policy. Subscription URLs may contain access credentials, so don't share the full URL in screenshots or logs.

System proxy, desktop TUN, and per-app proxy on Android

Traffic capture and routing are two separate steps. The system proxy, TUN, or Android's VpnService determines whether traffic reaches the client. Routing rules then decide whether captured connections use the proxy, connect directly, or get blocked. A rule in the routing table can't affect traffic that never reaches the client.

  1. For browser proxying on desktop: In v2rayN, select “Set system proxy” under System Proxy, then test with a browser that uses the system settings. If the browser works but another app is unaffected, check whether that app reads the system proxy settings. Apps with their own proxy options can also be pointed at the local listening port manually.
  2. If a desktop app ignores the system proxy: Try enabling TUN in v2rayN. TUN captures selected traffic through a virtual network interface and may require system approval or elevated privileges. After enabling it, test both regular websites and local network resources. If websites work but local resources don't, check your LAN bypass rules and system routes. Don't route every destination through the proxy as a workaround.
  3. To proxy only selected apps on Android: In v2rayNG, go to Settings → Per-app proxy. To include selected apps in the VPN, turn off “Bypass mode” and select them. To leave a few apps outside the VPN, turn on “Bypass mode” and select the apps to exclude. Reconnect after changing the list, then test one included app and one excluded app.

The VPN status icon means Android has established a VPN interface; it doesn't mean every app's traffic is routed through the remote node. For example, an app can be included in the VPN while a connection to a particular domain goes direct because of a core routing rule. Conversely, if an app is excluded at the system level, changing domain rules won't bring it back into the VPN.

Common issues when switching clients

Subscription update timed out. Will switching nodes help?

First identify whether the subscription URL or the node connection is failing. If the subscription URL can't be reached directly on your current network but you have a working node, connect to it and retry the update using the “through proxy” option, if your version offers one. If the server returns HTTP 401 or 403, check your subscription access and whether the URL has expired.

Why does the desktop show more nodes from the same subscription?

First make sure both clients updated the same group, and check whether the desktop list includes old nodes. Then pick one of the extra desktop nodes and compare its protocol, transport, and security type. The subscription service may return different content, or a client may skip entries it can't parse.

Why can v2rayNG connect to a node imported by v2flyNG, but v2flyNG can't?

Open the node details and check for REALITY or XTLS Vision. If either is present, keep the original settings and use v2rayNG. If it's a common VMess over WebSocket setup, compare the address, port, path, and TLS settings, then use the logs to distinguish a connection failure from a handshake failure.

An Android app still bypasses the proxy after reconnecting. What should I check?

Go back to Settings → Per-app proxy and check that the selected apps and Bypass mode match your intended setup. Force-stop the app, then reopen it to start a new connection. If it's included in the VPN, check whether a core routing rule is sending the destination domain direct.

Clients and downloads