HTTP/2 vs HTTP/3: what changes, and when the difference shows
By TechCompare · Updated · How we check
Keep HTTP/2 on and add HTTP/3 next to it. HTTP/3 helps most on lossy and mobile networks, and browsers fall back to HTTP/2 whenever QUIC can't get through.
HTTP/2 and HTTP/3 share one idea: many requests travel over a single connection at the same time, with compressed headers. The difference is underneath. HTTP/2 runs over TCP with TLS on top. HTTP/3 runs over QUIC on UDP, which handles encryption and lost packets itself. That change matters most on networks that drop packets or switch often, like phones on mobile data.
How this is calculated
HTTP/2, now RFC 9113, fixed the big limit of HTTP/1.1, where a connection carried one request at a time and browsers opened about six connections per site to cope. It sends many requests as streams over one TCP connection. TCP, though, delivers bytes strictly in order. One lost packet holds up every stream behind it until it's sent again. That's head-of-line blocking, and HTTP/2 only moved it from HTTP down into TCP.
HTTP/3 (RFC 9114) moves the streams into QUIC, so a lost packet only holds up its own stream. QUIC also sets up the connection and the encryption together, and it tells connections apart by an ID instead of the address and port. A phone that moves from Wi-Fi to mobile data can keep the same connection instead of starting over.
There are costs. QUIC runs outside the kernel on most servers, so it can use more CPU than TCP, which operating systems and network cards have been tuned for over decades. Some office and public networks block UDP outright. And HTTP/2's header compression, HPACK, relied on TCP's ordering, so HTTP/3 needed a new one called QPACK.
Both versions need HTTPS in browsers. No major browser speaks HTTP/2 over plain HTTP, and HTTP/3 has TLS 1.3 built in. The SSL Checker tries HTTP/1.1, HTTP/2 and HTTP/3 one at a time, so you see every version the server accepts, not only the one it prefers.
Verdict
Run both. HTTP/2 is the safe baseline that every current browser speaks. HTTP/3 is a free gain on a CDN and worth the setup on your own servers when many visitors are on phones. Don't turn HTTP/2 off, since some networks only ever let TCP through.
More SSL scenarios
Related guides
Frequently asked questions
Can I run HTTP/3 without HTTP/2?
Is HTTP/2 enough for most sites?
Does HTTP/2 server push still matter?
Related tools
DNS Lookup
Look up a domain's DNS records on Cloudflare or compare several resolvers at once, and read its SPF, DMARC and DKIM records in plain words.
Use toolOpen Graph Visualizer
Preview how your website links will look when shared on Google, Twitter, Facebook, and Discord.
Use toolPassword Generator
Generate secure, random passwords locally in your browser.
Use tool