# React Hydration Mismatch: Every Cause and Fix (2026) A React hydration mismatch happens when your server-rendered HTML differs from what React renders on its first client pass. React logs one error with a diff, then discards the server HTML from the nearest Suspense boundary down and re-renders it. Fix the divergence rather than silencing the warning. ## TL;DR React's own documentation is blunt about this: "You should treat mismatches as bugs and fix them."[^hydrateroot] Between them, the React and Next.js docs name nine causes — invalid HTML nesting, `typeof window` branches in render, browser-only APIs read during render, time-dependent APIs, browser extensions, CSS-in-JS misconfiguration, edge proxies that rewrite HTML, stray whitespace around the React root, and simply rendering different data on each side.[^nexterr][^hydrateroot] Since React 19 you get a single console error containing a `+ Client` / `- Server` diff, which usually points straight at the offending element.[^react19] The fix is almost never `suppressHydrationWarning`. That prop silences one element, one level deep, and React explicitly will not patch that element's mismatched text.[^hydrateroot] Everything below is written against `react@19.2.8` and `next@16.3.0`, the releases carrying the `latest` npm tag as of August 2026.[^npmreact][^npmnext] ## What you'll learn - What the "Hydration failed because the server rendered HTML didn't match the client" message actually means - The full documented cause list, straight from the React and Next.js docs - How to find the component responsible using React's diff - Why browser extensions still break hydration in React 19, despite the improvements - Whether `suppressHydrationWarning` fixes anything, and when it is the right call - How to render client-only content correctly, with `useEffect` versus `useSyncExternalStore` - How to stop dates, times, and locales from diverging between server and client - Why `next/dynamic` with `ssr: false` throws in the App Router - Why `useId` values can diverge between server and client - Whether a CDN or edge proxy can be the culprit - What a hydration mismatch costs you in production ## What does "Hydration failed because the server rendered HTML didn't match the client" mean? It means React attached to server-generated HTML, rendered your component tree once in the browser, and got a different result. Hydration is the step where React "converts the prerendered HTML from the server into a fully interactive application by attaching event handlers."[^nexterr] When the two renders disagree, React cannot safely attach those handlers to the existing DOM, so it discards the server HTML and re-renders on the client. The blast radius is larger than most people expect. React unwinds to the nearest Suspense boundary above the mismatch and client-renders from there; with no boundary above it, that means discarding the server HTML for the whole root.[^rfc] React's own release notes describe the same outcome from the other direction, referring to what happens "if React needs to re-render the entire document due to an unrelated hydration mismatch."[^react19] Before React 19 this surfaced as a pile of separate warnings — `Warning: Text content did not match. Server: "Server" Client: "Client"`, followed by `Warning: An error occurred during hydration. The server HTML was replaced with client content in

.`, followed by a thrown error.[^react19] React 19 collapsed all of that into one message: ```text Uncaught Error: Hydration failed because the server rendered HTML didn't match the client. As a result this tree will be regenerated on the client. This can happen if an SSR-ed Client Component used: - A server/client branch `if (typeof window !== 'undefined')`. - Variable input such as `Date.now()` or `Math.random()` which changes each time it's called. - Date formatting in a user's locale which doesn't match the server. - External changing data without sending a snapshot of it along with the HTML. - Invalid HTML tag nesting. It can also happen if the client has a browser extension installed which messes with the HTML before React loaded. https://react.dev/link/hydration-mismatch ``` That bullet list is not generic advice — it is React telling you which five buckets to check first.[^react19] ## What causes a React hydration mismatch? Next.js publishes a numbered list of seven causes on its error page for this message. React's `hydrateRoot` reference publishes a shorter list of four, two of which overlap with Next.js and two of which are additions.[^nexterr][^hydrateroot] Take the union and you get nine. Causes 1–7 below are Next.js's list in its own order, causes 8 and 9 are React's additions, and the right-hand column is our own diagnostic shorthand rather than anything either document says: | # | Cause (from the docs) | Typical tell (ours) | |---|-------|--------------| | 1 | Invalid HTML nesting — `

` or `

`, `` inside ``, `

#suppresshydrationwarning

React Hydration Mismatch: Every Cause and Fix (2026)