Baseline labels a web feature as "Widely available" once it's been supported across all major browsers for roughly 30 months, or "Newly available" if it's just landed everywhere but hasn't cleared that safety window yet.
/* Baseline: Widely available (as of 2023) */
.card { container-type: inline-size; }
Why this has changed our decision process
Instead of individually checking five browser versions on caniuse for every feature we're considering, one Baseline label answers the "is this safe to ship without a fallback" question directly - a genuine time saver on every project kickoff.
It doesn't remove judgment entirely
A client with an unusually old user base - a specific enterprise audience stuck on an old browser, say - still needs a case-by-case conversation. Baseline is a strong, fast default, not a replacement for knowing your actual audience.
What "Baseline" actually tells you
Before Baseline, checking whether a CSS feature was safe to ship meant cross-referencing caniuse.com against your analytics' browser breakdown and guessing at an acceptable risk threshold - a process every developer repeated independently, often incorrectly. Baseline, run jointly by the major browser vendors, gives a single, unambiguous answer: "Newly available" means it works in the latest version of every major browser; "Widely available" means it's been that way for 30 months, long enough that most real-world traffic has update through automatically.
How we use it day to day
MDN now surfaces a Baseline badge directly on feature pages, so the check happens at the point of writing the code rather than as a separate research step. Our rule of thumb: reach for "Widely available" features without a second thought, use "Newly available" ones with a documented fallback, and treat anything with no Baseline status yet as something to prototype behind a feature flag rather than ship broadly.