Choosing a Desktop or Android Client

V2Ray Client Comparison

Choose a client for your device first, then choose a core to match your existing configuration. Prioritize the core only when a specific setup requires it.

Recommended for desktop: v2rayN; for Android: v2rayNG

Use v2rayN on desktop to manage subscriptions and routing. On Android, use v2rayNG for VPN mode and per-app proxy settings. Consider v2flyNG only if your Android configuration specifically requires V2Fly.

View Downloads

Compare the Three Clients

Start with the platform and core rows; use the rest to see how each client fits your daily workflow. On narrow screens, scroll the table horizontally. Keyboard users can focus the table area before scrolling.

Comparisonv2rayNv2rayNGv2flyNG
Supported PlatformsWindows、macOS、LinuxAndroidAndroid
CoreSupports Xray and V2Fly; available options depend on the build and configuration.XrayV2Fly(v2fly)
MaintenanceActively maintained, with support for multiple desktop platforms.Actively maintained, focused on Android.Updates are less frequent. Check recent releases and system compatibility notes before choosing it.
Ease of UseBasic subscription setup is straightforward; system proxy, routing, and TUN each require separate configuration.Few steps to connect for the first time; you'll need to approve the system VPN permission.The basic import process is similar; make sure your subscription meets V2Fly core requirements before choosing this client.
Subscription ManagementSubscription groups make it easy to update and switch between sources.Supports subscription groups for managing configurations from different sources.Supports subscription imports and updates; grouping options depend on the version.
Routing ControlsManage routing rules in the GUI and check their order.Includes routing modes and rule settings, plus per-app traffic selection.Includes basic routing settings; available rule controls depend on the version.
TUN and Traffic RoutingIncludes TUN mode; availability depends on the system, permissions, and build.Uses Android's VpnService to create a virtual network interface, rather than a desktop-style TUN toggle.Routes traffic through Android's VpnService; setup differs from desktop TUN configuration.
Best ForDesktop proxy users and anyone who needs detailed subscription and routing controls.Android users setting up a proxy for the first time or managing traffic by app.Android users with an existing V2Fly configuration they want to keep using.

Maintenance refers to the project's update cadence; not every package is updated at the same time. Check the download page for supported systems and installation requirements.

How the Three Clients Differ

v2rayN: Desktop Subscription and Routing Management

v2rayN lets you manage subscription sources, the active configuration, and routing rules separately in its GUI. If you have multiple subscriptions, group them by source and give each group a clear name. If one group fails to update, you can troubleshoot it without reimporting every address. For everyday use with a browser or other apps that follow the system proxy, start with system proxy mode. Use TUN only when an app ignores the system proxy and you need to route its traffic through the client; check the required permissions and system support first. If traffic behaves unexpectedly after a routing change, confirm it is reaching the client, then check the rule order. Routing rules cannot proxy traffic from apps the client does not capture. When choosing a package, check your operating system and processor architecture first. Pick the interface that suits you; there is no need to choose a different subscription just to change interfaces.

v2rayNG: Android VPN Mode and Per-App Settings

For most Android users, getting started with v2rayNG is simple: import a subscription, select a configuration, and grant VPN permission when prompted. That is enough to test a basic connection. Leave per-app proxy settings alone at first. If only a few apps can connect, it may be hard to tell whether the subscription is wrong or the test app was excluded. Once the basic connection works, open per-app proxy settings and check the app list against the selected or bypass mode—the same list works differently in each mode. Also distinguish between the app starting and it staying connected in the background. If it works with the screen on but disconnects when the screen is off, check Android's battery and background restrictions for v2rayNG. If it cannot connect as soon as it starts, check VPN permission and whether another app is using the system VPN. These issues need different troubleshooting steps; changing cores should not be the first move.

v2flyNG: Keep Using a V2Fly Configuration

The clearest reason to choose v2flyNG is that you already have a configuration tested with V2Fly, or its provider specifies that core. The app can handle Android subscriptions and basic connections, but a similar interface does not mean settings are interchangeable. For example, a configuration that specifically relies on Xray's REALITY should not be copied straight into v2flyNG. And a VMess configuration is not automatically portable: transport, TLS, and custom routing settings can still differ. Before switching, save your original configuration and test one connection with clearly documented settings. Confirm that it starts and can reach its destination before moving the rest. If a previously verified configuration only times out occasionally, check the network and logs first; one timeout alone is no reason to switch clients.

Choose a Client for Your Setup

First-Time Setup: Test One Connection

Choose v2rayN for desktop or v2rayNG for Android. Import a single subscription, update it, then test one configuration. On desktop, start with system proxy mode; on Android, grant VPN permission first. Note which app successfully connects, then add routing or per-app settings one at a time. If no entries appear after an update, check the selected subscription group and the update message. Changing routing will not restore a missing list.

Advanced Setup: Choose a Core and Traffic Mode for Your Needs

For Xray-specific features, use Xray for the relevant configuration in v2rayN on desktop or use v2rayNG on Android. If you specifically need V2Fly, check which cores are available in your desktop build or consider v2flyNG on Android. If a desktop app ignores the system proxy, deciding whether to use TUN is separate from changing the protocol or core. When testing routing, change one setting at a time and compare the same app before and after.

Use a Subscription on Desktop and Android—Don't Copy Settings

Use v2rayN on desktop and v2rayNG on Android. If your subscription allows multiple devices and the configuration is compatible, you can use the same subscription URL on both. Give the groups the same name on each device so you can confirm they update from the same source. On desktop, choose system proxy or TUN to control which traffic is captured; on Android, use VPN permission and the per-app list. If a configuration works on your computer but not your phone, test both on the same network first, then check which apps are included on the phone.

Older Android Phones: Check Requirements and Background Settings

First, make sure your Android version meets the installation requirements, then check the processor architecture. If arm64 is explicitly supported, choose the matching package. If you are unsure of the architecture, consider the universal build—but it still requires the same minimum Android version. If the app installs but disconnects when the screen turns off, check battery optimization and background permissions. Test with the same network and configuration, both with the screen on and off; this usually makes the cause easier to find than repeatedly switching packages. v2flyNG is not a special version for older devices. Choose it only when your configuration requires V2Fly.

What to Check After Choosing a Client

Choose a version for your operating system and architecture on the download page, then follow the quickstart guide to import, connect, and test it. Pinpointing the step that fails is more useful than reinstalling: if a subscription won't update, check its URL and group; if the client starts but some apps cannot connect, check which traffic it captures; if traffic is reaching the client but errors persist, check the protocol, transport, and logs. If you changed several settings at once, restore the last configuration that connected, then adjust one setting at a time.

If you're unsure how the two cores differ, start with the Xray and V2Fly configuration compatibility guide. If you've chosen a client but are seeing timeouts, background disconnects, or startup failures, follow the relevant steps in Troubleshooting.