VLESS vs VMess vs Trojan vs Shadowsocks: what matters in 2026
VLESS, VMess, Trojan and Shadowsocks are proxy protocols that the same client apps support, and the practical difference is how each one looks to a network that is watching. VLESS with Reality looks like HTTPS to a real website and is the right default. Trojan looks like HTTPS to your own server. VMess is the older design VLESS replaced. Shadowsocks is the lightest and the easiest to fingerprint.
One table
| Property | VLESS | VMess | Trojan | Shadowsocks |
|---|---|---|---|---|
| Year | 2020 | 2016 | 2019 | 2012 |
| Own encryption | No, relies on TLS or Reality | Yes, AES/ChaCha with time-based auth | No, relies on TLS | Yes, AEAD ciphers |
| Needs a domain and certificate | Not with Reality | Only with TLS | Yes | No |
| Looks like | HTTPS to a real site (Reality) | encrypted blob or HTTPS | HTTPS | encrypted blob |
| Overhead | Lowest | Highest | Low | Low |
| Clock sensitivity | None | Must be within 90 s | None | None |
| Served by 404 VPN | Yes | No | No | No |
VLESS
VLESS carries a UUID for authentication and nothing else; it deliberately has no encryption of its own, because the transport layer provides it. With Reality, the server borrows the TLS certificate of a chosen public website, so the handshake is genuine and the network sees a visit to that site. Over WebSocket with TLS it travels through an ordinary web server on port 443 and looks like a website using a live connection. This is why one VLESS server can offer several entries that look different on the wire; a 404 VPN subscription carries several per location so you can switch when one is filtered. See what a VLESS key contains.
VMess
VMess was V2Ray's original protocol. It encrypts and authenticates on its own, which means it carries a recognisable structure and is sensitive to clock drift: a device more than 90 seconds off cannot authenticate. VLESS was designed as its replacement, and modern setups use VMess only where a server cannot be upgraded.
Trojan
Trojan takes the opposite approach from VMess: no protocol-level encryption, just TLS to your own domain with a password inside. It is simple and convincing, but it requires a domain and a certificate per server, and the server answers as itself rather than as a popular site. Reality achieves the same effect without the domain.
Shadowsocks
Shadowsocks is an encrypted SOCKS5 proxy. It is tiny, fast, works on anything, and its traffic is high-entropy data with no handshake, which inspection systems have learned to flag. 404 VPN does not serve it: the VLESS entries cover the same networks with a real TLS handshake. Shadowsocks 2022 ciphers fix the replay issues of older versions, if you meet it elsewhere.
Which to use
- VLESS with Reality or WebSocket with TLS by default: whichever connects on your network.
- If one is blocked, switch to the other entry of the same location.
- Shadowsocks, VMess and Trojan only when a server you use offers nothing else.
FAQ
Is VLESS encrypted?
The protocol is not; the transport is. With Reality or TLS the connection is TLS 1.3, the same as any HTTPS site.
Why did 404 VPN drop VMess?
VLESS does everything VMess did with less overhead and no clock dependency. Keeping VMess would add a recognisable protocol to the mix for no gain.
Is Trojan better than VLESS?
Trojan and VLESS over TLS are nearly equivalent. Reality gives VLESS the edge, because the certificate belongs to a real public site.
Can one app handle all four?
Yes. Happ, v2rayTun and v2rayN support all of them; a 404 VPN subscription link carries VLESS entries only.