Client Choice · Platforms and Cores

V2Ray Client Comparison

For desktop, start with v2rayN; for Android, start with v2rayNG. Consider v2flyNG only if your existing Android configuration specifically requires V2Fly.

Compare the Three Clients

Filter by operating system, then check core and routing needs. Scroll horizontally to view the table on narrow screens.

Comparison v2rayN v2rayNG v2flyNG
Platforms Windows、macOS、Linux Android Android
Core Supports Xray-core, V2Fly, and others; availability depends on your configuration and installed cores Xray-core V2Fly
Maintenance Actively maintained Actively maintained Community-maintained; updates are less frequent
Ease of use Easy subscription import; first-time users need to understand the difference between system proxy and TUN Import a subscription and select a configuration; VPN permission is required on first launch Setup is similar to v2rayNG; check core compatibility separately
Subscriptions Subscription groups support notes, update toggles, and filters Add multiple subscription groups and update configurations Import and update subscriptions; desktop-style filtering workflows may not apply
Routing rules Edit rules, reorder them, and choose rule sets in routing settings Adjust routing in settings; configure per-app proxying separately Adjust routing in settings; rule support depends on the V2Fly core
System proxy and TUN Includes system proxy and TUN options; availability depends on system permissions and your environment Routes traffic through Android's VPN service rather than a desktop-style system proxy toggle Also routes traffic through Android's VPN service
Best for Desktop users and anyone managing multiple subscriptions or editing rules Users setting up a proxy on Android for the first time, or with existing Xray-based configurations Android users who need to keep using V2Fly-compatible configurations

Client reviews: why choose each one

v2rayN: Desktop subscription management and routing

Desktop users can start with v2rayN. On Windows, choose between the desktop and classic WPF editions; on macOS and Linux, use the cross-platform desktop edition. To manage multiple subscriptions, add each one under “Subscription Group Settings,” with its own note and URL, then update. Filters affect which entries remain after an update. If the update succeeds but the list is empty, check the selected group and filters before importing again.

For traffic routing, check the match conditions, rule order, and outbound in “Routing Settings.” The system proxy determines how apps send requests to the client; routing rules determine where requests go once they reach it. If one app works in your browser but not another, check whether that app uses the system proxy. Use TUN only when you need to capture traffic from apps that do not, and check system permissions and local network access.

v2rayNG: Use Xray-core on Android

Choose v2rayNG when importing a subscription on Android for the first time or when your configuration specifically uses Xray features. Add the URL in “Subscription Group Settings,” return to the list and update it, then select a configuration and start the connection. Android will request VPN permission the first time. Granting permission allows the client to route traffic; it does not confirm that the remote server is reachable. After connecting, test with the app you actually plan to use.

To exclude certain apps from the proxy, first find the client's per-app proxy settings. They control which apps enter the VPN; routing settings apply to connections already inside the client. If only some apps have problems, check the app list and whether its policy includes or excludes them before reviewing domain or address rules. Changing both settings at once makes problems harder to diagnose.

v2flyNG: Keep Android configurations that require V2Fly

The main reason to choose v2flyNG is V2Fly compatibility—not package size or how old your phone is. Start here if your existing configuration runs on V2Fly and you want to keep using the same core on Android. Adding a subscription, updating the list, selecting a configuration, and granting VPN permission work much like they do in v2rayNG. However, importing a subscription does not guarantee that every configuration in it will work.

Before migrating, check the protocol, transport, and security settings. Even when the protocol name matches, the target core may not recognize the transport parameters or encryption settings. If a configuration requires Xray's REALITY, don't just switch to a similarly named protocol. Choose a client that supports the original configuration, or ask the configuration provider for a working V2Fly option. Test one configuration with clearly specified parameters before migrating the whole subscription group.

Choose a client for your use case

If you already have a configuration, check compatibility first. Otherwise, start with the recommended client for your platform.

First-time setup: test one connection

Use v2rayN on desktop and v2rayNG on Android. Import a subscription, select one configuration, and check that the app you need can connect. On desktop, start by testing apps that use the system proxy; on Android, grant VPN permission. You don't need to change routing rules or per-app settings for this first test. Establish a working baseline, then change one thing at a time.

Advanced routing: distinguish traffic capture from outbound routing

If you regularly edit desktop routing rules, start with v2rayN's routing interface. First make sure traffic enters the client, then decide whether matching traffic should go direct or through the proxy. After changing rule order, test both direct and proxied destinations. Also check that local network services remain accessible; a single working webpage is not enough to verify the routing setup.

Multiple devices: sync the source, not the rules

Use v2rayN on desktop and an Android client compatible with your configuration. Using the same subscription URL can simplify node list maintenance, but system proxy settings, Android VPN permissions, and per-app lists do not sync through a subscription. When switching devices, check the selected configuration and set the traffic capture scope separately on each platform. Don't share subscription URLs publicly as if they were ordinary text.

Older phones: check Android version and architecture

First confirm that your Android version meets the package's requirements, then check which app architectures your system supports. If arm64 is supported, choose the matching package; if you're unsure, try the universal package. A universal package covers more architectures but does not lower the minimum Android version. If the connection drops when the screen locks, check whether battery management restricts background activity before trying another client.