What Is HTTP/3?
HTTP/3 and QUIC Explained
HTTP/3 is the third major version of the web protocol. It carries the same kinds of requests and responses as HTTP/2 but runs on QUIC, a transport protocol built on UDP. In short, HTTP/3 is HTTP running over QUIC rather than over TCP.
A transport protocol decides how data moves between two computers. TCP, which HTTP/1.1 and HTTP/2 use, guarantees ordered, reliable delivery. UDP sends packets without those guarantees, so QUIC adds its own reliability and ordering on top, which lets it be designed around the problems of TCP.
Why QUIC Connects Faster and Stalls Less
Setting up a secure connection over TCP normally involves separate steps for the transport connection and the encryption handshake. QUIC combines them, so a new connection can be established with fewer round trips, the back-and-forth messages that add delay on long-distance links. Encryption is built into QUIC rather than added as a separate layer.
QUIC also removes a stall that affects HTTP/2 over TCP. Because TCP delivers bytes strictly in order, one lost packet can hold up every request sharing that connection until it is resent. In QUIC, each stream is delivered independently, so a loss affects only the stream it belongs to.
Connections can also survive a change of network. When a phone moves from Wi-Fi to a mobile network, its address changes, and a TCP connection tied to the old address usually has to be rebuilt. QUIC identifies connections with a connection ID, so the session can continue. This is called connection migration.
When HTTP/3 Makes a Noticeable Difference
The benefits matter most on networks with high latency or packet loss, such as mobile connections, crowded public Wi-Fi and long distances between visitor and server. On a fast, stable wired connection close to the server, the gains are often small, and the page's own design usually matters more.
HTTP/3 does not fix a slow server. If the server takes a long time to build a page, the request waits regardless of protocol. Measures such as time to first byte reflect server work as well as network speed, so a protocol upgrade cannot remove that delay alone.
Frequently asked questions
Does my website need HTTP/3?
Not necessarily. HTTP/3 is an optional improvement. Browsers and servers negotiate the best protocol they both support and fall back to HTTP/2 or HTTP/1.1 when needed, so a site works without it. Whether it helps depends on visitors' networks and on the site's design, and most sites gain more from reducing page weight first.
Why do some networks block HTTP/3?
Some corporate and restrictive networks block or limit UDP traffic, which HTTP/3 depends on. When that happens, the browser cannot use QUIC and switches to an older protocol, so the page still loads. This fallback is why HTTP/3 works as an optional upgrade rather than a requirement.