CLIENT SELECTION / 03

V2Ray Client Comparison: v2rayN, v2rayNG, and v2flyNG

The key differences are not the names, but the platforms, cores, and configuration entry points. Identify your device first, then check whether you need advanced routing, TUN mode, or a specific core to quickly narrow the choice.

View client installers Expand comparison table

LAYERED COMPARISON

Platform, Core, and Configuration Comparison

The table shows each client’s capability boundaries; it does not mean every feature is enabled automatically after installation. TUN, Android VPN service, routing rules, and subscription groups still require manual configuration.

Comparison criteria v2rayN v2rayNG v2flyNG
Platform support Windows、macOS、Linux Android Android
Core path Primarily follows the Xray ecosystem and can manage compatible desktop core configurations Xray core v2fly core
Maintenance status Actively maintained Actively maintained Actively maintained
Learning curve Moderate. Basic connections are straightforward, but advanced routing offers many options Low. Mobile controls are focused, and nodes can be selected after importing a configuration Moderate. The workflow resembles common Android clients, but users must understand the core differences
Subscription groups Well suited to managing multiple subscriptions, server groups, and batch updates Supports subscription imports, group management, and node switching Supports subscriptions and node management, with an emphasis on the v2fly core path
Routing interface The desktop configuration controls are comprehensive, making it easy to review and adjust rule sets Provides routing settings, preset rules, and per-app routing controls Provides basic routing configuration; rule capabilities depend on the v2fly core configuration
TUN and traffic capture Supports TUN mode as well as system proxy mode Captures traffic through the Android VPN service and supports per-app routing Works through the Android VPN service; exact behavior is determined by the v2fly configuration
Key features Desktop system proxy, TUN, batch subscription management, and a routing rules UI QR-code import, per-app routing, mobile network switching, and Xray protocol support v2fly core, QR-code import, and Android configuration management
Best for Desktop users who need advanced routing or manage multiple subscriptions Most Android users, as well as users who need Xray core features Users who specifically need the v2fly core or are comparing core compatibility

CLIENT NOTES

In-Depth Client Reviews

A client is the control layer between your configuration and its core. When choosing one, check whether the platform matches, whether the core meets the configuration requirements, and whether the interface supports your everyday maintenance tasks.

CLIENT / 01 Desktop pick

v2rayN: Desktop Configuration and Routing Management

v2rayN supports Windows, macOS, and Linux, making it the only desktop-focused option among the three clients. It brings subscription updates, node switching, system proxy, routing rules, and TUN mode into one interface, making it suitable for desktop environments where configurations need regular maintenance. For users who only need to import one subscription and enable the system proxy, the basic workflow is simple. As server lists, subscription groups, and routing rules grow, however, the interface exposes noticeably more controls than a mobile client.

Its main strength is management, not one-off connections. Multiple subscriptions can be updated and organized separately, routing rules can be reviewed through the graphical interface, and system proxy or TUN can be switched according to the required coverage. If applications that ignore the system proxy must use the same route, TUN is worth exploring. For browsers and standard desktop software, the system proxy is usually easier to troubleshoot.

Choosing the desktop edition or the classic WPF edition is a separate installer-level decision. The desktop edition uses a newer cross-platform interface and suits users who want a similar workflow across desktop operating systems; the WPF edition follows the classic Windows experience. There is no need to install both. Choose one based on your operating system and existing habits, then configure subscriptions and routing.

Platform Windows / macOS / Linux
Configuration focus Subscriptions, system proxy, routing, TUN
CLIENT / 02 Android pick

v2rayNG: Xray Core and Android App Routing

v2rayNG is designed for Android and uses the Xray core. QR-code scanning, clipboard imports, subscription updates, node selection, and the connection toggle all follow familiar mobile workflows. For most Android users, the basic setup is complete after importing a configuration, selecting a node, and allowing the Android VPN service to connect. Its protocol and transport capabilities follow the development of the Xray core, so v2rayNG is usually the more direct choice when a configuration depends on Xray features.

Choosing a mobile client is not only about whether it connects; you also need to understand how app traffic enters the route. v2rayNG captures traffic through the Android VPN service and provides per-app routing settings. If some apps should connect directly while others use the proxy, confirm the routing mode first and then choose the app list. Confusing allowlists and blocklists can send traffic along the opposite path from what you intended.

When you have many subscriptions, keep only the groups you actually need and avoid letting every historical node accumulate in one list. If an update fails, check the subscription URL, the network path used during the update, and client parsing compatibility separately instead of repeatedly switching nodes. v2rayNG works well for everyday mobile use and can share a subscription source with desktop v2rayN, but the routing interfaces and traffic-capture mechanisms differ between the two.

Platform Android
Configuration focus Xray, per-app routing, Android VPN service
CLIENT / 03 Core alternative

v2flyNG: The Android Path for the v2fly Core

v2flyNG also targets Android, but its defining difference is the v2fly core. It is not simply a themed version of v2rayNG, and the similar names do not make the two fully equivalent. The same server details can behave differently across cores and combinations of configuration fields, including differences in support, defaults, or parsing results. This distinction becomes decisive only when the configuration provider explicitly requires v2fly or troubleshooting calls for a comparison between core implementations.

It supports the familiar Android workflows for subscriptions, QR codes, and node management, and it handles app traffic through the system VPN service. The day-to-day operation is familiar, but users need to understand which core ultimately executes the configuration. If a subscription is organized mainly around Xray features, v2rayNG is the easier way to reduce compatibility variables. If an existing configuration has long been maintained around v2fly, v2flyNG preserves a more consistent core path.

Treating v2flyNG as an alternative does not imply weaker maintenance; it simply has a narrower selection criterion. It is better suited to users with existing v2fly configurations, users who need to reproduce specific core behavior, or users troubleshooting whether an issue comes from the client interface or core parsing. For new Android users without a core preference, starting with v2rayNG usually makes it easier to find consistent setup guidance.

Platform Android
Configuration focus v2fly, compatibility checks, existing configuration migration

SCENARIO FILTER

Narrow the Choice by Use Case

The platform determines what can be installed; the use case determines which capabilities you need. The recommendations below tie the choice to observable tasks rather than judging clients by feature count.

DECISION PATH

Four Steps to Choose a Client

The selection process can be split into platform, core, traffic capture, and maintenance. Answer one question at each step so similar product names do not distract you.

  1. 01

    Start with the Device Platform

    Put Windows, macOS, and Linux on the desktop path and choose v2rayN. Android follows the mobile path, where you then choose between v2rayNG and v2flyNG. If the platform does not match, further feature comparisons are not useful.

  2. 02

    Confirm the Core Required by the Configuration

    If an Android configuration explicitly depends on Xray features, choose v2rayNG; if it is explicitly maintained around v2fly, choose v2flyNG. When no core is specified and there is no existing migration requirement, v2rayNG is the more straightforward default.

  3. 03

    Determine the Traffic-Capture Scope

    On desktop, if you only need applications that follow the system proxy, start with v2rayN’s system proxy. Explore TUN when more applications must be covered. On Android, traffic runs through the system VPN service; configure per-app routing only when some apps need an exception.

  4. 04

    Assess Long-Term Maintenance

    The more subscriptions and routing rules you have, the more important stable grouping and a clear update process become. Multi-subscription management is better handled in v2rayN on desktop; on mobile, reduce duplicate configurations, keep only frequently used subscriptions, and record the current routing mode.

FINAL SELECTION

Choose v2rayN on Desktop, v2rayNG First on Android

v2rayN offers the most complete desktop management for Windows, macOS, and Linux; v2rayNG covers most Android use cases with the Xray core; v2flyNG is for configurations that explicitly require the v2fly core or need compatibility comparison. After choosing a client, visit the installer page and select the file matching your system architecture.

Go to the installer page View configuration guide