Skip to content
All writing

Node.js 20 has reached end of life: what it means for your website

Node.js 20 reached end of life on 30 April 2026. The dates for Node 22 and 24, why Vercel now blocks Node 20 deploys, and what to do for your website.

Tech newsPublished Updated 4 min readBy Muhammad Idrees

Node.js 20 reached end of life on 30 April 2026, which means it no longer receives security fixes. On Vercel, one of the most common hosts for Next.js sites, Node.js 20 was disabled for new deployments on 1 October 2026. A site already deployed keeps running, but the next time someone tries to publish a change, the deployment fails until the project moves to a newer version, such as Node.js 24. If your site was built in the last few years with Next.js or another JavaScript framework, it is worth checking now rather than on the day you need an urgent change.

What Node.js is, in one paragraph

Node.js is the software that runs JavaScript on a server. Next.js sites, many online stores, and plenty of custom web apps rely on it to build their pages and to handle forms, payments, and logins. Each major version is supported for a set period and then retired, so every site built on it needs an occasional upgrade, the same way a WordPress site needs PHP upgrades.

The dates

DateWhat happened
30 April 2026Node.js 20 reached end of life and stopped receiving security fixes.
14 July 2026Vercel announced it would disable Node.js 20 for builds and functions.
1 October 2026Node.js 20 disabled on Vercel. New deployments of projects still set to Node.js 20 show an error.

Other hosts and platforms have been dropping Node.js 20 on their own timelines, so check yours.

Is Node.js 20 still supported?

No. Node.js 20 stopped receiving security fixes on 30 April 2026. The Node.js project supports each long-term support (LTS) version for about three years, so every version on a website eventually needs the same upgrade. These are the end-of-life dates for recent versions, from the Node.js release schedule:

VersionEnd of lifeStatus in October 2026
Node.js 1430 April 2023Unsupported
Node.js 1611 September 2023Unsupported
Node.js 1830 April 2025Unsupported
Node.js 2030 April 2026Unsupported
Node.js 2230 April 2027Supported
Node.js 2430 April 2028Supported, and Vercel's example upgrade target

If your site runs on Node.js 22, it is supported until April 2027, but moving straight to 24 saves doing the upgrade twice in a year.

What it means for your website

  • Your live site keeps working. Vercel says invocations of functions that are already deployed continue as normal. Visitors notice nothing.
  • You cannot publish changes. A new deployment, whether a price change, a new page, or a security fix in your own code, fails until the Node.js version is updated.
  • Security fixes have stopped. Even on a host that still allows it, an end-of-life version gets no patches for problems found from now on.

The real risk is timing. The day you find out is usually the day you need an urgent change, such as a wrong price, a broken form, or a legal notice, and then the upgrade has to happen under pressure.

What to do

  1. Ask whoever looks after the site which Node.js version it uses. It is set in the project's settings on the host, or in a file in the code called package.json.
  2. Upgrade to a supported version. Vercel's own example moves projects to Node.js 24. On Vercel it is a setting in the project, or a line in package.json: "engines": { "node": "24.x" }. To see which version a computer has, run node -v in a terminal.
  3. Test before going live. Most sites upgrade without trouble, but older dependencies can break on a newer version. Build a preview, click through the forms and checkout, then publish.
  4. Write down the next date. Every Node.js version has an end-of-life date. Knowing the next one turns an emergency into a routine job.

Vercel also lets projects that cannot upgrade in time deploy as a container, where you manage the Node.js version yourself. It recommends upgrading instead where possible, because a container on an old version still has no security fixes.

If nobody looks after your site any more

This is common: a site built a few years ago, by a developer who has moved on, on a host account nobody has logged into since. Start by finding the logins for the hosting and the code. If you have those, any competent developer can do the upgrade. If you do not, that is the bigger problem to solve, and a good reason to make sure every future site comes with the code and written handover notes. The guide to what website maintenance should cover explains what to keep track of.

Need it done?

A Node.js upgrade on a typical Next.js site is a small job when the code and hosting are accessible. Send me the site address and what you have access to, and I will tell you what the upgrade involves.

Where to go next

Questions

Is Node.js 20 still supported?
No. Node.js 20 reached end of life on 30 April 2026 and no longer receives security fixes. Node.js 22 is supported until 30 April 2027 and Node.js 24 until 30 April 2028.
When did Node.js 20 reach end of life?
On 30 April 2026. It no longer receives security fixes.
Will my website stop working because of Node.js 20 end of life?
A site already deployed keeps running. On Vercel, new deployments of projects still set to Node.js 20 fail from 1 October 2026, so you cannot publish changes until the version is upgraded.
Which Node.js version should I upgrade to?
A currently supported version. Vercel's own example moves projects to Node.js 24. Test a preview build before publishing.

Need a website that brings in customers?

I reply within one business day. Website builds typically start at £750. Or get a free teardown of your current site

Start a project