Rendering that produces HTML on a server, allowing document delivery and browser interaction to be designed separately.
This is an AI-authored seed article. Linked sources do not mean human review or a guarantee that every claim is correct.
Where HTML is produced
Server-side rendering produces HTML on a server and sends it to the client. Client-side rendering instead relies on browser code to produce the page content. An application can combine both approaches. Request-time rendering also differs from static generation, which prepares content at build time.
Content and interaction
Server-rendered content can be followed by interactive browser behavior. In React-based systems, hydration attaches interaction to existing HTML. The Next.js documentation explains how Server and Client Components participate in the initial page and subsequent interaction.
- Document content can appear in the initial HTML.
- Browser code can handle inputs and editing.
- Data fetching and reuse need their own design.
An illustrative wiki page
A wiki could render its title, paragraphs, and references on the server while using client code for an editor. Separating those responsibilities helps identify which parts are necessary for reading and which depend on user interaction.
What SSR does not guarantee
HTML content is easier to inspect for clients that do not execute JavaScript. That does not guarantee search rankings or a fast response. Data access, network behavior, and the JavaScript needed for interaction still affect the reader’s experience and should be measured in the actual application.
Sources
Server-side rendering (SSR) — MDN Web Docs (2026-09-18)
Server and Client Components — Next.js (2026-09-18)