Rendering for Next.jss
Rendering in Next.js is the decision of where and when a component turns into HTML. Server Components run only on the server and ship no JavaScript, while Client Components marked with use client hydrate in the browser. Static, dynamic and streamed rendering control when a page is built.
Stage: App Router Basics · Part of the Next.js roadmap · Last reviewed 19 November 2026
What to learn in Rendering
- Decide whether a component should be a Server or Client Component
- Add the use client directive only where state or event handlers are needed
- Explain static rendering versus dynamic rendering for a route
- Stream slow parts of a page using Suspense boundaries
- Pass props from a Server Component into a Client Component safely
Rendering interview questions
When should a Next.js component be a Client Component?
Use a Client Component when it needs state, effects, browser APIs such as window, or event handlers like onClick. Everything else can stay a Server Component, which keeps its code out of the browser bundle and can read data directly on the server.
What is the difference between static and dynamic rendering in Next.js?
Static rendering builds the HTML once, at build time or on revalidation, and serves it from cache. Dynamic rendering builds it per request, which happens when a route reads cookies, headers or uncached data. Dynamic is slower per request but always current.
Where Rendering fits in the Next.js roadmap
Rendering belongs to the App Router Basics stage (beginner level), which takes about 16 hours. Files become routes.
Other units in this stage
Back to the full Next.js roadmap