Choose a Client

V2Ray Client Comparison

Choose a client for your device first, then check core compatibility and which traffic it handles. You can import the same subscription on multiple devices, but check routing and DNS settings on each one.

  • Top pick for desktop: v2rayN
  • Top pick for Android: v2rayNG
  • Consider v2flyNG if you specifically need v2fly

Platforms, cores
and configuration features

  • Windows / macOS / Linux / Android
  • Desktop TUN and Android VPN: a comparison
  • Scroll horizontally to view the table on narrow screens
Features and use cases for v2rayN, v2rayNG, and v2flyNG
Category v2rayN v2rayNG v2flyNG
Platforms Windows / macOS / Linux Android Android
Core Usually Xray; available cores depend on the current build Primarily Xray v2fly
Maintenance Actively maintained; separate download options for desktop and WPF editions Actively maintained; client updates include core compatibility Maintained independently; update schedule differs from v2rayNG
Ease of use Moderate; subscription updates and system proxy settings are separate steps Easy to get started; import and update a subscription, choose a node, then grant VPN permission Fewer basic features; check subscription and core compatibility first
Subscription groups Create groups by source to update and filter subscriptions separately Add and manage multiple subscription sources, with nodes grouped by source Manage subscription sources; group display depends on the installed version
Routing interface Visual routing controls make it easier to see how rules map to outbound connections Includes routing controls and per-app proxy settings, which work at different levels Basic routing controls; available options vary by build
TUN and traffic handling Supports TUN; availability depends on platform, build, and permissions. You can also start with the system proxy Uses Android's VPN service to handle traffic, with per-app control over which apps are included Uses Android's VPN service to handle traffic; it does not use the desktop TUN startup method
Best for Desktop users and anyone managing multiple subscriptions or custom routing rules Users setting up an Android proxy for the first time or using Xray-based configurations Android users with a v2fly-compatible subscription who need to keep using a v2fly-based configuration

This table compares common client features; it does not guarantee compatibility with every subscription. Maintenance status also does not guarantee that a particular build supports a specific OS version. Check the package notes and device requirements before installing.

How the three clients
differ in practice

  • Subscription updates change only the node source
  • Configure routing, DNS, and traffic handling separately

v2rayN: desktop subscriptions and routing

Top pick for desktop

v2rayN is a good fit for managing multiple subscriptions on a desktop. Create a separate group for each source so you can tell which subscription each node came from after an update. If one group fails to refresh, you won't need to rebuild the others. Windows x64 users can choose between the desktop and classic WPF editions. For a first install, start with the desktop edition's cross-platform interface; if you're used to the classic layout, stick with WPF. On macOS, choose a package for your chip. On Linux, first check your distribution's package format, then confirm your processor architecture.

For your first connection, start with the system proxy and test with an app known to use system proxy settings. If a browser connects but another app does not use the same outbound route, check whether that app has its own proxy settings before rewriting your rules. Enable TUN only when you need to handle traffic from apps that ignore the system proxy, and check whether it affects local network access. When editing routes, start with one easy-to-test rule to confirm the match order and outbound selection, then add exceptions one at a time.

v2rayNG: Android subscriptions and per-app proxy

Top pick for Android

v2rayNG is a good choice for setting up a subscription on Android for the first time. After importing the URL, update it, wait for the node list to appear, then select a node. On the first connection, approve the system VPN permission prompt. If the list is still empty after an update, check that the subscription URL is valid, the client can reach it, and its response uses a format the client can read. An empty list and a failed node connection are different issues and should be troubleshot separately.

Per-app proxy settings determine which apps send traffic through the VPN; client routing determines which outbound route handles that traffic. If an app is outside the VPN, adding a domain rule won't change its connection. Start testing with an app included in the VPN, then expand the scope as needed. If the connection often drops after the screen locks, check whether background restrictions, battery-saving settings, or another VPN app may be involved. Change system settings one at a time only if you can reliably reproduce the problem.

v2flyNG: for v2fly-compatible setups

Android alternative

Choose v2flyNG for core compatibility. If your configuration provider specifically requires v2fly, or you already have a configuration verified with that core, import it into v2flyNG and test a node. A successful import only means the client can read the input; it doesn't guarantee that every transport, security, and routing setting will work as-is. In particular, don't assume a configuration that relies on Xray-specific features can be migrated just because the subscription imports successfully.

To compare clients on the same phone, disconnect the active VPN before starting the other client. Test the basic connection on the same network, with the same compatible node and the same app, so VPN switching or node differences aren't mistaken for core issues. If you're keeping an existing v2fly configuration, check DNS and routing results separately. Being able to open a webpage doesn't prove that your original direct-connection exceptions were migrated correctly.

Narrow down your options
by use case

  • Test the basic connection first
  • Change one type of setting at a time so you can roll back easily

Recommendation
and download options

  • No specific core requirement? Start with the top pick for your device
  • Need v2fly? Start with the Android alternative

Top pick for desktop: v2rayN; top pick for Android: v2rayNG. If your existing Android configuration specifically requires v2fly, choose v2flyNG instead. Before installing, check your OS and processor architecture. After installation, update your subscription and test a basic connection before adjusting routing, DNS, or traffic handling.