Narrow down your options by platform, then choose based on your subscriptions and existing configuration. For desktop, start with v2rayN; for a fresh Android setup, start with v2rayNG. Consider v2flyNG only if an existing configuration specifically requires V2Fly.
The key differences are platform support, configuration formats and how traffic is routed. Desktop TUN and Android VPN are listed separately; they are not interchangeable options. Scroll horizontally to view the table on narrow screens.
Feature
v2rayN
v2rayNG
v2flyNG
Platforms
Windows、macOS、Linux
Android
Android
Core
Choose the Xray or sing-box core for your configuration
Xray
V2Fly(v2fly)
Maintenance
Actively maintained; separate desktop and classic WPF editions
Actively maintained; check Android compatibility and core changes
Maintained independently; check release notes for the compatibility you need
Ease of use
Moderate; understand the differences between system proxy, routing and TUN
Easy; import a subscription, choose a node and authorize the connection
Basic connections are straightforward; check configuration fields when reusing an existing setup
Subscription groups
Group subscriptions by source for separate management and updates
Supports subscription groups; switch sources to view their nodes
Supports subscription management; group features depend on the client interface
Routing interface
Manage built-in and custom rules through a graphical interface
Includes routing settings for adjusting common rules
Configure basic routing; custom fields must follow V2Fly syntax
TUN and traffic routing
Supports desktop TUN; availability depends on platform permissions and core configuration
Routes traffic through Android VPN with system authorization
Routes traffic through Android VPN with system authorization
Best for
Users managing multiple subscription groups or needing desktop routing or app traffic capture
Android users starting with a subscription or using an existing Xray configuration
Android users with specific V2Fly compatibility requirements
Using the same core does not mean settings can be imported directly between clients. Check the transport, DNS and routing fields as well as the proxy protocol.
WORKFLOW REVIEW
How the three clients compare in practice
Focus on where settings are changed, which traffic they affect and what needs to be rebuilt when switching clients.
v2rayN
Best for desktop
v2rayN keeps server lists, subscription groups, routing and traffic handling separate. Create distinct groups for work and personal subscriptions. After an update, check the nodes in the relevant group before changing your selection. When setting custom routes, first check whether a rule matches a domain or an IP address, then verify its outbound route. After adding an exception, test one destination that should connect directly and another that should use the proxy. This helps catch rules that are too broad.
If you mainly use apps that follow the system proxy, first check that the system proxy is working. For desktop apps that ignore it, consider TUN and check permissions and local network access separately. On Windows, start with the cross-platform desktop edition. Choose the classic WPF edition if you prefer its interface or need to keep an established workflow. Before switching editions, back up your subscriptions and custom rules; do not assume every local setting will migrate unchanged.
v2rayNG
Best for Android
v2rayNG is a good choice for getting started with a subscription. Add it, update the subscription, confirm that nodes appear in the list, select one and then connect. The first time you use Android VPN mode, Android will ask you to authorize it. If another VPN service is already running, check for conflicts. Seeing VPN connected in system settings only confirms that the traffic route is active; it does not mean the node can successfully handle requests.
For everyday use, keep routing and DNS settings simple. To control whether an app uses the VPN, check the app-proxy list mode and make sure the target app is included. A reversed list mode can look like a node failure. If your node and transport settings are specifically configured for Xray, test them in v2rayNG first rather than switching cores instead of checking the configuration fields.
v2flyNG
V2Fly compatibility option
Choose v2flyNG for compatibility, not because of your phone's age. If you already have a configuration tested with V2Fly, or its documentation explicitly requires that core, try a known-working node in v2flyNG. Before importing, check the subscription or configuration format, then verify the protocol, transport and routing fields. Seeing a node name does not guarantee that every setting was parsed correctly.
If the same subscription shows different node counts or types in different clients, first check that both received identical subscription content. Then compare the supported cores and import formats. Do not reset your entire setup because of one import error. Isolate a single node, verify the basic connection, then add routing and DNS settings back one at a time. This makes it easier to identify whether the issue is configuration syntax, server settings or the device's traffic routing.
SELECTION GUIDE
Choose a client for your setup
Your device determines which clients are available. Change cores or enable extra traffic options only when your configuration or workflow specifically requires them.
DOWNLOAD DECISION
Use v2rayN on desktop and v2rayNG on Android
Visit the download center and choose an installer for your platform and processor. In the Android downloads, choose v2flyNG only if an existing configuration specifically requires V2Fly. After installation, follow the setup guide to import your subscription and test the connection before configuring routing and traffic handling.