Pushes content changes from Payload to open pages without a reload
Cache plugins for Payload CMS 17
Cache Payload CMS reads in Redis or around the Local API. Revalidate the Next.js tags and paths that show a document as soon as it changes.
Managed redirects with cache-backed Next.js middleware and an orderable admin list
Moves frontend translation keys into the Payload database for editors to manage
Revalidates Next.js paths and cache tags when documents are published or deleted
Background jobs for scheduled publishing, cache revalidation and approval expiry
Revalidates Next.js cache tags for documents and their related content on save
Next.js cache revalidation that clears only the tags a Payload change touches
Generates chunked, cached XML sitemaps for Payload collections with cache invalidation on save
Manages site styling from the Payload admin with design sets, shortcuts and tokens
Cache revalidation hooks and Next.js helpers for Atomic Payload projects
Caches Payload database reads in Redis and clears them on writes
Stores interface strings as a Payload global with automatic string collection
Clears Next.js server cache when Payload documents change in chosen collections
Caches local Payload reads for pages and clears them on content changes
Caches Payload API responses in Redis, keyed by user and request URL
Caches Payload API responses in Redis and clears them when content changes
Appends a content hash to uploaded filenames so CDN caching can run longer
About these packages
Cache plugins sit between Payload and the pages that read from it. Some cache database or Local API reads and clear them on writes. Others run when a document changes and revalidate the Next.js tags or paths that show it.
What these plugins cover
- Redis Cache for Payload database reads, cleared on writes
- Cached Local API for caching reads made through the Local API
- Revalidate and Smart Cache for targeted Next.js tag revalidation
- ISR Revalidation and Next Cache Revalidate for paths and endpoints
- Older Redis Cache packages that cache REST API responses
- Atomic Core with cache helpers and a revalidation plugin
Choosing a cache plugin
Find out what is slow first. If the frontend is a Next.js app and pages go stale, Revalidate or Smart Cache is usually enough. Smart Cache also follows related documents. If the database is the bottleneck, use Redis Cache with its own Redis instance. Cached Local API does the same for Local API calls. Several packages share the name Redis Cache, so check the supported Payload version on each card. A cache backend for Payload itself is a different thing, and you will find it among the cache adapters.
Frequently asked questions
How do I revalidate Next.js pages when Payload content changes?
Install Revalidate, Smart Cache or ISR Revalidation. When a document changes, the plugin revalidates the Next.js cache tags or paths tied to it, so you don't write those hooks yourself.
Can I use Redis as a cache for Payload CMS?
Yes. Redis Cache stores Payload database reads in Redis and clears them on writes. Some older packages with the same name cache REST API responses instead, so check the supported version on their cards.
Do I need Redis or Next.js revalidation for Payload?
It depends on what is slow. Revalidation plugins clear the Next.js cache for pages that show a changed document, which fixes stale pages. Redis Cache or Cached Local API store query results, so repeat reads skip the database.



