Choose Between Three Clients
v2rayN, v2rayNG and v2flyNG Client Comparison
Narrow the options by platform first, then compare the core, subscription management, routing interface and system traffic handling. Start with v2rayN on desktop and v2rayNG on Android; choose v2flyNG when v2fly core compatibility matters.
3 clients
Xray · v2fly
Desktop · Android
Selection Order
Platform → Core → Features
The Bottom Line
Platform First, Core Second
These three clients are not interchangeable on the same platform. v2rayN targets desktop systems, while v2rayNG and v2flyNG are primarily for Android. Choose by device first, then consider configuration depth and core preference; this is usually faster than comparing every feature.
Choose v2rayN for Desktop
Works on Windows, macOS and Linux, with subscription groups, server filtering, routing rules and TUN settings in one graphical interface.
Go to Windows Downloads →Choose v2rayNG for Android
Powered by the Xray core, with a clear setup flow for everyday subscriptions, per-app proxy and Android system VPN mode.
Go to Android Downloads →Choose v2flyNG for the v2fly Core
When an existing setup is built around the v2fly core or needs consistent behavior with it, v2flyNG is the more direct Android alternative.
View v2flyNG Downloads →
Feature-by-Feature Comparison
Platform, Core and Configuration Comparison
“Easy” and “Moderate” describe the learning curve for first-time installation, subscription import and proxy-mode switching—not the number of features. Swipe horizontally on a phone to view the full table.
| Comparison Criteria | v2rayN | v2rayNG | v2flyNG |
|---|---|---|---|
| Platform Support | Windows、macOS、Linux | Android | Android |
| Primary Core | Primarily follows the Xray core family, with desktop core and configuration management | Xray | v2fly |
| Maintenance | Actively Maintained | Actively Maintained | Community Maintained |
| Learning Curve | Moderate. Basic connections are easy; routing, DNS, TUN and multiple subscriptions require more understanding. | Easy. Importing a subscription, selecting a server and starting a connection take only a few steps. | Easy to moderate. Basic connections are straightforward, but check configuration compatibility with the v2fly core first. |
| Subscription Groups | Well suited to managing multiple subscriptions, with groups, notes and server filters for organizing large lists. | Supports subscription imports, updates and basic grouping for everyday mobile management. | Supports common subscription imports and updates, focusing on basic connectivity and core compatibility. |
| Routing Rules Interface | Ample desktop space makes it suitable for reviewing and adjusting complex domain, IP, process and outbound rules. | Provides mobile routing settings and per-app proxy for common direct, proxy and block rules. | Provides basic routing configuration for common rules built around the v2fly core. |
| TUN and System Traffic Handling | Supports desktop TUN and system proxy modes, with a deeper configuration surface. | Uses Android VpnService to establish a system VPN connection and supports per-app proxy. | Uses Android VpnService to handle device traffic for standard mobile connectivity needs. |
| Key Features | Multiple subscription management, server filtering, routing-rule UI, system proxy, TUN, logs and connection diagnostics | QR code and clipboard imports, per-app proxy, routing settings, connection tests and mobile shortcuts | v2fly core, subscription imports, basic routing and Android system VPN connectivity |
| Best For | Desktop users, people managing multiple subscriptions, and advanced users who need fine-grained routing or TUN | Android beginners, everyday mobile users, and anyone needing the Xray core with per-app proxy | Users with existing v2fly configurations, a clear need for the v2fly core, or a preference for established configuration habits |
Read the Detailed Review
Which Client Fits Each Use Case?
The feature table helps rule out platform mismatches quickly; the notes below help assess the management cost of long-term use.
Desktop Pick
Xray Ecosystem
v2rayN: A Desktop Configuration and Management Hub
v2rayN’s strength is not just connecting to servers; it brings the desktop tasks people use most into one place. With many subscriptions, organize them by source, filter servers by name or other criteria, and inspect routing modes, rule order and outbound paths in a graphical interface. System proxy works well for browsers and apps that follow system settings, while TUN handles a broader range of network traffic. Choose between them based on the use case.
It has far more settings than mobile clients, so first-time users should understand the roles of “servers,” “subscription groups,” “system proxy,” “routing” and “TUN.” For a basic connection, there is no need to adjust everything at once: import the subscription, select a server and enable the system proxy. Once the connection is stable, add DNS, rule sets and TUN step by step for clearer troubleshooting.
Best for: Windows, macOS or Linux users who need multiple-subscription management, fine-grained routing, process-based split tunneling, log troubleshooting and desktop TUN.
v2rayN Desktop Settings
System Proxy
Subscription GroupsManage by source
Routing RulesMatch in order
TUN Mode
Android Pick
Xray Core
v2rayNG: A Simpler Everyday Android Experience
v2rayNG reduces the core mobile workflow to importing a configuration, selecting a server and starting the connection. Subscription links, clipboard content and QR codes are common import sources; after importing, update the subscription and switch configurations from the server list. The first time a system VPN connection starts, Android asks for VpnService permission. This is the normal step required to create a local VPN tunnel.
Per-app proxy is one of v2rayNG’s most practical mobile features. Choose which apps use the current connection or, conversely, which apps bypass it, reducing the need to switch global settings. Routing settings work well for common domain and IP rules, but editing many complex rules is less intuitive on a phone than on a desktop. For complex setups, organize them on desktop first, then import them to the phone for verification.
Best for: Android beginners, users who need the Xray core and per-app proxy, and anyone who mainly manages servers through subscriptions.
v2rayNG
Update SubscriptionRun manually
Per-App Proxy
Routing SettingsRule mode
Local DNS
Android Alternative
v2fly Core
v2flyNG: Choose It When You Need the v2fly Core
v2flyNG and v2rayNG may appear suited to similar situations, but the selection criteria differ. It uses the v2fly core, making it a better fit for users whose configurations are built around that core, who know its parameters, or whose provider explicitly recommends it. Basic use still centers on subscription import, server selection and Android system VPN connectivity, so switching from another mobile client does not require relearning the entire workflow.
If a subscription depends on Xray extensions, v2rayNG is usually the easier choice. If the configuration follows the standard V2Fly direction and should behave consistently with an existing environment, v2flyNG is a better fit. Installing both Android clients does not mean switching back and forth frequently; sticking with the client that matches the subscription makes it easier to tell whether an issue comes from the configuration, network or app settings.
Best for: Users who specifically need the v2fly core, have experience with related configurations, use standard protocol combinations, or want an Android alternative for core compatibility.
v2flyNG Configuration Highlights
Core Typev2fly
Subscription Updates
System VPN
Routing ModeChoose by configuration
Use-Case Selection
Choose a Client by Usage Pattern
The learning curve for the same client varies widely by user. Device count, subscription size and whether you need to arrange rules manually matter more than the interface design.
Differences That Cause Confusion
Clients, Cores and Protocols Are Different Layers
v2rayN, v2rayNG and v2flyNG are graphical clients that users operate directly. Xray and v2fly are cores that parse configurations, establish connections and process traffic. VMess, VLESS, Trojan and REALITY belong to the protocol or transport configuration layer. Choosing a client requires checking whether both its platform and core can read the current configuration—not just comparing client names.
A single subscription may contain several protocol combinations. Successful import only means the subscription format was recognized; it does not mean every entry is compatible with the current core. If some servers work while others fail, compare their protocols, transport and TLS parameters first, then decide whether to switch core direction.
-
Step One
Confirm the Platform
Use v2rayN on desktop; on Android, choose between v2rayNG and v2flyNG.
-
Step Two
Confirm the Recommended Core
For the Xray direction, prefer v2rayNG; for the v2fly direction, choose v2flyNG. v2rayN manages desktop use.
-
Step Three
Confirm Advanced Requirements
Check whether you need subscription groups, complex routing, per-app proxy, system proxy or TUN.
Final Recommendation
Choose v2rayN on Desktop, v2rayNG on Android
Windows, macOS and Linux users should start with v2rayN; Android users should generally choose v2rayNG. Select v2flyNG only when the subscription configuration, existing environment or core preference clearly points to v2fly. The download page lists installation options by platform and explains how to choose desktop versions, processor architectures and installer formats.