Browser Forecast: The Next Two Years, Measured Against 2021

Archi4 min read

browserssecurityregulation

Contents
  1. The next browser fight is over the address bar
  2. What the 2021 baseline actually assumed
  3. Extensions became the dividing line nobody campaigns on
  4. Passkeys put identity in the browser's hands
  5. Regulation sets the pace, Europe sets the calendar
  6. Three engines, one serious challenger
  7. What to watch through 2028

The next browser fight is over the address bar#

In 2021 the browser question was speed: which engine painted a page first. In 2026 it is control of what sits between you and the page, meaning the extension that filters your traffic, the passkey that proves who you are, and the choice screen you tapped once and forgot. Forecast the next two years by those three things and the picture gets clearer than any benchmark chart.

What the 2021 baseline actually assumed#

Five years ago Chrome ran about 65% of the market by most counts, Safari sat near 18%, and Firefox was already below 4% and falling. Extension developers wrote for Chrome and patched for the rest. Apple's rule that every iOS browser had to use WebKit was treated as permanent weather. Passkeys did not exist as a shipping product; the FIDO Alliance had published the shape of them, and Apple, Google and Microsoft announced support together in May 2022.

The Privacy Sandbox carried a published deadline for killing third-party cookies. Manifest V3 existed as documentation and a warning. The EU's Digital Markets Act was a proposal. Baseline, the effort to agree on which web features work everywhere, had not started.

Every one of those assumptions has since moved.

Extensions became the dividing line nobody campaigns on#

Chrome finished turning off Manifest V2 extensions in 2025. Content blockers now run through declarative rules rather than full access to page requests, with rule sets capped in the tens of thousands. Firefox still runs both formats. Safari sells content blocking as a separate app category.

The practical result is a two-tier extension market. The same ad blocker behaves differently depending on which browser you installed, and not because of the blocker's code. Expect that gap to widen through 2028: extension APIs will drift further apart, and enterprise security teams will start listing approved browsers by which extensions they allow rather than by rendering speed.

Passkeys put identity in the browser's hands#

Passkey support arrived across the major browsers in 2022 and 2023. By now a large share of consumer logins offer them, and the browser is the thing that brokers the exchange. That is a new job for software that spent two decades as a document viewer.

The next fight is export. A passkey stored in one browser's credential manager does not travel well, and switching browsers still means re-enrolling on dozens of sites. Regulators have not treated credential portability as a competition issue yet. They will. Watch for pressure on the major vendors to support a standard export format, likely framed as consumer protection rather than antitrust.

Regulation sets the pace, Europe sets the calendar#

Apple opened iOS to alternative browser engines in the EU in March 2024 to satisfy the Digital Markets Act. Choice screens became mandatory in the same period. Similar rules are moving in Japan and the UK on comparable timelines.

The forecast is not that every country copies the DMA word for word. It is that the compliance work gets done once and exported. A browser vendor that builds an engine-choice flow for Europe has already built most of what Japan or Brazil would ask for. That makes the rollout faster outside Europe than the DMA's own four-year drafting process suggests.

Three engines, one serious challenger#

Chromium, WebKit and Gecko still carry essentially the whole web. The interesting movement is below them. Ladybird is working toward a first alpha built on its own engine. Servo, the parallel rendering project Mozilla spun out in 2020, keeps attracting embedders who want a browser engine as a component.

Neither will take consumer share in the next two years. What they can do is keep the standards conversation honest. Baseline, started in 2023, has already made browser-support tables a normal part of feature planning. Five years ago a team shipped a Chrome-only feature and shrugged.

What to watch through 2028#

, Extension API negotiations. If Firefox drops Manifest V2 support to cut maintenance, the two-tier market becomes a three-tier one., Passkey export. A working interchange format would be the first real limit on browser lock-in since bookmarks sync., Choice screens. Their design, not their existence, decides whether they move share., AI sidebars and where the requests go. Every major browser now ships a panel that sends page content to a model. Disclosure rules for that traffic are the most likely new regulation of the decade., Mobile memory budgets. A browser using 900 MB on a mid-range phone loses users faster than one that renders a frame slower., Extension review times. Store approval queues of a week push small developers toward browsers with one-day reviews.

The throughline from 2021 to now is that browsers stopped competing on the page and started competing on everything around it. The next two years will be spent arguing over who owns that surrounding layer, and the answer will be settled in rulebooks, not benchmark suites.

More articles