The WebDX Community Group started work in 2022 to make it easier for developers to track the list of features that are widely available and those that are under development.

Since then, the Community Group has been busy developing the open-source web-features project, a shared catalog of features of the web platform, and the Baseline status to give developers clear information about which of these features work across a core browser set. Baseline badges have now been integrated in Can I Use, MDN, RUM Archive Insights, RUMvision and others. Watch the Baseline web features for the win video (September 2024) for a quick dive into the web-features project.

Today, we are happy to announce that the WebDX Community Group has reached a new milestone: most keys defined in the @mdn/browser-compat-data project (BCD), which powers support tables in MDN pages and contains the most complete set of fine-grained features defined in web specifications, have been mapped to 1000+ higher-level features in the web-features project. This provides a first nearly complete catalog of web features, along with their Baseline status. The catalog is available through the web-features package in the npm registry.

This effort would not have been possible without significant contributions from, and collaboration with, organizations such as Open Web Docs, MDN, browser vendors, and many others! Many thanks to them and to organizations that provided support in the background so that group participants could do the work.

Plotting browser support data in the catalog shows the evolution of the web platform in terms of number of features and Baseline status within browsers from the first release of Safari in June 2003 (95 features) to the end of February 2025 (1006 features), and the relative split between features that are implemented somewhere (328 as of February 2025), Baseline Newly Available (150 as of February 2025), and Baseline Widely Available (528 as of February 2025). Please keep in mind that the support data only covers browsers of the core browser set (Chrome, Edge, Firefox, Safari) and that the notion of Baseline only becomes meaningful once all these browsers have shipped a first version (after July 2015 for the Baseline Newly Available status, after January 2018 for the Baseline Widely Available status).

The list of features will of course keep growing as new features get discussed, standardized and implemented across web browsers. The group also expects to refine existing mappings, to further improve tooling (including the <baseline-status> web component to display the Baseline status of a web feature), and to work with browser vendors, maintainers of libraries, documentation and services to integrate web-features where it matters for web developers.

If you want to learn more about the project and provide feedback, you are welcome to attend the breakout session about web-features that Patrick Brosset, co-chair of the WebDX Community Group, will lead during Breakouts Day 2025 on 26 March 2025 (time still to be defined).

If you want to contribute and improve the developer experience of the web platform, please join the WebDX Community Group or bring your input to the web-platform-dx/web-features GitHub repository.