# Server-side rendering (SSR)

> Generating the page's HTML on the server per request — the browser gets a complete page, not a loader and a promise.

The client-side default — an empty div and a JavaScript bundle — means every visitor, crawler and link-preview bot must run the app to see anything. SSR runs it once on the server and sends the finished HTML: first paint is a page, not a spinner.

It is the middle point of the spectrum: static generation pre-renders at build time for content that rarely changes; SSR renders per request for pages that must be fresh or personal. Frameworks like Next.js let you choose per route, which is the correct granularity — the marketing page wants static, the dashboard wants SSR.

## Related terms

- https://dfieldsolutions.com/en/glossary/static-generation.md
- https://dfieldsolutions.com/en/glossary/hydration.md
- https://dfieldsolutions.com/en/glossary/client-side-rendering.md

---

Source: https://dfieldsolutions.com/en/glossary/ssr
DField Solutions — Dunakeszi, Hungary — dezso@dfieldsolutions.com
Booking: see https://dfieldsolutions.com/en/contact