Choose v2rayN
On a computer (Windows, macOS, or Linux), when you need subscription management, latency tests, system proxy, or TUN mode, download v2rayN first.
Start with the OS that fits you, then decide which client to download.
On a computer (Windows, macOS, or Linux), when you need subscription management, latency tests, system proxy, or TUN mode, download v2rayN first.
The default for most Android phones. Supports QR scan, subscription updates, and per-app proxy—with a low learning curve.
Works almost like v2rayNG, but uses the v2fly core. Pick it only when you specifically need v2fly.
A side-by-side look at platforms, cores, import methods, and standout capabilities — scan it in seconds.
| Comparison | v2rayN | v2rayNG | v2flyNG |
|---|---|---|---|
| Platforms | Windows / macOS / Linux | Android | Android |
| Built-in core | Xray / v2fly switchable | Xray | v2fly(v2ray-core) |
| Common protocols | VMess / VLESS / Trojan / SS and more | VMess / VLESS / Trojan / SS and more | VMess / VLESS / Trojan / SS and more |
| Subscription import | Supported | Supported (incl. QR code) | Supported (incl. QR code) |
| Node latency test | Supported | Supported | Supported |
| System proxy / VPN | System proxy, TUN | System VPN | System VPN |
| Per-app proxy | Not a focus | Supported | Supported |
| Install format | ZIP / DMG / DEB / RPM | APK install | APK install |
| Learning curve | Moderate (more features) | Lower | Lower (similar to v2rayNG) |
| Best for | Desktop users | Most Android users | Users who need the v2fly core |
Deep Dive
Go beyond the table — clarify the key decisions so you don’t download the wrong package.
This is the most important step — and the hardest one to get wrong. v2rayN for desktop (Windows / macOS / Linux); v2rayNG and v2flyNG for Android. If you mainly use a computer, stick with v2rayN — no need to choose between the two Android clients.
Likewise, phone users don’t need v2rayN. On Android, choose again based on whether you need the v2fly core.
These two clients share nearly the same UX — subscription import, QR scan, connect, and per-app proxy all feel familiar. The real difference is the core: v2rayNG defaults to Xray, while v2flyNG uses v2fly(v2ray-core)。
For most users, v2rayNG is enough. Choose v2flyNG only when your nodes or environment clearly depend on the v2fly core, or you prefer to follow the v2fly ecosystem.
On desktop, v2rayN usually offers a richer management experience — subscription groups, batch latency tests, system proxy and TUN switching — ideal for always-on use and multi-node setups. v2rayNG / v2flyNG focus on mobile: fast QR import, simple VPN permission, and per-app routing.
So there’s no absolute “best” client — it depends on your device. Desktop for computers, Android for phones is the most efficient decision path.
In daily use, all three clients cover common protocols like VMess, VLESS, Trojan, and Shadowsocks. What usually decides whether you can connect is whether the node works, whether your local network is restricted, and whether the proxy mode is on — not whether the app is named v2rayNG or v2flyNG.
Treat protocol support as “baseline capability for all”; put your energy into platform and core needs instead.
After downloading, follow the matching tutorial to import your subscription and connect.
FAQ
Frequent questions about which client to download.
The biggest difference is the platform: v2rayN is for desktop (Windows / macOS / Linux), v2rayNG is for Android. Both can import subscriptions and connect to common protocol nodes, but the UI and system integration differ.
With no special requirements, choose v2rayNG. Only when you clearly need the v2fly (v2ray-core) core should you pick v2flyNG. The workflow is nearly identical, so switching costs little.
Yes, but you don’t need to. Download by device: v2rayN on your computer, and either v2rayNG or v2flyNG on your phone — avoid installing too many and getting confused.
Speed mainly depends on node quality and your local network, not the client name. Picking a working node and keeping subscriptions updated usually matters more than the brand.
Basically no. Subscription import, QR scan, connect, and per-app proxy paths are very similar. Focus on the core difference, not relearning the whole app.