HTTP/2 vs HTTP/3: what actually changes for your website
HTTP/3 maps the same HTTP semantics onto QUIC on UDP instead of TCP: a lost packet need not block delivery on other streams (connection-wide congestion control still applies), the transport and encryption handshakes are merged with optional 0-RTT resumption, connections can migrate between networks, and encryption is mandatory. What RFCs 9113, 9114 and 9000 actually specify, what your site has to do (usually a host or CDN setting), and how to check what you serve - from the RFCs and Cloudflare's documentation, read 21 November 2026.
Per RFC 9113, RFC 9114 and Cloudflare's HTTP/3 documentation, read 21 November 2026: HTTP/2 and HTTP/3 are not competing products you pick between - they are two versions of the same protocol, and browsers negotiate the best one your server offers without any change to your website's code. The practical questions for a site owner are smaller and more useful: what actually changed underneath, is your host serving HTTP/3 yet, and is there anything to fix. Short answers: TCP became QUIC, probably check, and usually no.
What HTTP/2 changed, and what it left behind
RFC 9113 describes HTTP/2 as an optimized expression of HTTP semantics: it introduced header field compression and, critically, multiple concurrent exchanges on the same connection - so a browser no longer needs a handful of parallel TCP connections per site. (The 2022 RFC 9113 is the current spec; it obsoletes the original 2015 RFC 7540.) But HTTP/2 still runs over TCP, and TCP has no idea about those independent streams: one lost packet stalls every stream on the connection until retransmission arrives. That is the head-of-line blocking HTTP/2 moved from the HTTP layer down to the transport layer, where it stayed.
What HTTP/3 actually changes
RFC 9114 maps the same HTTP semantics onto QUIC, a transport protocol that runs over UDP instead of TCP and was standardized as RFC 9000. Per the RFC's abstract, QUIC brings stream multiplexing, per-stream flow control and low-latency connection establishment - and per Cloudflare's documentation, three practical consequences follow. First, reliability is per-stream: a lost packet delays the streams whose data it carried rather than every stream on the connection. Two qualifications keep that honest: one packet can carry data from several streams, and QUIC's congestion control applies across the entire connection (RFC 9114 says exactly that) - so loss can still slow everything indirectly. Second, the transport and encryption handshakes are combined into one, with optional zero round-trip time (0-RTT) resumption to servers a client has visited before - and RFC 9000 is blunt that 0-RTT provides no protection against replay attacks, so it is an option with security trade-offs, not a guarantee. Third, QUIC supports connection migration: connections are identified by a connection ID rather than the IP-address pair, so a phone switching from Wi-Fi to cellular can continue its connection instead of starting over. Supported is not unconditional - per RFC 9000, only clients migrate in this version of QUIC, and a network can still force a new connection. QUIC is also encrypted by default at the transport layer; there is no unencrypted HTTP/3.
What this means for a website owner
Less than the version number suggests. Per Cloudflare's documentation, version negotiation happens seamlessly between browser and server: if your host or CDN supports HTTP/3 and the browser does too, they use it; otherwise they fall back to HTTP/2. No markup, no JavaScript, no application code changes. Your checklist is therefore short: check what your site actually serves (browser developer tools show the protocol per request, often labeled h2 or h3), and if your host or CDN offers HTTP/3, turn it on - it is typically a setting, not a project. Managed hosts and CDNs have served HTTP/3 for years; Cloudflare's page notes it made HTTP/3 available to all its customers in 2021. If you run your own server, the web server's version and configuration decide - check its documentation rather than assuming.
Where the honest limits are
HTTP/3 is not a universal speedup, and this article promises no specific gains. The wins concentrate where TCP hurts most: high packet loss, high latency, mobile devices hopping between networks. On a fast, stable connection the difference may be invisible. Some networks block or throttle UDP, and clients then fall back to HTTP/2 - which is why the fallback existing matters more than the upgrade. And none of this replaces the unglamorous work: whether caching, compression and image weight matter more than a protocol version depends on your bottleneck, so measure yours rather than trusting anyone's universal ordering, including ours. Enable HTTP/3 because it costs you a settings toggle, not because you expect a transformation.
Sources, all read 21 November 2026: RFC 9113, HTTP/2 (header field compression; multiple concurrent exchanges on one connection; obsoletes RFC 7540 and 8740); RFC 9114, HTTP/3 (HTTP semantics over QUIC; stream multiplexing, per-stream flow control, low-latency connection establishment; HTTP/2 features subsumed by QUIC); Cloudflare Learning, What is HTTP/3? (QUIC on UDP; head-of-line blocking mitigation; combined handshake and 0-RTT; connection migration; encryption by default; seamless version negotiation with no website code changes; HTTP/3 available to all Cloudflare customers since 2021); RFC 9000, QUIC (0-RTT provides no protection against replay attacks; only clients migrate in this version of QUIC; connections not strictly bound to a single network path); per RFC 9114 section 1, QUIC provides reliability at the stream level with congestion control across the entire connection).
Tuning what your host or CDN actually serves? Omnistu's Cloud, Data and DevOps practice works on hosting setup, deployment pipelines, monitoring and data infrastructure - write to team@omnistu.com with what you are deciding.
Frequently asked questions
Do I need to change my website's code for HTTP/3?
No. Per Cloudflare's documentation, browsers and servers negotiate the HTTP version seamlessly; if both sides support HTTP/3 they use it, otherwise they fall back to HTTP/2. Your part is at most a host, CDN or server setting.
What does HTTP/3 actually fix compared to HTTP/2?
HTTP/2 multiplexes many requests over one TCP connection, but one lost packet still stalls them all (TCP-level head-of-line blocking). HTTP/3 runs over QUIC on UDP: a lost packet delays only the streams whose data it carried (congestion control stays connection-wide), handshakes are combined with optional 0-RTT (no replay protection, per RFC 9000), and connections can migrate across networks like Wi-Fi to cellular when the path allows it.
Is HTTP/3 always faster?
No honest source promises that. The gains concentrate where TCP struggles - packet loss, high latency, mobile network switching. On fast stable connections the difference may be invisible, and some networks block UDP, triggering fallback to HTTP/2. Whether caching, compression or image weight would help you more depends on your bottleneck - measure it.
How do I check if my site serves HTTP/3?
Open your browser's developer tools, watch the network panel's protocol column (often labeled h2 or h3) while loading your site, or ask your host/CDN. If your provider offers HTTP/3 and it is off, enabling it is usually a setting.
Is HTTP/2 now obsolete or unsafe to keep?
No. RFC 9113 is the current HTTP/2 specification (obsoleting the 2015 original), and HTTP/2 remains the fallback every HTTP/3 conversation depends on - including on networks that block UDP. Serving both is the normal, correct state.
What is QUIC?
A transport protocol standardized as RFC 9000, running over UDP. Per RFC 9114 it provides stream multiplexing, per-stream flow control and low-latency connection establishment, with encryption by default; HTTP/3 is the mapping of HTTP semantics onto it. Google began early QUIC work in 2012 and the IETF adopted it in 2016, per Cloudflare's history.