What Is HTTP/3? – Definition and How It Works
Learn what HTTP/3 changes, how QUIC over UDP removes transport head-of-line blocking, and what connection migration means in practice.
HTTP/3 keeps HTTP semantics and replaces the transport. Instead of TCP it uses QUIC, a protocol built on UDP that provides encryption, multiplexed streams, and faster connection establishment.
1. The Problem It Solves
HTTP/2 multiplexes streams over one TCP connection, removing application-layer blocking. But TCP delivers bytes strictly in order, so a single lost packet stalls delivery for every stream sharing that connection.
The more streams share a connection, the more one lost packet costs — the opposite of what multiplexing was meant to achieve.
2. How QUIC Fixes It
QUIC implements streams at the transport layer, and each is delivered independently. A packet lost on one stream does not delay the others.
Because QUIC runs over UDP in user space rather than in the operating system kernel, it can also evolve far faster than TCP, whose changes must propagate through every network stack in the world.
3. Faster Connection Setup
TCP requires a handshake, then TLS requires another. QUIC combines transport and cryptographic handshakes, establishing a secure connection in fewer round trips — and allowing zero round trips when resuming a previous connection.
On high-latency links, that difference is directly visible in how quickly a page starts loading.
4. Encryption Is Not Optional
QUIC encrypts by design, including most transport metadata. There is no unencrypted mode.
That improves privacy and complicates network middleboxes that inspected or optimised TCP traffic — one reason adoption depended on those intermediaries adapting.
5. Connection Migration
TCP connections are identified by the address and port at each end, so changing network — moving from wireless to mobile data — breaks them.
QUIC identifies connections by an identifier independent of address, so a connection can survive a network change. For mobile clients this means downloads and streams continue rather than restarting.
6. Comparison
| Aspect | HTTP/2 | HTTP/3 |
|---|---|---|
| Transport | TCP | QUIC over UDP |
| Head-of-line blocking | At TCP | Removed |
| Handshake | TCP plus TLS | Combined, fewer round trips |
| Encryption | Optional in principle | Always |
| Network change | Breaks the connection | Survives it |
| Middlebox visibility | Substantial | Minimal |
7. Practical Considerations
- UDP is sometimes blocked on restrictive networks, so clients fall back to HTTP/2.
- Discovery happens through an advertisement header or DNS records; a client does not simply assume it.
- Library support varies, and many HTTP clients still speak HTTP/2 only.
- The fingerprinting surface changes, since QUIC exposes its own implementation choices.
8. Summary
HTTP/3 keeps HTTP semantics and moves to QUIC over UDP, giving independent streams without transport-level blocking, faster handshakes, mandatory encryption, and connections that survive a network change.
The benefits are largest on lossy and mobile networks, and adoption depends on UDP being permitted along the path — with HTTP/2 remaining the fallback.