Client Comparison

V2Ray Client Comparison

v2rayN, v2rayNG, and v2flyNG: choose by platform first, then compare cores and routing features.

Desktop and phone clients handle proxy traffic differently. On desktop, first check whether apps use the system proxy. On Android, decide which apps should use the VPN. Consider the core before the interface and workflow only when your configuration specifically requires a certain core or feature.

Platform and Feature Comparison

Compare each feature across clients. On narrow screens, scroll horizontally; you can also focus the table and use the arrow keys. Maintenance status is a general guide, not a promise about release frequency or platform compatibility.

Feature v2rayN v2rayNG v2flyNG
Platform support Windows、macOS、Linux Android Android
Core Xray by default; choose a compatible core based on your node configuration Xray, for configurations that specifically require Xray features V2Fly, for configurations that need to retain V2Fly compatibility
Maintenance status Actively maintained; choose between the desktop and classic WPF editions Actively maintained; check system requirements before installing Community-maintained; check release notes for update cadence
Ease of use Moderate: after importing a subscription, choose between the system proxy and TUN Easy: import a subscription, select a node, then grant VPN permission Similar basic workflow; migrating from Xray requires an extra compatibility check
Subscription groups Supports subscription groups and group updates, making it easy to manage multiple sources Manage subscription sources in Subscription Group Settings Supports subscription import and updates; recheck sources and nodes when migrating
Routing rules Manage rules in Routing Settings and review their order and outbound settings Configure common routing rules and per-app proxy settings. Per-app proxy filters traffic by app, not by domain. Configure common routing rules; check custom rules against the fields supported by V2Fly
System proxy and TUN Includes System Proxy and Enable Tun Mode options; permissions and traffic coverage vary by system Routes traffic through Android VpnService; there is no desktop-style TUN toggle Also routes traffic through Android VpnService. A different core does not mean a different traffic-handling method.
Best for Desktop users, people managing multiple subscription sources, and anyone who needs to edit routing rules individually Android beginners and users who need per-app proxy settings or an Xray configuration Users who specifically need V2Fly compatibility and are willing to check migration settings one by one

Three Client Reviews

v2rayN

Best for desktop

When you need to check node sources, rule order, and traffic entry points in one place on desktop, v2rayN makes it easy to find all three in the same interface.

Managing multiple subscriptions and desktop routing

Manage subscriptions by source in Subscription Groups. If one group fails to update, check that source on its own instead of deleting your entire node list. Test the connection in a browser that uses the system proxy before enabling Enable Tun Mode. If you only need proxy access in a browser, there's usually no need to capture more traffic. When editing Routing Settings, check the order of exception and fallback rules, then test destinations that should connect directly and those that should use the proxy. Windows users can choose between the desktop and classic WPF editions: start with the cross-platform desktop edition for a fresh install, or consider WPF if you want to keep an established workflow. There's no need to run both clients just to compare their interfaces.

v2rayNG

Best for Android

For a first-time Android setup, or when a subscription specifically requires Xray features, start with v2rayNG.

Choosing VPN permission and per-app proxy settings

Add a source in Subscription Group Settings and update it, then select a node and connect. The first time you connect, Android will ask for VPN permission. If another app is already using the system VPN, stop it before testing. For per-app proxy settings, first check whether the list means “only include selected apps” or “exclude selected apps.” Then test with one app that should use the proxy and one that shouldn't. You can use an app list alongside domain-based routing, but changing the list won't fix a node handshake failure. If the connection drops only after the screen locks, check whether battery management is restricting background activity before assuming the node is incompatible.

v2flyNG

V2Fly alternative

Choose v2flyNG when you need to keep using the V2Fly core. A different core doesn't automatically mean better battery life or better support for older devices.

Migrating from an Xray configuration: what to check

First, test with a node known to meet V2Fly requirements, then restore subscriptions and routing gradually. A subscription parsing successfully only means the client can read its entries; it doesn't mean the core can connect using the original configuration. If an entry depends on Xray's REALITY or a specific flow, don't assume it will work unchanged with V2Fly. Check the protocol, transport, and security options against the server's requirements. For older devices, check system requirements and processor architecture before choosing an installer. If the test connection fails, keep the working configuration in your original client. Migrate special rules only after basic connectivity works; this makes it easier to identify differences in the core versus the rules.

Choose by use case

First-time setup: test one connection

Use v2rayN on desktop and v2rayNG on Android. Import a subscription, update it, then select a node manually. On desktop, test the system proxy first; on Android, grant VPN permission. Confirm that you can open a site you can normally access before changing routing. If you change the port, DNS, and traffic capture mode all at once, it will be hard to tell what caused a failure.

Advanced routing: define the scope first

To manage rules by domain, address, or outbound, check their order in v2rayN on desktop. To let a specific phone app bypass the proxy, start by checking the per-app list in v2rayNG. If you choose v2flyNG to keep an existing V2Fly configuration, retain the original outbound and match conditions first. Confirm the basic connection works before adjusting fallback rules.

Multiple devices: share subscriptions, configure each separately

Use v2rayN on desktop and v2rayNG on Android. If your service allows it, import the same subscription source on both devices. Active nodes, system proxy settings, local listening ports, and per-app lists still need to be configured on each device. If one device works and the other doesn't, first confirm that both subscriptions are updated and the same node is selected. Then compare traffic capture and routing settings on each device.

Older phones: check system requirements before choosing a package

Check the Android version first, then see whether the device can run arm64 apps. A 64-bit processor doesn't mean the installed system supports 64-bit apps. A universal package can help when you're unsure about the device architecture, but it won't lower the minimum Android version. If the app installs but disconnects often after the screen turns off, check background restrictions first. Don't switch to v2flyNG based on the phone's age alone.

What to check before switching clients

  1. Keep your working configuration.Note the node, core, and routing mode you're currently using. Subscription URLs may contain access credentials, so keep them on your own device and don't include them in screenshots or public logs.
  2. Pinpoint where the failure occurs.If a subscription update fails, first check whether its source is reachable. If nodes appear but won't connect, check node settings and core logs. If the logs show a successful connection but websites won't load, check traffic capture, DNS, and outbound settings instead of repeatedly importing the subscription.
  3. Change one setting at a time.Compare on the same device and network. Exit the old client or clear its proxy settings before starting the new one. Test one connection that should bypass the proxy and another that should use it. Being able to open a website alone doesn't prove that routing is working as expected.

Bottom line

For desktop, choose v2rayN; for Android, choose v2rayNG.On Android, choose v2flyNG only when you specifically need the V2Fly core. Select an installer based on your system and processor architecture. If you already have a client installed, start by importing a subscription.

Download V2Ray clients