Download websites that use Next.js

About Next.js

Of everything a crawler can find on a page, a rendering framework is one of the few signals that reflects a genuine architectural decision. Somebody argued about it, wrote it down, and hired against it. Next.js on a domain implies a build pipeline, a deployment step, a repository, and a person whose job includes maintaining all of them, which is why the marker works so well as a qualification filter.

Next.js is a JavaScript frameworks maintained by Vercel, distributed under the MIT license, and in public use since 2016. The framework wraps a component library with server rendering, static generation, file-based routing, and an opinionated build, so a single codebase can produce pages that behave like a brochure site and pages that behave like an application. Adoption tends to arrive alongside a wider set of choices, a design system, a headless content backend, a hosting platform built around the framework, and an analytics stack chosen by the same team.

As of September 2026 we detect the framework on 1,734,128 sites. United States accounts for 1,278,311, and .com recurs through the footprint, a distribution that tracks the product-led and venture-funded part of the web far more closely than it tracks any national market. Concentration of that kind makes the list useful as a proxy for company type rather than for geography.

The version fields deserve a warning rather than a headline. We track 34 distinct versions and record 7.0.2 more often than any other. Version visibility is not random. A release is only attributable when the deployed build leaves a fingerprint behind, in a build manifest, an asset path, or a response header, and exposing that fingerprint has been actively engineered out of newer releases and newer hosting defaults. The versions we can read therefore skew towards older and more openly configured deployments, and the modern part of the installed base is underrepresented in the version breakdown even though it is fully present in the site count. Anyone building a migration argument, a vulnerability exposure estimate, or a release adoption chart on this field should treat it as a floor for old versions rather than as a census.

For a commercial researcher the framework is a budget and headcount signal. Sites built this way have front-end engineers, a deployment pipeline, and an existing procurement path for developer tooling, which is a different sales conversation from the one you have with a site assembled in a page builder. For a technical researcher the same footprint is a compatibility map, because anything that has to live inside a page, a tag manager, a consent tool, a chat widget, an experimentation platform, behaves differently under server rendering and hydration than it does on a static page.

None of that can be assembled a domain at a time. A lookup tells you one site uses the framework. An export tells you how many sites in a country or a sector use it, which content, analytics, payment, and hosting choices travel with it, how the version spread looks across the whole group once the caveat above is applied, and which sites adopted or abandoned it between two files taken months apart. Population questions need populations, and that is the difference between a search box and a dataset.