Client guide / Platforms and cores

Comparing v2rayN, v2rayNG, and v2flyNG

Choose a client for your device first, then check which core your configuration needs. v2rayN is the desktop pick, v2rayNG is the Android pick, and v2flyNG is worth considering if you already use V2Fly configurations.

Download a client by platform Compare features

Compare platforms, cores, and configuration features

This table compares how the clients work; it does not rate them. Menus, protocol fields, and core options can change between versions, so check the installer and configuration requirements before installing. On narrow screens, swipe horizontally to view the table.

Platform, core, maintenance, and feature differences between v2rayN, v2rayNG, and v2flyNG
Comparison	v2rayN	v2rayNG	v2flyNG
Platform support	Windows、macOS、Linux	Android	Android
Core options	Typically uses Xray. Available cores and switching options depend on the version; v2fly is not necessarily included.	Xray	v2fly
Maintenance	Actively maintained; compatibility work may progress at different rates across platforms and UI branches.	Actively maintained; features evolve with client and core updates.	Community-maintained, with its own release schedule. Check feature compatibility before choosing it.
Ease of use	Basic subscription setup is straightforward; distinguish system proxy from TUN.	Straightforward for most users; importing a subscription requires Android VPN permission.	Basic use is similar to other Android clients, but v2fly compatibility needs extra checking.
Subscription groups	Organize and update multiple subscriptions in groups.	Group subscriptions, save their URLs, and update them.	Import subscriptions and organize them into groups; menus vary by version.
Routing rule UI	A visual rule editor makes it easier to review and adjust rules on desktop.	Includes routing settings and custom rule options, focused on common adjustments on a phone.	Includes routing settings; available fields depend on both the UI and the core.
TUN and traffic handling	Supports TUN, depending on the platform, companion core, permissions, and version.	Routes traffic primarily through Android VPN mode; desktop TUN instructions do not apply.	Routes traffic primarily through Android VPN mode, which is not the same as a desktop TUN toggle.
Key features	Desktop subscription management, rule editing, system proxy, and TUN configuration.	Per-app proxying, local DNS, and VPN mode settings.	Uses the v2fly configuration ecosystem, making it useful for checking compatibility with existing configurations.
Best for	Desktop users who regularly review rules and logs.	Android newcomers and anyone who needs per-app proxying.	Android users with existing configurations that specifically require the v2fly core.

Desktop pick

v2rayN: desktop subscriptions and routing

For Windows, macOS, and Linux. Choose v2rayN if you want to manage subscriptions, edit rules, or review logs on a larger screen.

Check your platform, then choose an interface and architecture

Open the panel for your platform on the download page, then choose an installer. Windows offers a newer cross-platform desktop edition and the classic WPF edition. Their main differences are the interface and workflow; a newer-looking UI does not necessarily mean better connection performance. Keep using a configuration workflow you already know, or follow the download page’s guidance if you’re installing for the first time.

For macOS, check whether your device uses Apple Silicon or Intel. For Linux, confirm both the processor architecture and the package format for your distribution. Cross-platform support does not mean permissions, system proxy settings, or TUN behavior are identical on every platform. Follow the menus in your current operating system.

For users who regularly adjust routing rules

Save the subscription URL in a group and update it, then review the rules in routing settings. The desktop interface makes it easier to compare domains, address ranges, outbound tags, and rule order. A larger screen can help prevent mistakes when setting up complex routing, but whether a rule takes effect still depends on the core and the actual traffic path.

Android pick

v2rayNG: Android subscriptions and per-app proxying

For everyday Android use, start with v2rayNG. Its Xray core, subscription groups, and per-app proxying cover common needs, from importing a subscription to adjusting basic routing.

Start with subscription groups

Open Subscription Group Settings from the side menu, create a group, and enter a note and subscription URL. Save it, return to the main screen, and update the subscription before selecting a configuration and connecting. Saving a URL alone does not create a usable configuration. If the list is empty, check the update result before reinstalling the app.

On first launch, Android asks for permission to establish a VPN connection. Grant permission, then check that your browser and other apps work as expected. Android’s VPN interface handles traffic routing; it does not provide a remote service. You still need to supply a subscription or connection configuration.

Choose which apps route through the proxy

In per-app proxy settings, check whether selected apps are routed through the proxy or bypass it. A checkbox alone does not tell you the resulting traffic path. Save your changes, reconnect, and test apps in both groups. This makes problems easier to isolate than changing several routing options at once.

Android alternative

v2flyNG: for existing V2Fly configurations

Consider v2flyNG when your existing configuration was built specifically for the v2fly core and you can confirm that its protocols and fields are compatible.

Choose by core, not by name

Both v2flyNG and v2rayNG are Android clients, but their key difference is the core family. V2Fly and Xray come from related ecosystems, yet their features and configuration formats have evolved differently. Even configurations using the same protocol name can differ in compatibility because of their transport or extension parameters.

If you already have a working v2fly configuration, keep the original file and subscription URL, then try importing it into v2flyNG. Test one configuration first and check the startup logs and target apps before migrating the full group. If a configuration relies on an Xray-specific feature, do not force it to run by deleting fields that cause errors; choose a compatible client and core instead.

Assess maintenance and older devices separately

As a community-maintained alternative, v2flyNG has its own update schedule, independent of v2rayNG. Before choosing it, check the current installer’s system requirements, core capabilities, and issue reports. Update frequency alone does not determine stability, and the app’s name does not tell you whether it is a better fit for an older device.

Android users will find basic subscription and VPN setup familiar, but checking core compatibility takes extra work, making v2flyNG a more involved choice than the recommended options. If you do not specifically need v2fly, start with v2rayNG. Compare alternatives only if a configuration compatibility issue arises; there is no need to install several clients and switch between them.

View the v2flyNG alternative download

Choose a client for your use case

Start with your device and configuration needs, then consider advanced features. These recommendations are not based on speed rankings or subjective scores.

Pre-migration checks and recommendations

Switching clients is rarely the first step. First determine whether the problem is caused by the configuration, permissions, or core compatibility, then decide whether to migrate.

Keep your configuration and test one change at a time

Record your current setup. Save the subscription URL, group notes, and any routing rules you changed. Subscription URLs may contain credentials, so do not post them in public forums or include them in screenshots.
Check the protocol and core. Confirm the protocol, transport, and security parameters used by your configuration. Even if it imports successfully, check for missing fields instead of relying on the configuration name appearing in the list.
Test a minimal configuration first. Disconnect the old client, then import just one configuration group into the new client. Keep the default routing, connect, and review the logs before testing your apps.
Restore advanced settings one at a time. Restore essential routing first, then adjust DNS, and finally configure per-app proxying or TUN. Change only one type of setting at a time so you can roll it back if something goes wrong.

Choose v2rayN for desktop and start with v2rayNG on Android

For desktop system proxy, subscription management, and rule editing, start with v2rayN. For Android subscription imports, VPN permission, and per-app proxying, start with v2rayNG. v2flyNG is for Android users with existing v2fly configurations who can confirm compatibility. All three are GUI clients; none can replace a valid remote service configuration or fix every connection problem just by switching apps.

When you’re ready to install, visit the client downloads page and choose a package for your operating system and architecture. If you’ve chosen a client but need help with the setup steps, read the subscription and connection guide. To learn more about cores, routing, and proxy modes, continue to the beginner-to-advanced guide.