Modernize Next.js

Next.js major versions ship real breaking changes — async request APIs, changed caching defaults, Turbopack as the default bundler, and the App Router model. This hub links every supported upgrade path plus the workflows for the build errors those upgrades surface.

What this covers

Next.js 16 is the current stable release. Start at the Next.js 16 upgrade hub for the full breaking-change picture, then pick the source-to-target page that matches the version you are on today. For a routing model change, see the Pages Router to App Router guide. Each page includes a repo-inspection prompt, step-by-step migration, a test plan, and rollback guidance.

Version timeline

• 16.x — current, active (released 2025-10-21)
• 15.x — maintenance (released 2024-10-21)
• 14.x — eol (released 2023-10-26 · EOL 2025-10-26)
• 13.x — maintenance (released 2022-10-25)

Next.js migration paths

• Next.js 13 to Next.js 15 Migration Guide — Version path
• Next.js 14 to Next.js 15 Migration Guide — Version path
• Next.js 15 to Next.js 16 Migration Guide — Version path
• Migrate Next.js Pages Router to App Router — Migration
• Upgrade to Next.js 15 — Upgrade hub
• Upgrade to Next.js 15 — Version path
• Upgrade to Next.js 16 — Upgrade hub
• Upgrade to Next.js 16 — Version path
• Fix Next.js Build Errors — Workflow

Frequently asked questions

Which Next.js version should I target?

Next.js 16 is the current stable release (GA October 21, 2025; 16.2.x as of mid-2026) and is in Active LTS. Next.js 15 is in Maintenance LTS, and 14 is end-of-life. If you are already on 15, the 15-to-16 step is well supported by the @next/codemod upgrade CLI; the biggest 16 changes are the fully-removed synchronous request APIs, Turbopack-by-default, the middleware-to-proxy rename, and the new revalidateTag signature.