Hydration mismatch in Next.js App Router when server-rendered content diverges from client render
The Problem Next.js documents hydration mismatch failures when server-rendered HTML differs from the initial client render. This commonly occurs when components use non-deterministic values like Date.now() , random IDs, or browser-only APIs accessed during render. The core issue is that developers often forget to handle the server/client boundary correctly.
nextjs