V2Ray Glossary

The name of this open-source proxy tool. V2Ray was the original project name; after the original author stopped maintaining it, the community forked and continued development under the name V2Fly. Both refer to the same underlying technology (V2Ray Core), and the two names are often used interchangeably in everyday context — see this beginner's guide for more.

Another open-source fork built on V2Ray Core, protocol-compatible with substantial performance and feature enhancements. It's currently one of the most actively developed core implementations, and doesn't change how you use the v2rayN / v2rayNG clients day-to-day.

A common term on the Chinese internet for "using a proxy tool to access restricted content." Tools like V2Ray, Shadowsocks, and Clash all fall under this umbrella — check your local laws and regulations to determine what's permitted.

A common term for internet censorship and blocking systems in certain regions. Several protocols in the V2Ray ecosystem (like Trojan and VLESS + TLS) are specifically designed to reduce the chance of being detected or interfered with by such systems.

The connection details for your proxy server (a collective term for address, port, protocol, key, and other parameters). A subscription link usually contains multiple nodes, which the client bundles into a selectable, testable list.

V2Ray's earliest in-house encryption protocol, where each node is tied to a UUID as its credential. It has a full feature set and is one of the most fully supported protocols in v2rayN / v2rayNG. For a more detailed protocol comparison, see this article.

A lighter protocol than VMess that drops built-in encryption (relying on outer-layer TLS encryption instead), resulting in lower protocol overhead and typically higher speed. It's the widely recommended newer protocol.

A simply designed, long-established proxy protocol with a mature ecosystem supported by nearly every client and low performance overhead — its main drawback is that its traffic pattern is relatively easy to detect.

A protocol that disguises proxy traffic as normal HTTPS web requests, giving it strong resistance to blocking. It typically requires a real domain name and a TLS certificate to use.

The transport-layer encryption protocol used by HTTPS. Protocols like VLESS and Trojan typically layer TLS on top, making the traffic indistinguishable from ordinary web browsing from the outside.

An HTTP-based persistent connection transport method, often used as a node's "disguise layer." It can be paired with CDN relaying and is one of the most common transport methods.

A UDP-based transport method with stronger resistance to packet loss. It can be smoother than TCP/WebSocket on unstable networks, though its compatibility isn't as good as WebSocket's.

A unique identifier in the format "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx" that the VMess protocol uses as your credential — functioning much like an account password, so be careful not to share it with anyone.

A link starting with http/https that returns a batch of node information when accessed by the client. Paste it into the client's subscription settings to import all the nodes at once, with support for scheduled auto-updates. See this article for the details on how it works and its format.

Usually measured in milliseconds (ms), this represents the round-trip time between your device and the proxy server — the lower the number, the more responsive the connection. Clients typically include a built-in latency test feature.

A set of rules that decides "which traffic goes through the proxy and which connects directly" — for example, routing traffic to sites in mainland China directly while sending everything else through the proxy, balancing speed and browsing experience. See the advanced tutorial for specific configuration steps.

When a domain name lookup bypasses the proxy tunnel and is handled directly by your local or ISP's DNS, potentially exposing which domains you're visiting. Clients usually include a corresponding DNS setting to prevent this.

A proxy mode where all network traffic is forwarded to the proxy server — useful when you want everything routed through the proxy uniformly.

Determines whether each request needs to go through the proxy based on an auto-configuration script (a PAC file) — a relatively lightweight routing method that most clients now recommend replacing with routing rules.

A preset routing rule mode that automatically routes IPs/domains in mainland China directly while sending traffic elsewhere through the proxy — the most common, no-configuration-needed routing method for beginners.

A client feature that batch-tests latency (and sometimes speed) for every node in a subscription, then sorts the results or automatically selects the best node — usually accessible via a button on the node list page.

The most widely used graphical client for Windows / macOS / Linux desktops, built on the V2Ray / Xray core. Its interface lets you manage subscriptions, switch nodes, and edit routing rules. Go to download.

The Android counterpart to v2rayN, with an interface and usage logic largely consistent with the desktop client — one of the most popular choices among Android users.

A community fork of v2rayNG with similar features and usage, but slightly different interface details. You can switch between the two anytime using the same subscription link. See this article for a more detailed comparison.

A deployment method that relays proxy traffic through CDN (Content Delivery Network) nodes, which can help hide the real server address and improve resistance to blocking. It's typically used together with WebSocket + TLS transport.

The ability of a client to recognize and connect to nodes using multiple protocols — VMess, VLESS, Shadowsocks, Trojan, and more — without needing separate software for each. Both v2rayN and v2rayNG support this.