HTTP/3 Explainer
HTTP/3 is a newer version of the web protocol that browsers and websites use to exchange pages, images, video, and application data. Its most important change is the transport underneath it. Earlier modern web connections typically use HTTP/2 over TCP. HTTP/3 uses QUIC, a transport protocol built on UDP, to make connections more resilient when a network is slow, busy, or changing.
QUIC combines functions that were once split across several layers. It establishes an encrypted connection, manages reliability, and carries multiple independent streams of data. A stream can hold part of a page request, an image, a font, or another resource. Because streams can progress independently, a problem with one lost packet does not necessarily make every other resource wait for that specific packet to be retransmitted.
This addresses a limitation called head-of-line blocking. With TCP, packets must be delivered in order within the connection. When one needed packet is missing, later packets may wait even if they belong to a different piece of content. HTTP/2 improved how browsers organize requests, but it still relied on TCP’s single ordered connection. HTTP/3’s QUIC streams can recover separately, helping a page stay responsive when a network drops or delays some traffic.
HTTP/3 also makes it easier for a connection to survive a network change. A phone may move from Wi-Fi to cellular service while a page is loading. QUIC can use connection identifiers that are not tied as closely to one network address, allowing a compatible connection to continue without restarting every step. That can reduce interruption for mobile users, though it depends on the server, browser, and network path all supporting the feature.
Security is built into QUIC from the start. It normally uses modern TLS encryption as part of establishing the connection, which reduces extra round trips and protects the transport handshake. Websites still need their normal application security practices, and HTTP/3 does not automatically make content trustworthy. It changes the method of delivery, not the responsibility to secure the site and its data.
Not every connection will use HTTP/3. Browsers and servers negotiate a compatible option, and a site can fall back to HTTP/2 or HTTP/1.1 when necessary. The central idea is practical efficiency: HTTP/3 is designed to carry many web requests with less interference between them, especially on the variable networks people use every day.
HTTP/3 is HTTP carried over QUIC. QUIC uses UDP and supports several independent streams inside one encrypted connection.
A lost packet can delay the stream that needs it without necessarily blocking unrelated streams. That can improve responsiveness on unreliable or changing networks.
No. Browsers and servers negotiate support, and sites can fall back to earlier HTTP versions when a compatible HTTP/3 connection is not available.
Explore more "Explainers"
Discover additional explainers across politics, science, business, technology, and other fields. Each explainer breaks down a complex idea into clear, everyday language—helping you better understand how major concepts, systems, and debates shape the world around us.