Download websites that use Redux

About Redux

Finding a state container on a public web page is not straightforward, and that is the first thing worth saying about this tag. Redux lives inside an application bundle, compiled and minified along with everything else, and by the time a browser loads the page there is often nothing left that names it. Where we do record it, the site has left a readable trace: an unminified build, a source map, a development hook, or a vendor chunk that kept its identity. As of October 2026 we detect it on 2,498 sites, and the honest reading of that figure is that it counts the sites where the library was visible, not the sites that use it.

What the tag means where we do see it is worth more than the count. A site running a central state store is not a brochure with a contact form. Application state that needs a single store, reducers and a predictable update flow implies a real interface behind the page: a dashboard, a configurator, a booking flow, a multi step account area, a product with logged in users. Released in 2015 under the MIT licence, the library arrived with the first large wave of single page applications and became the default answer for teams building something big enough to lose track of its own state.

Version evidence adds a second dimension. Across installs where a version string survives the build we can read 11 distinct strings, and 4.1.1 recurs more often than any other. A tail that long on a library with a small and stable public interface says more about how front ends age than about the library itself. Teams upgrade a bundle when they are already inside the build for another reason, not on a schedule, so the version string works as a rough proxy for when a front end was last seriously worked on.

For a researcher, all of that makes the list a filter for engineering maturity rather than a technology census. Developer tool vendors, component and design system sellers, error tracking and performance monitoring products, and recruiters mapping which companies genuinely build in house are all after the same population: sites with a real front end team behind them, as opposed to sites assembled from a template. Checking a single domain for a state library is a browser console away and answers nothing. Building the set, cutting it by domain suffix, by co-detected framework or by version age, and then diffing it against an earlier snapshot to see who rebuilt their front end is only possible with the whole population in a file, which is what our export is.