V2Ray Client Comparison
For desktop, start with v2rayN. For Android, start with v2rayNG. Consider v2flyNG only if your Android setup specifically requires the V2Fly core.
Platform, Core, and Feature Comparison
Start with platform, then check which core your configuration requires. On narrow screens, swipe horizontally. To see more columns with a keyboard, focus the table area and use the left and right arrow keys.
| Comparison | v2rayN | v2rayNG | v2flyNG |
|---|---|---|---|
| Platforms | Windows、macOS、Linux | Android | Android |
| Core | Can use Xray or V2Fly, depending on the configuration; available options vary by client and core settings | Xray | V2Fly(v2fly) |
| Maintenance | Actively maintained; desktop UI evolves across release branches | Actively maintained; Android UI and core are updated with releases | Community-maintained; check its release history for update cadence |
| Ease of Use | Easy to get connected; editing rules or enabling TUN takes extra setup | Low; import a configuration, select a node, grant permission, and test the connection | Core tasks are similar to v2rayNG; check core compatibility before choosing it |
| Subscription Groups | Supports group management and updating nodes by source | Add and update sources through subscription groups | Supports subscription management and works well for organizing V2Fly-compatible sources |
| Routing Interface | Manage rule sets, match conditions, and outbound settings in the GUI | Adjust routing and app coverage in settings; the layout differs from desktop | Includes routing settings; available options depend on the current client interface |
| TUN and Traffic Routing | Offers desktop TUN mode; requirements vary with system permissions and runtime environment | Routes traffic through Android's system VPN interface; system permission required | Also routes traffic through Android's system VPN interface; system permission required |
| Best For | Desktop users, people managing multiple subscription groups, and users who build their own rules | First-time Android proxy setup or users with an existing Xray configuration | Users with V2Fly-compatible configurations or those who need to keep using that core on Android |
App filtering determines which apps send traffic through the client. Routing rules determine which outbound route that traffic takes. When troubleshooting split tunneling, first check that the app is included in the client’s coverage, then review the rules.
Why Choose Each Client
These reviews follow the setup flow: where to import configurations, how traffic is routed by default, and what to check before switching clients.
v2rayN: Desktop Subscriptions and Routing
Downloads for Windows, macOS, and Linux are listed under v2rayN. The Windows download page offers both the desktop edition and the classic WPF edition. If you're new, start with the desktop edition; if you're used to WPF, you can stick with the classic version. For macOS, choose a package for Apple Silicon or Intel. On Linux, check your distribution's package format and then confirm the processor architecture. Package formats affect installation, not which nodes a subscription can recognize.
To get started, add a source under subscription groups and update it. Select a node, then test the connection with an app that respects system proxy settings. Subscription groups organize sources; they don't assign an outbound route to a specific app. The active routing rules determine the route. If only one app bypasses the proxy, first check whether it respects system proxy settings, then decide whether TUN is needed. When editing domain or IP rules, change one set of conditions at a time. Check rule order and the outbound tags they reference to tell whether the match order is wrong or the traffic isn't reaching the client at all.
v2rayNG: First-Time Android Setup and Everyday Use
v2rayNG is a good fit if you want to get a connection working on your phone first. Add a single share link through the import option. For a group of nodes that needs regular updates, enter its address under subscription groups and update it. Once the list is populated, select a node and start the connection. The first time you connect, Android will show a VPN permission prompt. If another app is already using the system VPN interface, disconnect it before trying again; there's no need to change node settings right away.
If you want some apps to use different routes, first decide whether an app should bypass the client entirely or whether its traffic should pass through the client and use a direct outbound rule. These are separate settings. Test a frequently used app within the default coverage first, then add app filters or routing conditions one at a time. Retest the same app after each change. If the connection drops only after the screen has been locked for a while, check battery optimization and background activity restrictions before assuming the subscription has failed.
v2flyNG: An Android Alternative for the V2Fly Core
If your existing documentation specifies V2Fly as the runtime, or you already have a configuration that uses this core, v2flyNG lets you keep the same core on your phone. Before importing, check the protocol, transport, and security settings—not just the node name. Two subscriptions can both populate a node list without every entry being compatible with the same core. For configurations that explicitly rely on Xray features, such as REALITY, consider v2rayNG first rather than repeatedly changing the subscription URL.
When switching from v2rayNG, keep your existing groups and first import one known-compatible configuration into v2flyNG. Test connecting, disconnecting, and reconnecting before adding other sources. The two apps store subscriptions and settings separately; importing nodes won't migrate routing rules or app filters. If the new app behaves differently with only certain destinations, compare the rules and app coverage in both apps before investigating core compatibility. Choose this alternative to meet configuration requirements, not because the core name implies a performance ranking.
Choose by Use Case
First-Time Setup: Test One Connection
Use v2rayN on desktop and v2rayNG on Android. Import one known-working configuration, select it, and connect. At first, check only whether the subscription updates and the node connects; don't change DNS, app filters, and routing rules all at once. If the list is empty, check whether you entered a subscription URL or a single share link, then make sure you updated the right group.
Advanced Routing: Match Rules to Outbound Routes
When managing multiple rules in desktop v2rayN, note the match target and expected outbound route for each one. Then test one destination that should connect directly and one that should use the proxy. When moving the configuration to Android, check which apps the client is routing. Even with the same node on both devices, app coverage and routing results may differ.
Multiple Devices: Shared Subscriptions Don't Sync Settings
Use v2rayN on desktop and v2rayNG on Android. If your phone specifically requires V2Fly, choose v2flyNG for that device. Whether a subscription can be used on multiple devices depends on the provider's terms. Even when a source can be reused, update the subscription, select a node, and save local rules separately on each device. When troubleshooting, note the device, subscription group, and traffic routing mode to avoid mistaking a device-specific setting for an outage affecting the entire connection.
Older Android Phones: Check Architecture and System Requirements
First, check whether the system supports arm64 apps. If you can't confirm this or the arm64 package won't install, see whether the universal package is suitable. A universal package supports more architectures but doesn't lower the client's minimum Android version. If it installs but frequently disconnects after launch, check VPN permissions and background activity settings first. Choose v2flyNG only if your configuration is compatible with V2Fly.
Recommendation
For desktop, choose v2rayN; for Android, choose v2rayNG. Choose v2flyNG only when you specifically need the V2Fly core and your existing Android configuration is compatible. Once you've chosen a client, select a package for your operating system and processor architecture in the download center.