IT infrastructure calculators

Node.js End of Life Dates

Release, end of support and end of life dates for every tracked Node.js version, with current status.

All products | Vendor lifecycle page | Source entry

Find a Node.js version

Jump to v14, v16 or v18 in the table for their support milestones. Active LTS receives new features and fixes; maintenance LTS receives critical fixes. The end-of-life date is the end of the project's regular support, not a promise that paid support from a separate provider is included. Check the official Node.js release schedule before an upgrade.

Coverage note: some values are retained from earlier reviews. Unresolved releases or dates may be omitted; feed retrieval is not verification of every displayed value.

Status calculated for 2026-11-04: 26 versions tracked; 1 supported, 2 security fixes only, 0 ending within 90 days, 23 end of life. Calculated from the dates stored here, not a vendor verification date. With JavaScript on, the calculation uses today's date.

Swipe the table sideways to see all columns ->

VersionStatusReleasedActive support endsSecurity support endsExtended support endsLatest
26 (LTS)Supported2026-05-052027-10-202029-04-30-26.13.0
25End of life2025-10-152026-04-012026-06-01-25.9.0
24 (LTS)Security fixes only2025-05-062026-10-202028-04-30-24.22.1
23End of life2024-10-162025-04-012025-06-01-23.11.1
22 (LTS)Security fixes only2024-04-242025-10-212027-04-30Not announced22.23.4
21End of life2023-10-172024-04-012024-06-01-21.7.3
20 (LTS)End of life2023-04-182024-10-222026-04-30Not announced20.20.2
19End of life2022-10-182023-04-012023-06-01-19.9.0
18 (LTS)End of life2022-04-192023-10-182025-04-30Not announced18.20.8
17End of life2021-10-192022-04-012022-06-01-17.9.1
16 (LTS)End of life2021-04-202022-10-182023-09-11Not announced16.20.2
15End of life2020-10-202021-04-012021-06-01-15.14.0
14 (LTS)End of life2020-04-212021-10-192023-04-30Not announced14.21.3
13End of life2019-10-222020-04-012020-06-01-13.14.0
12 (LTS)End of life2019-04-232020-11-302022-04-30Not announced12.22.12
11End of life2018-10-232019-04-222019-06-01-11.15.0
10 (LTS)End of life2018-04-242020-05-192021-04-30-10.24.1
9End of life2017-10-312018-04-012018-06-30-9.11.2
8 (LTS)End of life2017-05-302019-01-012019-12-31-8.17.0
7End of life2016-10-252017-04-302017-06-30-7.10.1
6 (LTS)End of life2016-04-262018-04-302019-04-30-6.17.1
5End of life2015-10-302016-04-302016-06-30-5.12.0
4 (LTS)End of life2015-09-092017-04-012018-04-30-4.9.1
3End of life2015-08-04Ended (no date published)Ended (no date published)-3.3.1
2End of life2015-05-04Ended (no date published)Ended (no date published)-2.5.0
1End of life2015-01-20Ended (no date published)Ended (no date published)-1.8.4

Frequently asked questions

Which Node.js versions are still supported?

Using the dates stored here, status calculated for 2026-11-04 shows 3 of 26 tracked Node.js versions are still in support (26 (LTS), 24 (LTS), 22 (LTS)). The table above shows the calculated status of every tracked version; retained values may still need vendor confirmation.

What is the newest Node.js version tracked here?

26 (LTS) (latest update 26.13.0), released 2026-05-05. This is the newest release included here, not necessarily the newest vendor release. Unresolved releases may be omitted while their dates or support status are checked. See the linked vendor source for current releases.

Where do these Node.js dates come from?

From the vendor sources linked at the top of this page (vendor lifecycle page) and the source entry. Vendors can revise dates, so confirm there before you schedule a migration.

Planning notes

Node.js major versions spend six months in the Current phase. Historically, odd-numbered releases became unsupported after six months, and even-numbered releases moved to Active LTS. The project says LTS releases typically get critical bug fixes for a total of 30 months, and that production applications should use only Active LTS or Maintenance LTS releases.

The project also states that, starting with Node.js 27, the release cycle becomes annual and every major version moves to LTS after its Current phase. Check the project's release schedule for the exact dates of the version you run.

Pin the major version in your CI and container images, and move to the next LTS while your current one is still in Maintenance, not after its end-of-life date.

Sources: Node.js previous releases and release phases.

Note: "Not announced" means no confirmed date is shown here; check the linked vendor source. "Ended (no date published)" means the source marks it ended without a date. Dates are compared as calendar days in your own time zone. A published end date counts as the last day of support.

Data: endoflife.date (MIT license), feed retrieved 2026-11-04. Retrieval does not mean every displayed value was verified that day. Some values are retained from earlier reviews, and unresolved releases or dates may be omitted. Confirm with the linked vendor source before a purchase or migration decision.