VLESS vs WireGuard vs AmneziaWG: which one survives your network
Use WireGuard when nothing interferes with it, AmneziaWG when a network blocks WireGuard by its packet signature but does not inspect TLS, and VLESS with Reality when the network does deep packet inspection or allows only TCP 443. That is the whole rule; the rest of this article explains why, and why 404 VPN ships VLESS rather than the other two.
What each protocol is
- WireGuard is a kernel-level UDP tunnel with a fixed cipher set. Small code, very fast, easy to identify: every handshake starts with the same bytes, and it runs over UDP only.
- AmneziaWG is WireGuard with junk packets and randomised headers added so that the handshake no longer matches the known signature. It is still UDP, and it is still a tunnel that does not look like anything else.
- VLESS is a lightweight proxy protocol from the Xray project. On its own it is just framing. The transport around it does the work: with Reality, the connection performs a real TLS 1.3 handshake that borrows the certificate of an ordinary website, so to the network it is a browser visiting that site.
Comparison
| Property | WireGuard | AmneziaWG | VLESS + Reality |
|---|---|---|---|
| Transport | UDP | UDP | TCP |
| Looks like | WireGuard | random noise | HTTPS to a real site |
| Passes UDP-blocking networks | No | No | Yes |
| Passes basic signature filters | No | Yes | Yes |
| Passes TLS fingerprint inspection | n/a | n/a | Yes, mimics a browser |
| Throughput on an unfiltered line | Highest | High | High |
| Phone battery | Best | Good | Good |
| Needs a special client | Yes | Yes, Amnezia or compatible | Yes: the 404 VPN app, Happ, v2rayTun |
Where WireGuard fails
Two situations. First, the network drops UDP for anything but DNS, which is common on mobile carriers abroad and in hotels. WireGuard has no TCP mode; it simply never connects. Second, the network recognises the handshake signature and blocks it. The tunnel connects for a few seconds, passes a little traffic, then goes silent.
Where AmneziaWG fails
It solves the second case but not the first: it is still UDP. It also stands out as high-entropy traffic to a single address with no TLS handshake, which some inspection systems classify as "unknown encrypted protocol" and throttle. It works well against filters that match specific signatures; it does not make the traffic look like anything legitimate.
Where VLESS with Reality fails
Rarely, and in specific ways: on networks that allow only ports 80 and 443 when the Reality entry runs on another port, and on networks that whitelist destination domains, since the camouflage site must be reachable. In the first case the fallback is VLESS over WebSocket with TLS on port 443, which goes through an ordinary web server. See what to do when Reality does not connect.
Why 404 VPN is built on VLESS
Because the failure mode of WireGuard is the one our users hit most: a tunnel that connects and passes nothing on a filtered network. Every 404 VPN location carries several VLESS entries, such as WebSocket with TLS and Reality, so the client has differently shaped connections to try. The cost is an app instead of a built-in client, and roughly one extra TLS handshake per connection.
FAQ
Is WireGuard more secure than VLESS?
Both encrypt with modern ciphers; WireGuard with ChaCha20-Poly1305, VLESS with Reality through TLS 1.3. Neither has known weaknesses. The practical security difference is that Reality traffic does not reveal that a VPN is in use.
Can I run WireGuard with 404 VPN?
VLESS is the main protocol. On some locations the dashboard also offers a WireGuard or AmneziaWG configuration for devices and routers that support only those; use it on networks that do not filter WireGuard.
Is AmneziaWG open source?
Yes. It is a fork of WireGuard maintained by the Amnezia project.
Which uses less data?
All three add a few percent of overhead. WireGuard's is the lowest; the difference over a month is negligible.