TodayTools

Compare protocols

HTTP/2 vs HTTP/3: what changed and is HTTP/3 faster

Donate
What brings you here?

The difference at a glance

HTTP/2

HTTP version 2

Best for: Networks that block UDP

On TCP, one lost packet holds up every file behind it.
  1. Style, from Website
  2. Script, from Websitelost
  3. Image waits, from Website
  4. Script again, from Website

HTTP/3

HTTP over QUIC

Best for: Phones and busy Wi-Fi

On QUIC, a lost packet only holds up its own file.
  1. Style, from Website
  2. Script, from Websitelost
  3. Image, from Website
  4. Script again, from Website

The short answer

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.

Which one fits you?

Tick everything that is true for you.

What do you need?

Your pick shows here

Tick one or more lines and we weigh them for you.

HTTP/2 and HTTP/3 side by side

HTTP/2 vs HTTP/3: differences row by row
What differsHTTP/2HTTP/3
Runs onTCP, with TLS on topQUIC, which runs on UDP
PortTCP 443UDP 443
Opening a new connectionTCP handshake plus TLS 1.3: 2 round trips1 round trip, 0 on a resumed visit
One lost packetStalls every stream on the connectionStalls only the stream it belongs to
Header compressionHPACKQPACK
Changing networkConnection breaks and must start againConnection moves with you, tracked by a connection ID
EncryptionTLS 1.2 or 1.3 in practiceAlways TLS 1.3, built into QUIC
StandardRFC 9113 (first RFC 7540, 2015)RFC 9114 (2022)

Watch each one work

Each page plays the real packets on a map, step by step, with every header explained.

Test yourself

Each line describes one of the two. Which one?

Question 1 of 8

Runs on

TCP, with TLS on top

Questions people ask

Is HTTP/3 faster than HTTP/2?

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.

How does a browser know a site supports HTTP/3?

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.

Does HTTP/3 replace TCP?

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.

Do I need to change my website for HTTP/3?

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.

More comparisons

Donate