static rendering
Rendering a page to HTML once, at build time or on a schedule, and serving that same result to every visitor.
In more detail
Static pages are fast and cheap because no code runs per request, and they can be cached on a CDN. The trade-off is that content is only as fresh as the last render.
Example
Next.js renders a route statically unless it uses Dynamic APIs such as cookies() or opts out with route segment config; the result includes an RSC payload.Related terms
- dynamic rendering — Rendering a route fresh on the server for each request, so it can show personalised or constantly changing data.
- 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.
- generateStaticParams — A function exported from a dynamic route that lists the param values to pre-render as static pages at build time.
- incremental static regeneration — Re-rendering a static page in the background after a set time or on demand, without rebuilding the whole site.
Taught in
- Client Components: use client & Hydration Models — Next.js 15 & Modern App Router Architecture
- Templates vs Layouts: Remounting & Page Transitions — Next.js 15 & Modern App Router Architecture
- Dynamic Routes: Slugs & generateStaticParams — Next.js 15 & Modern App Router Architecture
- 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
- Router Cache: In-Memory Client Prefetch Semantics — Next.js 15 & Modern App Router Architecture