CLIENT SELECTION
Start by narrowing the options by device platform, then compare the core, subscription management, routing controls, and traffic-handling method. For desktop devices, look first at v2rayN; on Android, compare v2rayNG and v2flyNG.
Choose by Platform
Your device comes first
QUICK ANSWER
The three clients are not complete substitutes on the same platforms. Desktop and Android users naturally follow different paths first; Android users are the ones who typically need to compare the two core options further.
DESKTOP PICK
Users on Windows, macOS, and Linux should start with v2rayN. It brings server lists, subscription groups, system proxy controls, routing rules, and TUN into one desktop GUI, making it suitable for progressing from basic connections to multiple subscriptions and fine-grained traffic routing.
Go to the v2rayN download page →ANDROID PICK
Most Android users can start with v2rayNG. It uses the Xray core, provides clear paths for importing subscriptions, switching configurations, and setting routes, and handles device traffic through the Android VPN service. Consider v2flyNG when an existing configuration explicitly depends on V2Fly behavior.
Go to the Android download page →FULL COMPARISON
Use this table to narrow down your choice, not to replace server-side requirements. Protocols, transport, security parameters, and authentication details must still match the server configuration item by item.
| Comparison Criteria | v2rayN | v2rayNG | v2flyNG |
|---|---|---|---|
| Platform Support | Windows、macOS、Linux | Android | Android |
| Primary Core | Xray | Xray | V2Fly |
| Maintenance Status | Actively Maintained | Actively Maintained | Actively Maintained |
| Learning Curve | Moderate. Basic imports are simple, but the desktop client has many settings and requires an understanding of the difference between the system proxy and TUN. | Relatively easy. Importing a subscription, selecting a configuration, and starting a connection follow a focused workflow. | Moderate. The workflow is similar to other Android GUI clients, but confirm V2Fly compatibility requirements before choosing it. |
| Subscription Groups | Well suited to managing multiple subscription sources, with options to update, filter, and switch servers by group. | Supports subscription imports and updates for everyday configuration switching on Android. | Supports subscription imports and configuration management, with an emphasis on the V2Fly core path. |
| Routing-Rule Interface | Offers comprehensive desktop controls for managing rule sets and directing domain and IP traffic. | Provides Android routing controls for common bypass, proxy, and app-traffic requirements. | Provides routing configuration for the V2Fly core; available rule capabilities depend on the specific configuration. |
| TUN & Traffic Handling | Supports TUN. Before enabling it, check system permissions, route conflicts, and local security-software settings. | Takes over TUN traffic through the Android VPN service and can handle connections by app and route configuration. | Handles device traffic through the Android VPN service, with behavior aligned to the V2Fly configuration model. |
| Standout Features | Desktop multi-subscription management, system-proxy switching, routing-rule UI, TUN, and log viewing. | Quick mobile configuration switching, per-app proxy selection, routing settings, QR-code and clipboard imports. | V2Fly core compatibility, mobile subscription management, app-traffic controls, and routing settings. |
| Best For | Desktop users, people managing multiple subscriptions, and users who need detailed routing or manage several computers. | Most Android users, as well as anyone who wants the Xray core and mobile GUI controls. | Android users with existing V2Fly configurations or a clear need for V2Fly core behavior. |
CLIENT NOTES
Expand each review for practical workflows and selection criteria; avoid drawing conclusions from the client or core name alone.
WINDOWS · MACOS · LINUX
v2rayN is suited to managing desktop connections, subscriptions, proxy modes, and routing rules in one place. To get started, import a subscription, select a working configuration, and enable the system proxy; once the basics are familiar, decide whether to use TUN based on software compatibility. This gradual workflow is clear for both beginners and advanced users.
Its strength is broad desktop coverage. Multiple subscription sources can be grouped, the log window helps reveal clues about connection startup and failed requests, and the routing interface is useful for direct, proxied, and blocked traffic rules. When office apps, browsers, and developer tools run together, centralized desktop settings are easier to maintain than configuring each app separately.
The number of settings is also something to watch. The system proxy, PAC, global mode, and TUN do not solve exactly the same problems, so avoid switching among them repeatedly without a clear reason. When a connection fails, keep one traffic-handling method in place and check the local network, subscription status, configuration parameters, and logs in that order.
ANDROID · XRAY
v2rayNG is designed for Android users who want to quickly import subscriptions, select configurations, and control the connection. Common actions are grouped in the main screen and side menu: import a single configuration from the clipboard or a QR code, or add a subscription URL and update it centrally. Users who maintain one subscription source usually do not need to enter advanced settings often.
The client handles traffic through the Android VPN service, so Android will ask for the relevant permission the first time it starts. Per-app proxy settings, routing rules, and DNS settings determine which traffic enters the client and should be adjusted to match your goal. If the basic configuration already connects normally, there is no need to change every advanced option at once.
v2rayNG uses the Xray core and is a good fit when the subscription clearly provides the corresponding protocol parameters. If an import succeeds but the connection fails, first check that the configuration is complete, the phone clock is accurate, background activity is not restricted, and the current network can reach the server address. Timeouts, authentication failures, and address-resolution details in the log can help narrow down the cause.
ANDROID · V2FLY
v2flyNG also targets Android, but its key distinction is not the interface—it is the V2Fly core. If a provider, existing configuration file, or established workflow is explicitly maintained around V2Fly, choosing v2flyNG reduces uncertainty caused by differences in core behavior. Without those prerequisites, starting with v2rayNG is usually more straightforward.
It includes the subscription and configuration management features commonly needed on mobile and handles device traffic through the Android VPN service. After importing a configuration, still verify the protocol, transport, and security parameters. The fields shown and default behavior may differ between core implementations, so a successful import alone does not prove full compatibility.
When choosing a client for an older phone, do not estimate performance from the device year alone. Confirm the processor architecture and package type first, then observe background restrictions, memory use, and actual connection stability. If the subscription explicitly requires V2Fly, v2flyNG is a sensible choice; without a core requirement, try the general v2rayNG package first.
SCENARIO GUIDE
Once the platform is clear, factor in your familiarity with the workflow, number of devices, and existing configuration setup.
Choose v2rayN on Windows, macOS, or Linux, and v2rayNG on Android. For the first setup, only import the subscription, select a configuration, and start the connection. Do not change routing, DNS, and TUN at the same time. After the basic connection works, learn advanced features one at a time.
Use v2rayN on desktop to manage routing rules, the system proxy, and TUN. On Android, use v2rayNG for per-app proxy and routing settings; if the environment explicitly requires the V2Fly core, use v2flyNG instead. Changing one variable at a time makes its impact easier to identify in the logs.
Use v2rayN on computers and v2rayNG on Android devices. The subscription source can remain the same, but the system proxy, TUN, per-app proxy, and background-operation policy must be configured separately on each device. Syncing a subscription does not automatically sync local network policies.
If you are unsure of the processor architecture, start by checking the general package notes in the Android download section. After installation, focus on background operation, battery policies, and available memory. Choose the client core based on subscription compatibility, not simply on how old or new the phone is.
DECISION PATH
If you are still unsure, narrow it down in the order below. Platform is the hard requirement, core compatibility comes second, and interface features are preferences to consider afterward.
If your primary device is Windows, macOS, or Linux, choose v2rayN. If it is Android, continue to the next comparison step. Users with multiple devices do not need to force the same client name everywhere; choose the client for each platform separately.
When an Android setup has no explicit core requirement, start with v2rayNG. If the configuration explicitly uses V2Fly or the existing workflow is maintained around the V2Fly core, choose v2flyNG.
For desktop subscription groups, a rule UI, and TUN, use v2rayN. For Android per-app proxy and mobile routing, use v2rayNG or v2flyNG. Advanced features should come after the basic configuration is working.
SELECTION NOTES
CLIENT
v2rayN, v2rayNG, and v2flyNG are GUI clients; VMess, VLESS, and Trojan are protocols that may appear in a configuration. After choosing a client, make sure it supports the required parameters and matches the server settings.
CORE
Xray and V2Fly are different core paths within the Project V ecosystem. The core affects protocol capabilities and configuration behavior, but the address, port, authentication, transport, and local network also determine whether a connection succeeds.
MODE
The system proxy mainly affects apps that follow system proxy settings; TUN handles a broader range of traffic. Start with the simplest method that meets your needs, and consider TUN only when apps do not honor the system proxy or another specific requirement arises.