Blog
Next.jsReactFrontend

Is the Next.js Pages Router Legacy in 2026?

July 29, 20261 min read

Yes — but legacy is not dead. When it is fine to stay on the Pages Router, when the move is worth it, and how to run app/ and pages/ side by side during an incremental migration.

Short answer: yes, but "legacy" does not mean "dead." The Pages Router is still supported, still receives bug fixes, and still runs a large share of production Next.js apps. What it does not get is new features — those all land in the App Router.

What "Legacy" Actually Means

  • No forced migration, no deprecation date
  • New APIs (Server Components, Server Actions, partial prerendering) are App Router only
  • The official docs now frame the migration guide as something you do "when you're ready"

When to Stay

  • The app is stable and the team is productive
  • Nothing on the roadmap needs an App-Router-only feature
  • getServerSideProps / getStaticProps cover your data-fetching needs
Rewriting a working Pages Router app for its own sake is rarely worth the regression risk.

When to Move

  • You want React Server Components to cut client-side JavaScript
  • You need streaming or nested layouts that persist across navigation
  • You are starting a new section of the app anyway

The Incremental Path

app/ and pages/ coexist in the same project. A route in app/ wins over the same route in pages/. Migrate leaf pages first, keep authentication and complex legacy flows in pages/, and move shared layouts last.

The most common App Router pain in 2026 is not instability — it is the caching model. Multiple cache layers interact differently depending on fetch options and rendering mode, and that is the part worth learning before you start.

Conclusion

Treat the Pages Router like a stable dependency you are slowly paying down, not an emergency. New surfaces in app/, existing ones migrated on their own schedule.