Caching and Revalidating Data in Next.js – Optimizing Performance with fetch, unstable_cache, and Smart Tags

Next.js provides powerful tools for caching and revalidating data. This article explains how to cache fetch requests, use unstable_cache for async functions, and apply revalidatePath, revalidateTag, and updateTag to selectively refresh data. These techniques help improve performance and deliver fresh content without rebuilding entire routes.

updateTagrevalidateTagunstable_cachedata caching

~2 min read · Updated Oct 25, 2025

Introduction


Caching stores the result of data fetching or computation to serve future requests faster. Revalidation updates cached data without rebuilding the entire application, ensuring freshness and performance.


Caching with fetch


By default, fetch requests are not cached. To enable caching, use cache: 'force-cache':


await fetch('https://...', { cache: 'force-cache' })

To revalidate data after a specific time, use next.revalidate:


await fetch('https://...', { next: { revalidate: 3600 } })

Caching async functions with unstable_cache


unstable_cache caches the result of async functions like database queries:


const getCachedUser = unstable_cache(
  async () => getUserById(userId),
  [userId],
  {
    tags: ['user'],
    revalidate: 3600,
  }
)

You can define tags and revalidation intervals for fine-grained control.


Revalidating with revalidateTag


revalidateTag refreshes cache entries by tag. Use 'max' for stale-while-revalidate behavior:


revalidateTag('user', 'max')

To tag fetch requests:


await fetch('https://...', { next: { tags: ['user'] } })

Or tag unstable_cache functions:


unstable_cache(..., ['user'], { tags: ['user'] })

Revalidating routes with revalidatePath


Use revalidatePath to refresh a specific route after a data mutation:


revalidatePath('/profile')

Immediate expiration with updateTag


updateTag is used in Server Actions to immediately expire cache entries. Ideal for read-your-own-writes scenarios:


updateTag('posts')
updateTag(`post-${post.id}`)

Key differences:

  • updateTag: Server Actions only, immediate expiration
  • revalidateTag: Server Actions and Route Handlers, supports stale-while-revalidate

Conclusion


With smart caching and targeted revalidation in Next.js, you can optimize performance, serve fresh data quickly, and avoid unnecessary route rebuilds. Tools like unstable_cache, revalidateTag, and updateTag give you precise control over cache behavior and data freshness.


Written & researched by Dr. Shahin Siami

Related Articles

Advanced Client-Side Routing and Performance Hooks in Next.js

Next.js provides a rich set of client-side hooks and caching utilities that empower developers to build dynamic, responsive, and secure applications. From reading route parameters to tracking navigation state and reporting performance metrics, this guide walks you through the most important tools available in the App Router.

Continue

Handling Authorization and Caching in Next.js: A Developer’s Guide

Next.js introduces powerful experimental features for access control and smart caching. This guide covers the unauthorized() function for custom 401 handling, unstable_cache for persistent memoization, updateTag for instant cache invalidation, and useLinkStatus for inline navigation feedback. Learn how to use these tools to build secure, performant, and responsive applications.

Continue

redirect and refresh in Next.js — Smart Redirects and Client Refreshing via Server Actions

The redirect function in Next.js allows you to navigate users to a new route, returning either a 307 or 303 HTTP response depending on context. It works in Server Components, Client Components, Route Handlers, and Server Actions. The refresh function is used exclusively within Server Actions to refresh the client router. This article explains how both functions work, with practical examples and key considerations.

Continue

NextRequest and NextResponse in Next.js — Managing Cookies, Headers, Redirects, and Rewrites

Next.js extends the native Web Request and Response APIs with NextRequest and NextResponse, offering powerful tools for managing cookies, headers, redirects, rewrites, and JSON responses. These utilities simplify server-side logic and improve control over routing, personalization, and security. This guide walks through their capabilities with practical examples and best practices.

Continue

headers, ImageResponse, notFound, and permanentRedirect in Next.js — Request Handling, Dynamic Images, Errors, and Redirects

Next.js offers powerful tools for handling HTTP requests and responses in Server Components. The headers function lets you read incoming request headers. ImageResponse allows you to generate dynamic images using JSX and CSS. The notFound function renders a custom 404 page, and permanentRedirect enables permanent redirection to another route. This article explains how to use each feature with practical examples.

Continue

A Complete Guide to Using metadata and generateMetadata in Next.js

In modern versions of Next.js, managing page metadata is more powerful and intuitive than ever. Metadata is automatically injected into the <head> of your pages and plays a vital role in SEO, social sharing, and user experience. This guide explains the two main ways to define metadata: using the static metadata object and the dynamic generateMetadata function.

Continue