--- title: vercel cache product: vercel url: /docs/cli/cache canonical_url: "https://vercel.com/docs/cli/cache" last_updated: 2026-08-11 type: reference prerequisites: - /docs/cli related: - /docs/caching/cdn-cache - /docs/caching/runtime-cache - /docs/caching/cdn-cache/purge summary: Learn how to manage cache for your project using the vercel cache CLI command. install_vercel_plugin: npx plugins add vercel/vercel-plugin --- # vercel cache The `vercel cache` command is used to manage the cache for your project, such as [CDN cache](/docs/caching/cdn-cache) and [Runtime cache](/docs/caching/runtime-cache). ## Related pages > **For AI agents:** Follow these links to understand how this page connects to the rest of the Vercel ecosystem. For the full cross-link map (inbound, outbound, prerequisites, and semantic neighbors), see the .graph.md link below. - [Add cache tags from Function responses, regardless of framework](https://vercel.com/changelog/add-cache-tags-from-function-responses-regardless-of-framework?from=related&source_path=%2Fdocs%2Fcli%2Fcache&source_site=vercel-docs&relationship=related) - [Invalidate the CDN cache by tag](https://vercel.com/changelog/invalidate-the-cdn-cache-by-tag?from=related&source_path=%2Fdocs%2Fcli%2Fcache&source_site=vercel-docs&relationship=related) - [Tag-based cache invalidation now available for all responses](https://vercel.com/changelog/tag-based-cache-invalidation-now-available-for-all-responses?from=related&source_path=%2Fdocs%2Fcli%2Fcache&source_site=vercel-docs&relationship=related) - [You can now invalidate the CDN cache by providing a source image](https://vercel.com/changelog/you-can-now-invalidate-the-cdn-cache-by-providing-a-source-image?from=related&source_path=%2Fdocs%2Fcli%2Fcache&source_site=vercel-docs&relationship=related) - [Manage cache tags for external origins](https://vercel.com/kb/guide/how-to-manage-cache-tags-for-external-origins?from=related&source_path=%2Fdocs%2Fcli%2Fcache&source_site=vercel-docs&relationship=related) — Learn how to use cache tags to optimally serve fresh content on Vercel when content from your external origin changes - [Diagnosing and fixing cache issues](https://vercel.com/docs/caching/cdn-cache/debug-cache-issues?from=related&source_path=%2Fdocs%2Fcli%2Fcache&source_site=vercel-docs&relationship=related) — Diagnose stale content and fix CDN cache, data cache, and build cache issues using the CLI. - [Invalidate by tag](https://vercel.com/docs/rest-api/edge-cache/invalidate-by-tag?from=related&source_path=%2Fdocs%2Fcli%2Fcache&source_site=vercel-docs&relationship=related) — POST /v1/edge-cache/invalidate-by-tags — Marks a cache tag as stale, causing cache entries associated with that tag to b - [Cache Status and Reasons](https://vercel.com/docs/caching/cache-status?from=related&source_path=%2Fdocs%2Fcli%2Fcache&source_site=vercel-docs&relationship=related) — Understand the cache status and reason shown for each request in Vercel logs, and what causes a response to miss, bypass - [Data Cache for Next.js](https://vercel.com/docs/caching/runtime-cache/data-cache?from=related&source_path=%2Fdocs%2Fcli%2Fcache&source_site=vercel-docs&relationship=related) — Vercel Data Cache is a specialized cache that stores responses from data fetches in Next.js App Router - [Dangerously delete by tag](https://vercel.com/docs/rest-api/edge-cache/dangerously-delete-by-tag?from=related&source_path=%2Fdocs%2Fcli%2Fcache&source_site=vercel-docs&relationship=related) — POST /v1/edge-cache/dangerously-delete-by-tags — Marks a cache tag as deleted, causing cache entries associated with tha Full cross-link map for this page: [/docs/cli/cache.graph.md](/docs/cli/cache.graph.md?from=related&source_path=%2Fdocs%2Fcli%2Fcache&source_site=vercel-docs&relationship=graph) Learn more about [purging Vercel cache](/docs/caching/cdn-cache/purge). ## Usage ```bash filename="terminal" vercel cache purge ``` *Using the \`vercel cache purge\` command to purge the CDN cache and Data cache for the current project.* ## Extended Usage ```bash filename="terminal" vercel cache purge --type cdn ``` *Using the \`vercel cache purge --type cdn\` command to purge the CDN cache for the currenet project.* ```bash filename="terminal" vercel cache purge --type data ``` *Using the \`vercel cache purge --type data\` command to purge the Data cache for the current project.* ```bash filename="terminal" vercel cache invalidate --tag blog-posts ``` *Using the \`vercel cache invalidate --tag blog-posts\` command to invalidate the cached content associated with tag "blog-posts" for the current project. Subsequent requests for this cached content will serve STALE and revalidate in the background.* ```bash filename="terminal" vercel cache dangerously-delete --tag blog-posts ``` *Using the \`vercel cache dangerously-delete --tag blog-posts\` command to dangerously delete the cached content associated with tag "blog-posts" for the current project. Subsequent requests for this cached content will serve MISS and therefore block while revalidating.* ```bash filename="terminal" vercel cache invalidate --srcimg /api/avatar/1 ``` *Using the \`vercel cache invalidate --srcimg /api/avatar/1\` command to invalidate all cached content associated with the source image "/api/avatar/1" for the current project. Subsequent requests for this cached content will serve STALE and revalidate in the background.* ```bash filename="terminal" vercel cache dangerously-delete --srcimg /api/avatar/1 ``` *Using the \`vercel cache dangerously-delete --srcimg /api/avatar/1\` command to dangerously delete all cached content associated with the source image "/api/avatar/1" for the current project. Subsequent requests for this cached content will serve MISS and therefore block while revalidating.* ```bash filename="terminal" vercel cache dangerously-delete --srcimg /api/avatar/1 --revalidation-deadline-seconds 604800 ``` *Using the \`vercel cache dangerously-delete --srcimg /api/avatar/1 --revalidation-deadline-seconds 604800\` command to dangerously delete all cached content associated with the source image "/api/avatar/1" for the current project if not accessed in the next 604800 seconds (7 days).* ## Unique Options These are options that only apply to the `vercel cache` command. ### tag The `--tag` option specifies which tag to invalidate or delete from the cache. You can provide a single tag or multiple comma-separated tags. This option works with both `invalidate` and `dangerously-delete` subcommands. ```bash filename="terminal" vercel cache invalidate --tag blog-posts,user-profiles,homepage ``` *Using the \`vercel cache invalidate\` command with multiple tags.* ### srcimg The `--srcimg` option specifies a source image path to invalidate or delete from the cache. This invalidates or deletes all cached transformations of the source image. This option works with both `invalidate` and `dangerously-delete` subcommands. You can't use both `--tag` and `--srcimg` options together. Choose one based on whether you're invalidating cached content by tag or by source image. ```bash filename="terminal" vercel cache invalidate --srcimg /api/avatar/1 ``` *Using the \`vercel cache invalidate\` command with a source image path.* ### revalidation-deadline-seconds The `--revalidation-deadline-seconds` option specifies the revalidation deadline in seconds. When used with `dangerously-delete`, cached content will only be deleted if it hasn't been accessed within the specified time period. ```bash filename="terminal" vercel cache dangerously-delete --tag blog-posts --revalidation-deadline-seconds 3600 ``` *Using the \`vercel cache dangerously-delete\` command with a 1-hour (3600 seconds) revalidation deadline.* ### Yes The `--yes` option can be used to bypass the confirmation prompt when purging the cache or dangerously deleting cached content. ```bash filename="terminal" vercel cache purge --yes ``` *Using the \`vercel cache purge\` command with the \`--yes\` option.* --- [View full sitemap](/docs/sitemap)