V2Ray CLIENT GUIDE

V2Ray Client Guide

Download v2rayN View Tutorial

Chinese-language instructions for desktop and Android devices, covering client selection, subscription import, and split routing, organized around real settings screens.

Free forever Open source Chinese documentation Xray · V2Fly
PRODUCT WALKTHROUGH

From subscription import to system-wide split routing

Configuration order determines troubleshooting efficiency. First turn the subscription into a usable node list, then confirm routing policies, and only then decide whether to enable TUN mode based on the apps that need it.

Preview real settings

Switch tabs to view the interface structures for subscriptions, routing, and TUN. The preview shows field relationships only; it does not generate node or connection data.

Subscription group settingssubscription
Group name Default group
Auto-update subscription
Update interval 24 hours
01 / SUBSCRIPTION

Subscription groups and update boundaries

A subscription URL distributes a node list; it is not the same as a single node. v2rayN can place sources in separate groups and assign each group a note, update interval, and server filters. On the first import, keep the URL intact, run one manual update, and confirm that the nodes appear in the right group before enabling automatic updates. When multiple subscriptions coexist, clear group names are easier to maintain than one mixed list. If a source changes, it can be updated and troubleshot separately without affecting other groups.

View the subscription import steps →
Subscription group3 settings
NoteDaily subscription
Group nameDefault group
Auto-update
02 / ROUTING

Routing rules run in match order

Split routing determines which requests use the proxy, connect directly, or are blocked from going out. Rules are usually ordered from specific to broad: handle explicit domains, IP ranges, and process conditions first, then keep a final catch-all rule. When editing, check both rule order and outbound names so a broad condition near the top does not intercept later requests. Unlike tools limited to simple mode switches, v2rayN directly manages rule sets and custom rules, making it useful on desktops that need to separate work services, local network resources, and ordinary web traffic.

Read the practical routing rules guide →
Rule ordertop → bottom
Domain matchProxy
Private addressDirect
Final ruleProxy
03 / TUN

TUN mode covers apps that do not support proxies

The system proxy mainly handles programs that actively read proxy settings; some command-line tools, game launchers, and standalone network components may bypass it. TUN mode receives a wider range of system traffic through a virtual network interface, then lets the core apply DNS and routing rules. Before enabling it, confirm that the node works in ordinary system proxy mode. TUN also involves permissions, a virtual adapter, and DNS configuration, which makes troubleshooting longer. Enable it only after basic connectivity is verified so node issues can be separated from system interception issues.

Read the TUN mode guide →
TUN modeadvanced
Enable TUN
Protocol stackMixed
Auto routing
04 / DIAGNOSIS

Latency results depend on the test target

Ping, real-connection latency, and download speed in a node list answer different questions. Ping is closer to basic network reachability and does not confirm a proxy-protocol handshake. Real-connection latency includes the proxy connection process, making it better for filtering out unusable nodes. Download testing reflects actual transfer capacity over a period of time, but is affected by server load, the local network, and the test resource. When troubleshooting, update the subscription first, run a real-connection test next, and finally use a browser request to confirm that the proxy works. Do not judge line quality by one number alone.

Understand the three latency tests →
Diagnostic orderchecklist
1Update the subscription list
2Run a real-connection test
3Verify a proxied request
DOWNLOAD BY PLATFORM

Choose a V2Ray client by device

Use v2rayN on desktop devices; on Android, choose between v2rayNG and v2flyNG. The download page further separates processor architectures and package types.

v2rayN

Windows

Offers both a modern desktop interface and the classic WPF interface. Suitable for desktop users who need system proxy support, routing rules, subscription groups, real-connection tests, and TUN mode.

Go to downloads
v2rayN

macOS

Choose an Apple Silicon or Intel package based on the device chip. The client interface follows the same configuration model as the desktop version, allowing you to manage subscriptions, switch active nodes, and set the system proxy.

Go to downloads
v2rayNG · v2flyNG

Android

v2rayNG uses the Xray core, while v2flyNG uses the V2Fly core. Most current devices use the arm64 package; if you cannot confirm the architecture, check the universal build.

Go to downloads
v2rayN

Linux

Provides desktop installers in deb and rpm formats, separated by x64 and arm64 architecture. Suitable for Linux desktop environments that need a graphical way to manage subscriptions and routing.

Go to downloads
View all clients and compare their differences →
QUICK START

Three checks for your first connection

Run import, testing, and verification separately to quickly determine whether the issue lies with the subscription, the node, or system proxy handling.

  1. 01

    Import and update the subscription

    Copy the complete subscription URL, add it under the client's subscription group settings, and enter a recognizable note. Save it and run one manual update, then confirm that the node list appears on the main screen. If the list is empty, first check whether the URL was truncated, the correct group was selected, and the subscription is still reachable. Do not jump straight to TUN or DNS changes.

  2. 02

    Choose a node and run a real-connection test

    Select a node from the current group and run a real-connection latency test. It goes through the proxy protocol's connection process, making it more useful than a simple Ping for determining whether the node can complete a handshake. Prefer nodes that return stable results rather than chasing the lowest number; region, traffic ratios, network congestion, and server load all affect real-world performance.

  3. 03

    Enable the proxy and verify the request path

    Start with system proxy mode for basic verification. Open a browser, visit an IP-check page, and make a normal web request. If the browser works but another program does not, check whether that program reads system proxy settings. If system-wide interception is required, enable TUN according to the advanced guide. This avoids making several changes at once and makes troubleshooting harder.

View the complete tutorial →
OPEN SOURCE ECOSYSTEM

How Project V, V2Fly, and Xray relate

Project V is an open-source technology ecosystem built around network proxy protocols, routing capabilities, and composable transports. In everyday use, V2Ray may refer to the earlier project and core, or serve as a general name for the wider client and protocol ecosystem. Clients, cores, and subscription services are separate layers: the graphical client handles settings and interaction, the core handles protocol processing and routing, and the subscription supplies a list of server configurations.

V2Fly continues the community maintenance path for cores and tools related to Project V, with v2flyNG using the V2Fly core as its Android implementation base. Xray is a related family of cores developed around a similar configuration model, with ongoing expansion of transport, protocol, and routing capabilities; common v2rayN and v2rayNG configurations typically center on the Xray core. The two core lines share many concepts, but supported options should be checked against the settings currently visible in the client and the core documentation.

v2rayN is a graphical desktop client for Windows, macOS, and Linux. It handles subscription management, node switching, system proxy settings, routing rules, speed tests, and TUN configuration. v2rayNG targets Android and uses the Xray core, focusing on subscription updates, active configuration selection, per-app proxying, and routing settings. v2flyNG also targets Android but uses the V2Fly core, making it an alternative when that core line is required.

All three clients are maintained as open-source projects. Updates commonly include interface changes, core compatibility updates, protocol support changes, and bug fixes. Before updating, read the system and architecture notes on the download page. If you have complex routing, DNS, or multiple-subscription settings, record the current configuration first, then verify the corresponding fields in the new settings screens one by one. Configuration formats evolve with core capabilities, so field locations in older tutorials may differ from the current interface.

Open-source development makes community review, issue reporting, and ongoing improvement possible, but it does not replace correct configuration. Connection results still depend on subscription contents, node availability, the local network, the scope of system proxy interception, and the DNS path. When troubleshooting, check each layer in order: whether the subscription updated, whether the node connects, whether the proxy is enabled, whether the app is intercepted, and whether the routing rule matches.

Project V Protocol, routing, and transport ecosystem
Xray v2rayN v2rayNG
V2Fly v2flyNG Configuration and core tools
CLIENT Management interface and system interception CORE Protocol processing and routing SUBSCRIPTION Server configuration list
TECHNICAL NOTES

V2Ray configuration and troubleshooting articles

Practical guides covering speed-test metrics, first connections, and protocol differences, with an emphasis on how to interpret evidence rather than simply listing settings.

Performance

How to read V2Ray latency tests: ICMP Ping, real-connection latency, and download speed compared

Breaks down what each test measures: Ping checks basic network reachability, real-connection latency includes the full proxy handshake, and download speed shows actual transfer capacity over time.

Read the full article
Getting Started

The complete v2rayN first-connection workflow: choose a node, run a real-connection test, and confirm the proxy works

Filter the subscription list for nodes that complete a connection, then check the client's proxy status and browser request results separately. This keeps node failures distinct from system interception issues.

Read the full article
Protocols

VMess vs. VLESS: the difference explained in one minute for everyday users

Explains how to interpret subscriptions containing both VMess and VLESS nodes by looking at user-visible encryption, transport overhead, and dependence on server-side configuration.

Read the full article
View all articles →
Download v2rayN