Is Next.js 15 end of life yet?

Search for the Next.js 15 end of life date and most pages will tell you October 21, 2026. That was the original date, and it has passed. It's no longer the whole story. The official support policy now says Maintenance LTS for Next.js 15 was extended, and security releases for Next.js 15 continue through January 31, 2027.

So Next.js 15 is still supported, for now, but only with critical bug fixes and essential security updates. Next.js 16 is the Active LTS version. Here's how to check where you are and move to 16 without breaking the site.

Check your version in a minute.

Run this from your project folder:

  • npx next --version prints the Next.js version.
  • node -v prints your Node.js version. You'll need it below.
  • Open package.json and look at the next line under dependencies. The lockfile shows the exact version that is installed.

The first number is the major version. 15.x means this page applies to you. 14.x or older is already unsupported.

What the support policy says.

VersionReleasedStatus
16.xOctober 21, 2025Active LTS. New features, bug fixes and security patches.
15.xOctober 21, 2024Maintenance LTS. Critical bug fixes and essential security updates only.
14.x and olderOctober 26, 2023 and earlierUnsupported.

The policy page also carries a notice: to give teams more time to upgrade, Maintenance LTS for Next.js 15 was extended beyond its original end date of October 21, 2026, and security releases continue through January 31, 2027. Plan around January 31, 2027, but treat it as a deadline, not a goal. The policy also says Maintenance LTS updates arrive as minor releases, even when they are breaking changes.

What you need before upgrading.

Next.js 16 raises the minimum versions:

  • Node.js 20.9 or newer. Node 18 is no longer supported.
  • TypeScript 5.1 or newer.
  • Browsers: Chrome, Edge and Firefox 111 or newer, and Safari 16.4 or newer.

If your host or build server runs Node 18, change that first. Our guide on checking your PHP version follows the same idea for PHP: runtime first, framework second.

What breaks in 16.

These are the changes in the official upgrade guide most likely to affect a real site:

  • Async request APIs. Next.js 15 still allowed old-style synchronous access to cookies(), headers(), draftMode(), params and searchParams. In 16 that is removed. You must await them. Image, icon and sitemap functions get async values too.
  • Turbopack is the default for next dev and next build. If you have a custom webpack config, the build fails until you pass --webpack, pass --turbopack, or move the config over. A plugin can add a webpack config without you knowing.
  • middleware is now proxy. Rename the file and function. The proxy runs on Node.js, not the edge runtime. If you rely on edge, keep middleware and don't blindly rename.
  • revalidateTag needs a second argument, such as revalidateTag('posts', 'max').
  • Image defaults changed. minimumCacheTTL is now 4 hours, only quality 75 is allowed unless you list others, local images with query strings need a config entry, and the redirect limit is 3.
  • Parallel routes need an explicit default.js in every slot, or the build fails.
  • Removed: AMP, the next lint command, serverRuntimeConfig and publicRuntimeConfig, and some experimental flags.

A safe upgrade order.

  1. Branch and back up. Make sure the site builds cleanly on its latest 15.x release first.
  2. Check Node and TypeScript against the minimums, locally and on the host.
  3. Run the codemod: npx @next/codemod@canary upgrade latest. It updates the Turbopack config, moves middleware to proxy, and migrates away from next lint.
  4. Run the async codemod separately: npx @next/codemod@canary next-async-request-api .. The upgrade codemod does not run it, and it is the change that touches the most files. Resolve any error comments it leaves.
  5. Fix the build, including any webpack config and the parallel route defaults.
  6. Check third-party packages. Auth, CMS and analytics libraries must support 16 and React 19.2.
  7. Test what earns money: forms, login, checkout, preview mode, image loading and any cached page that should update after an edit.
  8. Deploy to a preview first, compare it with production, then promote it.

Don't turn on React Compiler or Cache Components just to finish the upgrade. The guide says they are separate decisions.

Who should do this.

If the app has few routes and good tests, a developer can do it in a day or two. If it is large, uses a custom webpack config, or has no tests, give it a staging round. Agencies that have Next.js sites for several clients can pass us the upgrades as white-label work under their own name.

Want us to handle it?

We handle the tech side. We check your Next.js and Node versions, upgrade a preview copy, fix whatever breaks, then ship it and test the key pages with you.

Talk to us about a Next.js upgrade

Good questions.
Straight answers.

When does Next.js 15 reach end of life?

The original date was October 21, 2026, but the official support policy now says security releases for Next.js 15 continue through January 31, 2027.

Is Next.js 15 still supported?

Yes, as Maintenance LTS. That means critical bug fixes and essential security updates only. Next.js 16 is the Active LTS version.

Should I upgrade from Next.js 15 to 16 now?

Yes, if you can test it. January 31, 2027 is the last date given for security releases, and the upgrade may need Node, config and code changes.

Does Next.js 16 need a newer Node.js?

Yes. It needs Node.js 20.9 or newer and TypeScript 5.1 or newer. Node.js 18 is no longer supported.

What is the biggest breaking change from 15 to 16?

Synchronous access to cookies(), headers(), params and searchParams is removed, so you must await them. A codemod does most of it. The change to Turbopack by default is the next most common cause of a failed build.

Sources