What should I do with my Gatsby Js website in 2025?

The Golden Age of Gatsby

Gatsby.js had its heyday, particularly around 2019. With its ability to generate fast and optimized static websites, it quickly became a popular choice for developers looking to combine performance and modernity.

Thanks to its integration with GraphQL and an active community constantly creating plugins and resources, Gatsby.js seemed almost indispensable. But starting in 2021, its shine began to fade, as developers gradually turned to more dynamic solutions like Next.js or Astro.

No sign of life

In my last article, I already discussed Gatsby’s state in 2024, just after the merger between Gatsby (Cloud) and Netlify. Unfortunately, nothing has really changed since then. The framework seems frozen, with no new features or major updates, and a growing number of bugs.

This stagnation suggests that Gatsby no longer has the means or the will to compete with modern solutions, pushing more and more developers to seek alternatives for their projects. The Gatsby story seems to have reached its final chapter.

What should I do with my Gatsby website?

Keeping your website on Gatsby.js, a framework that is no longer updated, can quickly become problematic. Over time, the dependencies used by Gatsby risk becoming obsolete, which can lead to security vulnerabilities and incompatibilities with new technologies.

If bugs or errors appear, patches likely won’t be available. This can make the website unstable and difficult to maintain. For example, an error during a build will simply prevent you from modifying your website.

In short, staying on Gatsby today means running the risk of seeing your website age prematurely and become unusable in the near future.

You might as well seriously consider migrating to a more modern solution.

Alternatives

If you’re looking for an alternative to Gatsby.js, Astro.js and Next.js are top favorites. Astro focuses on simplicity and performance, perfect for creating ultra-fast static websites without loading tons of unnecessary JavaScript.

Next.js, on the other hand, offers a hybrid approach with the ability to mix static generation and server-side rendering, making it a versatile choice for the most complex projects.

As a consultant, I always take the time to analyze each client’s specific needs to recommend the framework best suited to their projects and objectives. Don’t hesitate to contact me to discuss!

The good news

There’s no need to change the headless CMS you’re currently using (Prismic, Dato, etc.), as it remains fully compatible with alternatives like Astro or Next.js.

The code used for your Gatsby website (JSX, React components) can be partially recovered to migrate to Astro. This is also a great opportunity to refresh your website’s design to give it a more modern look.

In any case, make sure your Gatsby website is updated to the latest available version (V5 from 2022, with Node 18 - React 18) to benefit from better performance and avoid issues between your CMS, hosting provider, and Gatsby.

Let’s take the time to discuss solutions now, so you don’t end up with an unusable website and in an emergency situation 🔥.

Sources

• Gatsby is going down, and it’s taking your website along with it.
• Should I Use Gatsby.js in 2024-2025?