The migration guide designs app/ to run alongside pages/ so a codebase can move one route at a time. On Next.js 16.4.5, one next build produced two route tables, Route (app) and Route (pages), served by one next start.
Shared, measured on /p (a Pages route) and /a (an App route):
public/files and.envvalues: both pages renderedNEXT_PUBLIC_GREETING.next.configredirectsandheaders: both redirects returned 307, and the custom header was on both responses.- Proxy: its response header appeared on both routes its
matcherlisted.
Not shared:
- The shell.
_appand_documentwrap onlypages/; the root layout wraps onlyapp/. The guide says to keep_app/_documentuntil the last page moves, and that styles inapp/layoutdon't reachpages/. - The client router. A
<Link>between the two routers did a full document load in Chrome 156 and Firefox 159: awindowmarker was lost andperformance.getEntriesByType('navigation')named the new URL. A<Link>withinpages/kept the marker. i18n. It is a Pages Router option. Withlocales: ['en', 'fr'],/fr/prendered the Pages route and/fr/areturned 404, andnext startwarned:i18n configuration in next.config.mjs is unsupported in App Router.The App Router does locales with anapp/[lang]segment instead.- Routing hooks.
next/routerworks only inpages/,next/navigationonly inapp/.
A URL must belong to one router. With pages/dup.js and app/dup/page.js, the Turbopack build failed with App Router and Pages Router both match path: /dup. An unmatched URL got the App Router's 404 page.