Desktop and Android Picks

V2Ray Client Comparison

For desktop, start with v2rayN; for Android, start with v2rayNG. Consider v2flyNG only if you specifically need the V2Fly core.

Platforms, Cores, and Settings

First rule out clients that don't support your device, then check which core your configuration requires. Importing a subscription, connecting to a node, and routing app traffic through a proxy are three separate checks.

On narrow screens, swipe horizontally. To scroll with the keyboard, focus the table area and use the arrow keys.

Compare the Three Clients
Featurev2rayNv2rayNGv2flyNG
PlatformsWindows、macOS、LinuxAndroidAndroid
CoreChoose Xray or V2Fly based on your configuration, installer, and available coresXrayV2Fly(v2fly)
MaintenanceActively maintainedActively maintainedUpdates are less frequent; choose if it meets your needs
Ease of useEasy to connect; advanced settings are spread across several menusEasy to get started; requires Android VPN permission on first connectionSimilar basic workflow; check configuration compatibility first
Subscription groupsName groups and update them individually—useful for managing multiple subscriptionsManage subscription groups and update nodesAdd and update subscriptions; group options depend on the current app interface
Routing interfaceManage routing rules and their order in a graphical interfaceRouting settings include presets and options for custom adjustmentsAdjust routing in settings; available options depend on the app interface
TUN and traffic handlingSupports TUN; system proxy and TUN are configured separately, with permissions varying by platformUses Android's VPN service to create a virtual interface; choose which apps to route in settingsUses Android's VPN service to create a virtual interface; its controls differ from desktop TUN settings
Best forDesktop users, people managing multiple subscriptions, and anyone who needs to edit routing rulesAndroid beginners and users with Xray configurationsAndroid users with configurations confirmed to work with V2Fly

The core determines whether a configuration can be parsed; the client determines how you manage its settings. Even if two apps show the same node name, that doesn't mean they support the same transport parameters. Maintenance status is a general description, not a release commitment, and doesn't tell you whether an installer will work on an older system.

What to Expect from Each Client

v2rayN

Top Pick for Desktop

A good fit for organizing subscriptions and routing rules on a computer. Name groups by source or purpose, update each group, then check whether its nodes have changed. The graphical routing interface makes it easier to fine-tune rules—for example, keeping a device on your local network on a direct connection while routing other matching requests through a proxy. Check rule order before making changes so broad rules don't take precedence over specific ones.

Start by enabling the system proxy, then test it with an app that respects that setting. If it works in one app but another connects directly, the node may be fine—the second app may have its own proxy settings. Consider TUN only if you need to route traffic that way, and check permissions, local network access, and how to revert the change first. The desktop and classic WPF versions of v2rayN for Windows have different interfaces, so make sure your window matches the tutorial before following its steps.

v2rayNG

Top Pick for Android

A good choice for Android users who want to import a configuration and connect before exploring advanced settings. It uses the Xray core, so try it first when a configuration specifies Xray. After importing, select a node and grant Android VPN permission when prompted. A VPN icon in the status bar means the virtual interface is active; successful access still depends on the node, routing rules, and which apps are included.

If only certain apps behave unexpectedly, check per-app proxy settings first and confirm whether the list includes or excludes those apps—don't reinstall right away. If the connection works in the foreground but drops when the screen is locked, check battery optimization and background restrictions. If another VPN is already active, review the system prompt and usage requirements before switching; don't mistake a VPN conflict for an expired subscription.

v2flyNG

V2Fly Core Alternative

A good fit when the configuration source explicitly says it supports V2Fly, or when you need to test the same V2Fly configuration on Android. It also routes traffic through Android's VPN service, and its installer may offer different processor architectures. The two Android clients have similar basic workflows, but the same subscription URL doesn't guarantee that every node in it will work. If a subscription includes settings for different cores, test only entries confirmed to be compatible.

Before switching, note the node, routing mode, and affected apps in use. After switching, test the same app on the same network to distinguish core differences from network fluctuations. If the core log says a parameter isn't supported, check the configuration provider's compatibility notes instead of guessing from the protocol name. Switching to V2Fly isn't a general fix for battery drain or background disconnections.

Choose a Client by Use Case

First install: test one connection

Install v2rayN on a computer or v2rayNG on Android. Import a subscription from a source you trust, choose a node, and test the connection with the default settings. Once it works, you can set up groups or adjust routing. If the list is empty, check that the subscription has been updated and the right group is selected. If entries appear but won't connect, check the core log instead of importing the subscription again. Follow the subscription import steps → to check each item.

Advanced setup: choose by core and traffic scope

For editing multiple routing rules and checking their order, start with desktop v2rayN. On Android, if you mainly need to control which apps use the VPN, check v2rayNG's per-app settings first. Change one variable at a time: keep the node and DNS settings fixed, test routing separately, then decide whether to change how traffic is handled. For example, if local network printing stops working, check direct-connection rules for the local network and the traffic scope before switching cores, which adds another variable to troubleshoot. See the routing rules guide →.

Multiple devices: share subscription sources, not local settings

Using v2rayN on a computer and v2rayNG on Android makes issues easier to compare; Android devices with V2Fly-compatible configurations can also use v2flyNG. First confirm that your subscription allows use on multiple devices, then import and update it on each one. Use the same group names to make sources easier to compare, but configure local ports, system proxy settings, per-app lists, and background permissions separately for each device. If it works on your computer but not your phone, check that both use the same configuration and test them under the same network conditions.

Older phones: check compatibility, then background settings

Check your Android version and the processor architectures supported by the installer. Choose arm64 only if the device runs a compatible 64-bit system. If you're unsure about the architecture, try the universal build—but it won't lower the minimum Android version. If installation fails, check the system message. If it installs but disconnects only when the screen is locked, review the app's background permissions. For battery tests, keep the network and node the same. Avoid frequent subscription refreshes or diagnostic logs at the same time, or it will be hard to tell which setting is draining power.

Choose a Client, Then an Installer

For desktop, choose v2rayN; for Android, choose v2rayNG. Use v2flyNG as an Android alternative only if you specifically need the V2Fly core and have confirmed your configuration is compatible. On the download page, select your device's platform, then choose the installer format and system architecture. Note your current system proxy or VPN settings before installing so you can restore them after testing.

Browse Downloads by Platform