StatCounter — browser market share (worldwide)
The share figures this spoke's engine-diversity argument leans on. StatCounter Global Stats measures browser usage from page views on the sites carrying its tracking code.
Worldwide, July 2026:
| Browser | Share |
|---|---|
| Chrome | 68.22% |
| Safari | 16.47% |
| Edge | 5.37% |
| [[firefox | Firefox]] |
| Samsung Internet | 2.06% |
| [[opera | Opera]] |
Tier: T3. These are first-party numbers from the measurement vendor, which is why they are worth holding, but the page carries no methodology statement — no panel description, no weighting, no note on how bot traffic is excluded. Treat the ordering as solid and the decimals as approximate. A known bias of the method: it counts page views, not people, so a browser used heavily by a few looks larger than a browser opened rarely by many.
A second panel, 2026-08-20. dap-browser-share measures a different thing on a different population — users rather than pageviews, US federal websites rather than the sites carrying a tracking tag — and publishes the query behind it, which is precisely what this page complains is missing here. Where they can be compared at all the ordering agrees; the levels do not, and should not be differenced.
Brave finally has a row (2026-10-11). review42-browser-usage-statistics reports that StatCounter only recently began breaking Brave out from Chrome, where its traffic was folded for years because Brave presents a Chrome user-agent by design. The new figure — 0.84% global, 2.05% US — is the first page-view-based measurement of Brave anywhere in this spoke, as against installer-count channels (brave's Homebrew/Play/Flathub numbers). The source calls it a floor: the disguise did not fully disappear with the breakout.
What the numbers do to the spoke's arguments
Three of the top four rows are Chromium (Gecko holds one, WebKit the other). Chrome plus Edge plus Opera plus Samsung Internet is roughly 77% of measured browsing on one engine, and every AI browser this spoke tracks except zen is another Chromium fork. The alternatives argument is therefore not about which engine wins — it is about whether anything outside Chromium stays viable enough to keep the web platform from being defined by one implementation.