Download websites that use Flickity

About Flickity

A carousel is a design decision before it is a technical one, and which carousel a site uses says something about how the site was built. Flickity is a JavaScript library from Metafizzy, available under a MIT licence since 2015, aimed at touch friendly sliders with physics based motion and snap points. Nothing about it arrives automatically. Somebody chose the library, wired it into a template and configured the options, which means a site carrying it was hand built or built by a studio rather than assembled in a hosted site builder that ships its own slider.

The population that follows from that is specific. As of September 2026 we detect the library on 60,021 sites, with 20,377 of them registered in United States and the address space weighted towards .com. Front end libraries of this kind cluster in e-commerce, publishing and portfolio work, where a product row or an image gallery is effectively the page. The buyer is a developer or an agency rather than a marketing department, and the commercially relevant consequence is that whoever picked the slider also picked the framework, the build tooling and the hosting.

Release data is unusually informative for a library that ships as a static file. We record 38 distinct releases across the detected sites, with the bulk sitting on 2. A pinned major line that never moves is normal for front end dependencies dropped in by hand, because nothing prompts an upgrade and upgrading risks breaking a layout that already works. Anyone reasoning about how quickly a JavaScript ecosystem migrates should read the spread in the field rather than the release notes.

Detection comes from the script a page loads and from the class names the library writes into the markup, so it is inferential in both directions. A minified application bundle that folds the library in can hide it completely, and those sites will be absent from our count. A page can also keep shipping the file long after the carousel was removed from the design. Errors run both ways and neither is large at population scale, but a list built this way describes observable evidence rather than intent, and a single domain deserves a check before anyone acts on it.

Looking up one domain answers whether that site uses the library. The downloadable list answers the question this category actually raises: which sites, in which markets, were built by people who make their own front end choices. Maintainers use it to see whether a breaking change would strand a real population. Component and template vendors use it to find sites already committed to hand rolled interaction code rather than to a builder's presets. Agencies use it as a way of finding other agencies' work, since a studio tends to reuse the same slider across every client site it ships, and one recognised library often unravels an entire portfolio.