Client-side rendering
Client-side rendering is the generation or updating of a web interface in a user's browser by code executed there.
Fast by Default
Client-side rendering sends a minimal document to the browser and uses JavaScript to fetch data and construct the rendered interface.
- How it is used
- Frames rendering architecture as a performance decision affecting visibility, interaction timing, user experience, and SEO.
- How deep it goes
- Defines the browser-side sequence and trade-off, but stops short of implementation details beyond comparing rendering approaches.
- Examples
- Uses DoorDash mobile performance, a minimal HTML shell, JavaScript bundles, and LCP measurements.
- What you can do after
- Evaluate rendering choices against device capability, network conditions, initial visibility, and measured LCP.
Web Component Development with Modern Libraries and Tooling
Client-side rendering is the technique of generating or updating a web application's interface in the browser using client-executed code.
- How it is used
- Provides browser-rendered web component instances and handles interactivity and updates alongside server-rendered instances.
- How deep it goes
- Works through component markup, browser setup, shadow-root reuse, and event handling; concentrates on web components rather than general rendering algorithms.
- Examples
- Contrasts browser-rendered greetings and a color-selecting radio group with greetings and controls inserted from server responses.
- What you can do after
- Build it from scratch with a vanilla web component, or apply it via Lit or wrec alongside server rendering.
Vanilla Web
Client-side rendering is the generation or updating of a web interface in the user's browser using client-side code.
- How it is used
- Places most UI logic in the browser, commonly for single-page applications.
- How deep it goes
- Defines the division of work and names DOM APIs and network requests, without walking through an implementation.
- Examples
- Uses single-page applications and requests for content or authentication as concrete use cases.
- What you can do after
- Evaluate/understand where browser-side rendering fits among web application architectures.
Acing the Frontend Interview
Client-side rendering generates or updates the user interface in the browser using client-side JavaScript.
- How it is used
- Deploys browser-side JavaScript to create dynamic interfaces and seamless navigation in React applications.
- How deep it goes
- Defines CSR and compares it with SSR and SSG, but stops short of browser rendering internals.
- Examples
- Uses React Router examples featuring basic, nested, protected, parameterized, and fallback routes.
- What you can do after
- Apply it via React Router and evaluate CSR against SSR or SSG when designing scalable React applications.
Read how Acing the Frontend Interview explains client-side rendering →
Modern Angular
Client-side rendering is the generation of a web application's user interface in the browser rather than on the server.
- How it is used
- Deploys Angular single-page applications as browser-loaded bundles served from static hosting.
- How deep it goes
- Explains bundling, static delivery, and route-fallback configuration, but defers hosting-provider-specific configuration.
- Examples
- Uses an Angular HRMS application, an /products route, a dist folder, and the index.html fallback.
- What you can do after
- Operate deployment by building an Angular CSR application and configuring server fallback for direct routes.
Also covered in
Related concepts
- server-side renderingcontrasts with · A web-rendering technique in which a server generates a user interface’s markup or other rendered representation before delivering it to a client.
- Fetch APIuses · The Fetch API is a web-platform interface for making network requests and processing their responses asynchronously through promises.
- renderingkind of · Rendering is the process of producing a presentational representation or visual output from structured content, data, application state, or a scene.
- deploymentused by · Deployment is the process of placing or releasing software, models, or configuration into a target environment so they can operate there.
- single-page applicationused by · A single-page application is a web application that loads a document and dynamically updates its content or interface without full-page navigation for most interactions.
- frontendimplemented by · Frontend code is software that runs on a user's device and provides application presentation or interaction, often communicating with backend services.
Questions about client-side rendering
What is client-side rendering?
Client-side rendering is the generation or updating of a web interface in a user's browser by code executed there.
Which Manning books explain client-side rendering?
Fast by Default, Web Component Development with Modern Libraries and Tooling, Vanilla Web, Acing the Frontend Interview and Modern Angular.
What is the difference between client-side rendering and server-side rendering?
Client-side rendering is the generation or updating of a web interface in a user's browser by code executed there. A web-rendering technique in which a server generates a user interface’s markup or other rendered representation before delivering it to a client.
What is client-side rendering a kind of?
Client-side rendering is a kind of rendering. Rendering is the process of producing a presentational representation or visual output from structured content, data, application state, or a scene.
What is client-side rendering also called?
Client-side rendering is also called CSR.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.




