Client selection / Platforms and cores

V2Ray client comparison

For desktop, choose v2rayN; for Android, choose v2rayNG. If your Android device needs a configuration built for the v2fly core, choose v2flyNG.

Comparison table / Feature overview

Three clients, compared by platform and features

Start with your device, then check which core your configuration requires. “Android VPN” in the table refers to how a client routes traffic from the device; it does not change the remote connection protocol and is not the same as desktop TUN mode. Scroll horizontally to view the table on narrow screens.

Feature v2rayN v2rayNG v2flyNG
Platforms Windows、macOS、Linux Android Android
Core Supports cores such as Xray and v2fly; choose a compatible option for your configuration. Xray v2fly (V2Fly series)
Maintenance Actively maintained, with desktop installers released for supported platforms. Actively maintained; the client and core have separate release schedules. Maintained independently, with a release schedule separate from v2rayNG.
Ease of use Basic connections are straightforward; custom routing and TUN require extra setup. Basic connections are straightforward; Android VPN permission must be approved on first launch. The import process is similar, but check core compatibility before choosing.
Subscription groups Group subscriptions by source and choose which groups to update. Add multiple subscription groups and browse configurations by source. Supports subscription groups for organizing configurations from different sources.
Routing interface Visual routing settings let you manage rules and their order. Choose a routing mode in settings and configure per-app proxying. Change the routing mode in settings; custom rules must use a format supported by v2fly.
TUN and traffic handling Desktop TUN mode is available; whether it works depends on system permissions and the configuration in use. Routes traffic through Android's VPN interface, with options to select specific apps. Routes traffic through Android's VPN interface; desktop TUN settings do not apply.
Best for Users who need desktop proxying, subscription groups, or visual routing settings. First-time Android proxy users or users with an existing Xray configuration. Users with a specific v2fly configuration requirement or those checking V2Fly compatibility.

An installer launching successfully does not mean every configuration will work. Before switching clients, confirm that the target core supports the protocols, transport, and security layer your configuration requires.

Client notes / Configuration differences

Once you’ve chosen a platform, check how you’ll use it

Desktop pick / Multiple cores

v2rayN

A good fit for starting with a desktop system proxy or managing multiple subscription groups in one place. On first use, import a subscription, make sure its configurations appear in the list, and select one. Enable the system proxy, then test the connection in an app that uses the system proxy settings. This helps determine whether the configuration is failing or the app is bypassing the proxy.

To route traffic selectively, review the rule order and matching outbound settings in the GUI. If only one app bypasses the system proxy, check whether it has its own proxy settings before enabling TUN. TUN changes how traffic enters the client; it cannot add support for protocols or transport options the core does not support.

Android pick / Xray

v2rayNG

A good fit for importing subscriptions or share links on Android, and for configurations that specifically rely on Xray features. After adding a subscription URL, update its group, then select a working configuration from the list. A successful import only means the client read the data; the connection also depends on the configuration fields, remote server, and current network.

Approve Android VPN permission when connecting for the first time. If only certain apps fail, check the per-app proxy list and whether the selected mode includes or excludes those apps, then review the routing mode. If another app using the system VPN interface is running, check which client currently handles traffic before switching; a permission conflict can look like a subscription problem.

Android alternative / v2fly

v2flyNG

Best suited to existing V2Fly configurations or comparisons with other v2fly environments. Before switching, keep the subscription groups, routing rules, and per-app settings from the original client. After importing the subscription again, test a known-working configuration first, then restore settings one at a time. Importing a subscription does not migrate the full setup.

Both Android clients can manage subscriptions, but being able to import a share link does not mean the core can run every option in it. Avoid moving configurations with Xray-specific security layers or flow-control fields directly to v2flyNG. When troubleshooting, check the protocol, transport, and security layer first, then see whether the logs show a parse error or a timeout after the connection attempt.

Choosing by use case / Recommended steps

Four common use cases: where to start

Recommendations / Downloads

Choose v2rayN for desktop; choose v2rayNG for Android

Consider v2flyNG when your existing configuration specifically requires v2fly or when you need to check V2Fly compatibility on Android. On the downloads page, select the right architecture and package format for your system. After installation, verify a basic connection before setting up routing or changing which traffic the client handles.

Download clients