Server-side cache of rendered static routes.
Skip to solutionKEEP THE
hardSystem Design
What is the Full Route Cache in Next.js?
160 views
01
Understand the problem
nextjsfull-route-cachecachingstatic
02
Attempt it yourself
Sketch your approach before reading the solution — that's what interviews test.
Nudge consolestandby
Stuck? Beam a request up — the console returns a conceptual nudge that guides your logic without spoiling the implementation.
03
Study the solution
The Full Route Cache stores the rendered HTML and RSC payload of statically-rendered routes at build time, so they're served instantly without re-rendering. It's invalidated by revalidation or a new deploy; dynamic routes skip it.
Solution ready — 2 min read
Classified // press E to declassify
04
Read the code
What lands in the Full Route Cache
// STATIC → rendered output stored in the Full Route Cache
export default async function Page() {
const posts = await fetch('/api/posts', { next: { revalidate: 3600 } }).then(r => r.json());
return <List posts={posts} />;
}
// DYNAMIC → NOT in Full Route Cache (rendered per request)
export const dynamic = 'force-dynamic';05
Join the discussion
Discussion (0)
Sign in to join the discussion.
No responses yet. Be the first to share what you think.
Transmission complete // awaiting log
KEEP THE
STREAK ALIVE.
Dossier 92 of 95 decoded in the Next.js track. One more won't hurt.