VLESS vs WireGuard: What's the Difference and Which Should You Use?
Published 11 min read
VLESS and WireGuard both sit in the protocol menu of many VPN apps, but they come from different worlds. WireGuard is a classic VPN tunnel: small, fast and built on UDP. VLESS is a lightweight proxy protocol that travels inside an ordinary TLS connection, usually with a companion called Reality.
Short version: WireGuard is usually the faster and lighter of the two, and it handles switching networks better. VLESS with Reality looks like normal HTTPS traffic, so it connects on strict networks that only allow web traffic, where WireGuard often can't. The rest of this guide goes a bit deeper into how each one works, for readers who like to know what's under the hood.
What is VLESS?
VLESS is a proxy protocol from the Xray ecosystem, also known as Project X. It appeared in 2020 as part of V2Ray, as a leaner successor to the older VMess protocol. Its author then started Project X and Xray-core, where VLESS is developed today. The Xray documentation describes it in one line: a stateless, lightweight transport protocol.
Three things define the VLESS protocol:
- It's tiny. A VLESS request starts with a short header: a version byte, a 16-byte user ID, a command, and the address and port you want to reach. After that, your data simply flows. The server's reply header is just a couple of bytes.
- It authenticates with a UUID. Each user is identified by a UUID, a long random identifier that works like a key. There are no usernames, passwords or timestamps involved.
- It doesn't encrypt anything on its own. This is the part that surprises people. In the classic setup, VLESS's own encryption setting is literally set to
none. The protocol leaves encryption to the layer it travels in, which is TLS or Reality. The Xray documentation is explicit that VLESS must be used with an outer security layer.
That last point is a design decision, not a weakness. VMess encrypted traffic itself and was then often wrapped in TLS anyway, so the same data got encrypted twice. VLESS drops the inner layer and lets TLS do the job once. Newer Xray releases also offer an optional encryption layer for VLESS itself, but VLESS inside TLS or Reality is still the usual setup, and it's the one this article covers.
VLESS most often runs over TCP. Xray can also carry it over other transports, such as WebSocket or gRPC.
VLESS is a proxy protocol, not a classic VPN tunnel
A classic VPN such as WireGuard works at the network layer: it wraps whole IP packets and sends them through the tunnel. VLESS works one level up. It relays connections: "open a TCP connection to this address and port, then pass the bytes along". It can relay UDP traffic too, carried inside the same kind of stream.
So how does a VLESS app cover everything on your phone, not just one browser? It uses the operating system's VPN interface, the same one any VPN app uses. The system hands all of the device's packets to the app, and a small component inside the app turns those packets back into connections and sends each one through the VLESS proxy. From your side it behaves like any other VPN. One side effect: tools like ping, which don't use TCP or UDP, often don't travel through the tunnel.
What is Reality (XTLS Reality)?
Reality is the security layer most often paired with VLESS today, which is why you'll see "VLESS Reality" or "XTLS Reality" written together. It was added to Xray in 2023 as a replacement for the normal TLS layer on the server side.
With ordinary TLS, a server operator needs a domain name and a certificate for it. Reality removes that requirement. Instead:
- The connection opens with a real TLS 1.3 handshake, the same kind your browser performs when it loads a secure website.
- The handshake borrows the identity of a real website: it names an existing, well-known site that supports TLS 1.3 and HTTP/2. The server doesn't need its own domain or certificate.
- The client and server recognise each other with an X25519 key pair. The app holds the server's public key, and the proof is tucked inside the handshake itself. Once the server recognises the client, it finishes the handshake with a temporary certificate that only a client holding the right key can verify.
- The client imitates the TLS behaviour of a common browser, so the handshake has the same shape as everyday web traffic.
The result: on the network, VLESS with Reality looks like ordinary HTTPS, usually on TCP port 443. Inside that encrypted TLS 1.3 session, VLESS carries your traffic.
The practical benefit: some hotel, airport, office and campus Wi-Fi networks only allow normal web traffic, and a protocol that looks like HTTPS usually connects fine there.
What is WireGuard?
WireGuard is a VPN protocol designed by Jason A. Donenfeld and added to the Linux kernel in 2020. It set out to be much simpler than older VPN protocols, and its core code is around 4,000 lines. Our OpenConnect vs WireGuard comparison has the longer introduction. The essentials:
- UDP only. Every WireGuard packet travels over UDP. There is no TCP mode.
- A Noise-based handshake. WireGuard's key exchange is built on the Noise protocol framework and completes in a single round trip.
- Fixed, modern cryptography. Curve25519 for key exchange, ChaCha20-Poly1305 for encrypting data and BLAKE2s for hashing. Nothing is negotiated, so there is no weaker option to fall back to.
- Roaming by keys. Each device is identified by its public key, not its network address. When your phone moves from Wi-Fi to mobile data, the tunnel carries on from the new address.
- Quiet when idle. WireGuard sends nothing when you aren't using the connection, unless a keepalive is configured.
Curious how tunneling protocols got here? The history of VPN is a quick read.
VLESS vs WireGuard at a glance
| VLESS (with Reality) | WireGuard | |
|---|---|---|
| Type | Proxy protocol, relays connections | VPN tunnel, carries IP packets |
| Transport | Usually TCP (other transports possible) | UDP only |
| Usual port | 443, same as HTTPS | No fixed port; often 51820 |
| Encryption | None of its own; provided by TLS 1.3 through Reality | Built in: ChaCha20-Poly1305 |
| Authentication | UUID, plus an X25519 key for Reality | Curve25519 public keys |
| How it looks on the network | Like ordinary HTTPS traffic | Like a stream of UDP packets |
| Connection setup | TCP handshake, then TLS handshake | One round trip |
| Speed and latency | Good; less suited to real-time traffic on poor connections | Usually the faster of the two |
| Switching networks | Connections have to be reopened | Continues almost instantly |
| Battery use | Moderate | Generally lower |
| Networks that only allow web traffic | Usually connects | Can't connect if UDP isn't allowed |
| Review and maturity | Open source, younger, less formal review | Small codebase, formally analyzed, in the Linux kernel |
Speed and latency
WireGuard is usually faster, and the reasons are structural. Its handshake takes one round trip. It runs over UDP, so a lost packet never holds up the packets behind it. And its encryption is quick on phone processors.
VLESS itself adds almost nothing: a few dozen bytes at the start of each connection. The cost comes from what it rides on. A new connection needs a TCP handshake and then a TLS handshake before any data moves. For browsing and downloads you rarely feel this once connections are open.
Where you can feel it is real-time traffic. Calls, games and other apps that use UDP get carried inside a TCP stream. TCP delivers everything in order, so one lost packet makes everything behind it wait. On a clean connection that's fine. On a weak one, it shows up as stutter or lag spikes.
One detail for the technically curious: because VLESS relays connections instead of wrapping packets, it avoids the classic "TCP inside TCP" slowdown, where two layers of TCP both try to repair the same loss.
Security and maturity
Both protect your traffic with modern cryptography, but they've had different amounts of outside review.
- WireGuard has a small, fixed design. It was published as an academic paper, its handshake has been formally analyzed by researchers, and it ships inside the Linux kernel. That's a lot of independent review for a VPN protocol.
- VLESS with Reality gets its encryption from TLS 1.3, one of the most studied security protocols there is. VLESS and Reality themselves are open source and actively developed, but they're younger and community-driven, and they haven't had the same level of formal analysis or independent auditing.
And as always: no protocol makes you anonymous. A VPN protects your connection from other people on the same network and from your internet provider. It doesn't hide who you are from sites you sign in to. Our guide on what a VPN does and doesn't protect against goes through the limits.
On your phone: battery and switching networks
WireGuard was designed with roaming in mind. Drop from Wi-Fi to 5G and the tunnel keeps going, because the server recognises your key, not your address. It also stays silent when idle, which is easy on the battery.
VLESS runs over TCP, and a TCP connection is tied to the network it was opened on. When your network changes, open connections end and have to be set up again. Apps handle this for you, but you may notice a short pause. Keeping TCP and TLS sessions alive also takes a little more work than WireGuard's quiet UDP, so battery use tends to be somewhat higher. For the everyday view, see should you use a VPN all the time.
Connecting on strict networks
This is where VLESS with Reality earns its place. Some hotel, airport, office and campus Wi-Fi only lets normal web traffic through. WireGuard needs UDP, so if a network doesn't allow UDP, it can't connect at all.
VLESS with Reality uses TCP and a genuine TLS 1.3 handshake, so it looks like normal HTTPS traffic, the kind these networks are set up to allow. It usually connects. That isn't a guarantee: every network is configured differently, and no protocol works everywhere.
These are also the networks where a VPN is most useful, since you don't control them. More on that in how to avoid leaking information over public Wi-Fi.
Setup complexity
If you only use a VPN app, both are a single tap. The difference matters if you ever run your own server.
- WireGuard is famously simple: a key pair on each side, an address and a port.
- VLESS with Reality has more moving parts: a UUID, an X25519 key pair, a short ID, a suitable website to borrow the identity of, and transport settings. Reality saves you from buying a domain and managing certificates, but there's more to get right.
Which one should you use?
- Choose WireGuard for everyday use: browsing, video, calls and gaming, especially on mobile data or when you move between networks a lot. It's fast, light on battery and very well reviewed.
- Choose VLESS (with Reality) when WireGuard won't connect or keeps dropping, which usually means you're on a network that only allows web traffic.
- Not sure? Let your VPN app pick, and only change protocols when you have trouble connecting.
Neither one is "the best VPN protocol" for every situation. They solve different problems, and a good app offers both.
VLESS and WireGuard in Hello VPN
Hello VPN offers both on iOS and Android: WireGuard and VLESS with Reality, next to HelloWG, OpenConnect and IKEv2. The Auto option picks a protocol for you, so most of the time you don't have to think about any of this. If a network gives you trouble, open the app's protocol settings and choose one yourself.
You can try it with the 3-day free trial. And if you'd like to compare the other options in the menu, read HelloWG vs WireGuard next.
Frequently asked questions
What is VLESS?
VLESS is a lightweight, stateless proxy protocol from the Xray (Project X) ecosystem. It identifies users with a UUID and has no encryption of its own. Instead it travels inside an encrypted layer, normally TLS or Reality, which protects the traffic.
Is VLESS better than WireGuard?
Not in general. WireGuard is usually faster, uses less battery and copes better with switching networks. VLESS with Reality is the better pick on networks that only allow web traffic, where WireGuard often can't connect.
Is VLESS encrypted?
Not by itself. In the usual setup the VLESS protocol sends data as it is and relies on the TLS or Reality layer around it for encryption. With Reality, your traffic is protected by TLS 1.3. Used without such a layer, VLESS would not be private, so apps always pair the two.
What is VLESS Reality?
It's VLESS running inside Reality, a security layer from the Xray project. Reality performs a real TLS 1.3 handshake and borrows the identity of an existing website, so the server needs no domain or certificate of its own, and the connection looks like normal HTTPS traffic.
What is the difference between VLESS and VMess?
VMess is the older protocol from V2Ray. It has its own built-in encryption, and its authentication depends on the clocks of the client and server being in sync. VLESS removes both: it authenticates with just a UUID and leaves encryption to TLS or Reality, which makes it simpler and lighter.
“WireGuard” is a registered trademark of Jason A. Donenfeld.