Client Selection

Compare v2rayN and v2rayNG with v2flyNG

The choice comes down to three factors: platform, the core required by your nodes, and routing complexity. Start with v2rayN on desktop; on Android, choose based on the Xray or V2Fly core.

View client downloads Open comparison table

Platform support Xray and V2Fly Subscription management Routing rules Traffic handling

CLIENT SELECTOR Actively maintained

v2rayN Desktop client

Windows macOS Linux

v2rayNG Android · Xray

Android first choice

v2flyNG Android · V2Fly

Alternative core

Desktop: v2rayN Android: v2rayNG

Side-by-side comparison

Platforms, cores, and configuration options

The table below describes each client’s role. Protocol support also depends on the node configuration, selected core, and its supported features—not just the name shown in the interface.

Comparison factor	v2rayN	v2rayNG	v2flyNG
Platform support	Windows、macOS、Linux	Android	Android
Primary core	Xray, with management options depending on the client	Xray	V2Fly
Maintenance status	Actively maintained	Actively maintained	Maintained
Learning curve	Moderate. Many options, but desktop menus are well organized	Low. Import a subscription, then choose a node and connect	Low. The workflow resembles common Android networking tools
Subscription groups	Well suited to managing multiple subscriptions, server lists, and groups	Supports subscription import, updates, and grouped use	Supports basic subscription import and node management
Routing rules interface	Full desktop configuration, suited to detailed rules and modes	Provides mobile routing settings by app and rule	Focuses on common routing settings and the V2Fly workflow
TUN and traffic handling	Supports desktop TUN mode as well as the system proxy	Takes over device traffic through the Android VPN service	Takes over device traffic through the Android VPN service
Standout features	Subscription groups, system proxy, routing rules interface, TUN, and tray controls	Xray protocol support, QR code import, per-app routing, and quick mobile connections	V2Fly core workflow, QR code import, subscription updates, and basic routing management
Best for	Desktop users, people managing multiple subscriptions, and users who need granular routing	Most Android users and anyone using nodes with Xray-specific features	Users who specifically need the V2Fly core or compatibility with existing configurations

Client-by-client review

Where each client fits

These are not simply different performance tiers. v2rayN handles desktop management, while the two NG clients target Android; their main distinction is the core ecosystem and configuration compatibility.

Desktop first choice

v2rayN: a complete desktop configuration hub

Windows · macOS · Linux

v2rayN brings node management, subscription updates, the system proxy, and routing rules into one desktop interface. After importing a subscription, you can browse server configurations by group and choose system proxy or TUN mode. For users who only need a single node, the initial interface may feel busy; when managing multiple subscriptions, switching routing schemes frequently, or reviewing runtime logs, those options become a clear advantage.

v2rayN is commonly used with Xray configurations, making it a strong fit for nodes that use Xray features such as VLESS, REALITY, or XTLS Vision. For standard VMess, VLESS, or Trojan configurations, follow the parameters provided by the service provider. Seeing a protocol name in the client does not eliminate the need to set required fields such as the transport, TLS, and server name.

Key strengthsCentralized desktop settings and clear subscription groups Keep in mindTUN may require system permissions and suitable drivers

Go to the v2rayN download page

Android first choice

v2rayNG: a popular mobile choice for Xray nodes

Android · Xray

v2rayNG keeps the workflow short: import a subscription or single configuration, update the server list, choose a node, and start the system VPN service. Common controls are available on the main screen, making it approachable for first-time mobile setup. QR codes, clipboard content, and subscription links cover the usual import methods, and moving an individual configuration between devices is straightforward.

Its primary core is Xray, so v2rayNG is usually the first option when a subscription includes Xray features such as REALITY or XTLS Vision. Per-app routing lets you include or exclude selected apps from traffic handling, while routing settings process destination addresses and rule matches. After changing these options, reconnect the current node so the new configuration takes effect.

Key strengthsBroad Xray support and a straightforward mobile workflow Keep in mindBattery optimization may affect background connections

Go to the v2rayNG download page

V2Fly alternative

v2flyNG: the choice when you specifically need V2Fly

Android · V2Fly

v2flyNG follows the V2Fly core path and suits users who have confirmed that their node parameters are compatible with V2Fly or who need to preserve an existing V2Fly configuration workflow. It also covers basic tasks such as subscription import, node selection, QR scanning, and connection through the system VPN service, so it is not limited to advanced users. The key question is core capability—not whether the interface looks similar.

If a subscription clearly depends on Xray-only features, choose v2rayNG first. If the configuration comes from a V2Fly environment and its protocol and transport parameters are supported, v2flyNG will more closely match the original runtime conditions. On older devices, also check the processor architecture and system version requirements when choosing a universal package. Being able to install a client does not mean every core feature is suitable for an older system.

Key strengthsA clear focus on the V2Fly core Keep in mindConfirm first whether the node depends on Xray features

Go to the v2flyNG download page

Use-case guide

Choose a client by how you use it

The platform narrows the candidates; the core determines compatibility. Use the scenarios below to narrow your choice, not to replace the node’s parameter documentation.

Key differences

How to choose between the Xray and V2Fly cores

Xray and V2Fly both belong to the broader Project V technology ecosystem and support multiple proxy protocols and transports, but their feature development is not fully synchronized. Xray adds features such as REALITY and XTLS Vision, so nodes containing these fields generally require the Xray core. V2Fly continues to maintain its own protocol and transport implementations and suits configurations within its supported feature set.

Start by checking the subscription or node documentation. If you see Xray-oriented parameters such as REALITY, Vision, or specific flow-control fields, use v2rayN or v2rayNG. If the configuration is explicitly marked V2Fly and uses a supported standard protocol and transport combination, consider v2flyNG. Seeing only VMess, VLESS, or Trojan is not enough to decide, because the same protocol can use different security layers and transport parameters.

The client is only the configuration entry point; the core actually establishes the connection. A successful import only means the client read the fields—it does not mean the selected core supports every parameter. If the connection fails after import, check the address, port, user ID, transport, security settings, server name, and core type in that order, then review the first specific error in the client log.

Core selection path

Confirm the platform

Use v2rayN on desktop; on Android, compare the two NG clients.

Read the node requirements

Pay close attention to REALITY, flow control, TLS, and transport-layer fields.

Match the core

Use v2rayNG for Xray configurations; V2Fly configurations may use v2flyNG.

Verify after connecting

Check the logs, routing mode, and system traffic-handling status.

Bottom line

Choose v2rayN on desktop and v2rayNG on Android

When desktop use requires subscription groups, the system proxy, TUN, and a routing rules interface, v2rayN offers the most complete coverage. For everyday Android use, choose v2rayNG; select v2flyNG only when you specifically need the V2Fly core or must preserve a compatible configuration.

Desktop recommendation

v2rayN

Works on Windows, macOS, and Linux. It brings server lists, subscription updates, the system proxy, routing rules, and TUN configuration together in one desktop interface, making it suitable for growing from basic connections to granular management.

Download the Windows version

Download for macOS Download for Linux

Android recommendation

v2rayNG

Suitable for most Android use cases, especially when a subscription includes Xray features. The connection workflow is clear, and the system VPN service plus per-app settings help control the scope of mobile traffic handling.

Download v2rayNG

View the import and connection guide