Gatsby pioneered the React static-site pattern and still runs capably on the sites already built with it. Momentum is gone: Netlify acquired it in 2023, the core team dispersed, and releases slowed to occasional patches. Next.js and Astro have taken the mindshare and the hiring market. Keep an existing Gatsby site if it works, but start new projects elsewhere. A framework without active development is a liability when you need to scale or track React's evolution.
- Mature React SSG with a large body of existing production sites
- GraphQL data layer unifies CMS, Markdown, and API sources
- Image pipeline and route-based code splitting built in
- MIT-licensed and self-hostable as plain static output
- Effectively in maintenance mode since the 2023 Netlify acquisition
- Release cadence slowed sharply, core team largely dispersed
- Plugin ecosystem has many long-unmaintained packages
- GraphQL data layer is a real learning curve for newcomers
- Build times historically lag Next.js and Astro at scale
Gatsby is a React-based static-site generator that introduced a GraphQL data layer for pulling content from any CMS, Markdown file, or API into one queryable graph. It defined the React SSG category in the late 2010s. Today it sits in maintenance mode, kept current enough to run but no longer actively evolving.
Where it fits
Gatsby targets React developers building content-driven sites: marketing pages, blogs, documentation, and portfolios that source data from headless CMSes like Contentful or WordPress. Its signature move is the GraphQL data layer, which normalizes every source into a single graph that pages query at build time. Combined with route-based code splitting and a built-in image pipeline, that produced fast static output from heterogeneous data.
That niche is now contested ground. Next.js absorbed the static-and-dynamic React workload, and Astro claimed the content-site lane with less ceremony and zero required client JavaScript. Both have taken the mindshare Gatsby once held. The framework fits best where it already lives: existing Gatsby sites that work and do not justify a migration.
Cost to adopt
Gatsby is free and MIT-licensed, and its static output self-hosts on any CDN. The real cost is not money. The GraphQL data layer is a genuine learning curve: contributors fluent in React still have to learn Gatsby’s source plugins, the schema customization API, and the build-time query model. Build performance historically lagged competitors on large sites, which spawned incremental-build features that themselves added complexity.
The larger cost is risk. Since the 2023 Netlify acquisition, releases slowed to occasional patches and much of the plugin ecosystem went unmaintained. Adopting Gatsby for a new project means betting on a framework whose development has effectively stalled.
How it compares
Next.js, the default React framework for both static and dynamic sites, with an active team at Vercel and the deepest hiring market. The clear recommendation for new React projects that once would have chosen Gatsby.
Astro, the content-site successor to Gatsby’s niche, shipping zero client JavaScript by default and supporting React islands. Lighter ceremony than Gatsby’s GraphQL layer for the same blog-and-docs workload.
SvelteKit, a full-stack framework outside the React family with smaller bundles and an actively developed core. Pick when leaving React is on the table and bundle size matters.
What changed recently
Little has shipped. Netlify acquired Gatsby in February 2023, and within months most of the core team had departed, slowing the release cadence to occasional maintenance patches. The most recent meaningful update was gatsby@5.16.0 on January 26, 2025, which added React 19 and Node.js 24 support across the team-maintained packages, followed by a single patch (5.16.1) on February 10, 2025. Version 5 remains the only line in long-term support, and no new feature roadmap has been published since the acquisition.
Sources
- Gatsby releases, github.com, latest 5.16.1 on 2025-02-10
- Gatsby version support, gatsbyjs.com, accessed 2026-06-05
- Is Gatsby.js Still Worth Using in 2026?, robinwieruch.de, 2026
- Is Gatsby.js dead and is this the end for them?, ikius.com