Lighthouse | Baseline Features audit adds browser compatibility data
Lighthouse is making browser compatibility easier to inspect without leaving the page audit workflow. Published on July 27, 2026, the new Baseline Features diagnostic shows the Baseline status of web platform features detected on a page, giving web designers and frontend teams a faster way to identify features that may need closer compatibility checks.
Lighthouse brings Baseline browser support directly into page audits
The Baseline Features audit is now part of the Best Practices category in Lighthouse. Instead of checking every CSS property, HTML feature, or web API separately, developers can inspect which web platform features Lighthouse detects and see their Baseline status inside the same report used for other site quality checks.
For template creators and frontend teams, this creates a useful compatibility checkpoint. Modern layouts increasingly depend on newer CSS and browser capabilities, so having interoperability information next to the audited page can make it easier to spot features that deserve additional testing before they become part of a production template or website.
The audit identifies web features and their Baseline status
The diagnostic uses data from the web-features package to identify web platform features present on the page. Each detected feature can appear with one of three Baseline states: Limited availability, Newly available, or Widely available. These categories give developers a clearer indication of how established a feature is across the core browser ecosystem.
Lighthouse also shows an occurrence of the feature in the page's source code and links its web feature ID to webstatus.dev. That combination can help developers move from a general compatibility warning to the specific implementation that needs to be reviewed.
Why this is useful for template and frontend testing
Browser compatibility often becomes more complicated when templates combine modern CSS, JavaScript components, external libraries, and third-party services. The audit can provide an additional layer of visibility by showing which detected features may already have broad interoperability and which ones still have more limited availability.
This does not replace testing a website across the browsers and devices that matter to its audience. It does, however, make Baseline information easier to include in an existing Lighthouse review, especially when evaluating a new template, redesign, component library, or frontend experiment.
Third-party scripts can also appear in the results
One detail worth watching is that the Baseline Features audit can detect features used by third-party scripts and active browser extensions, not only code written directly for the website. That gives the report a broader view of what is running on the audited page, but it also means developers should check where a detected feature actually comes from before changing their own template code.
The audit is available in the current version of Lighthouse and Chrome DevTools, so designers and developers already using Lighthouse for Best Practices, performance, accessibility, or SEO reviews can add compatibility information to the same general testing workflow.
REMEMBER: Baseline status is a useful compatibility signal, but production templates should still be tested against the browsers and devices required by the site's actual audience.{alertSuccess}
Daisuki's Take: What This Means for Web Designers
For web designers, the most useful part of this update is not another Lighthouse metric. It is having browser interoperability information closer to the point where we are already checking whether a page is ready for production.
This can be particularly valuable when experimenting with newer CSS or web platform features in reusable templates. A design may look correct in the browser used during development, while the Baseline audit gives us another signal that a specific implementation deserves broader compatibility testing.
We would treat the audit as a practical filter rather than a final compatibility verdict. Used alongside real browser testing, it can make it easier to decide which modern features are comfortable choices for a template today and which ones still need fallbacks, additional testing, or a more cautious rollout.
Sources and Recommended Links
- The Baseline Features audit is now available in Lighthouse | web.dev Official Site
- Baseline Features | Chrome for Developers Official Documentation
- Baseline | web.dev Official Site
