Node.js LTS Versions Explained: Which Release to Run in Production

By Seahawk November 15, 2026 5 min read

Run Node.js 26 in production today. As of November 15, 2026 it is the Active LTS line, code name Lithium, and it is supported until April 30, 2029. Node.js 24 is also safe, with support until April 30, 2028. Node.js 22 reaches end of life on April 30, 2027, so plan to leave it in the next few months. Node.js 20 and everything older no longer receive security fixes.

Below is the full schedule, how the release system works, what changes with Node.js 27, and the commands to check and switch versions.

Node.js Versions and Support Dates

These dates come from the Node.js releases page and the Release working group's published schedule. The project notes that future dates can change.

VersionCode nameStatus on Nov 15, 2026First releasedLTS startEnd of life
Node.js 27None yetAlpha, not for productionPlanned Apr 22, 2027Planned Oct 20, 2027Apr 30, 2030
Node.js 26LithiumActive LTSMay 5, 2026Oct 28, 2026Apr 30, 2029
Node.js 24KryptonMaintenance LTSMay 6, 2025Oct 28, 2025Apr 30, 2028
Node.js 22JodMaintenance LTSApr 24, 2024Oct 29, 2024Apr 30, 2027
Node.js 25NoneEnd of lifeOct 15, 2025Never LTSJun 1, 2026
Node.js 20IronEnd of lifeApr 18, 2023Oct 24, 2023Apr 30, 2026

Node.js 26 moves from Active LTS to Maintenance on October 20, 2027. Node.js 18 and earlier are all end of life.

How Node.js Releases Work

Every major version passes through phases. For Node.js 26 and earlier the pattern is:

  • Current. The first six months after release. New features land here and library authors add support.
  • Active LTS. Even-numbered versions are promoted each October. For twelve months they receive bug fixes, security updates and features the release team has vetted.
  • Maintenance LTS. The next eighteen months. Only critical bug fixes and security updates.
  • End of life. No fixes of any kind.

Odd-numbered versions such as 23 and 25 never became LTS. They went unsupported after about six months, which is why they do not belong on a production server.

The Node.js project's own advice is to run only Active LTS or Maintenance LTS releases in production. LTS stands for long-term support, and it covers roughly 30 months of fixes.

What Changes With Node.js 27

Node.js 26 is the last line under the old model. In its post on evolving the release schedule, the project set out a new one that starts with Node.js 27:

  • One major release a year instead of two. It arrives each April and is promoted to LTS each October.
  • Every release becomes LTS. The odd and even rule is gone. Node.js 27 will be an LTS line.
  • A six-month Alpha phase comes first. Alpha builds run from October to March. They may contain breaking changes and are meant for library authors and CI pipelines, not production.
  • LTS lasts 30 months with no separate Maintenance phase. A line gets 36 months in total from its first Current release to end of life.
  • Version numbers match the year. 27.0.0 ships in 2027 and 28.0.0 in 2028.

For a site owner the practical effect is small. You still upgrade from one LTS line to the next, and each October a new one becomes available. The main thing to remember is that "avoid odd numbers" stops being the rule after Node.js 26.

Which Version to Run Today

  • New project: start on Node.js 26. It has the longest support window of any production-ready line.
  • Running Node.js 24: no rush. Schedule a move to 26 some time before April 2028.
  • Running Node.js 22: start testing on 26 now. Support ends on April 30, 2027.
  • Running Node.js 20 or older: upgrade as a priority. These versions are already end of life.
  • Node.js 27 alpha: use it in automated tests if you maintain a library. Do not deploy it.

Before you settle on a version, check two things. First, your framework's minimum. Next.js 16, for example, requires Node.js 20.9 or later, so every supported LTS line works. Second, what your host offers. Some managed platforms list only a few major versions, and shared hosts with a Node.js selector can lag behind.

How to Check Your Node.js Version

On any machine with shell access:

node -v

The output looks like v26.13.1. The first number is the major version, which is the one that matters for support dates. To see whether that build belongs to an LTS line, run:

node -p "process.release.lts"

It prints the code name, such as Lithium, or undefined if the build is not an LTS release.

On a hosting platform, look in the project or application settings for a Node.js version field. Inside a running app, log process.version. Check production itself, because a developer's laptop and the server often differ.

How to Switch Node.js Versions

On your own machine or VPS

A version manager lets you install several versions side by side. With nvm on macOS or Linux:

nvm install 26
nvm use 26
nvm alias default 26
node -v

nvm install --lts installs the newest LTS release without naming a number. nvm itself runs on Windows only through WSL, Git Bash or Cygwin, so Windows users normally use the installer from nodejs.org or a separate Windows version manager.

Pin the version in the project

Add a file named .nvmrc to the project root that contains only the version:

26

Anyone who runs nvm use in that folder gets the same major version. Also declare it in package.json:

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

Some platforms read this field. On Vercel it overrides the version chosen in the project settings.

On a hosting platform or in a container

Managed platforms have a version setting per project. On a server that runs Docker, the version is set by the base image named in your Dockerfile, so pin the major version there. Our Dockerfile best practices guide covers base images.

A Safe Upgrade Routine

  1. Switch the version in a branch, not on the live server.
  2. Reinstall dependencies from the lockfile with npm ci. Packages that include compiled code are rebuilt for the new version.
  3. Run the test suite and a full production build.
  4. Deploy to a staging environment and click through the important journeys: login, checkout, forms.
  5. Deploy to production and watch the error logs for a day.

Major upgrades happen about once a year. Minor and patch updates within a line matter just as much because they carry security fixes. Node.js 26.13.1, released on November 10, 2026, was a security release. If you manage servers for clients, put the end-of-life dates above in a shared calendar and review them every October when a new LTS line arrives.

For more guides like this one, see our Node.js articles and the wider host infrastructure section.

SeaPHP

Mission-critical PHP services and Next.js migrations.

Complex upgrades for PHP applications and websites. PHP-to-Next.js migrations for what comes next.