Desktop devices
Choose v2rayN for Windows, macOS, and Linux. Its GUI covers subscriptions, system proxy, routing rules, and TUN, making it suitable for expanding from basic connections to advanced configuration.
Go to desktop downloads ›
Three clients · Choose by device
V2Ray Client Comparison: v2rayN, v2rayNG, and v2flyNG
Start with your device, then consider the core and configuration depth. Choose v2rayN for desktop platforms and v2rayNG for Android; consider v2flyNG when you already rely on V2Fly configurations.
The short answer
The platform determines the starting point; the core sets the configuration limits
These three clients are not simple substitutes on the same platform. v2rayN targets desktop, while v2rayNG and v2flyNG target Android. Rule out unsuitable options by device first, then compare cores, routing methods, and advanced features for a more direct choice.
Everyday Android use
Choose v2rayNG first. Its Xray core, routing modes, remote DNS, per-app proxying, and VPN mode are organized in one settings interface for a clearer setup path.
Go to Android downloads ›V2Fly configuration ecosystem
If your existing setup is based on the v2fly core and you want to preserve its behavior, v2flyNG is an Android alternative. After importing, check the transport and routing parameters.
Read the v2flyNG review ›
Detailed comparison
Platform, core, and feature comparison
“Setup difficulty” describes the amount of configuration needed to import a subscription, choose a routing mode, and establish a connection; it does not indicate feature strength. TUN and VPN modes are also affected by system permissions, network conditions, and client settings.
| Comparison criteria | v2rayN | v2rayNG | v2flyNG |
|---|---|---|---|
| Platform support | Windows、macOS、Linux | Android | Android |
| Primary core | Supports key desktop core configurations such as Xray | Xray | v2fly |
| Maintenance status | Actively maintained | Actively maintained | Maintained |
| Setup difficulty | Moderate; many options, with a clear basic workflow | Low; Android settings are centralized and the connection path is short | Low to moderate; requires understanding V2Fly configuration differences |
| Subscription groups | Well suited to managing multiple subscriptions and server groups | Supports subscription management and group switching | Focused mainly on basic subscription management |
| Routing rules UI | Comprehensive desktop configuration for fine-grained rules | Provides common routing modes and custom settings | Covers basic routing and core configuration |
| TUN / VPN mode | Supports TUN configuration for handling traffic from more applications | Uses Android VPN mode to handle device traffic | Provides Android VPN operation; capabilities depend on the core and configuration |
| Key features | System proxy, subscription groups, routing rules, logs, and TUN | QR-code import, per-app proxying, routing modes, DNS, and VPN mode | V2Fly core, subscription import, basic routing, and Android VPN mode |
| Best for | Desktop users, users with multiple subscriptions, and users who need advanced routing | Android beginners, everyday users, and users who need per-app proxying | Users with existing V2Fly configurations who value continuity with their established setup |
| Selection summary | Top desktop pick | Top Android pick | Android alternative |
On narrow screens, swipe horizontally to view all columns. Before downloading, choose a package that matches your processor architecture; all download options are listed on the downloads page.
Expand review
Which configuration approach suits each client
The comparison table helps you narrow the options quickly; the reviews below help confirm which configuration workflow fits long-term use. Focus on subscription volume, routing complexity, DNS requirements, and device coverage.
A
Top desktop pick
Actively maintained
v2rayN: a complete configuration hub for desktop
Available for Windows, macOS, and Linux. It brings subscription updates, server filtering, system proxy, routing rules, DNS, logs, and TUN into a desktop GUI, making it suitable for managing multiple configuration sources over time.
Choose v2rayNWhere does it stand out?
v2rayN’s main strength is its broad desktop configuration coverage. Beginners can simply import a subscription, choose a server, and enable the system proxy; advanced users can continue with groups, routing, DNS, and TUN. Features unfold progressively, so you do not need to understand every option on your first use.
When multiple subscriptions are involved, the desktop interface is better suited to filtering and grouping. Server names, subscription sources, and routing policies can be managed separately, while logs help pinpoint the stage of a connection problem instead of repeatedly changing every parameter.
What to confirm before choosing
- If you only need browsers and other applications that follow the system proxy, start with system proxy mode.
- If you need to cover applications that ignore the system proxy, evaluate TUN mode and its permission requirements.
- The desktop version and classic WPF version use different interface paths; choose according to your current system and workflow.
- After changing routing rules, reconnect to ensure the new configuration is fully loaded.
B
Top Android pick
Actively maintained
v2rayNG: Xray core with integrated Android settings
v2rayNG targets Android, and initial setup usually starts with a subscription link or QR code. Routing modes, remote DNS, per-app proxying, Mux, and automatic subscription updates are grouped together, making it suitable for Android users who want a clear GUI.
Choose v2rayNGWhy is it the top Android pick?
The Xray core offers broad support for common protocol and transport combinations, while v2rayNG turns core settings into an approachable Android interface. For everyday use, you do not need to edit a complete configuration file: import a subscription, choose a server, confirm the routing mode, grant VPN permission, and start testing.
Per-app proxying is especially useful on mobile devices. You can specify which apps enter the proxy path and which keep their normal network route. Compared with handling the entire device uniformly, this works better when you need to control background traffic or separate work apps from everyday apps.
Configuration checklist
- After a subscription update, confirm that the current server is still in the expected group.
- If a webpage will not open, check VPN permission, routing mode, and remote DNS in that order.
- After enabling per-app proxying, verify whether the list uses include mode or exclude mode.
- After changing networks, reconnect to refresh the VPN tunnel in the system.
C
Android alternative
Maintained
v2flyNG: continue using V2Fly core configuration habits
v2flyNG also runs on Android, but its focus is the v2fly core. It is better suited to users who already understand V2Fly configuration structures and whose subscriptions and server parameters are organized around that core.
View v2flyNG downloadsWhere it fits
If your existing setup has long relied on V2Fly behavior, staying within the same core family can reduce parameter decisions during migration. Basic subscriptions, server selection, routing, and Android VPN operation remain available, and the everyday connection flow is similar to that of common Android clients.
It should not be treated as a fully equivalent replacement for v2rayNG simply because the names look similar. Their core directions differ, and whether the same shared configuration works directly depends on the protocol, transport, security parameters, and core support. If import succeeds but the connection fails, return to the configuration source and confirm its core requirements.
What to confirm before choosing
- Confirm that the subscription or individual configuration explicitly supports the v2fly core.
- Do not compare interface labels alone; check the transport and security parameters.
- On older devices, confirm the processor architecture before choosing an arm64 or universal package.
- When migrating from another client, review DNS and routing settings one by one.
Choose by use case
How to choose for beginners, advanced users, multiple devices, and older phones
The client name is only the entry point. The practical choice depends on your device, existing configuration, and the traffic you need to control. The four cases below cover common decision paths.
Key capabilities explained
The practical differences between subscription groups, routing UI, and TUN
These terms often appear together, but they solve different problems. Understanding their boundaries helps you avoid switching clients for an advanced option you do not actually need.
Subscription groups
Subscription groups separate different configuration sources and narrow the selection in the list. With many subscriptions, v2rayN benefits from more desktop space and better filtering; v2rayNG is suited to maintaining a small number of everyday groups on mobile.
Groups do not automatically fix invalid configurations. If nodes disappear after an update, first check the subscription URL, update result, and filtering conditions rather than immediately changing routing or DNS.
Routing rules UI
The routing interface assigns domains, addresses, or application traffic to different outbounds. v2rayN is well suited to reviewing multiple rules and their priorities on a large screen; v2rayNG offers common modes and a mobile settings entry point, making it practical to start with a preset and add rules as needed.
Rule order can affect matching results. Record the current mode before editing, reconnect afterward, and test destinations that should use the proxy separately from those that should connect directly.
TUN and Android VPN mode
TUN handles traffic from applications that do not actively read system proxy settings. On desktop, v2rayN provides the relevant configuration; Android clients establish a tunnel through the system VPN interface. The goals are similar, but their permissions, DNS behavior, and routing implementations are not interchangeable.
If the system proxy already covers the current application, there is no need to enable TUN just for completeness. Enable and configure it step by step only when you need games, command-line programs, or other special applications to use the proxy.
Final recommendation
Choose v2rayN for desktop and v2rayNG for Android
This is the default choice for most users. Put v2flyNG among the top candidates only when an Android configuration explicitly depends on V2Fly core behavior. Once the client is chosen, open the downloads page and select the package for your platform and processor architecture.