mediumFrontend

How does fetch caching work in the Next.js App Router (force-cache, no-store, revalidate)?

Q: How does fetch caching work in the Next.js App Router (force-cache, no-store, revalidate)?

**TL;DR.** fetch options control the **Data Cache**: { cache: 'force-cache' } caches indefinitely, { cache: 'no-store' } never caches (makes the route dynamic), and { next: { revalidate: N } } caches but **revalidates after N seconds** (ISR). next: { tags } enables **on-demand** invalidation. force-cache cache forever revalidate: N ISR every Ns <text c

908 views

Understand the problem

Controlling the Data Cache per fetch call.

nextjsfetchcachingrevalidate

Attempt it yourself

Sketch your approach before reading the solution — that's what interviews test.

Stuck? AI Nudge Available

Get a conceptual hint to guide your logic without spoiling the final implementation.

Study the solution

The solution is waiting

Give it an honest attempt first — then compare your thinking with the full walkthrough.

Read the code

Three caching intents

// stable reference data — cache forever
await fetch('https://api/countries', { cache: 'force-cache' });

// blog list — refresh at most every 10 min (ISR), taggable
await fetch('https://api/posts', { next: { revalidate: 600, tags: ['posts'] } });

// per-request/personalized — never cache (route becomes dynamic)
await fetch('https://api/me', { cache: 'no-store' });

Join the discussion

Discussion (0)

No responses yet. Be the first to share what you think.

How do you analyze and reduce bundle size in Next.js?

How do you fetch data in Next.js Client Components (SWR, React Query, use)?