Running a Gatsby site?

Gatsby build stuck or slow as treacle? We unstick it.

Gatsby was the right call in 2019 and the ecosystem has moved on. Teams still running it tell us the same story: builds that take forty minutes, plugins that have not seen a release in two years, and a GraphQL layer nobody fully understands. We unblock the build, or we move the site to something that is still getting shipped.

  • Since 2015Fixing technology
  • FreeEstimates
  • US teamReal engineers

gatsby-build.log

still broken

What it is

Gatsby at a glance

Gatsby is a React based static site generator and front end framework that popularised using GraphQL as a data layer in front of Markdown, a CMS or almost anything else with an API. It was founded in 2015, hit version 1 in 2017, and dominated the Jamstack conversation through 2019 and 2020.

Netlify acquired Gatsby Inc. in 2023, and most new work in the ecosystem now points toward Next.js or Astro. Gatsby itself is still released and still supported, but the plugin network that used to be its strength has thinned out, which is why most of our Gatsby work is a choice between fixing the current site or moving it to something with a wider community.

Type
React static site generator with a GraphQL data layer
First released
2015, version 1.0 in 2017
License
MIT, open source
Maintained by
Gatsby team, now part of Netlify
Typically used for
Marketing sites, blogs, documentation, content heavy React sites

The honest version

Gatsby pros and cons

No technology is all upside. This is where Gatsby earns its place and where it tends to cause trouble.

Where Gatsby is strong

  • Fast pages when the build finishesThe output is mostly static HTML with hydrated React, which loads quickly even on slow connections and ranks well without extra tuning.
  • GraphQL as a unified data layerMarkdown, Contentful, WordPress or a custom API all get queried the same way from your page components, which keeps the data code readable.
  • Strong image pipelinegatsby-plugin-image produces responsive, lazy loaded, properly sized images with blurred placeholders, which is still a hassle to set up from scratch in other stacks.
  • Big library of startersMany blog, docs and marketing starters exist, which shortens the distance from empty repo to a working site.
  • Works well with headless CMSesSource plugins for Contentful, Sanity, WordPress and others handle the ingestion, so editors keep their familiar back end.
  • Deploys to any static hostThe output is plain files, which means Netlify, Vercel, Cloudflare Pages or your own S3 bucket all work without lock in to a specific runtime.

Where Gatsby bites

  • Build times get painful at scaleA content site with a few thousand pages and a handful of large images regularly pushes builds past twenty minutes, and incremental builds do not always catch every change.
  • The plugin ecosystem has stalledMany popular plugins have not had a release in over a year. Some fail outright on modern Node versions and the only maintained fork is a GitHub comment thread.
  • GraphQL adds a layer of indirectionEvery piece of data has to be sourced, transformed and queried through the schema, which is elegant until something fails and the error points at a generated type rather than your code.
  • Hiring is getting harderNew React developers learn Next.js or Remix. Finding someone who can confidently debug a Gatsby build and its schema is a smaller pool each year.
  • Upgrades between major versions are not cheapGatsby 2 to 3 to 4 to 5 each involved plugin breakage and node API changes that cost real engineering time per site.
  • The future is uncertainDevelopment continues under Netlify, but roadmap momentum sits with other frameworks. Betting new projects on Gatsby in 2026 is a harder case to make.

Sound familiar?

Common Gatsby problems we fix

The Gatsby problems that bring people to us, and what you have once each one is fixed.

JavaScript heap out of memory

The production build runs out of memory

A large image set, a plugin that holds everything in memory, or a GraphQL query that pulls far more nodes than it needs. We raise the right limits, swap the offending plugin and trim the query.

Build completes within its budget

GraphQL Error: Cannot query field

Schema errors after a content change

A new content type, a missing frontmatter field on one post, or a source plugin that inferred a type nobody expected. The build now refuses to start.

Schema stable across content

Plugin is not compatible with your gatsby version

Plugins broke after a Gatsby upgrade

A minor version bump brought in a peer dependency change and half the plugin list stopped loading, usually because their own releases predate the new API.

Plugins updated or replaced cleanly

Build failed: Exit status 137

CI keeps killing the build

A container with four gigabytes of memory is being asked to do a build that genuinely needs eight, and the only clue in the log is an unceremonious exit.

Build sized to the actual workload

deprecated: createPage without ownerNodeId

Deprecation warnings everywhere after upgrade

Custom gatsby-node code using the older createPage signature, fine on the old version, now logging thousands of warnings and failing on the next major.

Node API calls brought up to date

last commit: 18 months ago

The site is on an abandoned stack

A previous agency built the site, left, and nothing has been updated since. Plugins are stale, Node is pinned to an old version, and the team wants to know whether to patch or replace it.

Clear plan with costs for both paths

4 minute incremental build

Preview deploys take forever

Every pull request builds the whole site again because incremental builds are not configured or the plugins in use defeat them. Editors stop reviewing content as a result.

Preview turnaround back to minutes

no path forward

Migration to Next.js or Astro

The team has decided Gatsby is no longer the right tool but the content, redirects, SEO and CMS wiring all need to come across without a traffic dip.

Live on the new stack, traffic held

What we do

Gatsby help, from fix to migration

Fix the Gatsby site you have, or plan a clean exit from it. Either path, we run it.

Build rescue
Builds that fail, time out or silently produce the wrong output. We trace the specific plugin, query or image step that is causing it.
Upgrades
Moving from Gatsby 2 or 3 onto a current version, with plugin replacements where the originals are abandoned.
Performance and bill
Build time cut, image pipeline tightened, and CDN usage brought in line so your hosting cost stops climbing on every content change.
Content model cleanup
GraphQL schema flattened, source plugins consolidated and the CMS wiring made predictable so editors stop breaking the build.
Migration off Gatsby
A measured move to Next.js or Astro, with content, redirects and SEO preserved, so your rankings and your editors both survive the transition.
Managed Tech
Dependency watch, Node version upgrades, broken plugin alerts and a human on call when something in the build pipeline changes.

How it works

From first message to fixed

  1. Look Free estimate

    Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.

  2. Fix

    We fix the cause, not the symptom. If something is down, getting it back up comes first.

  3. Harden

    Backups, monitoring, updates and access, so the same problem can't quietly come back.

  4. Hand back or stay on

    You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.

Often found together

Running Gatsby alongside something else?

We work on the whole stack, so the problem can be wherever it actually is.

Questions

Gatsby questions

Something else? Call+1 737 727 7327

Should we stay on Gatsby or move off?

It depends on how much custom code sits on top of it. A content site with a handful of pages and a working CMS is cheaper to keep patched than to rewrite. A larger site with thirty plugins, half of them unmaintained, usually comes out ahead on a measured move to Next.js or Astro. We will tell you plainly which bucket your site is in.

Why is our Gatsby build so slow?

Three culprits do most of the damage. Gatsby image processing on a large library, a source plugin pulling the whole CMS on every build, and a GraphQL query that fetches far more than the page actually renders. We measure where the time is going and cut the ones that will not pay back.

Can you fix GraphQL schema errors in gatsby-node?

Yes. Most of these come from inferred types changing when a content field goes missing or a new type appears. We pin the schema explicitly where it matters, add the fields the inference misses, and keep the generated types in the repo so the next change does not surprise you.

How do we migrate from Gatsby to Next.js without losing SEO?

We map every current URL to its equivalent on the new stack, set up permanent redirects for anything that has to move, bring metadata, structured data and sitemaps across, and watch the search console for drops in the first few weeks after the switch. Content, redirects and rendering are the three places this usually goes wrong, and all three are planned up front.

Our plugins are unmaintained. What do we do?

For each one we check whether a maintained fork exists, whether the functionality can be moved into a small piece of local code, or whether the plugin was carrying more than the site actually needs. Most sites end up with a shorter plugin list and less surface area for the next upgrade.

How much does Gatsby help cost?

Free estimates. Tell us what the site is doing, send a recent build log if you have one, and we come back with a price before any work starts.

Free estimate

Gatsby giving you trouble?

Tell us what you're running and what's going wrong. A person reads it and comes back with an estimate.

  • No charge to find out what it will take
  • If it's urgent, say so

Replies come from a person. By sending, you authorize us to email you back. No marketing.