After a server-rendered page arrives, its scripts “hydrate” it: they connect event handlers and state to the existing HTML so it becomes interactive, without rebuilding the content.
Example
A tabbed panel shows its first tab as plain HTML. Once hydrated, clicking another tab switches the panel.
Why it matters
Hydration lets a page be readable without scripts and interactive with them. Problems arise when the hydrated page differs from the server HTML, or when important text only exists after hydration.