revalidatePath

revalidatePath allows you to invalidate cached data on-demand for a specific path.

Usage

revalidatePath can be called in Server Functions and Route Handlers.

revalidatePath cannot be called in Client Components or Proxy, as it only works in server environments.

Parameters

revalidatePath(path: string, type?: 'page' | 'layout'): void;

• path: Either a string that represents your route file structure. This can be a literal path like /product/123, or a route pattern with dynamic segments like /product/[slug]. Do not append /page or /layout, use the type parameter instead. Must not exceed 1024 characters. This value is case-sensitive. You do not need to include a trailing slash, regardless of your trailingSlash config.
• type: (optional) 'page' or 'layout' string to change the type of path to revalidate. If path contains a dynamic segment, for example /product/[slug], this parameter is required. If path is a literal path like /product/1, omit type.

Use a literal path when you want to refresh a single page. Use a route pattern plus type to refresh all matching pages.

Returns

revalidatePath does not return a value.

What can be invalidated

The path parameter can point to pages, layouts, or route handlers:

• Pages: Invalidates the specific page
• Layouts: Invalidates the layout (the layout.tsx at that segment), all nested layouts beneath it, and all pages beneath them
• Route Handlers: Invalidates Data Cache entries accessed within route handlers. For example revalidatePath("/api/data") invalidates this GET handler:

export async function GET() {
  const data = await fetch('https://api.vercel.app/blog', {
    cache: 'force-cache',
  })
 
  return Response.json(await data.json())
}

Using revalidatePath with rewrites

When using rewrites, you must pass the destination path (the actual route file location), not the source path that appears in the browser's address bar.

For example, if you have a rewrite from /blog to /news:

module.exports = {
  async rewrites() {
    return [
      {
        source: '/blog',
        destination: '/news',
      },
    ]
  },
}

To revalidate this page, use the destination path:

// Correct: use the destination path
revalidatePath('/news')
 
// Incorrect: the source path won't match the cache entry
revalidatePath('/blog')

This is because revalidatePath operates on the route file structure, not the URL visible to users. Cache entries are tagged based on which route file renders them.

Relationship with revalidateTag and updateTag

revalidatePath, revalidateTag and updateTag serve different purposes:

• revalidatePath: Invalidates a specific page or layout path
• revalidateTag: Marks data with specific tags as stale. Applies across all pages that use those tags
• updateTag: Expires data with specific tags. Applies across all pages that use those tags

When you call revalidatePath, only the specified path gets fresh data on the next visit. Other pages that use the same data tags will continue to serve cached data until those specific tags are also revalidated:

// Page A: /blog
const posts = await fetch('https://api.vercel.app/blog', {
  next: { tags: ['posts'] },
})
 
// Page B: /dashboard
const recentPosts = await fetch('https://api.vercel.app/blog?limit=5', {
  next: { tags: ['posts'] },
})

After calling revalidatePath('/blog'):

• Page A (/blog): Shows fresh data (page re-rendered)
• Page B (/dashboard): Still shows stale data (cache tag 'posts' not invalidated)

Learn about the difference between revalidateTag and updateTag.

Building revalidation utilities

revalidatePath and updateTag are complementary primitives that are often used together in utility functions to ensure comprehensive data consistency across your application:

'use server'
 
import { revalidatePath, updateTag } from 'next/cache'
 
export async function updatePost() {
  await updatePostInDatabase()
 
  revalidatePath('/blog') // Refresh the blog page
  updateTag('posts') // Refresh all pages using 'posts' tag
}

This pattern ensures that both the specific page and any other pages using the same data remain consistent.

Examples

Revalidating a specific path

import { revalidatePath } from 'next/cache'
revalidatePath('/blog/post-1')

This will invalidate one specific path for revalidation on the next page visit.

Revalidating a Page path

import { revalidatePath } from 'next/cache'
revalidatePath('/blog/[slug]', 'page')
// or with route groups
revalidatePath('/(main)/blog/[slug]', 'page')

This will invalidate any path that matches the provided page file for revalidation on the next page visit. This will not invalidate pages beneath the specific page. For example, /blog/[slug] won't invalidate /blog/[slug]/[author].

Revalidating a Layout path

import { revalidatePath } from 'next/cache'
revalidatePath('/blog/[slug]', 'layout')
// or with route groups
revalidatePath('/(main)/post/[slug]', 'layout')

This will invalidate any path that matches the provided layout file for revalidation on the next page visit. This will cause pages beneath with the same layout to be invalidated and revalidated on the next visit. For example, in the above case, /blog/[slug]/[another] would also be invalidated and revalidated on the next visit.

Revalidating all data

import { revalidatePath } from 'next/cache'
 
revalidatePath('/', 'layout')

This will purge the Client-side Router Cache, and invalidate the Data Cache for revalidation on the next page visit.

Server Function

'use server'
 
import { revalidatePath } from 'next/cache'
 
export default async function submit() {
  await submitForm()
  revalidatePath('/')
}

Route Handler

import { revalidatePath } from 'next/cache'
import type { NextRequest } from 'next/server'
 
export async function GET(request: NextRequest) {
  const path = request.nextUrl.searchParams.get('path')
 
  if (path) {
    revalidatePath(path)
    return Response.json({ revalidated: true, now: Date.now() })
  }
 
  return Response.json({
    revalidated: false,
    now: Date.now(),
    message: 'Missing path to revalidate',
  })
}