The App Router's client cache holds the RSC payloads of prefetched and visited routes, keyed by segment, in the tab's memory. A reload empties it. How long an entry may be reused on a <Link> navigation is its stale time:
static, default 300 s: prerendered pages,loading.jsUI, and anything prefetched withprefetch={true}orrouter.prefetch().dynamic, default 0 s: a dynamic page you visited. Every new visit fetches it again. Legacy: this was 30 s until Next.js 15.0.
Both are set under experimental.staleTimes in next.config; the build lists it under "Experiments (use with caution)". The server sends the value with each response (x-nextjs-stale-time: 300). With Cache Components, a page's cacheLife stale sets it per route: a page with stale: 45 got x-nextjs-stale-time: 45.
Expiry is lazy. An expired prefetch is fetched again when the link is hovered; an expired page is fetched again when you navigate to it.
Back and Forward ignore stale times. They restore what was on screen from memory, even a dynamic page with dynamic: 0.
The cache is emptied, not just for the route touched, when a Server Action calls revalidatePath or updateTag or sets a cookie: visible links were prefetched again straight away. router.refresh() did the same for their page segments. The cacheLife docs also list an action's refresh(), but in the mutations chapter's test it caused no new prefetches.
I checked these on Next.js 16.4.5 under next start, with Cache Components on and off (the same results), in Chrome 156 and Firefox 159. Expiry timings ran in Chrome only.