Client Picks

V2Ray Client Comparison

For desktop, choose v2rayN; for Android, choose v2rayNG. Consider v2flyNG if you already have V2Fly configs and want to keep using the same core on Android.

Platforms · Cores · Features

Compare the Three V2Ray Clients

Start with your device, then narrow down your options based on the core required by your existing configs. Scroll horizontally to view the table on smaller screens.

Platform Support & Everyday Settings
Comparison v2rayN v2rayNG v2flyNG
Platform support Windows、macOS、Linux Android Android
Core Xray is a common choice; available cores depend on the client Xray; suited to configs that require Xray-specific fields V2Fly; suited to existing V2Fly configs
Maintenance Actively maintained; the Desktop and classic WPF editions may have different interfaces and release schedules Actively maintained; the client interface and core are separate layers, so an update may affect only one of them Maintained as an independent project; client releases do not track V2Fly core releases
Ease of use Easy to get connected; learn about TUN if an app doesn't use the system proxy Easy to get connected; approve the system VPN request the first time you connect Similar basic workflow to v2rayNG; check that your configs work with V2Fly before switching
Subscription groups Group subscriptions by source, then update and filter them separately Manage sources under “Subscription Group Settings” and switch groups to view configs Manage subscription sources; migrate existing groups and local settings one by one
Routing interface Organize rules under “Routing Settings”—a good fit for desktop users who regularly adjust rules and outbound settings Manage traffic rules under “Routing Settings”; choose which apps are covered separately under “Per-App Proxy” Set rules using the options provided by the client; rule fields must meet V2Fly core requirements
TUN & traffic routing Offers desktop TUN; requirements vary by OS, permissions, and runtime environment Creates a virtual network interface with Android VpnService; there is no desktop TUN toggle Also routes traffic through Android VpnService; there is no desktop TUN toggle
Best for Desktop users who manage multiple subscriptions or need fine-grained routing controls Android beginners and users who need per-app VPN controls or Xray configs Android users with existing V2Fly configs who want to minimize core migration changes

This table compares the options each client provides; it does not mean a config can be moved between all three without changes. Subscriptions provide connection configs, routing determines where traffic goes, and the system proxy, desktop TUN, or Android VPN determines which traffic reaches the client in the first place. When troubleshooting, check these three layers separately.

Settings & Migration Trade-offs

Client Reviews

Top Pick for Desktop

v2rayN: Start with the system proxy; enable TUN only if needed

If you manage several subscriptions on your computer, v2rayN makes it easier to organize groups, filter configs, and adjust routing in one place. On Windows, choose between the Desktop and classic WPF editions based on the interface you prefer. If you're used to WPF, there's no need to redo your setup just to switch interfaces. To get started, import a subscription, select one config, and test it with an app that uses the system proxy. If your browser connects but a desktop app doesn't, first check whether that app respects the system proxy; consider TUN only after that. TUN expands the range of traffic the client can capture, but it won't fix a broken subscription or incorrect connection settings. After enabling it, test both desktop apps and local network resources. If behavior changes, switch back to the previous mode and check your routing rules.

Top Pick for Android

v2rayNG: Approve VPN access, then choose which apps to include

For first-time Android users, v2rayNG is a solid default choice. Add a source under “Subscription Group Settings,” update it, then select a config from the relevant group. Approve the system VPN connection request the first time you connect, then test with the app you want to use. To route only certain apps through the client, go to “Settings → Per-App Proxy” and check whether the current mode includes or excludes the selected apps. The same selections mean opposite things in the two modes, so review them again whenever you switch. Including an app in the VPN scope doesn't mean every destination it accesses will use the proxy outbound; routing rules still determine where traffic goes. If the connection drops when the app moves to the background, check the system VPN status and battery settings before changing cores or DNS.

V2Fly Core

v2flyNG: Keep V2Fly Configs That You've Already Verified

If you already have configs verified with V2Fly and need to keep using that core on Android, consider v2flyNG. Check the protocols, transport, security settings, and routing fields in the config—not just whether it appears in the imported list. A client can read a subscription without being able to run every config it contains. If a config relies on Xray's REALITY or Vision, keep it in a compatible Xray environment rather than repeatedly changing fields after switching clients. If you do need to migrate, keep your old client settings and test one known-working config in the new client first. Once the connection and app access both work, migrate groups and routing gradually. When testing two Android clients, connect them one at a time to avoid having one replace the other's system VPN.

Choose by Use Case

Beginners, Advanced Setups, Multiple Devices & Older Phones

First time? Test one connection

Choose v2rayN for desktop or v2rayNG for Android. Import one source, select one config, and test it with a familiar app. There's no need to change routing, DNS, and proxy scope all at once. If it doesn't work, first find out whether the subscription failed to load, the config can't connect, or only a particular app has an access issue. Follow the quick start guide for the recommended steps.

Advanced setup: Test traffic routing and rules separately

For frequent desktop rule changes, use v2rayN. On Android, use per-app proxy settings if you only want to change which apps enter the VPN. Test one destination expected to connect directly and another expected to use the proxy, changing one setting at a time. This helps pinpoint whether the issue is traffic scope, route matching, or DNS resolution. See advanced configuration for more on rules.

Multiple devices: Sync subscription sources, not local settings

Use v2rayN on your computer and v2rayNG on Android; switch to v2flyNG on your phone only if you need V2Fly compatibility. You can import the same compatible subscription on each device, but configure the system proxy, per-app list, routing, and DNS separately for each one. If a config works only on your computer, first compare the cores and protocol fields on both devices, then check how each one captures traffic.

Older phones: Check the OS version and device architecture first

An older phone doesn't necessarily need a different core. Check the client's system requirements on the download page, then choose a package that supports your device's architecture. If you're unsure which architecture to pick, start with the client's universal package; it still requires a supported OS version. If the app installs but disconnects when the screen locks, check battery optimization and background restrictions before switching between Android clients based on the phone's age alone.

Bottom Line

Choose v2rayN for desktop and v2rayNG for Android

In most cases, choose based on your platform. Use v2flyNG as your first choice on Android only if you already have V2Fly configs and want to keep using the same core. Once you've chosen a client, visit the download page to find the option for your OS and device architecture.

Browse Clients & Downloads