0
Challenge · 18Rendering & Caching
What makes a route dynamic
Renderingused in ~92% of apps
Almost every Next.js tutorial teaches this wrong, and it costs people real money in compute bills and real points in interviews: they think a folder named [slug] makes a page 'dynamic.' It doesn't. The word 'dynamic' means two completely different things, and conflating them is the single most common rendering mistake juniors make.
Core idea. A dynamic SEGMENT (a `[slug]` folder) is a ROUTING concept — it captures a URL part into `params`. Dynamic RENDERING is an EXECUTION concept — the page is built per-request instead of once. They are unrelated. What forces request-time rendering is reading request data (`searchParams`, `await cookies()`, `await headers()`, `await draftMode()`) or reading uncached data — never the shape of the folder name.
poke it, drag it,
try to break it
try to break it
no slides here.
you drive.
you drive.
Playground, this isn't a screenshot
0
Idle1
Server render2
Stream chunks3
First paint4
JS arrives5
HydratedRequest the page
browser viewportblank
waiting for request…
server: renderToPipeableStream(<App/>)
stream: <html>… flushed in chunks →
stream: <Suspense> fallback first, then data
browser: paint HTML (fast FCP, no JS)
browser: download client bundle.js
hydrateRoot(el, <App/>) — attach handlers
JS attached: no
Try clicking Like before stage 5.
↑ play a little first, then dig in