← ← Back to all products
Next.js
Active
Frameworks Latest Version: 16.1.6 Latest Release: Jan 27, 2026
Next.js is a React framework by Vercel for building full-stack web applications with server-side rendering and static generation.
Versions
8
Latest Version
16.1.6
Active Support
2
EOL
6
Lifecycle Timeline
Today ↓
16
16
15
15
14
14
13
13
12
12
11
11
10
10
9
9
Active SupportSecurity SupportEOL
Versions
| Release | Release Date | Active Support | EOL | Latest Version | LTS | Status |
|---|---|---|---|---|---|---|
| 16 | Oct 22, 2025 | - | No | 16.1.6 | Yes | Active |
| 15 | Oct 21, 2024 | - | Oct 21, 2026 | 15.5.12 | Yes | Active |
| 14 | Oct 26, 2023 | - | Oct 26, 2025 | 14.2.35 | Yes | EOL |
| 13 | Oct 25, 2022 | - | Dec 21, 2024 | 13.5.11 | No | EOL |
| 12 | Oct 26, 2021 | - | Nov 21, 2022 | 12.3.7 | No | EOL |
| 11 | Jun 15, 2021 | - | Jan 27, 2022 | 11.1.4 | No | EOL |
| 10 | Oct 27, 2020 | - | Jun 15, 2021 | 10.2.3 | No | EOL |
| 9 | Jul 8, 2019 | - | Oct 27, 2020 | 9.5.5 | No | EOL |
Frequently Asked Questions
Which versions of Next.js have reached end of life?
The following Next.js versions have reached end of life and no longer receive security updates: 14, 13, 12, 11, 10, 9. It is recommended to upgrade to a supported version.
Is it safe to continue using Next.js 14?
Next.js 14 has reached end of life and no longer receives security patches or bug fixes. Continuing to use it may expose your systems to known vulnerabilities. We strongly recommend upgrading to a supported version.
What is the latest version of Next.js?
The latest version of Next.js is 16.1.6, released in the 16 release cycle.
How many versions of Next.js are currently supported?
Next.js currently has 2 actively supported version(s): 16, 15.
When does Next.js 16 reach end of life?
Next.js 16 does not have a specific end-of-life date announced yet.
What should I do when Next.js reaches end of life?
When a Next.js version reaches end of life, you should: 1) Plan your migration to a supported version as soon as possible. 2) Review the release notes for breaking changes. 3) Test your applications thoroughly in a staging environment. 4) Update your dependencies to ensure compatibility with the new version.