Parallel routes let one layout render several independent page trees at once. Each @folder is a slot, passed to the parent layout as a prop with that name; children is an implicit slot (app/page.js is app/@children/page.js). Slots aren't route segments: app/dash/@team/settings/page.js serves /dash/settings. Each slot can have its own loading.js and error.js, so a dashboard panel can stream or fail on its own.
Each URL needs an answer from every slot. For /dash/settings, @team has a page but children and @analytics may not. What they show depends on the navigation:
- Soft navigation (
<Link>,router.push): Next.js remembers each slot's active page and keeps it. Clicking from/dashto/dash/settingsswaps only@team; the others keep showing their/dashpages, though the URL no longer matches them. - Hard navigation (reload, pasted URL): that memory is gone. Next.js renders each unmatched slot's
default.js.
So default.js is the slot's answer for "I have nothing for this URL after a full load". It can return null (a modal slot that's closed), call notFound(), or render a real fallback. It receives params.
In Next.js 16.4.5, strict route matching (on by default since 16.4.0) checks this at build time: a missing default.js for any slot, children included, fails next build. Before that, a missing named-slot default meant a 404 at request time, which some docs pages still describe; deprecated.looseRouteMatching: true restores it.
Slots are combined into one page for the segment, so they share its rendering mode: if one slot is dynamic, all of them are. A layout that picks a slot by role still renders both on the server, so authorize inside each slot.