How do Parallel Routes behave on soft navigation and a full reload?

Explains named slots, retained active state, hard-navigation fallbacks, and the required default files in Next.js 16.

1Say itAnswer out loud first

2CompareCompare with Core answer

3RefineRefine with Stronger and Advanced

TL;DR

Parallel Routes use named @slot folders that a parent layout receives as props, and the slot name does not change the URL. During soft navigation, Next.js can retain each slot's active subpage. On a full reload, it renders default.tsx for any slot that does not match the requested URL, or a 404 if no fallback exists. In Next.js 16, every parallel slot needs an explicit default file.

Full answer below

Practice focus

Parallel Routes, slots, soft versus hard navigation, default fallbacks, and version-specific build behavior.

Answer first

Answer path

Core answer first, then checkpoints toward a stronger answer.

Start
Core answer
Start here. This is the direct spoken answer to practice first.
Overview
Parallel slots can navigate independently, but a server handling a direct request cannot reconstruct every slot's previous client state.
Parallel Routes use named @slot folders that a parent layout receives as props, and the slot name does not change the URL. During soft navigation, Next.js can retain each slot's active subpage. On a full reload, it renders default.tsx for any slot that does not match the requested URL, or a 404 if no fallback exists. In Next.js 16, every parallel slot needs an explicit default file.
Checkpoint
Stronger answer
Optional upgrade with examples, trade-offs, and sharper phrasing.
This makes parallel routes useful for dashboards, split views, and modal slots whose areas navigate independently. I define a meaningful fallback for each slot and remember that is itself an implicit slot, so it may also need a default in this structure. I test direct entry and refresh, not only links inside the running application, because retained client state can make an incomplete route tree appear correct. If one slot at a segment is dynamic, I treat the whole composed segment as dynamic rather than assuming mixed slot behavior.

Review signals

Use these to catch weak phrasing, shallow reasoning, and risky claims.

Common mistakesCandidateCommon mistakesMistakes that weaken the answer or signal shallow understanding.Open details

Details

Treating @slot as a URL segment.
Testing only client-side navigation and missing refresh behavior.
Adding empty defaults without deciding the correct unmatched state.

How do Parallel Routes behave on soft navigation and a full reload?

Practice focus

Answer path

Overview

Review signals

Follow-up prompts

Continue practice

Next interviewer turn

Tech stacks

Skill areas

Human editorial direction

Was this drill useful?

Found this answer useful?