What is HTTP/3?

HTTP/3 is the most current version of the Hypertext Transfer Protocol (HTTP), which is the protocol used to transfer data between web browsers and websites. Protocols are a set of rules or standards that dictate how data or information is transmitted, received, and interpreted between devices, systems, or parties.

HTTP/3  improves how data is delivered across the internet by using a newer transport protocol called QUIC, instead of the traditional TCP used by HTTP/1.1 and HTTP/2. HTTP/3 was designed to make websites more reliable, more secure, and faster to load. This is especially true for networks with high latency or packet loss (like mobile networks).

In simplest terms, HTTP/3 is an update to existing versions of HTTP aimed at providing faster and more secure web experiences. 

Which problems does HTTP/3 solve?

HTTP/3 addresses several long-standing challenges associated with TCP-based web communication. Specifically, it does improve the following: 

Head-of-line blocking. One of the most notable issues is head-of-line blocking. With TCP, if a single packet is lost during transmission, subsequent packets must wait until the missing packet is retransmitted. This can delay the entire connection even when most data has arrived successfully. QUIC solves this by allowing multiple independent streams within a connection. If a packet belonging to one stream is lost, only that stream is affected while other streams can continue delivering data.

Slow connection setup. HTTP/3 also improves connection setup latency. Traditional HTTP requires multiple handshake steps before application data can be transmitted. QUIC reduces the number of round trips required to establish a secure connection, which can significantly reduce latency - especially for users connecting over long distances.

Mobile network performance. HTTP/3 is better suited to modern mobile networks, where connectivity conditions frequently change and packet loss is more common.

What is QUIC and why does HTTP/3 use it?

HTTP/3 uses QUIC because it provides better performance and resilience compared to TCP. QUIC (Quick UDP Internet Connections) is a transport protocol originally developed by Google and later standardized by the IETF.

QUIC (Quick UDP Internet Connections) is a transport protocol originally developed by Google and later standardized by the Internet Engineering Task Force (IETF). It was designed to address some of the limitations of TCP while maintaining strong security and reliability guarantees.

QUIC operates over UDP, which allows it to implement advanced features at the protocol level rather than relying on the operating system’s TCP stack. This flexibility enables faster innovation and performance improvements.

What are the key benefits of QUIC?

• Faster connection setup – Connections can be established in fewer round trips, sometimes even allowing data to be sent immediately with 0-RTT resumption.

• Built-in encryption – QUIC integrates TLS 1.3 directly into the protocol.

• Stream multiplexing without blocking – Data is divided into independent streams.
  Better performance on unreliable networks – Packet loss affects only the impacted streams rather than the entire connection.

HTTP/3 Architecture

HTTP/3 uses a new architecture that runs HTTP on top of QUIC, a transport protocol built on UDP instead of TCP. In this model, QUIC handles connection management, multiplexing, congestion control, and encryption, combining functions that were previously split across multiple layers.

Each HTTP request and response is carried over an independent QUIC stream within a single connection. Because these streams operate independently, packet loss in one stream does not block others.

HTTP/3 also integrates TLS 1.3 directly into QUIC, making encryption mandatory and enabling faster, more efficient connection setup. This architecture improves performance, reliability, and resilience on modern networks.

What are the key benefits and features of HTTP/3?

HTTP/3 provides better security

Security is built directly into HTTP/3. All HTTP/3 connections are encrypted by default, using TLS 1.3 integrated directly into the QUIC protocol. Unlike earlier versions of HTTP, where encryption is optional, HTTP/3 does not support unencrypted connections.

This integrated approach also simplifies the process of establishing a connection, because the encryption handshake and transport setup occur together. As a result, HTTP/3 can often establish secure connections faster than traditional HTTPS over TCP.

HTTP/3 makes websites faster

HTTP/3 can improve website performance, although the exact impact depends on several factors such as network conditions, server configuration, and application design.

In many real-world scenarios, HTTP/3 can reduce latency and page load times, particularly when network conditions are less than ideal. Because QUIC handles packet loss more efficiently and establishes connections more quickly, users may experience faster content delivery and more consistent performance.

HTTP/3 is particularly beneficial in environments where:

• Mobile connectivity is common

• High latency networks are involved

• Packet loss occurs frequently

• Multiple resources are loaded simultaneously

Keep in mind that websites that are already highly optimized may see smaller improvements compared to those operating on more challenging network conditions.

How is HTTP/3 different from HTTP/1.1 and HTTP/2?

The main difference between HTTP/2 and HTTP/3  is the underlying transport protocol. The chart below describes the key differences between HTTP/3 vs. HTTP/2. 

Both HTTP/1.1 and HTTP/2 rely on TCP, which was previously the traditional transport protocol for internet traffic. While HTTP/2 introduced major improvements like multiplexing multiple requests over a single connection, it still had some limitations from TCP.

HTTP/3 replaces TCP with QUIC, a modern transport protocol designed to improve performance. Because QUIC handles many features like encryption, congestion control, and connection management directly at the transport layer, HTTP/3 can reduce delays and recover more efficiently from network disruptions.

Do browsers support HTTP/3?

Yes. Most modern browsers now support HTTP/3 and can automatically use it when it is available.

Major browsers that support HTTP/3 include:

• Google Chrome

• Microsoft Edge

• Mozilla Firefox

• Apple Safari

Browsers use a mechanism called protocol negotiation to determine the best supported protocol between the client and server. If HTTP/3 is available, the browser will typically use it automatically. If not, it will fall back to HTTP/2 or HTTP/1.1, all without the person browsing being aware of this activity occurring behind the browser. 

Because of this automatic negotiation, users generally do not need to configure anything manually to benefit from HTTP/3.

Do websites need to change anything to use HTTP/3?

Yes. In order to support HTTP/3, web servers or infrastructure providers must enable support for QUIC and HTTP/3.

This typically requires:

• A web server, proxy, or CDN that supports HTTP/3

• QUIC enabled at the transport layer

• TLS configuration compatible with TLS 1.3

Many modern web servers, reverse proxies, and content delivery networks now support HTTP/3. In many cases, enabling HTTP/3 is primarily a configuration change rather than a major architectural update.

How can Fastly help? 

Fastly’s CDN supports HTTP/3 and QUIC at the edge, allowing compatible browsers to connect using faster, more efficient transport than traditional TCP-based protocols. By enabling HTTP/3, Fastly helps reduce connection setup time, improve performance on unreliable networks, and deliver content more quickly to end users.

By supporting HTTP/3 across its global edge network, Fastly enables customers to deliver lower latency page loads, improved streaming performance, and stronger security through the built-in TLS 1.3 encryption used by QUIC. These improvements help organizations deliver faster, more resilient digital experiences to users worldwide while maintaining compatibility with existing HTTP infrastructure.