V2Ray Client Comparison
For desktop, start with v2rayN; for Android, start with v2rayNG. Consider v2flyNG on Android only when your existing configuration specifically depends on V2Fly.
Platforms, cores, and configuration features
On narrow screens, scroll horizontally to compare all three clients. Maintenance status is a general assessment, not a guarantee of release frequency or support duration.
| Comparison criteria | v2rayN | v2rayNG | v2flyNG |
|---|---|---|---|
| Platform support | Windows、macOS、Linux | Android | Android |
| Core | Supports Xray and other cores; choose based on your protocol and configuration | Xray | v2fly(V2Fly) |
| Maintenance status | Actively maintained | Actively maintained | Community-maintained; check system compatibility before installing |
| Ease of setup | Easy to get started; multiple subscriptions and custom rules require extra setup | Easy to get started; requires Android VPN permission | Core functions are similar; confirm your configuration is compatible with the core first |
| Subscription groups | Create groups by source and manage or update each one separately | Manage multiple subscriptions and refresh them by source | Supports subscription import and updates; check the app's interface for group management options |
| Routing rules interface | Visual rule list for organizing rules by destination and outbound | Common routing options and per-app proxy settings | Common routing options; available rules depend on the core and configuration |
| TUN and traffic routing | Desktop TUN mode; requires the right system permissions and core support | Routes traffic through Android's VPN service | Routes traffic through Android's VPN service |
| Best for | Desktop users, users with multiple subscriptions, and anyone who needs fine-grained traffic routing | Android users who need subscription imports, server switching, or per-app proxy settings | Android users who need to reuse V2Fly configurations known to be compatible |
Desktop TUN and Android's VPN service can both route network traffic, but they differ in permissions, setup, and routing granularity. Don't look for a desktop TUN toggle in Android's VPN permission prompt, and don't assume that enabling the system proxy routes traffic from every app.
How the three clients compare in practice
v2rayN: Multiple desktop subscriptions and visual routing
v2rayN lets you manage subscription sources, the active server, and routing rules separately. With a single subscription, import it, select a server, then enable the system proxy to test your connection. With multiple sources, name groups by source. If an update fails, retry just the affected group so you don't disturb subscriptions that are working. The routing interface also lets desktop users check matching destinations, rule order, and outbounds without rewriting the entire configuration to change one exception.
Windows users can choose between the desktop edition and classic WPF edition based on interface preference. On macOS, check whether your machine uses Apple Silicon or Intel; on Linux, check the processor architecture and package format used by your distribution. These are differences between installation packages, not protocols. If your browser works but an app still connects directly, first check whether it follows the system proxy, then consider enabling TUN. Keep your existing settings before switching, and afterward check that local network access and DNS resolution still work.
v2rayNG: Android subscriptions and per-app proxy
v2rayNG is a good default choice for Android. After importing a subscription, update the list, select a server, start the connection, and approve the Android VPN prompt. A successful subscription update only means the client retrieved the configuration; it doesn't mean the selected server is reachable. For an initial check, test the same app with the connection off and on before setting up per-app proxy rules. This makes it easier to tell a server issue from an app-list issue.
For per-app proxy, first check whether the list includes only selected apps or excludes them; these settings do opposite things. If the connection drops when an app moves to the background, check whether battery management is restricting the client and whether another VPN is routing traffic. If only one app behaves unexpectedly, check the app list and routing rules first rather than reimporting the subscription or reinstalling the client.
v2flyNG: Choose it only for V2Fly configuration compatibility
Choose v2flyNG because your existing configuration depends on V2Fly, not because its name or interface resembles v2rayNG. Before switching, check the subscription's protocols, transport settings, and security parameters. A server appearing in the list doesn't guarantee the core can use all its settings. If the subscription includes configurations that rely on Xray-specific features, such as REALITY servers, stick with v2rayNG. A successful import does not prove compatibility.
To test a migration, start with a known-working server that meets the target core's requirements. Keep the default routing and DNS settings, and compare only the connection result. Once the basic connection works, rebuild per-app rules and DNS settings one at a time. Even with both clients installed on the same device, stop the active connection before testing the other one; otherwise, the system VPN may be taken over by the wrong client and lead to a false diagnosis.
Choose by device and use case
Which client to choose and where to download
For desktop, v2rayN is the top pick: it works with the system proxy out of the box and makes it easy to manage multiple subscriptions and routing rules as your needs grow. For Android, v2rayNG is the top pick for Xray configurations and per-app proxy settings. Keep v2flyNG as an alternative only when you specifically need V2Fly compatibility. Choose an installation package for your operating system and processor architecture, then test a basic connection before changing advanced settings.