Baseline Features Audit in Lighthouse
New diagnostic audit in Lighthouse reports Baseline status of web platform features used on a page.
The Baseline Features audit is now available in Lighthouse.
Editorial position: The Baseline Features audit provides factual status reporting without immediate migration pressure.
What is landing
The Baseline Features audit is now part of Lighthouse’s Best Practices category. It reports the Baseline status of web platform features detected on a page using the web-features package. This diagnostic tool helps developers understand which web features are broadly supported. The audit identifies whether each feature on a page is classified as "Baseline" — meaning it is widely supported across browsers — or not. This information is presented in the Lighthouse report, giving developers a clear view of the compatibility landscape for their current page implementations.
How the platform behavior changes
No changes to browser behavior occur. The audit analyzes the page’s use of web features and categorizes each as Baseline or not. This information appears in Lighthouse reports, offering transparency without altering how features function. The audit works by parsing the page’s JavaScript, CSS, and HTML to detect the use of specific web APIs, CSS properties, and other platform features. It then cross-references these detections with the Baseline list maintained in the web-features package. The result is a list of features used on the page, each marked according to its Baseline status.
Compatibility and migration
The audit itself imposes no compatibility requirements. However, it reflects the current state of web feature support as defined by the Baseline list. In practice: Developers can use this data to prioritize features with broader support, though the audit does not prescribe migration paths. Because the audit is purely diagnostic, it does not enforce any changes or require updates to existing code. Teams can run the audit periodically to track how their feature usage aligns with broader support over time. There is no indication in the source that the audit will evolve to enforce standards or that it will change how browsers handle non-Baseline features.
Implementation notes
The audit integrates with existing Lighthouse workflows. No new configuration is required beyond using the current Lighthouse version. It relies on the web-features package, which must be available in the development environment. Developers can run the audit as part of their normal Lighthouse scans, either through Chrome DevTools or via the Node.js CLI. No additional setup or configuration is needed to enable the audit; it is included automatically in the Best Practices section of the report. The only requirement is that the version of Lighthouse being used supports the audit — which, according to the source, is the current version at the time of publication.
Performance and operations
The audit runs as part of standard Lighthouse scans, with no reported performance impact. Operational workflows remain unchanged; teams can incorporate the audit into existing performance monitoring without additional overhead. The audit executes during the standard Lighthouse page load and analysis process. It does not require extra network requests, significant computational resources, or additional page interactions beyond what Lighthouse normally performs. As a result, teams can run it alongside other audits without expecting a noticeable slowdown in their workflows. There is no evidence in the source to suggest that the audit introduces new performance considerations or operational complexities.
Security considerations
No specific security implications are documented. The audit focuses on feature compatibility status and does not interact with security protocols or data handling. The audit does not access sensitive data, modify page behavior, or communicate with external services beyond Lighthouse’s normal operations. It operates entirely on the contents of the page being audited and the locally available web-features package. Watch out: While the audit itself is neutral from a security perspective, teams should ensure that their Lighthouse scans are run in secure environments, particularly when auditing pages that contain sensitive information. As with any development tool, care should be taken to avoid exposing audit results or scan data in insecure contexts.
Reasons to wait
Teams should evaluate whether the audit aligns with current priorities. Watch out: The audit reports status only and does not guide feature adoption or deprecation. It may not provide actionable insights for projects not focused on Baseline compliance. The audit does not include recommendations, migration pathways, or guidance on how to address non-Baseline features. It is strictly a reporting tool. For projects that are not actively tracking Baseline support or that are focused on experimental features, the audit may not offer immediate value. Teams should also consider that the Baseline list itself can evolve, so the audit’s output may change over time as new features become widely supported.
Who should act
Developers and QA teams interested in web platform support can benefit from the audit. It is particularly useful for projects targeting broad compatibility or assessing feature usage against Baseline standards. The audit is most relevant for teams that need to understand how their current implementations align with widely supported web features. It can help in planning future updates, identifying potential compatibility risks, and making informed decisions about feature adoption. Teams that regularly conduct performance or compatibility audits as part of their development process will find the Baseline Features audit a straightforward addition to their toolkit.
Bottom line
The Baseline Features audit offers a clear, factual view of web feature support in current pages. It integrates seamlessly into Lighthouse without requiring changes to existing tools or processes. The audit provides a diagnostic snapshot, but it does not enforce standards, recommend updates, or alter browser behavior. Teams can use it to gain insight into how their feature usage aligns with broader compatibility, but they should not expect it to drive migration or dictate technical direction.