Cloudflare, Google Chrome, and Mozilla Firefox add support for HTTP/3, the next major version of the HTTP protocol
Context & Ripple Effects
This is the second time Cloudflare has front-run the web's protocol upgrades: in 2015 it pushed its HTTP/2 rollout to all users to force wider adoption, and in 2016 it made TLS 1.3 and opportunistic encryption defaults across its network. Now it is repeating the CDN-first playbook alongside both major browsers.
The browser side follows an established sequence too — Chrome abandoned SPDY for HTTP/2 back when Google Chrome ditched SPDY, and Chrome and Firefox shipped TLS 1.3 support together in 2018. A CDN plus two browsers deploying at once means the new protocol gets real-world reach from day one, not a standards-paper existence.
First-order effects
- Sites served through Cloudflare can immediately negotiate HTTP/3 with visitors running current Chrome or Firefox builds, making the performance gains live for a large share of web traffic without origin-server changes.
Second-order effects
- Competing CDNs and hosting providers face pressure to add equivalent support or cede a measurable speed advantage, while site owners on other platforms must push their infrastructure vendors to keep pace.
Third-order effects
- If this deployment pattern holds — a single CDN plus two browsers moving first, standards bodies ratifying after — the interval between major HTTP revisions keeps compressing relative to the sixteen years that separated HTTP/1.1 and HTTP/2, and web performance becomes an arms race decided at the edge.
The trend: Web protocol adoption is shifting from slow committee-led rollouts to rapid co-deployment by CDNs and browsers, with Cloudflare repeatedly positioning itself as the forcing function.