Partial hydration
Partial hydration is a rendering technique that attaches client-side behavior only to selected interactive regions of server-rendered content.
Fast by Default
Islands architecture renders mostly static content without JavaScript and hydrates only isolated components that require interactivity.
- How it is used
- Uses progressive rendering to reduce client-side hydration blocking by hydrating only interactive components.
- How deep it goes
- Defines selective hydration and compares trade-offs, but stops short of implementation code or framework-specific setup.
- Examples
- Contrasts all-at-once rendering with independently hydrated components using a rendering comparison table and architecture figure.
- What you can do after
- Evaluate rendering trade-offs using hydration behavior, blocking characteristics, and architectural constraints.
Vanilla Web
Islands architecture is a rendering pattern in which mostly static server-rendered HTML contains independently hydrated interactive regions.
- How it is used
- Limits client-side JavaScript on mostly static, server-rendered pages by hydrating only interactive regions.
- How deep it goes
- Defines independent hydration and compares rendering models, but does not provide hydration code or an implementation procedure.
- Examples
- Uses custom elements as possible island boundaries and names Astro and Eleventy as frameworks associated with the model.
- What you can do after
- Evaluate/understand it as an option for reducing browser JavaScript while retaining selected interactive regions.
Also covered in
Related concepts
- hydrationcontrasts with · Hydration is the client-side process of attaching application behavior, state, and interactivity to previously rendered user-interface markup.
- progressive renderingkind of · Progressive rendering is the incremental processing and display of independently available interface content rather than waiting for the complete result.
- Next.jsused by · Next.js is a React-based web application framework that provides features such as routing, rendering strategies, server-side capabilities, and build tooling.
- Web Componentsuses · Web Components are browser standards and APIs, including custom elements and shadow DOM, for creating reusable web interface elements with encapsulated structure, presentation, and behavior.
- server-side renderinguses · A web-rendering technique in which a server generates a user interface’s markup or other rendered representation before delivering it to a client.
- React Server Componentsuses · React Server Components are React components whose rendering and data-access work occurs on the server, providing results to clients without sending their implementation to the browser.
Questions about partial hydration
What is partial hydration?
Partial hydration is a rendering technique that attaches client-side behavior only to selected interactive regions of server-rendered content.
Which Manning books explain partial hydration?
Fast by Default and Vanilla Web.
What is the difference between partial hydration and hydration?
Partial hydration is a rendering technique that attaches client-side behavior only to selected interactive regions of server-rendered content. Hydration is the client-side process of attaching application behavior, state, and interactivity to previously rendered user-interface markup.
What is partial hydration a kind of?
Partial hydration is a kind of progressive rendering. Progressive rendering is the incremental processing and display of independently available interface content rather than waiting for the complete result.
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.

