Client Selection Guide

v2rayN, v2rayNG, and v2flyNG compared

Choose by platform first, then compare the core and workflow. Pick v2rayN for desktop devices; use v2rayNG first for everyday Android use; choose v2flyNG when you specifically need the v2fly core.

Go to Downloads View Comparison

Windows v2rayN macOS v2rayN Linux v2rayN Android v2rayNG first

Full Comparison

Platform, Core, and Feature Differences

Maintenance status in this table is qualitative and does not indicate a fixed release schedule. Feature locations may change as client interfaces evolve, but the platform focus and core direction remain clear.

Comparison Criteria	v2rayN	v2rayNG	v2flyNG
Platform Support	Windows、macOS、Linux	Android	Android
Primary Core	Desktop versions can use the core options provided by each client; common configurations primarily follow the Xray ecosystem	Xray	v2fly
Maintenance Status	Actively maintained	Actively maintained	Actively maintained
Learning Curve	Straightforward basics with many Advanced options	A short everyday connection workflow	Straightforward basics, with core differences to understand
Subscription Groups	Well suited to managing multiple subscription groups, with per-group updates and configuration filtering	Supports subscription import, updates, and configuration-list management	Supports subscription import, updates, and configuration-list management
Routing Rules Interface	The desktop interface manages routing rules, the system proxy, and related Advanced options	Provides routing settings and a per-app proxy entry point	Provides routing settings based on the v2fly core
TUN / System Traffic Handling	Supports TUN-related modes and can also use the system proxy	Uses the Android VPN service to handle traffic, with configurable per-app scope	Uses the Android VPN service to handle traffic and can work with routing rules
Key Features	Multi-platform desktop support, subscription groups, routing-rules UI, system proxy, and TUN configuration	Xray core, per-app proxying, QR code or link import, and quick mobile controls	v2fly core, subscription management, mobile configuration switching, and routing settings
Best For	Desktop users, people managing multiple subscriptions, and Advanced users who need detailed routing	Everyday Android users who need the Xray core and per-app proxying	Users whose subscription explicitly requires the v2fly core or who need to keep a v2fly configuration path
Selection Summary	Best for desktop	Best for Android	Android alternative

Client-by-Client Review

Which Client Fits Each Use Case

The three clients serve different platforms and core paths. Desktop and Android are different use cases, so there is no need to force one client to win in every category.

Best for Desktop

v2rayN: Multi-Platform Desktop Support and Full Configuration Access

Windows · macOS · Linux

v2rayN is a graphical desktop client. Windows users can choose between the desktop edition and the classic WPF edition; macOS offers packages for different processor architectures; Linux provides common package formats. All three desktop systems follow the same product direction, making v2rayN a good fit for users who want a similar workflow across devices.

The usual workflow is to add a subscription group, update subscriptions, select a configuration, and start the system proxy. When you have many subscriptions, groups keep work, home, and other use cases separate. For further tuning, open the routing rules, DNS, system proxy, or TUN-related settings. There are more entry points than on mobile clients, so complete a basic connection first and adjust Advanced settings one at a time.

v2rayN is best for users who work on desktop systems long term, manage multiple subscriptions, need rule-based traffic routing, or want to maintain complex configurations through a graphical interface. If you only need to import one configuration temporarily, you can keep the default routing and basic system proxy settings instead of changing everything on first launch.

Download for Windows Download for macOS Download for Linux

Best for Android

v2rayNG: Xray Core and Per-App Proxying

Android · Xray

v2rayNG is designed for Android and follows the Xray core path. Common tasks are importing configurations, updating subscriptions, selecting a configuration, and starting the connection. Subscription URLs, share links, and QR codes can all create configurations; the available protocols and transport combinations depend on the subscription content and server settings.

Mobile traffic handling relies on the Android VPN service. Per-app proxying limits which apps use the client, making it useful when you only want to handle a browser, messaging app, or designated work app. Routing settings determine where different domains, addresses, or network traffic go. If you are unsure what a rule means, start with the subscription-provided configuration and default options.

For most Android users, v2rayNG is the straightforward choice. The reason is not the number of features, but its clear platform focus, broad Xray core compatibility, and short everyday workflow. When the processor architecture is known, choose the arm64 package; if you are unsure, select the universal version in the download center.

Download v2rayNG View the Configuration Guide

Android alternative

v2flyNG: Choose It When You Need the v2fly Core

Android · v2fly

v2flyNG also targets Android, but follows the v2fly core path. It provides common mobile features such as subscription import, configuration switching, routing settings, and traffic handling through the system VPN service. The basic workflow is similar to other Android graphical clients, but the deciding factor should be the required core, not button placement or interface layout.

When the subscription provider, existing configuration notes, or usage environment explicitly requires the v2fly core, v2flyNG can reduce troubleshooting caused by an inconsistent core path. If no special requirement is stated, most Android users should start with v2rayNG. You can install both clients for separate testing, but only one should handle system traffic at a time to avoid conflicting connection states.

v2flyNG also offers arm64 and universal packages. On mainstream devices, identify the processor architecture first; for older devices, unclear architecture information, or failed installation of a specific package, use the universal version. After importing the same subscription, check the supported protocols, transports, and routing settings for the selected core.

Download v2flyNG View Core Terminology

Use-Case Routing

Choose by Device and Workflow

The recommendations below are based on platform, core, and operational cost. If you already have a working configuration, also follow the client and core requirements specified by its provider.

First-Time Setup

Once the basic workflow works, enable per-app proxying, subscription filtering, or custom routing as needed. This separates installation, subscription, and rule issues, making troubleshooting easier than changing several settings at once.

Advanced

Advanced users often manage multiple subscription sources and divide traffic by domain, address, or application. Before making changes, keep one working baseline configuration, then add rules one at a time. Reload the configuration after each change and verify that the active configuration belongs to the intended subscription group.

Multi-Device Use

A subscription delivers configuration; it does not automatically unify every local setting across operating systems. The desktop system proxy and the mobile VPN service use different mechanisms. When switching devices, confirm the active configuration, routing mode, and subscription update time instead of copying every Advanced option unchanged.

Older Android Devices

Universal packages cover more processor architectures, but actual operation also depends on the system version, the manufacturer’s background-process policies, and device resources. If the connection drops after the screen locks, check the battery-optimization allowlist, background permissions, and per-app scope instead of repeatedly changing subscriptions.

Decision Rules

Do Not Choose by Feature Count Alone

Whether a client fits depends on the platform, core, configuration source, and actual scope of use. More features do not mean every feature needs to be enabled.

01

Lock In the Platform First

Windows, macOS, and Linux go directly to the v2rayN path. On Android, choose between v2rayNG and v2flyNG. When the platform does not match, further feature comparisons have little practical value.

02

Confirm the Core Requirement Next

On Android, check v2rayNG first by default. Choose v2flyNG only when the subscription notes, existing configuration, or usage environment clearly points to the v2fly core. A core name is not a speed tier and does not replace protocol or transport settings.

03

Choose How Traffic Is Handled Last

On desktop, use the system proxy or TUN-related modes as needed. Android uses the system VPN service to handle traffic and can define a per-app scope. If only a few apps need access, start with a narrower scope so the rules are easier to inspect.

04

Keep a Baseline Configuration for Troubleshooting

Add DNS, routing, and subscription filters only after the first connection works. If the connection fails, return to the baseline configuration and confirm that the subscription is updated, the active configuration is selected, the system time is correct, and no other client is handling traffic.

Final Recommendation

Choose v2rayN on Desktop, v2rayNG First on Android

Windows, macOS, and Linux users should download v2rayN. Android users should download v2rayNG first; switch to v2flyNG when the configuration explicitly requires the v2fly core. The download center lists the appropriate packages and processor-architecture options by platform.

View All Downloads Continue to the Guides