Client comparison · Three options

V2Ray client comparison guide

Three clients cover four platforms: v2rayN targets Windows / macOS / Linux desktops, while v2rayNG and v2flyNG target Android, and the differences come down to core and feature focus. Below we break down platform support, core, maintenance status, setup difficulty, subscription groups, routing rules, TUN support and who each one suits, then give a pick order for four usage scenarios.

  • 3 clients
  • 4 platforms
  • Core Xray / V2Fly

Desktop · Windows / macOS / Linux

v2rayN

Installers for all three desktop platforms, with subscription groups, graphical routing rule editing and a TUN mode switch in one interface — the default pick for desktop use.

Mobile · Android

v2rayNG

Xray core with three routing modes and per-app proxy toggles; import a subscription, pick a node and connect. When you need a v2fly core comparison, switch to v2flyNG in the same download card.

Item by item · 8 dimensions

Three clients compared item by item

The table covers eight rows: platform support, core, maintenance status, setup difficulty, subscription groups, routing rules, TUN support and who each client suits. Maintenance status is described qualitatively, without version numbers or release dates.

v2rayN vs v2rayNG vs v2flyNG: features and positioning
Comparison point v2rayN v2rayNG v2flyNG
Platforms Windows / macOS / Linux Android Android
Core Xray Xray v2ray-core(V2Fly)
Maintenance status Actively maintained; desktop and classic WPF builds released in parallel Actively maintained; updates follow the Xray core Maintained by the V2Fly community; updates follow v2ray-core
Setup difficulty Moderate: many settings; first-time setup means understanding subscriptions and routing Low: import a subscription, pick a node and connect Low: same UI as v2rayNG, same steps
Subscription groups Multiple subscriptions with group management and batch updates Subscription import with a grouped node list Subscription import with a grouped node list (same as v2rayNG)
Routing rules UI Graphical rule editor; add domain / IP / port rules one by one Three routing modes plus custom rules Routing settings shared with v2rayNG
TUN support TUN mode switch on the desktop build TUN mode switch; requires granting the system VPN service Routes traffic through the system VPN service
Best for Users who work mainly on a computer and need fine-grained rules Everyday Android use, where importing a subscription and connecting is enough Users who need a v2fly core for comparison or compatibility checks

On narrow screens the table scrolls sideways to show all four columns; version numbers and installer file names for the three clients are listed on the client cards on the download page.

In depth · Client by client

Which client fits which situation

The table shows the differences; this section covers the trade-offs. Each client gets a short review and a fact list, and every download link in those lists points to the matching platform on the download page.

  • ProtocolsThe Xray core covers VMess / VLESS / Trojan / SS / REALITY; the V2Fly core covers VMess / VLESS / Trojan / SS.
  • SubscriptionsAll three accept share links and subscription URLs, and updated nodes are shown by group.
  • EcosystemAll three build on the open-source Project V ecosystem: free clients, open code and the same configuration syntax.

v2rayN

Top desktop pick Xray core

The main desktop client, with installers for Windows, macOS and Linux. The download page offers two v2rayN builds: the desktop build uses the newer cross-platform interface with the same steps on all three systems, while the classic WPF build keeps the traditional layout and menu structure, so long-time Windows users don't have to relearn anything.

Subscription management handles multiple subscriptions and groups, and batch updates arrange nodes by group. Routing rules come with a graphical editor where domain, IP and port rules are added one by one and take effect immediately. The desktop build includes a TUN mode switch: turn on TUN in settings when you want all system traffic to go through the proxy.

Platforms
Windows / macOS / Linux
Core
Xray
Maintenance status
Actively maintained
Setup difficulty
Moderate
Build options
Desktop / Classic WPF
Download
Windows · macOS · Linux

v2rayNG

Top Android pick Xray core

The default choice on Android, running the Xray core. The interface follows mobile habits: three routing modes (proxy only / bypass LAN / global), per-app proxy toggles, and a single switch for launch on boot — settings sit on one screen, with no menu hunting.

Subscriptions can be imported from share links or subscription URLs, and updated nodes are listed by group; long-press a node to run a real connection latency test and filter out the ones that won't connect. TUN mode has its own switch in the client and asks for system VPN service permission the first time you enable it; if you'd rather not use TUN, connect with the default VPN service method.

Platforms
Android
Core
Xray
Maintenance status
Actively maintained
Setup difficulty
Low
Key settings
Routing modes · Per-app proxy · Launch on boot
TUN mode
Switch inside the client
Download
Android

v2flyNG

Alternative v2fly core

An Android client sharing its UI with v2rayNG, with the v2fly (v2ray-core) core instead. Subscription import, routing settings and the node list look and work the same, so the learning curve is identical.

It is positioned as an alternative: when you want to compare how the v2fly core performs, or check whether a node behaves differently at the core level, install it for cross-checking. The download page also offers arm64 and universal builds; both clients can be installed on the same phone, and you switch by opening the one you want.

Platforms
Android
Core
v2ray-core(V2Fly)
Maintenance status
Maintained by the V2Fly community
Setup difficulty
Low
Positioning
Alternative · Core comparison
TUN mode
Handled by the system VPN service
Download
Android

Use cases · Four situations

Pick a client by use case

The same client can be a good or bad fit depending on the situation. These four cases cover most of the hard choices: first install, split routing, several devices, and older phones.

First install: connect first, tune later

Install v2rayN on desktop and v2rayNG on Android, import a subscription and connect once with the default routing mode (proxy only) to confirm pages load. Only then touch per-app proxy and custom rules, changing one setting at a time so you can roll back easily.

Split routing: prefer the graphical rule editor

To route by domain or IP range, use v2rayN's graphical routing rule editor on desktop — adding rules one by one beats hand-written config. On Android, start with one of v2rayNG's three routing modes and add custom rules on top. Field names differ between the two, so rules must be checked item by item when moved.

Multiple devices: import the subscription URL separately

The same subscription URL can be imported into v2rayN and v2rayNG, each keeping its own node list. Everything else is not shared: routing rules, per-app proxy and launch on boot must be set up on both sides. When switching devices, copy the subscription URL rather than exporting a config file.

Older phones: choose the universal build

On phones from before 2015 or 32-bit devices, pick the universal Android build instead of arm64; both v2rayNG and v2flyNG universal builds sit on the same client card on the download page. On older phones, leave TUN off at first and connect with the default VPN service method for stability.

Decision path · Four steps

Four steps from device to core

Work through them in order and you'll know which client to install and which package to download within four steps.

  1. Step 1: choose by device

    Desktop (Windows / macOS / Linux) means v2rayN; Android means v2rayNG. Together the two clients cover four platforms, so there's no need to mix one client across devices.

  2. Step 2: confirm the Android core

    Use v2rayNG with the Xray core by default; install v2flyNG only when you need a v2fly core for comparison. The two can coexist with separate subscriptions and no interference.

  3. Step 3: choose the desktop build

    The download page offers two v2rayN builds: pick the desktop build for a consistent cross-platform interface, or the WPF build if you prefer the traditional layout and menus. Keep only one to avoid two sets of config overwriting each other.

  4. Step 4: verify the connection once

    Import a subscription, pick a node, turn on the proxy and open a test page to confirm the exit address changed. Run a real connection latency test on nodes first to filter out the ones that won't connect. Full steps are in Getting started.

Coexistence and switching

v2rayNG and v2flyNG can be installed on the same phone, and you switch by opening the one you want; on desktop, keep only one v2rayN build. The three clients can share subscription URLs, but routing rules and per-app proxy settings are independent, so re-check them after switching clients.

Verdict

v2rayN on desktop, v2rayNG on Android

Desktop · Windows / macOS / Linux

v2rayN

Installers for all three platforms, with subscription groups, graphical routing rules and a TUN mode switch in one interface — the pick for everyday desktop use.

Download v2rayN

Android

v2rayNG

Xray core with three routing modes and per-app proxy; when you need a v2fly core comparison, choose the v2flyNG package on the same download card.

Download v2rayNG