Choosing a Client

V2Ray Client Comparison

For desktop, start with v2rayN; for Android, start with v2rayNG. Consider v2flyNG if you already have a configuration built for the v2fly core.

Compare the clients Choose by use case

Side-by-Side Client Comparison

Start with the clients supported by your device, then check whether their cores work with your configuration. Subscription groups, routing controls, and traffic handling determine how each client fits into everyday use.

On narrow screens, swipe horizontally to scroll the table. Keyboard users can focus the table and use the arrow keys to scroll sideways.

Comparison v2rayN v2rayNG v2flyNG
Platforms Windows、macOS、Linux Android Android
Core Can use Xray, v2fly, and other cores depending on the node type and configuration Xray v2fly (the V2Fly core)
Maintenance Actively maintained Actively maintained Community-maintained; check recent releases and compatibility with your system before choosing
Ease of Use Moderate: choose an installer, then understand the difference between system proxy and TUN Easy: import a node, select it, and grant permission when prompted Similar basic steps; check core compatibility if you already have a configuration
Subscription Groups Organize and update subscriptions from different sources in separate groups Manage sources in Subscription Group Settings, then update your subscriptions Supports subscription imports and group management; menu names vary by version
Routing Interface A graphical routing interface lets you view and edit rules and their matching order Choose a routing mode in settings and adjust rules using the available options Choose a preset policy in Routing Settings; for complex configurations, confirm that the core supports the required fields
TUN and Traffic Handling Desktop TUN mode is available; configure the system proxy separately Uses Android's VPN service to handle traffic, with options to choose which apps are covered Also uses Android's VPN service to handle traffic; available settings depend on the installed version
Best For Desktop users, especially those managing multiple subscription groups or editing routing rules First-time Android users or anyone with an existing Xray configuration Android users who specifically need the v2fly core or already have a compatible configuration

The core handles connections; it is not the same as the client interface. Two clients may offer similar import menus but still support different configurations.

How the Three Clients Differ

Compare the choices you'll make during installation with the menus you'll use for updates and troubleshooting.

v2rayN: Desktop Subscriptions and Routing

Top pick

v2rayN is a good fit for managing subscriptions in one place on a desktop and for users who regularly work with routing rules. Keep subscriptions from different sources in separate groups under Subscription Group Settings. If an update fails, you can troubleshoot that group without deleting and reimporting your entire node list. On Windows, choose between the desktop edition and the classic WPF edition: if you're installing for the first time, start with the desktop edition; if you prefer the familiar interface and workflow, stick with WPF. On macOS, choose the package for your processor. On Linux, check which package format your distribution uses. To connect a browser that follows system settings, first try System Proxy → Automatically Configure System Proxy from the tray menu. For apps that ignore that setting, consider Enable Tun. This helps you verify that the node works before troubleshooting traffic handling.

v2rayNG: Everyday Connections on Android

Recommended

If your provider supplies an Xray configuration or supports common Android import methods, v2rayNG is the first client to try. Add the subscription URL in Subscription Group Settings, then choose Update Subscription to fetch the nodes. Saving the URL and updating the list are separate steps, so an empty list doesn't necessarily mean the import failed. Start a node and approve the VPN permission prompt the first time you connect. On Android, the VPN service routes traffic through the client; you don't need to look for the desktop-only Automatically Configure System Proxy setting. When migrating from another setup, start with the default routing scope to confirm the connection, then adjust per-app settings. If the connection works but specific apps don't behave as expected, check whether they're included in the traffic scope before reimporting the entire subscription.

v2flyNG: Keep Using a v2fly Configuration

Alternative Core

Choose v2flyNG because you need its core, not because its interface looks simpler. If your provider specifies v2fly or an existing configuration works reliably with that core, test one confirmed-compatible node before importing the full subscription. This helps you tell whether an issue is with an individual configuration or with subscription updates, groups, or routing. When switching from v2rayNG, don't rely on familiar node names appearing in the list: a successful import only means the client read the entry, not that its core supports the protocols, transport, and security settings it contains. If the configuration requires an Xray-specific feature such as REALITY, stick with v2rayNG. If it specifically requires v2fly, choose a suitable policy in v2flyNG's Routing Settings rather than copying every setting from another client.

Which Client Fits These Four Scenarios?

Start with the problem you need to solve. Once the connection is stable, decide whether to change cores, traffic handling, or routing rules.

First Install: Get One Connection Working

Use v2rayN on desktop and v2rayNG on Android. If you have a subscription URL, add it and update the subscription; if you have a single node link, import that node directly. Test a configuration your provider explicitly supports before changing DNS or routing. If a subscription update fails, check the URL and update log first. If the node appears but won't connect, check the connection log. Troubleshoot these steps separately to see whether you need to retry the update or verify the node settings. For the full walkthrough, see the Getting Started guide.

Advanced Setup: List the Rules You Need to Keep

If you regularly reorder rules, route different domains differently, or manage multiple subscription sources, use v2rayN's desktop interface. On Android, first decide whether you need to choose which apps send traffic through the client or route traffic by domain or address. The first controls which apps are covered; the second controls where traffic goes after it reaches the client. Change one setting at a time and test one destination that should connect directly and another that should use the proxy. This makes it easier to tell which setting took effect.

Using a Computer and Phone: Don't Copy Every Client Setting

Use v2rayN on your computer and v2rayNG on your phone. If your provider allows multiple devices and both clients support the supplied configuration, you can add the same subscription URL to each. Group names, the selected node, routing, and traffic scope are usually saved separately on each device rather than synced through the subscription. If it works on your computer but not your phone, check that both use the same node, confirm VPN permission on the phone, and then compare the core and routing settings. There's no need to reset the other device just because one fails.

Older Android Phones: Check System Requirements Before Choosing a Package

Installation depends first on the Android version and the app architectures supported by your device. If your phone supports 64-bit Android apps, choose the arm64 package. If you're unsure about its architecture, try the universal package, but note that it doesn't lower the minimum Android version. If the app installs but disconnects after the screen locks, the core may still be compatible; check whether the system restricts background activity. Don't assume v2flyNG is a lightweight edition based on its name. Unless your existing configuration needs v2fly, start with v2rayNG on a compatible device.

Desktop and Android Download Picks

Top pick for desktop: v2rayN; top pick for Android: v2rayNG. Choose v2flyNG on Android only when you specifically need the v2fly core. Check the download page for packages and system requirements.

View Client Downloads