Layer 4: The Router Cache. This lives in the browser. When a user navigates between pages, Next.js stores the RSC payload for each visited route in client-side memory. Navigating back to a previously visited page uses this cached payload without a server request. It has a short automatic TTL — around 30 seconds for static data, 0 seconds for dynamic. But it can cause stale content to appear briefly when navigating back to a page you just invalidated on the server. [...] }) Layer 3: The Full Route Cache. This operates at the route level, not the data level. For static routes (routes with no dynamic data), Next.js caches the entire rendered HTML and RSC payload at build time or on first request. Subsequent requests are served from this cache instantly without re-rendering. Dynamic routes with cache: 'no-store' or noStore() bypass this layer entirely. [...] When content is stale, start at Layer 4 (router cache in browser, try navigating away and back), then check Layer 3 (did revalidatePath run?), then check Layer 2 (did revalidateTag clear the right tags?). If memory is growing, check Layer 2 for unbounded entries. That is the complete mental model. Everything else in the App Router caching docs is an elaboration of this structure.