Download websites that use fullPage.js

About fullPage.js

Scroll behaviour is one of the few front end choices a visitor registers within a second of arriving. fullPage.js replaces ordinary scrolling with full viewport sections that snap into position, so a page built on it does not flow past the reader, it advances one screen at a time. A site carrying the library has made a deliberate presentation decision, normally taken by a designer rather than by a back end engineer, and normally for a page whose job is to impress rather than to inform.

Licensing is where that choice becomes commercially interesting. Álvaro Trigo released the library in 2013, wrote it in JavaScript, and distributes it under GPL v3 for open projects while selling a separate commercial licence to everyone else. A company running the plugin on a site that sells something is therefore either a paying customer or a candidate to become one, which is an unusual property for a front end dependency and the reason both the author and his competitors have a stake in who is running it.

As of October 2026 we detect the library on 7,543 sites. South Korea alone accounts for 6,045 of them, and the .com zone leads the domain endings. A single country holding that much of a general purpose JavaScript plugin is rarely a matter of national taste. Libraries spread through the channels that deliver them, and for scroll driven design those channels are premium templates, agency starter kits and locally written tutorials, so a market where one such channel took hold will show exactly this shape.

Version data points the same way. Across the detected installations we record 68 distinct releases, clustered around 2.9.7. A dependency on an actively maintained site narrows toward recent releases over time, so a spread this wide describes pages that were built, launched and then left untouched, each frozen at whatever release the template or the tutorial happened to ship with. Marketing microsites and portfolios behave that way by nature, because nobody revisits a launch page once the launch is over.

Detection has an honest limit worth stating. We identify the library from its signature in delivered JavaScript, so installations that pass through a build step which renames internals, or that are compiled into a single application bundle with everything else, can go unrecognised. The population we publish therefore leans toward sites that load the plugin as a recognisable file, which is the common case for template built pages and the less common case for hand engineered applications.

Checking one domain answers a question nobody really has. Knowing that a particular studio portfolio snaps between sections is trivia until it sits beside every other site doing the same thing, at which point it becomes a market: a licence compliance list for the author, a prospect list for template and theme vendors, a design trend readable by country and by domain zone, and a way for anyone selling to small studios and marketing teams to find the sites those studios actually built. The downloadable export is that whole population in one file, with the country, the zone and the rest of each site's stack attached, which is the part a per domain lookup can never assemble.