HTTP/2
HTTP version 2Best for: Networks that block UDP
- Style, from Website
- Script, from Websitelost
- Image waits, from Website
- Script again, from Website
Compare protocols
Best for: Networks that block UDP
Best for: Phones and busy Wi-Fi
HTTP/2 and HTTP/3 send the same requests and responses. The difference is underneath: HTTP/2 runs on TCP, so one lost packet holds up every request on the connection. HTTP/3 runs on QUIC over UDP, where each stream recovers on its own, the connection opens in one round trip and it survives a switch from Wi-Fi to mobile data.
Tick everything that is true for you.
Your pick shows here
Tick one or more lines and we weigh them for you.
| What differs | HTTP/2 | HTTP/3 |
|---|---|---|
| Runs on | TCP, with TLS on top | QUIC, which runs on UDP |
| Port | TCP 443 | UDP 443 |
| Opening a new connection | TCP handshake plus TLS 1.3: 2 round trips | 1 round trip, 0 on a resumed visit |
| One lost packet | Stalls every stream on the connection | Stalls only the stream it belongs to |
| Header compression | HPACK | QPACK |
| Changing network | Connection breaks and must start again | Connection moves with you, tracked by a connection ID |
| Encryption | TLS 1.2 or 1.3 in practice | Always TLS 1.3, built into QUIC |
| Standard | RFC 9113 (first RFC 7540, 2015) | RFC 9114 (2022) |
Each page plays the real packets on a map, step by step, with every header explained.
Each line describes one of the two. Which one?
Question 1 of 8
Runs on
TCP, with TLS on top
On clean, fast networks the difference is small. On mobile data or lossy Wi-Fi, HTTP/3 is often noticeably faster, because a lost packet no longer blocks every request and the connection opens sooner.
The server says so in an Alt-Svc header over HTTP/2, or in an HTTPS record in DNS. The browser then tries QUIC on UDP 443 and keeps HTTP/2 as a fallback.
For web traffic that uses it, yes. QUIC does the jobs TCP did, such as resends and ordering, but per stream and inside UDP. TCP is still used everywhere else.
No. Pages, URLs and headers stay the same. Only the server, load balancer or front proxy needs HTTP/3 turned on and UDP 443 open.