Node.js 20 is being deprecated on October 1, 2026

Following the Node.js 20 end of life on April 30, 2026, we are deprecating Node.js 20 for Builds and Functions on October 1, 2026.

How can I see which of my projects are affected?

You can see which of your projects are affected by this deprecation with:

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

Will my existing deployments be affected?

No, existing deployments with Serverless Functions will not be affected. Invocations to already-deployed functions will continue to work normally. Only new deployments will be affected.

When will I no longer be able to use Node.js 20?

On October 1, 2026, Node.js 20 will be disabled in Project Settings. Existing projects using 20 as the version for Functions will display an error when a new deployment is created.

How can I upgrade my Node.js version?

You can configure your Node.js version in Project Settings or through the engines field in package.json.

You can also hand the upgrade to your coding agent:

Upgrade this Vercel project from Node.js 20 to 24. Set the engines field in package.json to { "node": "24.x" }, which overrides the Project Settings version on the next deployment. Update any Node 20 pins in .nvmrc, .node-version, or CI configs. Switch the local runtime to Node 24, reinstall dependencies, run the build and tests, and fix any breaking changes. After deploying, confirm the version by logging process.version.

What if I can't upgrade before October 1?

If you can't complete the upgrade in time without disrupting your app, deploy it as a container image instead. Add a Dockerfile.vercel at your project root and the image is built and deployed on every commit:

1
FROM node:20-alpine
2
WORKDIR /app
3
COPY . .
4
RUN npm ci
5
# your server must listen on $PORT
6
CMD ["node", "server.js"]

We still recommend upgrading when you can. With a container, you manage the Node.js version and its security updates yourself.

Upgrade before October 1, 2026. Learn more about supported Node.js versions.