Software & Protocols
4 Questions
Is the V2Ray client free?
Yes. The v2rayN, v2rayNG, and v2flyNG clients offered here are open-source and completely free, with public source code anyone can audit. Watch out for lookalike sites bundling paid software.
Which protocols does V2Ray support?
The core supports VMess, VLESS, Trojan, Shadowsocks, SOCKS, HTTP, and other protocols, with TCP, WebSocket, gRPC, mKCP transports and optional TLS/Reality encryption for flexibility across different network environments.
What's the difference between v2rayN, v2rayNG, and v2flyNG?
v2rayN is the desktop client for Windows/macOS/Linux; v2rayNG is the Android client; v2flyNG is a mirror build sharing v2rayNG's codebase. All three are maintained by the same developer and work almost identically — just pick the one for your device.
Can I use it on multiple devices at once?
That depends on whether your node or subscription provider limits concurrent connections — the client itself has no device limit, so you can install it on your computer, phone, and router simultaneously.
Download & Installation
3 Questions
Should I download the 32-bit or 64-bit version for Windows?
Computers bought after 2010 are almost always 64-bit — just download the x64 build. If you have an older 32-bit system or the version won't run, switch to x86. For Windows on ARM devices with Snapdragon chips, choose the ARM64 build.
What if macOS says "the app is damaged and can't be opened"?
This happens because the installer isn't signed by Apple — it's completely normal. Open Terminal, run xattr -cr /Applications/v2rayN.app to clear the quarantine flag, then reopen the app.
Not sure what architecture your phone uses? Which APK should you download?
Most Android phones released after 2018 use the arm64-v8a architecture — just download the recommended build. If installation fails or you're unsure of your device model, download the universal build instead. See the full version list at the download center.
Subscriptions & Nodes
4 Questions
What do I need before I get started?
You'll need a subscription link or at least one node share link/QR code, usually provided by your node provider. The client itself is just a connection tool and doesn't include any nodes.
Can I share my subscription link with others?
We don't recommend it. Subscription links are usually tied to an account or data quota — sharing them can lead to multiple people sharing bandwidth or triggering throttling/bans. Keep them private and never post them publicly.
Why did the number of nodes decrease after updating my subscription?
This is usually because the subscription provider removed some expired nodes, or the client has "auto-remove invalid nodes after update" enabled. You can disable this to verify manually — see our subscription import guide for details.
Can subscription nodes and manually added nodes be used together?
Yes. v2rayN's server list supports subscription nodes and manually added nodes coexisting without interfering with each other — just switch between them in the list.
Connections & Troubleshooting
4 Questions
What if I can't connect after adding a node?
Check in order: ① Is your system clock accurate (within 90 seconds)? ② Has the subscription or node expired? ③ Is a firewall or antivirus blocking the client? ④ Try a different transport protocol or core. Our quick start guide also covers basic troubleshooting steps.
What's the difference between TUN mode and system proxy?
System proxy only affects apps that follow that setting — command-line tools or some apps may bypass it. TUN mode takes over all traffic at the network adapter level for true global proxying, though it uses slightly more resources and configuration.
What if I'm connected but the speed is very slow?
Try switching to a lower-latency node, check if the node is overloaded, verify your routing rules aren't sending traffic that should stay on a direct connection through the proxy, or switch transport protocols (e.g., from WebSocket to gRPC).
Why does the connection suddenly drop frequently?
Common causes include an unstable node route, local network fluctuations, the system or router entering sleep mode and interrupting long connections, or multiple devices sharing the same node and triggering rate limits.