Browser support matrix
Which browsers real traffic uses, and how much support each one gets. Measured from Datadog RUM over the 30 days to 29 September 2026, counting user sessions across all AEM applications.
Browsers are banded by share of sessions:
| Band | Share of sessions | What it means |
|---|---|---|
| Priority 1 | 5% or more | Full support. Must render and behave correctly. |
| Priority 2 | 1–5% | Graceful degradation. May lose polish, must stay usable. |
| Priority 3 | Under 1%, within top 90% | Best effort. No guarantees, no dedicated fixes. |
Priority 1
Section titled “Priority 1”Together 44.75% of sessions.
| Browser | Version | Share |
|---|---|---|
| Mobile Safari | 26 | 12.00% |
| Chrome Mobile | 152 | 11.24% |
| Chrome | 152 | 8.00% |
| Chrome Mobile | 153 | 7.65% |
| Chrome | 153 | 5.86% |
Priority 2
Section titled “Priority 2”Together 26.84% of sessions.
| Browser | Version | Share |
|---|---|---|
| Samsung Internet | 30 | 3.47% |
| Chrome Mobile | 151 | 3.05% |
| Safari | 26 | 2.32% |
| 576 | 2.20% | |
| Chrome | 151 | 2.19% |
| Edge | 153 | 2.11% |
| Edge | 152 | 2.04% |
| Chrome Mobile iOS | 153 | 1.65% |
| Chrome Mobile iOS | 152 | 1.55% |
| 578 | 1.52% | |
| 577 | 1.44% | |
| Chrome | 150 | 1.17% |
| Mobile Safari | 18 | 1.11% |
| Mobile Safari | 27 | 1.02% |
Priority 3
Section titled “Priority 3”66 entries, together 18.45% of sessions, none above 1%.
Most of the band is not distinct engines. In-app browsers — Facebook, Instagram, Google, Snapchat — report their own app version, not the Chromium or WebKit build underneath, so one engine appears as several rows. One entry, meta-webindexer, is a crawler rather than a user.
What the band does show is how far back real traffic still reaches. The oldest version of each engine still present:
| Engine | Oldest version in the tail |
|---|---|
| Chrome (desktop) | 109 |
| Chrome Mobile | 138 |
| Safari | 16 |
| Mobile Safari | 16 |
| Firefox | 154 |
| Edge | 150 |
| Samsung Internet | 29 |
No Safari or Mobile Safari below 16 appears anywhere in the top 90%.
Using the matrix
Section titled “Using the matrix”Don’t transcribe these versions into your build config. @tmedxp/browserslist-config already encodes the matrix as a browserslist target list — wire it into @babel/preset-env or postcss-preset-env and your output is compiled and prefixed to match.
Refreshing this page
Section titled “Refreshing this page”The numbers come from the AEM Applications RUM Overview dashboard in Datadog, which holds the live Browser Matrix widgets. Re-running the measurement and rewriting this page is the update-browser-matrix skill.