Download websites that use Materialize CSS

About Materialize CSS

Front end frameworks age in public. Pages built with them do not get rebuilt when the project behind them slows down, so a framework's footprint keeps recording a moment long after the moment has passed. Materialize CSS is a clear case.

The library appeared in 2014 as a community implementation of Google's design language, written in JavaScript and released under MIT by a group of university students rather than by a company. No vendor is listed for it in this dataset, which is accurate rather than a gap. There is no commercial entity behind the project, no support offering and no roadmap to buy into. The components are the familiar set of grids, modals, carousels, form fields and navigation, with the interactive side built on the helper library that framework code assumed at the time.

Version data tells the rest of the story. We record 96 distinct version strings, with readings clustering hard on 1.0.0. A distribution that collapses onto one release is what a codebase that stopped moving looks like from the outside. Nobody upgrades because there is nothing to upgrade to, and the sites carrying the library are frozen at whatever their build step captured.

There is a practical consequence for anyone who has to work on those sites. A frozen framework version pins the surrounding code with it, because the components expect a helper library of a particular vintage and the styles assume a browser landscape that has since moved on. Rebuilding such a page means replacing the layer rather than upgrading it, which changes both the size of a quote and the argument that comes with it. Buyers of this cut usually want the scale of that problem before deciding whether a service line is worth building around it.

For a researcher the framework is therefore best read as a date stamp on a website rather than as a technical choice worth arguing about. A page carrying it was most likely put together in a particular window by a developer who wanted a specific look without pulling in the vendor's own toolkit, and it has not been rebuilt since. Agencies selling rebuilds, security and dependency researchers cataloguing unmaintained front end code, and design tool vendors sizing a migration audience all want that same population for different reasons.

As of October 2026 the library is detected on 8,690 sites, 3,505 of them in United States, with domain volume concentrated in .com. The figure depends on the library staying recognisable in the page, as a delivery network link, a named file or a version comment, so copies compiled into an application bundle or renamed by a build step do not register and real usage sits above the count. Class names on their own are not proof either, because markup often survives a migration to something else entirely. The download is a way to ask how much of the web is still standing on a paused framework, which is a question about a population and cannot be answered one domain at a time.