VLESS is a lightweight proxy protocol from the V2Ray and Xray family. It carries your traffic between an app on your device and a server, and it identifies you with a single ID called a UUID. By default it does no encryption of its own: it travels inside an outer layer such as TLS or REALITY, and that outer layer is what the network sees.

The technical details below come from the Xray project's own documentation, read 16 November 2026.

What VLESS is

The Xray project describes VLESS as "a stateless lightweight transport protocol" that acts as a bridge between an Xray client and an Xray server (Project X documentation). In practice:

  • It is a proxy protocol. VLESS defines how a client asks a server to forward a connection. It gets called a VPN because VPN apps use it as the tunnel between your device and their server.
  • It identifies you with a UUID. The server holds a list of the IDs it accepts, and the client presents one of them.
  • It leaves encryption to the layer around it. The documentation says VLESS "must be used with an outer transport-security layer" on public networks, which means TLS or REALITY. An optional built-in mode, VLESS Encryption, exists and is switched off by default.

VLESS is older than Xray. The release notes for V2Ray v4.27.0, published on August 6, 2020, list "VLESS PREVIEW 1.3" as a feature (V2Ray release notes). Xray-core published its first release on November 25, 2020, and its README says that version was forked from V2Ray's code (Xray-core on GitHub). Our guide to what V2Ray is covers the wider platform.

How a VLESS connection works

A VLESS request opens with a short header: a version byte, the 16-byte UUID, optional add-ons, a command, and the port and address of the destination. Your data follows it (VLESS protocol description). The server checks the UUID against its list and, if it matches, forwards the data.

By default VLESS encrypts neither that header nor the data, so the wrapper does the protecting. A typical connection has three steps:

  1. Your app opens a TLS or REALITY connection to the server, often on port 443, the port HTTPS websites use.
  2. Inside that encrypted connection, it sends the VLESS header and then your traffic.
  3. The server forwards the traffic to the site or service you asked for and passes the replies back the same way.

To anyone watching the network, the connection presents itself as TLS to a server. Looking like TLS is not the same as looking like ordinary browsing, and Vision and REALITY exist to narrow that gap. Our guide to TLS encryption explains what that layer hides.

VLESS vs VMess vs Trojan

All three are proxy protocols that Xray supports, and all three can run over the same transports. They differ in how they identify you and in whether they encrypt anything themselves. The summary below follows the Xray documentation's transport reference.

  • Identifies you with: a UUID in VLESS and VMess, a password in Trojan.
  • Its own encryption: optional and off by default in VLESS; handshake authentication and payload encryption in VMess; none in Trojan, which only authenticates.
  • TLS or REALITY around it on public networks: required for VLESS, unless VLESS Encryption is on, and for Trojan; supported but not required for VMess.

VMess is the older protocol and carries its own encryption, which the documentation notes lacks the forward secrecy of TLS 1.3. VLESS drops that inner layer and leaves the job to TLS or REALITY. Trojan takes the same approach as VLESS, with a password in place of the UUID.

VMess also needs the clocks on both ends to agree: the documentation asks for the system time to be within 120 seconds of the real time (VMess documentation). VLESS has no such requirement.

What Reality, Vision and XHTTP add

The names that follow VLESS in a setup such as "VLESS + Vision + Reality" are separate pieces that fit around it.

REALITY

REALITY replaces ordinary TLS as the outer layer. The documentation calls it "a modified form of TLS that uses the appearance and handshake characteristics of a target site as camouflage" (REALITY documentation). The person running the server points it at a real website, which they need not own. A client that holds the right key gets a working proxy connection. Any other visitor, including a system probing the server to find out what it is, is passed through to that website and receives its genuine response.

For someone running a server, REALITY also removes two chores that ordinary TLS brings: buying a domain name and configuring a TLS server (REALITY README).

Vision

Vision is a flow-control mode for VLESS, written xtls-rprx-vision in a configuration. Much of what you send through a proxy is already TLS, because HTTPS makes up a major share of internet traffic, so a proxy that runs over TLS ends up carrying TLS inside TLS. The Xray documentation treats that pattern as a signature that can give proxy traffic away, and it names Vision as the way VLESS reduces it: Vision pads the inner handshake with random-length data.

When the inner connection is TLS 1.3, Xray can also copy the already-encrypted data straight through without processing it again (VLESS inbound documentation).

XHTTP

XHTTP is a transport, meaning a way of carrying the stream. It sends the connection as HTTP requests: in its most compatible mode, uploads are split into a series of requests and the download arrives as one streamed response. The Xray developers designed it to pass through content delivery networks and other HTTP middleboxes (XHTTP announcement, published December 5, 2024). XHTTP works with either TLS or REALITY as the outer layer.

Three ways the pieces combine:

  • VLESS + Vision + REALITY: VLESS over a plain TCP connection, with REALITY as the outer layer and Vision handling the TLS-inside-TLS pattern. This is the example configuration in the REALITY project's README.
  • VLESS + XHTTP + TLS: VLESS carried as HTTP requests inside ordinary TLS.
  • VLESS + XHTTP + REALITY: the same transport with REALITY as the outer layer.

Is VLESS detectable?

No protocol can promise that it will go unnoticed, and the Xray documentation says as much. Being able to communicate securely over the public internet "does not imply the ability to circumvent censorship", it says, and using TLS or REALITY "does not mean that proxy traffic has the same characteristics as ordinary HTTPS traffic" (transport reference).

VLESS with Vision and REALITY is built to narrow that gap. A server's IP address can still be blocked, whatever protocol runs on it. Our guide to deep packet inspection explains how that inspection works.

VLESS vs WireGuard

WireGuard is a VPN protocol that runs over UDP only. Its own documentation says it "explicitly does not support tunneling over TCP" and "does not focus on obfuscation" (WireGuard's known limitations, read 16 November 2026). The Xray documentation adds that the UDP packets of protocols like WireGuard have distinctive characteristics.

VLESS takes the opposite approach: in the setups above it travels inside TLS or REALITY, the kind of connection HTTPS websites use.

Use WireGuard on networks that leave VPNs alone, and VLESS on networks that block them. We didn't run our own speed tests, so we make no claim about which is faster on your connection. For more on each side, see what WireGuard is and UDP vs TCP for VPNs.

How to use VLESS

There are two routes: run a server yourself, or use an app that has VLESS built in.

Run your own server

Xray-core is free, open-source software, published under the Mozilla Public License 2.0. To use it yourself, you rent a server, install Xray, generate a UUID and a key pair (the xray uuid and xray x25519 commands), write matching server and client configurations, and keep the software up to date.

On your device you need a client app. Xray-core's README lists clients for each platform, among them v2rayN for Windows and v2rayNG for Android (README read 16 November 2026). Our guides to V2Ray on iOS and V2Ray on Android walk through the client side.

Searching for free VLESS servers turns up public lists of shared server details. Whoever runs a proxy server can see which sites you connect to through it, so a server run by a stranger is a question of trust as well as cost.

Use an app with VLESS built in

The other route is a VPN app whose maker runs the servers and builds VLESS into the app. Tegant VPN is our own app, and it works this way. Tegant's XRay option runs VLESS with Vision and Reality, Trojan over TLS, VLESS with XHTTP over TLS, and VLESS with XHTTP over Reality. In the app you switch from WireGuard to XRay, pick a server and connect.

XRay is part of Tegant Premium on iPhone, iPad, Mac and Android, and it is available in 15 of Tegant's 18 server countries; France, Italy and Spain are WireGuard only. The free tier, where it is available, is WireGuard only. No VPN can guarantee access on every network, and that includes ours.

Rules on VPNs differ from country to country and change often, so check the current law where you are. Our guide to how VPN rules differ by country has more.

VLESS questions

Is VLESS a VPN?

Strictly, no. VLESS is a proxy protocol: it defines how a client asks a server to forward connections. VPN apps use it as the tunnel between your device and their server, which is why the two words get used together.

Is VLESS encrypted?

Not by itself, by default. VLESS relies on the TLS or REALITY layer around it for encryption. The Xray documentation says it must be used with such a layer on public networks, unless the optional VLESS Encryption mode is switched on.

What is a VLESS server?

A server running Xray-core, or another program that supports VLESS, set up to accept VLESS connections. It holds the list of UUIDs it accepts and forwards traffic for clients that present one. You can run your own or use a provider's.

Is there a VLESS app for Windows?

Yes. Xray-core's README lists several Windows clients, v2rayN among them (read 16 November 2026). You still need a server to connect to. Tegant has apps for iPhone, iPad, Mac and Android only, so it is not an option on Windows.

Is VLESS free?

The software is free and open source. A server is not: someone has to rent and run it, whether that is you or a VPN provider.


Tegant VPN supports WireGuard and, with Premium, XRay, so you can switch protocols depending on your network. Learn more about Tegant VPN.