What is HTTP/3?
Turkish: HTTP/3
HTTP/3 runs HTTP semantics over QUIC and UDP, reducing connection setup time and limiting the impact of packet loss.
What Is HTTP/3?
HTTP/3 runs HTTP semantics over QUIC instead of TCP. QUIC uses UDP and includes TLS 1.3 security as part of the protocol. The goal is more resilient web communication, especially on mobile networks and connections where packet loss is common.
HTTP/2 multiplexes streams over one TCP connection, but packet loss at the TCP layer can still affect the whole connection. In HTTP/3, streams are separated within QUIC, so loss on one stream blocks others less often. Connection setup can also be shorter, and a device can keep a connection identity while moving from Wi-Fi to mobile data.
Where It Helps
CDNs, high-traffic websites, media services, and products with many mobile users may benefit most from HTTP/3. Support should still be introduced gradually; if a client or network cannot use HTTP/3, the system normally falls back to HTTP/2 or HTTP/1.1.
HTTP/3 does not change HTTP methods, headers, or status codes. Application code often stays the same; most work happens in the server, CDN, firewall, and observability layers.
Related Terms
HTTP is the core web communication protocol that defines request-response exchanges between browsers, API clients, and servers.
HTTP/2HTTP/2 speeds up web pages and API responses by using multiple streams and compressed headers over a single connection.
QUIC ProtocolQUIC is a modern UDP-based transport protocol with built-in TLS 1.3 encryption that gives HTTP/3 faster connection setup and recovery.
WebRTCWebRTC is a real-time communication standard for plugin-free audio, video, and data channels between browsers and mobile apps.