V2Ray Clients
Compared and reviewed

For Windows, macOS, and Linux, v2rayN is the recommended choice. Its desktop interface makes it easy to view subscription groups, server lists, and logs together, and revisit routing settings after making changes. You can update multiple subscription sources separately by group instead of mixing every configuration into one list. Grouping helps with organization; it doesn't mean the client automatically picks the best-performing server for you.

The Windows download page offers the desktop edition and the classic WPF edition. The desktop edition uses a cross-platform interface for a similar workflow across desktop systems; the WPF edition retains the classic Windows interface. Menus may differ, so don't assume a screenshot of one interface represents every release package. Choose one edition to start with. When troubleshooting, avoid running multiple instances at once, as they may compete for local ports.

For everyday browsing, start with “Set system proxy” under “System proxy,” then choose a suitable mode under “Routing.” The system proxy affects only apps that honor that setting. If an app ignores it, consider TUN. TUN adds permissions, a virtual network interface, and more DNS troubleshooting, so it isn't required for every connection. Check which cores are available in your release package; the client name alone doesn't tell you which core it uses.

v2rayNG is the usual starting point for Android users. It uses the Xray core and brings subscription imports, configuration selection, and connection controls together in a mobile interface. The first time you connect, Android asks for VPN permission. Grant it so the client can route traffic through Android's VPN interface. This permission enables traffic routing on your device; it doesn't provide a remote configuration or replace importing a subscription.

To limit which apps use the connection, check the per-app routing options under “Settings” and choose which apps should use the proxy. Per-app routing decides which apps the client handles; domain or IP routing determines how requests are routed by the core. These are separate settings. After changing them, test the specific apps you want to use—one successful browser visit doesn't confirm that every app is routed as expected.

Common phone issues include battery restrictions, background app cleanup, and network changes. If the connection drops when the screen locks, check battery optimization and background-running permissions before switching cores. Another service using the VPN interface may also conflict with the client. For a simpler start, keep the default DNS and basic routing, confirm that one configuration works, and then enable extra features one at a time to make problems easier to pinpoint.

Choose v2flyNG because you need the v2fly core—not because a different app name is expected to improve your connection. It makes sense when your existing configuration is built for that core or you need to compare its protocol, transport, and routing behavior. Like v2rayNG, it runs on Android, provides subscription and configuration management, and routes traffic through the system VPN interface. The basic workflow is similar to other Android proxy clients.

Xray and v2fly are both part of the Project V ecosystem, but their feature development has diverged. Being able to import a subscription only means the client recognizes its format; it doesn't guarantee that the current core supports every protocol parameter or transport extension. For core-specific extensions, check the configuration requirements and logs. Don't assume a configuration that works in another client will work unchanged here.

For Android users without a specific core requirement, v2rayNG is still the recommended starting point because it keeps the initial setup simpler. If you keep v2flyNG as an alternative, manage its configurations and app data separately. Before uninstalling either client, save any subscription sources and custom rules you need. Hide subscription URLs and account details before sharing logs; don't post usable configurations as ordinary screenshots.