Compare the three clients
Use this table to help choose a client; check the specific release notes for exact features. On narrow screens, scroll horizontally to see all columns.
| Category | v2rayN | v2rayNG | v2flyNG |
|---|---|---|---|
| Platform support | Windows / macOS / Linux | Android | Android |
| Core | Manage multiple cores on desktop; Xray is a common configuration path. For V2Fly configurations, check the selected core and current release. | Uses the Xray core; supported configurations depend on the bundled core. | Uses the V2Fly core; configuration must follow the protocols and fields it supports. |
| Maintenance | Actively maintained. Back up subscriptions, routes, and custom settings before updating. | Actively maintained. After updating, check permissions, services, and configuration compatibility. | Community-maintained. Check for a current release and system requirements before installing. A V2Fly option for users who need it. |
| Ease of use | Moderate learning curve. The many settings are easier to review on a desktop. | Easy to get started. After importing a subscription, check the active configuration and grant VPN permission. | Basic tasks are straightforward, but first check whether your existing configuration supports V2Fly. |
| Subscription groups | Manage subscription groups on a larger screen, with options for organizing multiple sources and updates. | Manage subscriptions and groups, then update or switch configurations on mobile. | Subscription management is available; group controls and options vary by installed version. |
| Routing UI | Includes a routing interface for reviewing rule order and outbound settings. | Includes routing options; understanding complex rules may require custom configuration and core documentation. | Includes routing options, with available fields and rules limited by the V2Fly core. |
| TUN and traffic routing | Includes TUN features; availability depends on platform, permissions, and release. You can also start with the system proxy. | Routes traffic through Android's VPN service; this is not a direct equivalent of desktop TUN settings. | Routes traffic through Android's VPN service; requires system permission and suitable background operation. |
| Key strengths | Bulk desktop management, subscription organization, route editing, and multiple traffic-routing options. | Xray configurations, mobile connection management, and per-app routing options. | Works with V2Fly configuration workflows; verify subscription and routing behavior with this core. |
| Best for | Desktop users and advanced users who want a visual way to manage rules. | Most Android users, especially those who need Xray features. | Android users with configurations specifically targeting V2Fly who are prepared to check compatibility. |
| Download | Choose a desktop version → | Explore v2rayNG → | Explore v2flyNG → |
v2rayN: Desktop subscriptions and routing
For desktop users who want to review configurations, rules, and runtime logs in one place.
Built for ongoing configuration management
What matters isn't the number of settings, but how clearly you can track the relationship between subscription sources, the active configuration, and routing outbounds.
Get started with v2rayN →v2rayN's main advantage is the room a desktop interface gives you to work. Review subscription groups, configuration lists, routing settings, and logs task by task. It's a good fit if you regularly adjust rules, keep multiple subscription sources, or compare configurations. You don't need to enable every advanced option right away. Start by importing a subscription, selecting an active configuration, and testing the connection with the system proxy; this makes problems easier to isolate.
Choose the right build before comparing features. The Windows download page offers a desktop version and a classic WPF version, which may have different interface workflows. For macOS, choose between Apple Silicon and Intel; for Linux, check both processor architecture and package format (deb or rpm). The desktop version uses a cross-platform UI, while the classic WPF version keeps familiar Windows interactions. Don't assume menus are in the same place in both interfaces.
A routing UI can make editing easier, but rules still match from top to bottom. Before adding a direct-connection rule, make sure the corresponding outbound exists. After changing domain rules, check DNS and domain resolution policies too. TUN can handle apps that don't follow the system proxy, but it adds requirements such as permissions, a virtual interface, and system routes. If your browser works but another app isn't routed, check how that app connects before switching to TUN.
The trade-off: more settings in one place can make a mistaken change affect more. Make subscription updates, core updates, and routing changes separately, changing one category at a time while monitoring logs. If your configuration is stable, keep a recoverable copy before testing new features. This makes troubleshooting easier than changing several options at once.
v2rayNG: Android and Xray configurations
For users whose main device is a phone and who want to start with a subscription import.
Check configuration support and system permissions first
Mobile connections depend on core settings, VPN permission, app inclusion, and background restrictions.
Get started with v2rayNG →v2rayNG uses the Xray core and is a solid default choice for Android. For typical subscription users, the routine is to update the subscription, select a configuration, start the service, and check the logs. If your subscription includes security or transport settings that rely on Xray features, confirm that the installed app's core supports them. Importing a configuration and seeing its name is only the first step; a successful connection also requires matching server and local settings.
Android VPN permission creates a system-level traffic routing connection; it is not authorization for your subscription service account. On first launch, read the system prompt and grant permission, then check whether another app is using a similar service. Per-app routing lets you limit which apps are covered, but can also explain why a browser works while another app doesn't. When troubleshooting, first check whether the app is included, then review domains, DNS, and rules instead of repeatedly switching subscriptions.
The trade-off is limited editing space on mobile. You can manage a handful of common settings in the interface, but complex rules require a clearer understanding of the configuration structure. Start with simple rules, confirm they work as expected after network changes and screen lock, then add exceptions gradually. If the service stops in the background, check battery management and background permissions; changing clients won't remove device-level restrictions.
v2flyNG: An alternative for V2Fly configurations
For users who've confirmed their core requirements—not those switching just because the name looks familiar.
Start by identifying the configuration behavior you need to preserve
Choose based on protocol and rule compatibility, not on the assumption that different cores are interchangeable.
Get started with v2flyNG →v2flyNG uses the V2Fly core. It's an option for Android users with configurations specifically designed for that core, or who need to verify routing and protocol behavior with V2Fly. Cores in the Project V ecosystem share some concepts and configuration conventions, but their protocol implementations, transport support, and field requirements can differ as the projects evolve. Don't copy a configuration that relies on Xray features into v2flyNG and expect it to work just by changing a name.
Importing a subscription and selecting a configuration works much like it does in other mobile clients. The real work is checking which configurations are supported. Before migrating, note the protocol, transport, TLS settings, and routing dependencies, then check each one against the target core. If a subscription contains configurations with different requirements, organize them separately rather than assuming both apps will generate identical runtime configurations from it.
Don't assume v2flyNG is a lightweight replacement for older phones. Reliable use still depends on system requirements, processor architecture, background restrictions, and configuration complexity. For first-time users without a specific V2Fly requirement, starting with v2rayNG is usually the more direct route to a working setup. If you do need this core, test v2flyNG with that goal in mind and keep your original configuration so you can restore it.
Choose by use case
One client can cover several use cases. Start with the task that matters most right now; there's no need to take on configuration overhead for advanced features you don't yet need.
What to check before downloading
Check platform, configuration compatibility, and traffic routing separately to avoid having to switch clients after installation.
- Check your device and architecture. Download the v2rayN build for your desktop platform; on Android, start with v2rayNG. Match both the processor architecture and package format—don't choose by client name alone.
- Check which core your subscription requires. Review the protocol, transport, and security settings, especially configurations that depend on Xray. If V2Fly is specifically required, consider v2flyNG; don't choose based only on which interface feels familiar.
- Decide which apps need traffic routing. The desktop system proxy works only with apps that follow system settings; TUN routes more network traffic. On Android, check VPN service permissions and per-app coverage. Don't assume the options are identical across platforms.
- Keep a working copy of your configuration. Before changing clients, note your subscription groups, routing, DNS, and custom settings. Export formats may not be compatible between clients, and a subscription link is not interchangeable with native JSON.
The bottom line: v2rayN is the top desktop pick, v2rayNG is the top Android pick, and v2flyNG is for specific V2Fly configuration needs. All three manage configurations and connections; installing a client doesn't provide a working subscription. After downloading, prepare a trusted, complete configuration and grant the required permissions, then test the connection on your device.
Visit the client downloads page to choose a platform and package. For your first setup, follow the quick-start guide. To learn about cores, routing, or TUN, continue to the full tutorial.