Last checked and updated on 01 Jun 2026
How Next.js Handles Version Support and LTS
Next.js follows a clear LTS model for each major version. A major version starts in Active LTS from its initial release and stays there until the next major version ships. During this phase, it receives new features, regular bug fixes, performance improvements, and security patches.
Once a newer major version is released, the previous one moves into Maintenance LTS. In this stage, the team only ships critical bug fixes and essential security updates. Maintenance LTS lasts exactly two years from the initial release date of that major version. Updates in this phase come as semver-minor releases, even if they include breaking changes within the minor version.
After the two-year Maintenance LTS period ends, the version reaches End of Life (EOL). At that point, no further updates, bug fixes, or security patches are provided by the Next.js team.
| Phase | Duration | What You Get |
|---|---|---|
| Active LTS | Until next major release | New features, bug fixes, performance improvements, security patches |
| Maintenance LTS | 2 years from initial release | Critical bug fixes and essential security updates only |
| End of Life (EOL) | After Maintenance LTS | No updates from the Next.js team |
What Are the Real Risks of Using an EOL Version of Next.js?
When you run an EOL version of Next.js, you no longer receive any security patches or bug fixes from the core team. New vulnerabilities discovered in React, Node.js, or the framework itself will remain unaddressed in your codebase.
Dependency conflicts become common because newer packages and tools often drop support for older Next.js majors. This can break your build process or force you to pin outdated dependencies, increasing technical debt over time.
In practice, most engineering teams notice that upgrading becomes significantly harder the longer they stay on an EOL release. Features like the App Router, Turbopack improvements, and React updates are only available in newer majors, so you miss out on performance gains and developer experience improvements that the rest of the ecosystem is using.
What Actually Happens When Next.js Support Ends for a Major Version?
Once a major version reaches EOL, the Next.js team stops all maintenance for that line. No more patches will be published, even for critical issues. You are responsible for any security or stability problems that arise afterward.
Your application continues to run, but it gradually falls behind the ecosystem. Newer versions of React, TypeScript, ESLint, or other core dependencies may stop supporting your Next.js version, forcing you to either stay frozen or undertake a larger migration later.
Some teams choose third-party extended support services for EOL versions when a full rewrite is not immediately feasible. However, the cleanest long-term path is usually planning an upgrade while the version is still in Maintenance LTS.
How Do You Check Which Next.js Version Your Project Is Using?
The fastest way to check your current Next.js version is to look in your package.json file under the dependencies or devDependencies section.
You can also run this command in your project root:
npm list nextOr if you are using Yarn or pnpm:
yarn why nextpnpm list nextCompare the major version shown against the release table on this page to determine whether you are on Active LTS, Maintenance LTS, or EOL.
FAQ
Q1: What is the difference between Active LTS and Maintenance LTS in Next.js?
Active LTS includes new features and regular updates, while Maintenance LTS only provides critical bug fixes and security patches for two years after the initial release.
Q2: Does Next.js provide any support for versions after they reach EOL?
No. Once a major version reaches EOL, the official team no longer publishes any updates, patches, or security fixes for that line.
Q3: Can I safely run a Next.js version that is in Maintenance LTS?
Yes, many teams do this successfully when they need more time before upgrading. Just be aware that you only get critical fixes, and you should plan the upgrade before the two-year window closes.
Q4: How long does a Next.js major version typically stay in Active LTS?
It stays in Active LTS until the next major version is released. The exact duration varies depending on the release cadence of new majors.
Q5: Should I upgrade immediately when a new major version comes out?
It depends on your project. Staying on the latest Active LTS is generally recommended for new features and better performance. If you are on Maintenance LTS, evaluate the breaking changes and plan the upgrade during a maintenance window.