For desktop, start with v2rayN; for Android, v2rayNG is the default pick. Compare v2flyNG if you already have Android configurations that specifically depend on V2Fly. Narrow down by device first, then check protocol and transport settings.
Start by checking whether the platform and your existing configuration are compatible, then consider your workflow. On narrow screens, swipe horizontally to scroll the table, or focus it and use the arrow keys.
Comparison criteria
v2rayN
v2rayNG
v2flyNG
Platforms
Windows、macOS、Linux
Android
Android
Core
Choose a supported core based on your configuration and version; Xray is common
Primarily Xray
V2Fly
Maintenance
Actively maintained
Actively maintained
Community project; check release history for the latest updates
Ease of use
Straightforward import; learn the differences between system proxy, TUN, and routing rules
Subscriptions, server selection, and connection controls are grouped in a straightforward mobile interface
The basic import steps are similar; first check whether the profile is V2Fly-compatible
Subscription groups
Group multiple subscription sources to update and filter them by source
Manage multiple subscriptions and update or switch between them on your phone
Add and update subscriptions; grouping options depend on the version
Routing interface
Manage routing in the GUI, with controls for fine-tuning rules and their order
Adjust common traffic-routing options in the interface; advanced controls vary by version
Check the current version for common routing options and custom configuration controls
TUN and traffic handling
Supports system proxy; TUN availability depends on the OS, client version, and permissions
Handles traffic through Android's VPN interface; this is separate from the desktop TUN toggle
Handles traffic through Android's VPN interface and requires system permission
Best for
Desktop users, people with multiple subscription sources, or anyone who needs fine-grained routing
First-time Android users or those with Xray-compatible subscriptions
Android users with existing V2Fly-compatible profiles who want to keep using their current setup
Adding a subscription, recognizing a profile, and connecting successfully are three different things. All three clients can manage subscriptions, but a single source may include different protocols and transports. A profile appearing in the list doesn't mean the current core can use it.
Client Reviews: Differences in Everyday Use
Desktop · Multiple Sources
v2rayN: Subscription Groups and Routing
Choose v2rayN if you regularly switch subscription sources on your computer or need different traffic routes for your browser and developer tools. When importing subscriptions, give each group a name that identifies its source. After updating, select servers from the relevant group. If different subscriptions contain profiles with the same name, check their groups to confirm where they came from rather than assuming they are identical based on the name alone. Start small when editing routes: test a known rule, then check whether an earlier rule is matching first.
If you just want to check whether your browser can connect, start with the system proxy. If a target app doesn't use it, consider the app's own proxy settings or TUN. TUN changes how traffic reaches the client; it doesn't mean all traffic has to use the same outbound route. If your browser works but your terminal doesn't, first check whether they use the proxy differently. Avoid changing the client, core, and routing mode all at once. Choose the installer for your desktop OS and CPU architecture. On Windows, pick the desktop or classic WPF edition based on your preferred interface.
Android · Xray
v2rayNG: Subscriptions and Connections on Android
For a first-time Android setup, v2rayNG has a clear workflow: add a subscription, refresh the profiles, select one, tap Connect, and approve Android's VPN permission prompt. Granting permission only lets the client handle system traffic; it doesn't confirm the server is reachable. Once the VPN icon appears, test access in an app you intend to use. If only one app fails, check for per-app routing or exclusion settings first.
When moving from desktop, you can usually import a compatible subscription again, but there's no need to copy over your desktop routing settings. Local proxy ports and terminal proxy variables on desktop are different from per-app settings on a phone. If a profile works on your computer but not your phone, compare the selected profile, core, and current network. Also check whether another app has already enabled Android's VPN. Separating device-specific issues from subscription problems makes troubleshooting much faster.
Android · V2Fly
v2flyNG: Keep Using V2Fly-Compatible Configurations
Choose v2flyNG if you have a configuration explicitly marked as V2Fly-compatible or need to test how that type of profile behaves on your phone. Import one known-compatible profile first as a baseline, then update the full subscription. If a profile is missing or won't connect, check whether the current core supports its protocol, transport, and security settings. The same protocol name alone doesn't guarantee that configurations are interchangeable. For example, if a profile relies on Xray's REALITY, v2rayNG is the better choice because it supports the relevant settings.
Choose v2flyNG for core compatibility, not because of your phone's age. If you're switching from another Android client, disconnect its VPN first, then import and test in the new client. Once you've confirmed the new client meets your connection and routing needs, decide which one to keep. If the problem only appears after the screen locks, check Android's background and battery settings before blaming the core for dropped connections.
Recommendations for Four Common Use Cases
Check Platform and Configuration Before Downloading
For desktop, start with v2rayN; for Android, start with v2rayNG. Choose v2flyNG only if you've confirmed that you need to keep using a V2Fly-compatible configuration on Android. In the Download Center, select your platform, then choose an installer for your CPU architecture or distribution package format. If you already have a working setup, note your subscription groups, commonly used routes, and traffic-handling method before switching clients so you can check each one in the new setup.