Choosing supported browsers one version at a time is easy to get wrong. Web Platform Baseline gives you a shared way to judge whether a web feature is supported across major browsers, and Browserslist can turn a Baseline target into a project browser query.
Baseline is a starting point for a support policy, not a promise that every visitor can use every feature. Pair it with your audience's browser data, feature-specific checks, and testing of important user journeys.
What Baseline tells you
Baseline classifies web platform features, including CSS, JavaScript, and browser APIs, by availability in the core browser set: Chrome on desktop and Android, Edge, Firefox on desktop and Android, and Safari on macOS and iOS.
| Status | Meaning |
|---|---|
| Limited availability | The feature is not supported across all core browsers. |
| Newly available | The feature works in the latest stable versions of the core browsers, but older releases may not support it. |
| Widely available | The feature has been supported across the core browsers for at least 30 months. |
These are feature-level statuses. A page that uses only widely available features can still have problems caused by your code, a browser bug, an embedded webview, an older device, or assistive technology. Baseline does not assess accessibility, security, usability, or performance.
Pick a target that fits your users
Start with your real audience if you have browser analytics or real-user monitoring. Look at browser families and versions, not just a single total compatibility percentage. If your customers use managed devices, older phones, or in-app browsers, account for those separately.
If you do not have useful usage data yet, Baseline Widely available is a reasonable conservative starting point for many small websites. It is not a guarantee of support for every user. A product with a strict support commitment may need an older target; a site built for a known, up-to-date audience may choose a newer one.
You can choose a moving target or a fixed feature set:
- Moving targets, such as Widely available, evolve as browser support changes. They are useful when you want your allowed feature set to grow over time.
- Year-based targets, such as Baseline 2024, refer to a fixed feature set. They make changes easier to review consistently, but you should revisit the choice as your users and requirements change.
Use the Baseline target guide for more detail on using site analytics to compare targets.
Put the target in your Browserslist configuration
Browserslist is used by many front-end tools to describe which browser versions a project supports. You can put a Baseline query in the browserslist field in package.json:
{
"browserslist": [
"baseline widely available"
]
}
Merge the field into your existing package.json; do not replace a browser policy that other parts of your build already rely on without checking what consumes it. If you prefer a fixed target, use a query such as "baseline 2024". The web.dev Browserslist guide describes the available queries, including options for downstream browsers.
Tools that read Browserslist can use the query to select browser versions for tasks such as transforming code or checking compatibility. The query does not make all CSS, JavaScript, or browser APIs work in those browsers. Confirm that each tool in your build supports the features you care about; a target is only as useful as the checks and transformations that consume it.
Check individual features before adopting them
When a feature falls outside your chosen target, check its current status in the Baseline feature catalog and the relevant MDN compatibility data. A newly available feature may be appropriate when your users have recent browsers, but the status alone cannot tell you what percentage of your visitors can use it.
For CSS, @supports lets you provide a fallback and add styles only when a browser recognizes a capability:
.cards {
display: block;
}
@supports (display: grid) {
.cards {
display: grid;
grid-template-columns: repeat(2, minmax(0, 1fr));
}
}
The fallback should still make the content and essential actions usable. JavaScript has its own feature-detection patterns; a CSS support query does not detect JavaScript APIs. Even a positive feature check only confirms that the browser recognizes the capability, not that the whole user journey works as intended. See MDN's guides to the @supports at-rule and the CSS.supports() method.
Do not add a polyfill automatically whenever a feature is below your target. Decide what happens when the feature is missing: if it is an optional enhancement, a simpler experience may be enough; if it is essential, provide a tested fallback or reconsider using it. Polyfills can add code and may not reproduce every browser behavior, so weigh their costs against the impact on your users. The Baseline and polyfills guide explains this trade-off.
Make browser support part of your workflow
Write down the target and why you chose it. Then:
- Check important features against the target before relying on them.
- Use build or lint tools that actually consume your Browserslist setting.
- Test critical flows in browsers and devices that reflect your users, including any required webviews.
- Test keyboard and assistive-technology use separately; Baseline is not an accessibility test.
- Revisit your browser data and target when your audience or support commitments change.
Baseline can reduce repetitive compatibility research, but it does not replace testing. Use it to make a consistent starting decision, then choose fallbacks according to what your application does and who depends on it. For implementation examples, see our guides to modern CSS techniques and WebGPU for JavaScript developers; the latter also shows why checking a feature's browser support matters before making it central to an experience.