Client, Core, and Platform Boundaries

V2Ray Client Comparison

When choosing between v2rayN, v2rayNG, and v2flyNG, start with the device platform, then check which core the configuration requires. For desktop systems, v2rayN is the usual choice; on Android, v2rayNG is generally the first option, while v2flyNG is best reserved for cases that specifically require the v2fly core.

Download Client View Setup Steps

Platform support Proxy core Subscription management Routing rules TUN and VPN integration

Quick Takeaways

Choose by device first

Selection order

Windows、macOS、Linux

Choose v2rayN. It provides desktop access to subscription management, system proxy settings, routing rules, and TUN configuration.

Typical Android use

Choose v2rayNG first. It typically works with the Xray core and routes app traffic through Android's system VPN interface.

A specific need for the v2fly core

Choose v2flyNG. Do not switch clients just because their names look similar; first confirm the requirements of the existing configuration and core.

The client manages configuration and user interaction, while the core handles connections. Whether a subscription works also depends on matching protocols, transport, security parameters, and server-side settings.

Three-Client Comparison Table

This table defines selection boundaries rather than guaranteeing identical features across every package, system version, and configuration. For TUN, VPN interfaces, or background operation, also check system permissions.

Comparison of platforms, core support, maintenance, learning curve, and notable features
Comparison criteria	v2rayN	v2rayNG	v2flyNG
Platform support	Windows、macOS、Linux	Android	Android
Primary core relationship	Typically paired with supported cores such as Xray on desktop; the exact setup depends on the client settings and selected package	Typically uses the Xray core	Uses the v2fly core
Maintenance status	Actively maintained	Actively maintained	Actively maintained, with a focus on v2fly core requirements
Learning curve	Moderate; there are more settings, and you need to understand the differences between system proxy, routing, and TUN	Low to moderate; the first connection requires permission to use the system VPN	Moderate; the workflow resembles other Android clients, but core compatibility boundaries should be understood first
Subscription groups	Well suited to managing multiple subscriptions and groups and switching profiles in a desktop interface	Well suited to importing, updating, and organizing subscriptions on mobile	Manages Android subscriptions with an emphasis on v2fly configurations
Routing rules interface	Offers a more complete desktop workspace for reviewing and adjusting rule sets, domains, and network scopes	Provides mobile routing and per-app settings; complex editing is limited by the screen and system behavior	Provides routing configuration for the v2fly core; verify rule syntax before use
TUN or system-level integration	TUN may be available depending on the client and system; it usually requires additional permissions and should not conflict with other network tools	Routes traffic through Android's VPN interface and can be combined with per-app proxy controls	Routes traffic through Android's VPN interface; behavior still depends on system permissions and background policies
Best suited for	Desktop users, advanced users who need detailed routing, and users managing multiple subscriptions	Most Android users, plus anyone who needs per-app proxying and mobile subscription management	Android users who specifically need the v2fly core or must verify v2fly configuration compatibility

A Closer Look at Each Client

Platform compatibility is only the first step. Reviewing subscription management, application integration, and core compatibility requirements can reduce the need to switch clients after installation.

Windows · macOS · Linux

v2rayN: The Desktop-First Choice

Best for desktop

v2rayN's main advantage is not support for one particular protocol, but its ability to bring subscriptions, server profiles, system proxy settings, routing rules, and TUN controls into one desktop GUI. If the goal is simply to establish a basic connection, start by importing a subscription, updating the list, selecting a profile, and enabling the system proxy; there is no need to edit complex routing rules immediately. Advanced users can use the desktop interface to inspect inbound ports, DNS, rule sets, and the scope of application integration.

It is important to remember that v2rayN is a client, not the Xray core itself. The client stores and generates configuration, invokes the core, and exposes the controls; the core processes protocols and connections. Whether a protocol or transport works depends on three things: whether the client can represent the required settings, whether the selected core supports them, and whether the subscription provides complete parameters.

The system proxy works for browsers and desktop apps that read the operating system's proxy settings. Command-line tools, development environments, and programs that manage their own network connections may not follow it automatically. If a browser works but a terminal does not, first check the terminal's own proxy options and environment variables, then decide whether TUN is necessary. Do not immediately blame the node configuration.

Download v2rayN View the Desktop Setup Process

Android · Xray Core

v2rayNG: The Standard Android Choice

Best for Android

v2rayNG is designed for Android. It can import profiles from links, the clipboard, or subscriptions, then use the system VPN interface to route app traffic through the proxy. When connecting for the first time, Android asks you to approve VPN access; this is a required step for the network integration provided by the system. If another network tool is already using the same interface, both apps usually cannot hold it at once, so check which connection is currently active.

Choosing a mobile client involves more than protocols; background operation matters too. Battery-saving policies may restrict activity after the screen is locked, resulting in a connection that works in the foreground but drops after running in the background. In that situation, check VPN permission, battery optimization, background activity limits, and the manufacturer's auto-start settings in order. Per-app proxying defines which apps are included or excluded; it is not the same as domain routing rules in the core.

v2rayNG typically works with the Xray core and is suitable when the subscription includes the corresponding protocols and security parameters. When migrating a profile from desktop, do not copy only its display name; recheck the address, port, user identifier, transport, TLS, SNI, and other fields. The desktop and Android interfaces differ, but the connection parameters themselves must remain consistent.

Download v2rayNG View Subscription Import Steps

Android · v2fly Core

v2flyNG: Choose It for a Specific Core Requirement

Alternative core

v2flyNG also runs on Android, but it should be chosen because you specifically need the v2fly core, not as a drop-in replacement for v2rayNG. The two clients may offer similar workflows for importing subscriptions, toggling connections, and granting system VPN permission, but their underlying core families, configuration capabilities, and handling of certain parameters are not identical.

Consider v2flyNG if an existing configuration is explicitly marked for v2fly or you need to verify a v2fly routing or transport configuration. If the subscription is primarily built around Xray features, first confirm that the v2fly core can recognize every parameter. Successful import only means that the client read the content; it does not guarantee that the core will execute it as expected or that every node suits the current network environment.

Everyday troubleshooting is similar to that of other Android clients: first confirm system VPN permission, then check that the local connection is running, and finally review subscription parameters and core log messages. If only some profiles fail, compare their protocol, transport, security parameters, and domain settings instead of repeatedly reinstalling the client. This makes it easier to distinguish configuration issues, core compatibility problems, and system background restrictions.

View the v2flyNG Download Page Understand Clients and Cores

Choose by Use Case

A user may have both a desktop device and an Android device, so the right answer is not always a single client. The key is to use the appropriate client on each platform and keep subscription parameters and routing targets clear.

Clients, Cores, and Proxy Configuration

Choosing the right client is only the beginning. Mixing these three layers together makes subscription updates, connection failures, and apps that bypass the proxy much harder to diagnose.

Client management

v2rayN, v2rayNG, and v2flyNG are all GUI clients. They import subscriptions, save profiles, select the active server, invoke the core, and provide controls for system proxy settings, VPN interfaces, per-app rules, and routing edits. A normal-looking interface does not mean that the core has connected successfully.

Core execution

Xray and v2fly are proxy core families. The core reads the configuration generated by the client and handles protocols, transport, security parameters, DNS, and routing. If the configuration contains fields the core does not support, the client may fail to start, connections may fail, or some features may not take effect.

Proxy settings control traffic integration

The system proxy, an app's own proxy settings, Android's VPN interface, and desktop TUN determine how traffic enters the client. If a browser works but a terminal does not, check the integration method first; only after confirming that traffic reaches the client should you inspect core routing and the remote connection.

Recommended troubleshooting order

Confirm the platform: use v2rayN for desktop systems and v2rayNG or v2flyNG for Android.
Confirm the core: for typical Android use, start with the Xray path; choose the v2fly path only when the configuration explicitly requires it.
Confirm the configuration source: verify that the subscription URL works and that the protocol, transport, security parameters, and domain fields are complete.
Confirm application integration: on desktop, check the system proxy, app-specific settings, or TUN; on Android, check VPN permission and the per-app scope.
Handle routing last: add split-routing rules only after the basic connection works, so you do not change multiple variables at once and make the issue harder to isolate.

Common Questions After Choosing a Client

Use the questions below to determine whether you really need to switch clients. Most connection problems should first be investigated through permissions, configuration, and traffic scope.

Should Windows users choose between v2rayN and the two NG clients?

No. v2rayNG and v2flyNG are designed for Android, while v2rayN is the desktop choice for Windows. Similar names do not mean the clients support the same platform, and Android packages should not be used on desktop systems.

A subscription imports successfully but the connection fails. Does that mean the wrong client was chosen?

Not necessarily. Successful import only means that the client could read the subscription. You must also check whether the core supports the protocol and parameters, whether the system clock is accurate, whether the domain and TLS settings match, and whether app traffic has actually entered the client. Review the specific error first, then decide whether to change the core path.

Can v2rayNG and v2flyNG connect at the same time?

On Android, only one app can normally occupy the system VPN interface at a time. Disconnect the current connection before testing the other client. Keep the subscription configuration consistent during comparison and record each core's messages separately, so an interface conflict is not mistaken for an invalid configuration.

Why do some desktop apps bypass the proxy even when the system proxy is enabled?

The system proxy affects only apps that actively read that setting. Some terminal tools, development environments, and programs with their own networking need a separate proxy address or environment variables. Confirm the local listening address and port, then configure the app according to its documentation; evaluate TUN only when broader traffic integration is actually needed.

Do routing rules still matter when TUN is enabled?

They solve different problems. TUN mainly expands or changes how traffic enters the client, while routing rules determine which exit is used by connections that have already reached the core. Enabling TUN does not automatically create split-routing rules suited to your needs; before editing routes, define the domains, network scope, and default exit clearly.