Download websites that use Gatsby

About Gatsby

The version column is where Gatsby becomes interesting. We record 836 distinct versions across the sites where the framework is detectable, with 5.16.1 at the head of the distribution. A spread of that width is not the familiar story about users who fail to upgrade.

Gatsby builds its pages ahead of time. The version stamped into a delivered site is the version installed on the machine that ran the build, frozen on the day it ran. A site rebuilt every week tracks the project closely. A site published once and left alone keeps advertising the toolchain of that afternoon for years afterwards. What the distribution measures, then, is rebuild cadence across an entire population, which is a more useful thing to know than an upgrade rate.

The framework itself is a React based static site generator written in JavaScript and released under the MIT licence, first published in 2015. Content is pulled at build time from a headless content system, an API or the file system, and turned into static HTML. Detection implies a decoupled stack: the content lives somewhere else, a build pipeline exists, and somebody on the team owns it.

Detection leans on the artefacts a build leaves behind: bundle names, a runtime manifest, the page data files fetched during client side navigation. Most builds ship those untouched, which makes a build time framework easier to recognise than a server side one, but a heavily customised pipeline or a partial export can shed them. The count is close to complete for default deployments and conservative everywhere else.

Ownership of the project matters to how the population should be read. The framework is now stewarded by Netlify, a hosting company rather than an independent foundation, which gives its direction a commercial gravity that anyone assessing platform risk should factor in. Trajectory is what matters in that assessment rather than a single count, and trajectory needs repeated snapshots of the same population taken over time.

As of September 2026 the framework is detectable on 76,249 sites. United States accounts for 46,476 of them and .com heads the suffix breakdown, a mix weighted toward marketing sites, documentation portals and agency built projects rather than toward transactional commerce.

For competing framework and platform vendors, the segment that matters is not everyone using it but everyone using it whose build has gone stale, because those teams are already paying for the choice in maintenance. Agencies selling replatforming work read the list the same way. Hosting platforms use it for displacement. A per-domain lookup hands back one version string with no context around it. The list hands back the distribution, and a distribution is the only form in which the real question can be answered.