What Is VLESS? How the Protocol Works, Authentication, and Encryption
Technical Editorial Team · Published February 19, 2026 · Updated November 10, 2026
What is VLESS?
VLESS is a proxy protocol that lets your device access websites and network services through a proxy server.
For example, if you cannot connect to a website directly from your current network, you can use a VLESS-compatible client to connect to a proxy server. The server accesses the website and sends pages, video, or other data back to your device.
VLESS defines how the client and proxy server communicate, including how to identify users, specify a destination, and forward data.
Put simply, VLESS tells the proxy server “who I am and where I want to connect,” and the server helps establish that connection.
VLESS itself is neither a VPN app nor a proxy server. To use it, you also need a compatible client and an available proxy service.
What are the advantages of VLESS, and why use it?
VLESS is a proxy protocol in the V2Ray/Xray ecosystem, developed after VMess. Its simpler design separates authentication, proxy requests, and connection encryption.
Compared with proxy protocols such as Shadowsocks and VMess, VLESS stands out for its lightweight protocol design, reduced unnecessary double encryption, and flexible connection options.
- Lightweight protocol: VLESS uses a compact request format to communicate user identity and the destination address. Authentication does not depend on synchronized client and server clocks.
- Less double encryption: Common configurations protect communication with an outer security mechanism such as TLS or REALITY, without requiring another encryption layer within VLESS.
- Flexible connections: VLESS can work with different transports and security mechanisms, allowing a suitable connection setup for the network environment.
These features suit a range of proxy deployments and let clients and servers improve transport and connection protection separately.
However, the protocol design does not guarantee that VLESS will be faster than other protocols. Actual speed and stability depend mainly on the network path, server, transport, and configuration.
For more on the differences between protocols, see:
- VLESS vs. VMess: How Do Their Protocol Designs Differ?
- VLESS vs. Shadowsocks: How Do Their Protocols and Connections Differ?
How does VLESS protect a connection?
VLESS primarily handles user identification and proxy data forwarding. Common VLESS configurations do not encrypt data within the protocol; they use mechanisms such as TLS or REALITY to protect communication between the client and proxy server.
That is why clients may show VLESS + TLS or VLESS + REALITY. Both use the same VLESS proxy protocol, with different forms of connection protection. Some configurations also use XTLS Vision to optimize the handling of certain encrypted traffic.
Recent Xray versions also offer optional VLESS Encryption, which can add encryption at the protocol layer.
For REALITY handshake authentication, traffic camouflage, and XTLS Vision, see What Is VLESS REALITY? Handshake Authentication and XTLS Vision.
Technical deep dive: VLESS protocol details
The sections above introduce the purpose and design of VLESS. The following sections explain how it works through four areas: protocol structure, authentication, encryption, and transports.
VLESS protocol structure
VLESS is a communication protocol between a client and a proxy server. It defines how proxy requests are organized and how the server identifies users, determines the destination, and handles subsequent data.
In a typical VLESS connection, the client establishes the underlying connection and then sends a VLESS request. After parsing the request and authenticating the user, the server connects to the destination service and forwards data.
What information does a VLESS request contain?
The main fields of a VLESS request header are:
| Field | Length | Purpose |
|---|---|---|
| Version | 1 byte | Protocol version |
| UUID | 16 bytes | User identifier |
| Addons Length | 1 byte | Length of additional information |
| Addons | Variable | Optional additional information |
| Command | 1 byte | Request type |
| Port | 2 bytes | Destination port |
| Address Type | 1 byte | Destination address type |
| Address | Variable | Destination IP address or domain name |
These fields make up the main contents of a basic VLESS request. The client does not need to include a complete HTTP request in the header or describe the TLS or REALITY handshake at the VLESS layer.
The VLESS request header is binary, using compact fields to express the information needed for a proxy connection.
What request types does VLESS support?
VLESS distinguishes proxy request types through the Command field.
| Command | Value | Purpose |
|---|---|---|
| TCP | 0x01 | Establish a connection-oriented data stream |
| UDP | 0x02 | Forward UDP datagrams |
| Mux | 0x03 | Multiplexing-related requests |
TCP requests establish a continuous data stream, for example when accessing an HTTPS website.
UDP requests forward DNS, real-time communication, or other application data that uses UDP. Because UDP does not provide a continuous byte stream like TCP, VLESS needs appropriate framing to preserve datagram boundaries.
Mux is used for related multiplexing mechanisms. Availability depends on the proxy core and its version.
These commands show that VLESS does more than pass along a destination address: it also tells the server how to handle the traffic that follows.
How does VLESS authenticate users?
VLESS commonly uses a UUID as a user identifier.
A UUID is a 128-bit identifier, usually displayed as a hyphenated string, for example:
550e8400-e29b-41d4-a716-446655440000
When sending a request, the client includes the UUID in the VLESS request header. The server reads it and checks whether it belongs to a configured, authorized user.
If authentication succeeds, the server continues processing the proxy request. If it fails, the server generally rejects or terminates the connection.
What characterizes UUID authentication?
Basic VLESS authentication has three characteristics:
- No clock synchronization requirement: Unlike parts of the traditional VMess authentication design, VLESS does not require precisely synchronized client and server clocks.
- Simple request format: The UUID is used directly as the identity credential, without an additional timestamp-based authentication process.
- Separate identity and connection protection: The UUID identifies an authorized user; the relevant encryption mechanism protects the communication contents.
A UUID is an identity credential, not an encryption key or a mechanism for encrypting communication.
With a VLESS configuration that lacks suitable connection protection, identity information in the basic request may be exposed on the network. UUID authentication should therefore not be equated with secure encryption.
VLESS encryption mechanisms
An important design feature of VLESS is the separation of the basic proxy protocol from communication encryption.
In common configurations, VLESS identifies users, describes proxy requests, and forwards data, while TLS or REALITY protects the connection between the client and proxy server.
This avoids requiring another round of protocol-layer encryption on a connection already protected by an outer encryption layer.
What does VLESS encryption=none mean?
Traditional VLESS configurations often contain:
"encryption": "none"
This disables optional encryption at the VLESS protocol layer. It does not mean the entire network connection is unencrypted.
For example, in a VLESS + TLS configuration, TLS can provide encryption and integrity protection between the client and proxy server.
In a VLESS + REALITY configuration, the corresponding REALITY handshake, authentication, and connection protection mechanisms perform those roles.
To determine whether a VLESS connection is protected, examine the complete configuration rather than just the encryption field.
What is VLESS Encryption?
Recent Xray versions introduce optional VLESS Encryption, allowing VLESS to use an additional encryption mechanism at the protocol layer.
This means that “VLESS itself does not support encryption at all” is no longer an accurate general statement.
To use VLESS Encryption, confirm that both the client and server support the mechanism and use compatible parameters.
The roles of VLESS Encryption, TLS, and REALITY, and how they can be combined, depend on the actual version and configuration. VLESS Encryption is not enabled by default on every VLESS node.
How do VLESS and VMess differ in encryption design?
| Aspect | VLESS | VMess |
|---|---|---|
| User identification | UUID | Authentication mechanism based on a user ID |
| Clock synchronization | Basic authentication does not depend on synchronized clocks | Traditional authentication depends on time |
| Protocol-layer encryption | Common configurations disable it; recent Xray versions support optional encryption | The protocol design includes payload encryption |
| Outer connection protection | Can use TLS, REALITY, and other mechanisms | Can use security mechanisms such as TLS |
| Design | Separates identity, proxy requests, and connection protection | Integrates more authentication and encryption mechanisms within the protocol |
The main difference is how authentication, proxy requests, and encryption are organized, rather than one protocol always being safer or faster.
For a detailed comparison, see VLESS vs. VMess: How Do Their Protocol Designs Differ?.
VLESS transports
VLESS defines the format of proxy requests, but the data still needs an underlying network connection for transport.
A VLESS node configuration therefore usually specifies a transport, such as RAW, WebSocket, gRPC, or XHTTP.
These transports determine how VLESS data is carried and affect connection establishment, network compatibility, and traffic handling.
| Transport | Main characteristics |
|---|---|
| RAW | Carries data directly over underlying connections such as TCP, with a relatively simple structure |
| WebSocket | Carries proxy data over a WebSocket connection |
| gRPC | Uses gRPC communication based on HTTP/2 |
| XHTTP | Uses Xray's HTTP transport mechanism, with support for different operating modes |
A transport is not the same as a proxy protocol.
For example, VLESS + WebSocket and VLESS + XHTTP both use VLESS; only the way VLESS data is carried differs.
Transports have different performance, compatibility, and deployment requirements. Their names alone do not tell you which is faster.
How do transports and security mechanisms fit together?
A complete VLESS node configuration typically consists of several parts:
| Configuration layer | Purpose | Examples |
|---|---|---|
| Proxy protocol | Authentication and proxy requests | VLESS |
| Transport | Carry proxy data | RAW, WebSocket, XHTTP |
| Connection protection | Encryption, authentication, and handshakes | TLS, REALITY |
| Traffic processing | Optimize processing for particular connections | XTLS Vision |
For example, VLESS + RAW + REALITY uses the VLESS proxy protocol, carries data over RAW, and protects the connection with REALITY mechanisms.
Each component has its own role; they are not interchangeable protocols.
For transport compatibility with CDNs, see the related VLESS + Cloudflare: What Does a CDN Do in a Proxy Connection?.
How VLESS, REALITY, and Vision relate
VLESS, REALITY, and XTLS Vision often appear in the same node configuration, but they serve different purposes.
VLESS handles proxy requests, REALITY handles connection handshakes, authentication, and protection, and XTLS Vision optimizes the processing of encrypted traffic in applicable scenarios.
REALITY does not change the basic VLESS authentication or proxy request format. Vision is not an independent proxy protocol either.
VLESS can therefore be used without REALITY, and REALITY should not be understood as a new version of VLESS.
For REALITY authentication, handshakes, traffic camouflage, and how Vision works, see What Is VLESS REALITY? Handshake Authentication and XTLS Vision.
How does VLESS differ from a VPN?
VLESS is a proxy protocol. VPN generally refers to technologies or services that use a client to establish a network tunnel and capture and forward device traffic.
The two concepts operate at different levels.
When using VLESS, which apps send traffic through the proxy depends on the client's operating mode and routing rules.
For example:
- System proxy mode: Apps that support system proxy settings can send traffic through a specified proxy port.
- TUN mode: The client captures device traffic through a virtual network interface, then decides how to handle it according to routing rules.
- Rule-based routing: The client uses domain names, IP addresses, or other rules to decide whether traffic connects directly or passes through a proxy server.
VLESS can thus serve as the proxy protocol inside a VPN-style client, but VLESS itself does not create virtual network interfaces or manage system routes.
For more, see How Does V2Ray Differ from a Traditional VPN?.
Summary
VLESS is a proxy protocol in the V2Ray/Xray ecosystem, primarily handling user identification, proxy requests, and data forwarding.
It features a compact request structure, basic authentication without clock synchronization, and flexible combinations with transports and security mechanisms.
Common VLESS configurations use TLS or REALITY to protect connections. Recent Xray versions also offer optional VLESS Encryption.
The key to understanding VLESS is distinguishing the proxy protocol, transport, and connection protection: VLESS defines how to make proxy requests; the other mechanisms determine how to carry and protect the connection.