hardSystem Design

What changed about caching defaults in Next.js 15?

Q: What changed about caching defaults in Next.js 15?

**TL;DR.** Next.js 15 made caching **opt-in rather than aggressive-by-default**: fetch and GET Route Handlers are **no longer cached** by default, and the client **Router Cache no longer reuses page segments** by default ( staleTime 0). You now opt **into** caching explicitly when you want it. Next 14 fetch cached by default Router reuses segments surprising staleness N

1.0k views

Understand the problem

Less aggressive caching out of the box.

nextjscachingnext-15defaults

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

Opt back into caching in Next 15

// Next 15: fetch is NOT cached by default — opt in explicitly:
await fetch('/api/posts', { next: { revalidate: 60 } });   // ISR
await fetch('/api/config', { cache: 'force-cache' });       // persist

// Cache a GET Route Handler:
// app/api/posts/route.ts
export const dynamic = 'force-static';

Join the discussion

Discussion (0)

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

What are React Server Components and why does Next.js use them?

How do you handle instrumentation and observability in Next.js (instrumentation.ts)?