Client Selection Guide

V2Ray clients compared

Start with your operating system, then check core compatibility, routing options, and how the client handles traffic.

Client Feature Comparison

Your platform determines which client you can install; the core determines whether your configuration works as expected.

Scroll horizontally on narrow screens to compare all three clients.

Feature v2rayN v2rayNG v2flyNG
Supported Platforms Windows、macOS、Linux Android Android
Proxy Core Typically Xray; the core used depends on the node type and client configuration Xray V2Fly(v2fly)
Maintenance Actively maintained Actively maintained Check the project's release history for updates. Don't use V2Fly core updates to infer how often the client itself is updated.
Ease of Use Straightforward for basic tasks; understand the difference between system proxy and TUN before setting up traffic routing. Import a subscription, choose a node, and connect. On first use, approve the system VPN permission. The connection process is similar, but check protocol, transport, and security compatibility before importing.
Subscription Management Supports subscription groups, making it easy to update multiple sources separately. Add multiple subscriptions and browse nodes by source. Import and update subscriptions. Grouping options may vary by installed version.
Routing Rules Edit routing rules, match conditions, and outbound selections in the graphical interface. Adjust traffic routing in the mobile settings; the controls differ from the desktop version. Use the client's routing settings; supported rule syntax depends on the V2Fly core.
TUN and Traffic Handling Offers system proxy and TUN modes. TUN depends on platform permissions and network conditions. Routes traffic through Android's VPN service; it does not use the desktop TUN toggle. Also routes traffic through Android's VPN service. A different core does not mean a different traffic-handling method.
Best For Desktop users who manage multiple subscriptions or maintain routing rules. Android users new to proxy clients or already using an Xray configuration. Android users who have confirmed they need V2Fly compatibility.

Importing a subscription doesn't guarantee that every node will work. Before switching clients, check the node's protocol, transport, and security settings, then test the routing behavior.

Client Reviews

A look at what each client does well and where it has limitations in everyday use.

v2rayN: Desktop Subscription Management and Routing

v2rayN is a good fit for managing multiple subscriptions on a desktop. Keep each source in its own subscription group so you can find nodes by source after updating. Configure routing in the graphical interface: choose which destinations should connect directly, then set where other traffic goes. Before changing rules, note their current order and the default outbound. When rules overlap, a broad rule near the top may match first and prevent a later, domain-specific rule from taking effect. See the routing configuration reference for rule fields and order.

For everyday use with browsers and other apps that follow the system proxy, start with system proxy mode. If an app doesn't use the system proxy, consider TUN and check virtual network adapter permissions and conflicts with other network tools. After enabling TUN, test both internet access in the apps you need and access to local network devices. Test each mode separately so you can pinpoint issues.

v2rayNG: Android Subscription Import and Xray Configuration

v2rayNG is a good place to start with an Xray-compatible subscription. Add the subscription URL, update it, select a node, and connect. The first time you connect, Android will ask for permission to establish a VPN. Granting permission only allows the client to route traffic; it doesn't confirm that the server is reachable. Test with the apps you actually use. If only one app is affected, check whether per-app proxy settings include it.

When you use the same subscription on desktop and Android, both devices share the node source, but system proxy, per-app scope, and routing options are stored locally on each device. If the desktop works but Android doesn't, select the same node on both and test the phone over Wi-Fi and mobile data separately. Matching nodes make it easier to tell whether the issue comes from the network or Android's local settings. See the Android setup guide for steps.

v2flyNG: Android Option for V2Fly Compatibility

Consider v2flyNG when your server is configured for V2Fly or your configuration provider specifically requires the V2Fly core. Subscription import is similar in both Android clients, but their cores don't support exactly the same combinations of transport and security settings. For example, nodes that rely on REALITY should be matched to an Xray-compatible client. Seeing a node name in the list doesn't mean every setting will work.

When switching clients, keep the existing settings and first test a few nodes known to be compatible. Then check routing and per-app scope. If both clients are installed, disconnect the current one before starting the other to avoid mistaking an Android VPN service handoff for a core issue. Long-term use on older devices depends on the Android versions and processor architectures supported by the current installer, as well as actual background behavior—not the core's name.

Choose a Client by Use Case

Start with the problem you need to solve, then decide whether to change the default settings.

Bottom Line

For desktop, start with v2rayN; for Android, start with v2rayNG. Choose v2flyNG on Android only when you have a specific need for V2Fly core compatibility.

On the download page, choose your operating system first, then check the processor architecture and package format. Windows users can choose Desktop or WPF based on interface preference. On Linux, choose deb or rpm according to your distribution's package manager, not your desktop environment.