Download websites that use scrollreveal

About scrollreveal

Before browsers could tell a script that an element had entered the viewport, working it out meant listening to every scroll event and measuring positions by hand. scrollreveal did that measuring for a generation of landing pages, and it is decoration rather than plumbing, which is frequently the more revealing signal. The library watches elements as they cross into the viewport and applies a transition when they arrive, so headings rise, cards fade in and a long page unfolds in stages instead of arriving all at once. Nothing about a working site requires the behaviour. Someone chose it, and the choice was made by a person thinking about how a page should feel.

Choosing it also says roughly when in the build the decision happened. Scroll animation gets added late, usually by whoever assembled the landing page rather than by whoever configured the server, and the library is small enough to drop into a theme with a single script tag and no build tooling. Hits therefore cluster on brochure sites, agency portfolios, product launch pages and commercial templates. In the template case the choice belongs to the theme author and propagates to every buyer who never touched the header, so a researcher reading each hit as an independent decision by a site owner will sometimes be reading one author's decision repeated across a marketplace.

As of September 2026 we record scrollreveal on 116,712 sites, 30,124 of them in United States, with the domain mix leaning heavily toward .com. A distribution like that fits a library that spread through design blogs, theme marketplaces and English language tutorials rather than through corporate procurement. The library first appeared in 2014, is written in JavaScript and is distributed under GPL v3, which is worth checking before it goes into client work.

Detection has a floor, and the floor matters here more than it would for server software. The library is often concatenated into a theme's minified bundle, wrapped by a page builder, or swapped for a few lines built on the browser's own intersection observer. A copy that survives bundling without a recognisable signature is not counted, and a site that replaced the library with native code looks to a scanner exactly like a site that never animated anything. Treat the figure as sites where the library is identifiable rather than as every site that ships it.

Checking a single domain tells you whether one page animates on scroll, which is seldom a question worth asking. The list answers the inverted version. Which studios build on the same front end stack, which theme families carry the library forward, which market segments still load a dedicated animation script instead of relying on the browser, and how that population changes as native alternatives mature. For a design tool vendor looking for users, an agency mapping its competitors, or an engineer auditing front end weight across a portfolio of acquired sites, the value sits in the shape of the whole set rather than in any single row.