Client Comparison · Platforms and Cores

V2Ray Client Comparison and Selection Guide

For desktop, start with v2rayN; for Android, start with v2rayNG. Consider v2flyNG only if you have a specific need for a V2Fly configuration. Check your device and node requirements before comparing interfaces.

Download v2rayN Browse Android clients

Compare the Three Clients

The client provides the interface and manages configuration; the core handles protocols and connections. Whether a feature works also depends on node settings, the operating system, and permissions. Scroll horizontally to view the table.

Platforms, cores, workflows, and intended users
Comparison criteria v2rayN v2rayNG v2flyNG
Platform support Windows、macOS、Linux Android Android
Core options Choose Xray or V2Fly to match the protocol; options depend on the installed version Xray V2Fly（v2fly）
Maintenance Actively maintained; choose between the desktop edition and classic WPF edition Actively maintained; check for updates to both the client and its core Community-maintained; check update cadence and feature coverage separately
Getting started Basic subscription setup is straightforward; system proxy and TUN are separate options Import a configuration and grant VPN permission to test; check background restrictions Similar workflow to other Android clients; check core compatibility first
Subscription management Manage multiple subscription groups, update them in bulk, and organize server lists Manage subscription groups, update them, and select nodes from a mobile-friendly interface Import and update subscriptions; group management depends on the installed version
Routing interface Routing settings and rule editing are available for centralized management on desktop Set routing modes and custom rules through the mobile interface Uses V2Fly routing capabilities; verify which rules and fields are available in your version
TUN and traffic handling Includes TUN features; availability depends on the platform, permissions, and supporting components. TUN is not the same as a system proxy Routes traffic through Android's VPN service; its controls and permissions differ from desktop TUN Routes traffic through Android's VPN service; this does not mean it works like desktop TUN
Best for Desktop users who manage multiple subscriptions and maintain routing rules Android users setting up a client for the first time, importing QR codes, or needing Xray features Android users with existing V2Fly configurations who need to test how that core behaves
Download Windows · macOS · Linux View v2rayNG installation options View v2flyNG installation options

Client Reviews: Workflows and Limitations

v2rayN: Manage Desktop Subscriptions and Routing

For desktop, start with v2rayN. Its workspace brings server lists, subscription groups, logs, and settings together, making it easier to organize configurations with a keyboard and mouse. When you need to name, update, or adjust routing for multiple subscriptions, a desktop interface makes long fields easier to review than repeated edits on a phone.

To get started, open Subscription groups > Subscription group settings from the top menu, add and save a subscription URL, then update the subscription. Select an active server from the list and choose how to route traffic. Menus may vary slightly between desktop editions, so look for the same setting by name in your version. Selecting a server does not mean every app is using the proxy.

The Windows download page offers both the desktop and classic WPF editions. The desktop edition uses a cross-platform interface, while WPF retains the classic Windows layout; they do not use different node protocols. On macOS and Linux, choose the package for your platform; Windows packages will not work. To change core mappings, check Settings > Parameter settings > Core type settings for the relevant protocol. After switching, review the logs to confirm the core accepts the configuration.

TUN can handle apps that do not follow system proxy settings, but takes more setup than a system proxy. Before enabling it, check permissions, routing, and DNS, and turn off other tools that are already handling network traffic. A TUN toggle is not a substitute for testing node connectivity. If node parameters are wrong, routing more traffic through TUN can cause connection problems in more apps.

v2rayNG: The Go-To Choice for Android

For Android, start with v2rayNG. It uses the Xray core, and the usual workflow is to import a subscription, update the node list, select a server, and connect. Manage subscription URLs under Subscription group settings in the top-right menu, then return to the main screen and update the subscription. Import share links from the clipboard or use the QR code option. Subscription URLs and individual node links serve different purposes, so check which one you have before importing.

The first time you connect, Android prompts you to allow a VPN connection. Granting permission lets the client receive traffic through the system's virtual network interface. It does not mean the node has connected successfully or that every app's traffic is being routed. If per-app settings are enabled, check both the app list and whether it includes or excludes the listed apps.

Find routing under Settings > Routing settings in the side menu; submenu names vary by version. Start with the defaults, confirm that your browser and target apps can connect, then add domain rules or app exceptions as needed. If the connection drops when the screen turns off or takes a while to recover after switching networks, check battery optimization and background permissions before switching cores.

v2flyNG: An Alternative When You Need V2Fly

Choose v2flyNG because you need the V2Fly core, not because an alternative client is necessarily lighter. If you have a tested V2Fly configuration and want to use the same core behavior on Android, add it to your test options. For a first-time import of a typical subscription, v2rayNG is easier to follow alongside this site's beginner guides.

Before importing, check the server protocol, transport settings, and security parameters. If the client can read the subscription text, it has parsed it; whether it can connect depends on which fields that version of the core supports. If a node relies on Xray-specific extensions, do not assume a failed connection is caused by your phone's network. Check the logs for configuration parsing, handshake, or connection errors and troubleshoot each layer in turn.

The exact menus for subscription management and routing depend on the installed version, so do not assume every v2rayNG screenshot applies. To assess maintenance, check the client's actual update history and how closely its core is kept up to date; names, icons, and successful installation prove neither. Before switching clients, keep a restorable copy of your configuration and test a few known-good nodes. Avoid changing the core, DNS, and routing all at once.

Choose by Use Case

Four Checks Before Downloading

  1. Check your device and package architecture. The Windows download options on this page are x64 desktop and WPF editions. For macOS, choose Apple Silicon or Intel; for Linux, check the package format and architecture; for Android, choose arm64 or a universal package. Package format and processor architecture are separate requirements.
  2. Check your subscription and node parameters. A subscription URL updates a list of nodes; an individual node link imports one configuration, and native JSON is another format. Keep all parameters supplied by the source. Do not delete fields you do not recognize or share a private subscription URL publicly.
  3. Check which traffic will be routed. Desktop system proxy settings mainly affect apps that follow them. TUN and Android's VPN service receive traffic through a virtual network interface. In either case, routing rules determine whether a connection uses the proxy or goes direct.
  4. Keep a way to restore your setup. Before changing clients or cores, save the necessary configuration and current rules. Stop the existing connection before starting a new one, then test a few targets to avoid two tools handling network traffic at the same time. For more steps, see the cross-platform guide.

Switching clients should not be your first troubleshooting step. If all three clients use the same incorrect settings, a different interface is unlikely to fix the problem. Check the system clock, subscription status, node address, port, and TLS settings first, then check how the device routes traffic. If the connection is established but one app fails, check whether its traffic is being routed and whether a rule matches it.

Recommendations and Downloads

For desktop, start with v2rayN. Windows, macOS, and Linux users should choose the package for their platform. For the classic Windows workflow, see the WPF edition; for a cross-platform interface, see the desktop edition. Once you have chosen an interface, check the core and routing against your node requirements.

For Android, start with v2rayNG. It is a good starting point for common subscriptions and Xray configurations. Reserve v2flyNG for cases that specifically need V2Fly; it is not a universal fix for connection problems. After installation, test a node before adjusting routing or background permissions.

The differences between these clients are mainly their platforms, cores, and configuration workflows; they do not determine connection speed. Your experience also depends on the server, network path, node load, and local rules. Choose a client that handles your existing configuration correctly and is easy to troubleshoot and maintain.

Compare download options for all three clients Continue to the setup guide