Client Comparison
V2Ray Client Comparison
Best for desktop: v2rayN. Best for Android: v2rayNG. Consider v2flyNG if you specifically need the V2Fly core.
Platform, Core & Feature Comparison
First rule out clients that don't support your device, then check which core your existing configuration requires. Importing the same link on two phones doesn't mean both clients support its protocols and transport settings. Scroll horizontally to view the table on narrow screens.
| Feature | v2rayN | v2rayNG | v2flyNG |
|---|---|---|---|
| Platforms | Windows、macOS、Linux | Android | Android |
| Core | Supports cores such as Xray; V2Fly availability depends on the release package and the client's core list | Xray | V2Fly(v2fly) |
| Maintenance | Actively maintained | Actively maintained | Community-maintained; check release notes for recent updates |
| Ease of use | Easy to connect; offers plenty of routing and system proxy options | Simple connection setup; requires Android VPN permission | Similar import steps to v2rayNG; check that your configuration is compatible with the core |
| Subscription groups | Add multiple subscription groups and update or switch between them separately | Add multiple subscription groups and view or update entries by group | Supports subscription imports and updates; group management varies by version |
| Routing interface | View and edit rules in a graphical interface, useful for managing multiple routing conditions | Configure routing and per-app proxying separately to control destination addresses and app coverage | Adjust routing in settings; available rule fields depend on client and core support |
| TUN & traffic routing | TUN is available on compatible systems; permissions and behavior depend on the OS and core | Creates a virtual interface through Android's VPN service | Creates a virtual interface through Android's VPN service |
| Best for | Desktop users and anyone who regularly manages subscriptions or routing rules | Anyone who wants to quickly import a subscription on an Android phone | Android users with existing V2Fly configurations or a need to compare V2Fly behavior |
Desktop TUN and Android VPN can both route traffic, but permissions, app coverage, and system restrictions differ. A feature listed as supported doesn't mean the client will route every app by default.
01 Best for desktop
v2rayN: Manage subscriptions and routing in one place
v2rayN stands out not just for supporting three desktop platforms, but for letting you manage subscriptions, nodes, and routing in one interface. If you maintain several subscriptions, group them by source, update the group you need, then choose from its new entries. When an update goes wrong, first determine whether the whole subscription failed or just one node won't connect. For the former, check the subscription URL and update method; for the latter, inspect that entry's protocol settings. This makes issues easier to pinpoint than deleting and reimporting every subscription.
For your first connection, start with the system proxy and check that an app using the system proxy settings works. Some apps ignore those settings; if so, consider the app's own proxy options or TUN. You don't need to enable TUN just because you've installed the client. If you regularly edit routing rules, use the graphical interface to check rule order, domain conditions, and outbound routing. Permissions and desktop integration vary by OS, so don't copy traffic-routing settings from one device to another without checking them. On Windows, choose the Desktop or classic WPF edition based on your interface preference. If you're following an older guide, match its interface names to the settings in your version.
02 Best for Android
v2rayNG: Xray core and per-app proxying
v2rayNG is a good fit if you already have a subscription URL and want to get connected on your phone. After adding a subscription, update its group to fetch the node list. If you have a single share link, import it as an individual configuration rather than entering it as a subscription URL. The first time you connect, Android will ask you to authorize the VPN connection. If another service is already using Android's VPN, check whether you can stop it before launching v2rayNG; switching nodes won't resolve a system-level conflict.
To control which traffic gets routed, distinguish per-app proxy settings from routing rules. Per-app settings decide which apps enter the virtual interface; routing rules decide where traffic already inside the client goes. If an app shouldn't use the client, first check whether it's included in the app list. If the same app needs different routes for different sites, check the domain or address rules. If the connection drops when the screen locks, first check whether the system is stopping the background service or whether the node still fails after you reopen the app. There's no need to start by reimporting your configuration.
03 Android alternative
v2flyNG: Keep using existing V2Fly configurations
Choose v2flyNG for its core, not because its interface looks similar to v2rayNG. For example, if you have a configuration that you've already used with V2Fly and want to compare its behavior on Android, start by testing a known-working configuration in v2flyNG. Before testing, check the protocol, transport, and security settings. If any of them rely on another core's implementation, a successful import doesn't guarantee a connection. In particular, don't assume a REALITY configuration that depends on Xray will work unchanged with V2Fly.
When migrating, start with one configuration rather than moving your entire subscription list, routing rules, and app list at once. Confirm the basic connection first, then restore routing. If behavior changes, you'll know to look at the last setting you restored. Don't assume v2flyNG will be lighter on an older phone; installation and performance also depend on the OS, processor, and package. If you don't specifically need V2Fly or have a configuration to reuse, v2rayNG is usually easier to follow alongside this site's Android getting-started guides.
Choose a Client by Use Case
Beginners: Get a basic connection working first
Use v2rayN on a computer and v2rayNG on an Android phone. First identify whether you have a subscription URL or a single share link, then choose the right import option and test a known-working entry with an app you use regularly. Once connected, adjust routing, DNS, or app coverage one setting at a time, testing with the same app after each change. That makes it easier to tell whether a problem is in the basic configuration or in a rule you added later. For step-by-step instructions, see the subscription import guide.
Advanced users: Choose based on routing complexity and core requirements
If you regularly route desktop traffic by domain, address, or outbound tag, use v2rayN's routing interface and save a restorable copy of your rules before editing. On Android, v2rayNG's per-app settings are usually enough if you just want to control which apps are routed; there's no need to write domain rules for every app. Choose v2flyNG only when you specifically need to test V2Fly behavior on a phone. For a useful comparison, keep the subscription, network, and test destination the same, and change one condition at a time.
Multiple devices: Share the subscription source, configure routing separately
Use v2rayN on desktop and v2rayNG on Android. If your subscription allows multiple devices and its entries are compatible, you can import the same URL on both. Updating a subscription refreshes the node list; it doesn't sync system proxy settings, routing rules, or app lists. For example, routing only your desktop browser and routing only selected Android apps into the virtual interface are separate settings. Verify each device independently, even after setting up the first. If only one device fails, start by checking its system permissions and traffic-routing method.
Older phones: Check OS requirements and processor architecture
On the download page, check the package's OS requirements and processor architecture. Choose the arm64 package if you've confirmed your device uses arm64; otherwise, check whether a universal package is available. A universal package supports more processor architectures but doesn't lower the minimum OS version. If the app installs but disconnects often, start by testing a small number of entries with a single connection and with the screen locked, then check whether battery management is limiting background activity. Don't assume background drops are caused by the core, or switch to v2flyNG based on the phone's age alone.
Download Recommendations
For desktop, choose v2rayN. For Android, choose v2rayNG. If you know you need the V2Fly core on Android, choose v2flyNG. On the download page, select your platform first, then choose a package based on your device architecture or desktop interface preference.
Go to Downloads