Platforms, cores, and configuration options
V2Ray Client Comparison
Choosing v2rayN and Android Clients
For desktop, start with v2rayN; for Android, start with v2rayNG. Consider v2flyNG only when you specifically need compatibility with V2Fly configurations. Choose based on your device and configuration, not similar client names.
What Each Client Can and Can't Do
This table summarizes features commonly found in each GUI. Setting names, core combinations, and available features may change as clients are updated; check the release notes for your installer. Scroll horizontally to view the table on narrow screens.
| Category | v2rayN | v2rayNG | v2flyNG |
|---|---|---|---|
| Platforms | Windows, macOS, and Linux; the WPF edition is Windows-only | Android | Android |
| Core | Typically uses Xray-core, with sing-box available for some configurations; not a dedicated V2Fly frontend | Xray core | V2Fly core |
| Maintenance | Actively maintained; check release notes separately for the cross-platform desktop and WPF editions | Actively maintained; core capabilities vary by client version | Community-maintained; check release notes for update cadence and core compatibility |
| Learning curve | Basic imports are straightforward; system proxy, routing, and TUN each require some understanding | Straightforward for typical Android use; requires VPN permission | Similar to other Android clients for basic imports; verify V2Fly compatibility first |
| Subscription groups | Separate group settings let you manage subscription URLs, updates, and group filters | Supports subscription management and separating configurations by source | Supports subscription management; imported content depends on core and parser support |
| Routing interface | Routing presets and rule management make it well suited to editing routes on desktop | Routing settings let you customize domain-, address-, and app-based routing | Includes routing settings; advanced fields depend on the current interface and core support |
| TUN and traffic handling | Supports TUN mode; permissions, virtual network adapters, and DNS need to be configured together | Handles traffic through Android's VPN service; this is different from enabling TUN on desktop | Handles traffic through Android's VPN service and requires system authorization |
| Best for | Desktop users, users with multiple subscription sources, and users who need fine-grained routing | Everyday Android use and users with existing Xray configurations | Android users with existing V2Fly configurations who want to stay on that core |
v2rayN: Desktop Subscription and Routing Management
v2rayN is a good fit for organizing multiple subscription sources, checking server configurations, and editing routing rules on a computer. Its main window brings the server list, subscription groups, and connection controls together, making it useful if you switch configurations often. Use v2rayN across desktop platforms rather than looking for a different client for each OS, but choose an installer that matches your operating system and processor architecture.
Windows users should distinguish between Desktop and the classic WPF edition. Desktop uses a cross-platform interface and runs on Windows, macOS, and Linux; WPF is Windows-only and retains the classic desktop workflow. Layout, tray behavior, and some settings may differ. If you're already familiar with WPF, choose the edition that fits your workflow. For cross-platform use, consider Desktop first, and don't assume the two editions share identical configuration directories.
Subscription groups are one of v2rayN's key management advantages. Each source has its own URL and update settings, making it easier to troubleshoot a group and distinguish subscription entries from manually added configurations. Routing presets provide a starting point, but check domain matching, IP matching, and outbound tags separately. The system proxy determines which apps send connections to the local entry point; it doesn't automatically route all traffic through the proxy.
TUN can handle apps that ignore the system proxy, but it takes more setup. Before enabling it, check the core combination, permissions, and DNS settings, and make sure a standard connection works first. If something goes wrong, switch back to system proxy mode to help isolate server connection issues from virtual network adapter issues. TUN isn't a necessary first step if you only use a browser.
v2rayNG: The Android Pick
v2rayNG is an Android client built around the Xray core. If you have a compatible subscription and want to import it and connect from your phone, the workflow is simple: add a subscription, update it, select a configuration, and connect. The first time you start the VPN service, Android will ask you to authorize the VPN connection. This is the standard permission flow for handling device traffic.
Android handles traffic differently from a desktop system proxy. The VPN service sends device traffic through the client, where the configuration and routing rules determine what happens next. App filtering and routing rules operate at different levels: if an app isn't included in the VPN, changing domain routing alone won't ensure its traffic goes through the client. Other apps using Android's VPN service may also replace or interrupt the connection.
v2rayNG supports subscription management and routing settings, making it suitable for everyday use and some advanced routing needs. However, a phone screen isn't ideal for editing lots of complex rules. First confirm that a basic configuration connects, then add custom rules. When troubleshooting, change one setting at a time instead of altering DNS, app filters, and routing together.
Most newer Android devices use arm64, but the year you bought your phone doesn't tell you its architecture. Check the ABI reported by the device; if you're unsure, consult the download page's notes on the universal build. If background connections are unreliable, check battery optimization, background restrictions, and network switching before changing your configuration. Switching clients won't necessarily change the OS's background management behavior.
v2flyNG: An Alternative for V2Fly Configurations
v2flyNG is also an Android client, with a GUI built around the V2Fly core. Its main use case is the core itself: consider v2flyNG if you already have a tested V2Fly configuration, need to reproduce its behavior, or are following instructions written specifically for V2Fly. If you're new to Android clients and don't have an existing configuration to support, v2rayNG remains the first choice.
Xray and V2Fly are both part of the Project V ecosystem, but their features have evolved differently. Support for the same proxy protocol doesn't mean their advanced parameters are interchangeable. Before switching, check the protocol, security layer, transport, and individual configuration fields. If the server instructions require a feature specific to one core, verify compatibility before choosing a client.
Everyday use still comes down to importing a subscription, selecting a configuration, and starting the VPN service. If a subscription updates but no usable configurations appear, check its format and the client's parser support. If a configuration appears but fails to start, check the core logs. The first issue is usually with importing; the second is with execution, so troubleshoot them differently.
Check the current release notes to understand maintenance status. Community maintenance doesn't mean every new core feature immediately appears in the Android interface, and an app being installable doesn't guarantee compatibility with your current subscription. If you already have a stable configuration, keep a record of it before testing a new installer. Don't assume this client is a lightweight edition designed for older or low-spec phones.
Choose a Client for Your Device and Experience
Start with platform support and compatibility, then compare workflows. A client's name doesn't guarantee speed or reliability.
Which Client to Choose and What to Download
For desktop, start with v2rayN; for Android, start with v2rayNG. Both handle common needs such as importing subscriptions, switching configurations, and routing traffic. Keep v2flyNG as an alternative when you specifically need V2Fly compatibility; there's no need to maintain duplicate configurations just to install another client.
Before downloading, check your platform, processor architecture, and required core. On Windows, choose Desktop or WPF. On macOS, choose Apple Silicon or Intel. On Linux, match the package format and architecture to your distribution. On Android, choose arm64 or a universal build based on your device ABI. Matching the installer is only the first step; check the download page and current release notes for minimum system requirements.
All three clients are tools for configuring and connecting to a service; installing one doesn't provide a working server address or subscription. If a connection fails, check the subscription, system time, and network access first, then review routing and DNS. Switching clients won't automatically fix an invalid server configuration.
For an overview of Xray and V2Fly, read the Project Overview. To configure inbound, outbound, and routing fields, see the Configuration Guide. If you've installed a client but haven't imported a configuration yet, follow the Setup Guide step by step.