Platform in Platforms
Baseline support overview
Published
Baseline is a cross-browser support signal for web platform features. It covers APIs and CSS properties as well as JavaScript syntax. Consistent support in seven browser and platform combinations determines one of three tiers: widely available; newly available; limited availability. “Baseline 2026” is the yearly feature set collecting the features that reach newly available during 2026, and it stays open until the year ends.
How it works
Section titled “How it works”Baseline was started by the Chrome team and is defined by the
W3C WebDX Community Group; the data is published
as the web-features npm package from the
web-platform-dx/web-features
repository. MDN and Can I Use read this data, as do Lighthouse and DevTools.
The seven browsers whose support counts
Section titled “The seven browsers whose support counts”MDN’s Baseline glossary entry judges features against a fixed set. It includes Safari on iOS and macOS; Chrome on Android and desktop; Edge on desktop; Firefox on Android and desktop. Samsung Internet and Opera are outside this set, as are the Android WebView and the WeChat WebView. Their support does not move a feature between tiers, so a feature can be “widely available” and still fail in an embedded WebView.
The three tiers
Section titled “The three tiers”| Tier | What qualifies | MDN badge |
|---|---|---|
| Widely available | Consistent support in each of the seven browsers for at least 30 months | Green check |
| Newly available | Works in at least the latest stable release of each of the seven browsers | Blue check with the year, for example “Baseline 2022” |
| Limited availability | Missing from at least one of the seven | Grey cross |
The 30-month clock on web.dev/baseline starts on the
feature’s keystone date, which the
Baseline definition
defines as the release date of the last core browser to add support (reading
@mdn/browser-compat-data and excluding partial_implementation entries), not on the
yearly label. The high tier has a second condition: the keystone date must also precede
the latest Firefox x.0 ESR release, so a feature Firefox shipped shortly after an ESR cut
can wait past the 30 months. Ignoring that clause, a feature that reached newly available
in 2026-02 becomes widely available in 2028-08; one that crossed in 2026-11 waits until
2029-05, so two features in the same “Baseline 2026” set can graduate 9 months apart.
Yearly feature sets
Section titled “Yearly feature sets”Features are also grouped by the calendar year in which they crossed into newly available. web.dev defines Baseline 2024 as “all items that become part of Baseline Newly available in 2024”, applies the same formula to 2025, and describes 2026 as the latest feature set, still in development. Baseline 2026 is therefore not a closed list; it grows through 2026-12 as browser releases land. See By browser for the Baseline status of PWA features and support in browsers outside the Baseline set.
Examples
Section titled “Examples”Use Baseline’s published data at build time. It does not detect support at runtime.
Reading a feature’s Baseline status from web-features
Section titled “Reading a feature’s Baseline status from web-features”The web-features package exposes each feature’s status with baseline set to
one of "high", "low", or false, the dates baseline_low_date and baseline_high_date, and
a support map keyed chrome, chrome_android, edge, firefox, firefox_android,
safari, and safari_ios holding the version that most recently introduced the feature
(data.schema.json,
github.com). A build script can gate a code path on it:
import { features } from 'web-features';
const { status } = features['web-share'];if (status.baseline === 'high') { console.log(`Widely available since ${status.baseline_high_date}`);} else if (status.baseline === 'low') { console.log(`Newly available since ${status.baseline_low_date}; Firefox ${status.support.firefox ?? 'none'}`);} else { console.log('Limited availability: ship the fallback path');}The support map is where the per-browser detail lives; baseline alone does not say
which of the seven browsers is missing.
Detecting the feature itself at runtime
Section titled “Detecting the feature itself at runtime”A “widely available” status does not establish support in a user’s browser, and WebViews are outside the definition. Test for the API at runtime and keep a fallback:
async function shareOrCopy(url) { if (!('share' in navigator)) { await navigator.clipboard.writeText(url); // no share sheet: copy instead return 'copied'; } await navigator.share({ url }); return 'shared';}Baseline decides whether the fallback is worth maintaining; feature detection decides whether it runs.
Observed behaviour
Section titled “Observed behaviour”Baseline measures browser support only. MDN states that it “is not a substitute for accessibility, usability, performance, security, or other testing”, and that it may not reflect older devices and releases, browsers outside the definition such as operating system web views, or assistive technology. For a PWA, check manifest behaviour per browser and per OS, along with install prompts and WebAPK behaviour; the tier cannot establish those behaviours.
web.dev/baseline lists tools that surface Baseline status. These include the Chrome DevTools
Elements panel for CSS properties and a Lighthouse “Baseline Features” audit. ESLint CSS
rules and Browserslist queries also expose it, as does the webstatus.dev dashboard. VS Code and a Netlify
extension also display it. Each of them reads the same web-features data, so a disagreement between two
tools comes from different versions of the package; they use the same criteria.
See also
Section titled “See also”- Baseline (compatibility) (developer.mozilla.org)
- Baseline (web.dev)
- web-platform-dx/web-features (github.com)
- By browser
- By OS
- PWAs on Firefox
Specifications
| Specification | Status |
|---|---|
| None. | |