Next.js Fetch Caching Serving Stale Data
Your Next.js fetch requests cache data too aggressively, serving stale information even after cache revalidation. Updated data doesn't appear, users see outdated content.
Fetch caching issues occur when cache options aren't set correctly, revalidate tags aren't applied, or browser cache conflicts with Next.js caching.
Error Messages You Might See
Common Causes
- Using default fetch cache without explicit revalidate time
- Revalidate time set too high, keeping stale data too long
- Not using revalidateTag() for on-demand revalidation
- Browser cache conflicting with Next.js cache (Set-Cookie, Cache-Control headers)
- ISR not triggering revalidation properly on deployment
How to Fix It
Set revalidation: Control cache duration:fetch(url, { next: { revalidate: 3600 } }) caches 1 hour. Use 0 for no cache.
Use revalidateTag(): For on-demand updates:fetch(url, { next: { tags: ['posts'] } })
// In server action: revalidateTag('posts')
Disable cache for dynamic data: const data = await fetch(url, { cache: 'no-store' }) always fetches fresh.
Check headers: Ensure Cache-Control header set correctly. Vercel sets cache headers automatically, don't override.
Real developers can help you.
Mehdi Ben Haddou
- Founder of Chessigma (1M+ users) & many small projects
- ex Founding Engineer @Uplane (YC F25)
- ex Software Engineer @Amazon and @Booking.com
Matt Butler
Software Engineer @ AWS
BurnHavoc
Been around fixing other peoples code for 20 years.
AUXLE
I am a Full Stack Developer experienced in building Websites, Web apps and Cross Platform Mobile Apps for Startups and Companies.
Taufan
I’m a product-focused engineer and tech leader who builds scalable systems and turns ideas into production-ready platforms.
Over the past years, I’ve worked across startups and fast-moving teams, leading backend architecture, improving system reliability, and shipping products used by thousands of users. My strength is not just writing code — but connecting product vision, technical execution, and business impact.
PawelPloszaj
I'm fronted developer with 10+ years of experience with big projects. I have small backend background too
Anthony Akpan
Developer with 8 years of experience building softwares fro startups
legrab
I'll fill this later
Bastien Labelle
Full stack dev w/ 20+ years of experience
Kingsley Omage
Fullstack software engineer passionate about AI Agents, blockchain, LLMs.
You don't need to be technical. Just describe what's wrong and a verified developer will handle the rest.
Get HelpFrequently Asked Questions
What's the default fetch cache behavior?
By default, Next.js caches fetch results at build time. Use revalidate option to refresh periodically.
How do I invalidate cache immediately?
Use revalidateTag() in server action after mutation: revalidateTag('posts'). Cache invalidates immediately across all pages using that tag.
Should I use cache: 'no-store'?
Only for user-specific data or real-time updates. For public data, use ISR with revalidate time for better performance.