Node.js 26 LTS: What's New and How to Upgrade

Node.js 26 LTS: What's New and How to Upgrade

Node.js runs a large share of the world's web back ends, build pipelines, and server-side rendering, including most Next.js applications. On 28 October 2026, Node.js 26 was promoted to Long Term Support, which makes it the recommended version for production applications that want the longest runway: it will receive maintenance until the end of April 2029. The release also marks a turning point for the project, as it is the last version under the familiar schedule of two major releases a year. For teams still on Node.js 20, which is already out of support, or on Node.js 22, which ends in April 2027, this is a good moment to plan the next step.

What's New in Node.js 26

• Temporal API enabled by default. The modern date and time API for JavaScript is now available without an experimental flag, offering a far more reliable way to work with dates, time zones, and calendars than the legacy Date object.
• V8 14.6. A newer JavaScript engine brings performance improvements and support for recent language features.
• Undici 8. The HTTP client that powers the built-in fetch() has been updated.

For business applications, the Temporal API is the change most likely to have a practical impact over time. Date handling is a common source of bugs, especially in applications that work across time zones, schedule events, or handle invoices and deadlines in different regions.

What Was Removed

As with every major version, some deprecated APIs have been removed. They include http.Server.prototype.writeHeader(), which should be replaced with writeHead(), and the legacy _stream_* modules. Most modern applications are not affected directly, but older code and some dependencies may still use them, which is why testing is essential before upgrading.

Node.js Support Dates

• Node.js 20: end of life since 30 April 2026
• Node.js 22: in maintenance, end of life on 30 April 2027
• Node.js 24: supported until 30 April 2028
• Node.js 26: Long Term Support since 28 October 2026, supported until the end of April 2029

Applications running on Node.js 20 or older no longer receive security fixes from the Node.js project and should be upgraded as a priority.

A New Release Model from Node.js 27

Node.js 26 is the last release under the old model of two major versions a year, with only even-numbered versions becoming LTS. From Node.js 27, the project moves to one major release per year. Each release starts as Current in April and is promoted to LTS the following October, every release becomes LTS, and each LTS line receives roughly 30 months of support. Version numbers will follow the calendar year of each release, so Node.js 27 arrives in 2027. An alpha channel aimed at library authors and CI testing opened in October 2026. For businesses, the new model makes upgrade planning more predictable: one major upgrade per year, on a fixed schedule.

Should You Upgrade Now?

If you are on Node.js 20 or older, yes: you are running unsupported software, and upgrading should be a priority. If you are on Node.js 22, plan the move before its end of life in April 2027, and consider going directly to Node.js 26 for the longest support window. If you are on Node.js 24, there is no urgency, since it is supported until 2028, but moving to Node.js 26 when convenient extends your runway by another year.

Before upgrading, confirm that your framework, hosting platform, and key dependencies support Node.js 26. Managed platforms and serverless providers sometimes add support for new LTS versions a little after release.

How to Upgrade Safely

• Check compatibility. Review the engines field of your key dependencies and the supported versions of your framework and hosting platform.
• Update every environment. Change the Node.js version in local development files such as .nvmrc, Docker base images, CI configuration, and production runtime settings, so they all match.
• Rebuild native modules. Packages with native add-ons must be reinstalled or rebuilt for the new version.
• Run your test suite. Pay attention to deprecation warnings and failures related to removed APIs, HTTP behavior, and streams.
• Test in staging. Run the application under realistic load in a staging environment before switching production.
• Roll out gradually. Where possible, deploy to a portion of traffic first and monitor errors and performance closely.

Frequently Asked Questions

When did Node.js 26 become LTS?

Node.js 26 was promoted to Long Term Support on 28 October 2026, with version 26.13.0. It will receive maintenance until the end of April 2029.

Is Node.js 20 still supported?

No. Node.js 20 reached end of life on 30 April 2026 and no longer receives security fixes from the Node.js project.

Should I upgrade from Node.js 22 to 24 or 26?

Node.js 26 offers the longest support window, until April 2029, compared with April 2028 for Node.js 24. If your framework and hosting platform support it, moving directly to Node.js 26 is usually the better choice.

Does Next.js support Node.js 26?

Check the current Next.js documentation and your hosting platform before upgrading. Frameworks and managed platforms typically add support for new LTS versions, but support can arrive at slightly different times.

What is the Temporal API?

Temporal is a modern JavaScript API for working with dates, times, time zones, and calendars. It replaces many uses of the legacy Date object with a more reliable and explicit design, and is enabled by default in Node.js 26.

How is the Node.js release schedule changing?

From Node.js 27, there will be one major release per year. Each release starts as Current in April, becomes LTS in October, and receives roughly 30 months of support. Every release will become LTS.

Conclusion

Node.js 26 LTS gives production applications support until April 2029, modern date handling with the Temporal API, and a newer engine and HTTP stack. With Node.js 20 already unsupported and Node.js 22 ending in April 2027, now is a sensible time to plan the upgrade, check compatibility, update every environment, and test thoroughly. If you need help upgrading Node.js or Next.js applications, modernizing outdated dependencies, or setting up a predictable upgrade process for the new yearly release cycle, our team can take care of it with minimal disruption.