v2rayN
For Windows, macOS, and Linux. Manage subscriptions in one place, adjust routing rules, and configure the system proxy or TUN as needed.
Platform first · Match the core
V2Ray Client Comparison
V2Ray Client Comparison
and Selection Guide
Choose v2rayN for desktop and v2rayNG for Android. Consider v2flyNG if you already need a v2fly configuration. Match your device and configuration before comparing features.
v2rayNG
For Android, powered by the Xray core. Import a subscription, grant VPN permission to connect, and choose which apps use the proxy.
Platform, Core, and Feature Comparison
All three clients offer a graphical interface, but they are not simply different names for the same software. The client handles configuration and the interface; the core handles protocols, transport, and routing. A subscription URL can contain different types of configuration. Whether it imports and connects depends on the client's parsing capabilities and the core's supported features—not just how similar the interfaces look.
Maintenance status is described in general terms and does not imply that projects follow the same release schedule or that every new feature is available in every build. Check the release notes and client interface for current menu names, minimum system requirements, and feature support.
| Comparison | v2rayN | v2rayNG | v2flyNG |
|---|---|---|---|
| Platforms | Windows、macOS、Linux | Android | Android |
| Core | Xray / sing-box; choose based on configuration and features | Xray | v2fly |
| Maintenance | Actively maintained, with ongoing desktop releases | Actively maintained, with updates focused on Android and the Xray ecosystem | Community-maintained with an independent release schedule; check the release notes before installing |
| Ease of use | Basic connections are straightforward; system proxy, routing, and TUN each require separate setup | Basic connections are straightforward; requires VPN permission and background settings | Basic operation is simple; check v2fly configuration compatibility first |
| Subscription management | Group subscriptions, refresh them, and switch configurations; suited to multiple sources | Subscription groups and refresh controls for everyday switching on mobile | Subscription management available; supported formats and update options depend on the app |
| Routing interface | Desktop rules interface makes it easier to review presets and edit matching conditions | Mobile routing settings and per-app proxy controls | Routing settings available; rule fields depend on core support |
| TUN and traffic handling | TUN features available; requires a compatible core, permissions, and platform | Routes traffic through Android VpnService; desktop TUN steps do not apply | Routes traffic through Android VpnService; behavior depends on the client implementation |
| Best for | Desktop users, subscription managers, and users who need fine-grained routing | Android beginners, users with Xray configurations, and those who need per-app proxying | Android users with existing v2fly-compatible configurations who specifically need that core |
v2rayN: Desktop Subscriptions and Routing
For desktop use, start with v2rayN. Windows, macOS, and Linux users can manage subscriptions within the same client family, but must download the build for their operating system and processor architecture. The desktop interface offers more room to manage configuration lists and subscription groups, and edit rules—useful when maintaining separate configurations for work, study, or testing.
Desktop or WPF?
The Windows download section offers Desktop and WPF builds. Desktop uses a cross-platform interface; WPF retains the classic Windows interface. New users can start with Desktop, while those familiar with the classic interface may prefer WPF. The interface technology alone does not determine connection speed; performance also depends on the core, nodes, network, and rules.
More features mean more settings to manage
To get started, import a subscription, select a configuration, set up the system proxy, and test the connection in a browser. Set up TUN only if apps that ignore the system proxy need proxy access. Before switching between Xray and sing-box, check that your configuration and routing options work with the target core. Changing cores is not a universal troubleshooting fix. v2rayN is a good fit for users who want to manage traffic capture and routing separately.
v2rayNG: The Everyday Choice for Android
Android users should start with v2rayNG, especially when their subscription provider says the configuration is designed for Xray. Its mobile interface brings subscriptions, configuration selection, and connection controls together for easy on-demand use. When the app first requests Android VPN permission, note that this creates a local traffic-routing tunnel; it does not add a network service to your subscription.
Per-App Proxy and Background Operation
To proxy only selected apps, check the per-app proxy settings. Confirm whether the list shows apps included in or excluded from the proxy, then save and reconnect to test. Battery optimization, background restrictions, and other VPN connections can also affect everyday use. If the app works until the screen locks and then disconnects, check these settings before switching clients.
The main learning curve with v2rayNG is Android permissions and background management—not mastering every protocol setting. Beginners can troubleshoot more easily by keeping the default routing, testing one working configuration, and then adjusting app coverage as needed, rather than changing DNS, routing, and transport settings all at once.
v2flyNG: Choose It When You Need v2fly
v2flyNG is an Android alternative built around the v2fly core. Choose it when your existing configuration fits the v2fly ecosystem—not because the name sounds familiar, the package is smaller, or its performance seems better without testing. V2Fly and Xray are related but independently developed core projects. They share some protocols and concepts, but you should not assume their extensions, parameter formats, or implementation details are interchangeable.
Check Compatibility Before Migrating Subscriptions
If the server documentation requires an Xray-specific feature, don't assume v2flyNG can fully support it just because it recognizes the link. A successful import only means the client accepted the input; it does not confirm support for the protocol, transport, security settings, or core features. Test a known-compatible configuration first, then add the full subscription to make problems easier to identify.
When assessing maintenance, check whether the latest release notes cover your system and configuration needs rather than comparing update frequency alone. v2flyNG may suit users with a stable v2fly setup who want to keep using the same configuration approach. Android proxy beginners without a specific core requirement should start with v2rayNG.
See the v2flyNG alternative · Browse protocol and core terminology
Choose a Client by Use Case
Check Compatibility Before Downloading
- Check the platform and architecture. Choose a desktop build for Windows, macOS, or Linux. For macOS, check whether your Mac uses Apple Silicon or Intel; for Linux, check the package format and processor architecture. On Android, choose a build for your device's architecture—universal does not mean compatible with every system.
- Check configuration requirements. Review the server's protocol, transport, and security settings, and confirm core support. Protocol names such as VMess and VLESS are only part of a configuration; all parameters must match.
- Check which traffic needs to be captured. For browser-only use, start with the system proxy. If a specific app is not being proxied, check its own settings, per-app coverage, or TUN requirements.
- Keep a way to roll back. Before migrating, note your subscription groups, routing presets, and key local settings. Change one type of setting at a time so you can restore things more easily and distinguish client differences from network issues.
The best choice is not necessarily the client with the most features. Make sure you understand how it captures traffic on your device, which core runs your configuration, and where to start troubleshooting. For desktop, choose v2rayN; for Android, choose v2rayNG. Reserve v2flyNG for specific v2fly compatibility needs. If an imported configuration will not connect, see connection troubleshooting before reinstalling repeatedly.