Full Route Cache
The third Next.js caching tier: the server stores the rendered HTML and RSC payload of static routes and serves them without re-rendering.
In more detail
It is filled at build time and refreshed by revalidation. Routes that use Dynamic APIs, or export dynamic = 'force-dynamic', skip it. Revalidating a tag or path the route depends on clears its entry.
Related terms
- static rendering — Rendering a page to HTML once, at build time or on a schedule, and serving that same result to every visitor.
- Data Cache — The second Next.js caching tier: a server-side store of fetch results that persists across requests, users and deployments.
- route segment config — Constants exported from a page, layout or route file, such as dynamic, revalidate or runtime, that change how that segment is rendered and cached.
Taught in
- Data Cache: Cross-Request Persistence & Fetch Tags — Next.js 15 & Modern App Router Architecture
- Full Route Cache: Static Rendering & Segment Config — Next.js 15 & Modern App Router Architecture