Node.js 18 (LTS support ends April 30, 2025) and the Vercel legacy build image will be deprecated on September 1, 2025. If you are still using the legacy build image on this date, new builds will display an error.

What changes between the legacy build image and latest build image?

• The minimum version of Node.js is now 20.x

• The Python toolchain version is now 3.12

• The Ruby toolchain version is now 3.3.x

How do I know if I am still using the legacy build image?

• Projects using Node.js 18.x in Build and Deployment Settings use the legacy build image

• Projects using overrides in package.json use the legacy build image

Will my existing deployments be affected?

Existing deployments will not be affected. However, the Node.js version will need to be updated on your next deployment.

How can I see if my projects are affected?

You can see which projects are affected by this deprecation by running the following commands:

npm i -g vercel@latest
vercel project ls --update-required

How do I upgrade?

To upgrade with the dashboard, visit the Build and Deployment settings for your project and upgrade the version.

To upgrade with code, use the engines field in package.json:

{
  "engines": { 
    "node": "22.x"
  }
}

This date coincides with the previously announced deprecation of Node.js 18 on the Vercel platform. Learn more about differences between build images.