# Legacy build image is being deprecated on September 1, 2025

By Steven Van · 2025-04-10

Projects still on Node.js 18 or the old build image will get errors on new builds after September 1, 2025; existing deployments keep working.

Vercel is [deprecating its legacy build image](<https://creatorstoolbox.com/tools/vercel>) on September 1, 2025, alongside Node.js 18, whose LTS support ends April 30, 2025. Projects still on the legacy image after that date will see an error when new builds run. Existing deployments are not affected, but the Node.js version has to be updated on the next deployment, according to [Vercel's build image documentation](<https://vercel.com/docs/builds/build-image/build-image>).

The latest build image raises the minimum Node.js version to 20.x, moves the Python toolchain to 3.12 and the Ruby toolchain to 3.3.x.

A project uses the legacy image if it has either of these:

- Node.js 18.x set in Build and Deployment Settings

- Overrides in package.json

To list affected projects, install the latest CLI with npm i -g vercel@latest and run vercel project ls --update-required. To upgrade, change the version in the project's Build and Deployment settings, or set the engines field in package.json, for example "node": "22.x".

![Vercel](<https://www.google.com/s2/favicons?domain=vercel.com&sz=128>)

Vercel

The platform for frontend developers — deploy, preview, and scale web apps and AI agents with zero config.

[View Vercel →](<https://creatorstoolbox.com/tools/vercel>)

[Original source](<https://vercel.com/docs/builds/build-image/build-image>)

[Read Legacy build image is being deprecated on September 1, 2025 on Creators Toolbox](<https://creatorstoolbox.com/blog/vercel-legacy-build-image-is-being-deprecated-on-september-1-2025>)

---
Canonical source: https://creatorstoolbox.com/blog/vercel-legacy-build-image-is-being-deprecated-on-september-1-2025