Cache and revalidation tab
Cache lifetime, lazy invalidation, what updates when you edit a post, scheduled revalidation, workers, browser cache, Cloudflare and object cache.
TurboCache → Settings → Cache and revalidation controls how long pages live, what happens when content changes and how the cache talks to browsers, CDNs and your host.
Cache
- Cache lifetime (default 60 days) — after this a page is refreshed. Content changes trigger updates anyway, so a long lifetime is safe.
- Cleanup timeout (default 182 days) — entries nobody requested for this long are deleted from disk by the hourly cleanup.
- Lazy invalidation (default on) — serve the existing page while the updated one is prepared in the background (header
STALE). Turn off if visitors must see edits instantly; they then get an unoptimised page until optimisation completes. - Forced updates show original (default off; shown when lazy invalidation is on) — on a content update, delete the page so the fresh, unoptimised version shows immediately. This is the wizard’s “Always up-to-date content” choice.
- Automatic processing (default on) — rebuild expired and deleted pages in the background without waiting for a visitor.
- Encodings (default: gzip and Brotli on) — store pre-compressed copies, served as-is. Brotli needs the PHP brotli extension.
- Logged-in users (default off) — cache pages for logged-in visitors too. Only when members see identical markup; never for shops or membership dashboards. For per-user caching use Per-user cache instead.
- 404 pages (default off) — cache “Not found” pages.
Revalidation
- On post update (default on) — update the cache when a post, page, product or comment changes.
- Operation (default Revalidate) — Revalidate rebuilds in the background; Delete removes the page so the next visitor triggers the rebuild.
- Dependent pages — which pages update together with the changed post. Defaults: the post itself, front page / blog page, post type and date archives, category / tag / taxonomy archives (and parents) on; author archive and feed off. A changed WooCommerce product also refreshes the shop page.
- Global changes — Menus (default on) and Term edits (default off) refresh the whole site. Saving the Customizer, switching theme, changing permalinks, the site title or widgets, updating anything, and activating or deactivating a plugin also refresh the whole site.
The Divi Theme Builder templates, options, Customizer checkbox is stored but, in version 2.1.0, Divi refreshes are controlled by Purge hooks on the CDN and advanced tab, and Customizer saves always refresh the site.
Scheduled update
- Daily revalidation (default off) — run an operation over the whole site every day.
- Time (default 03:00, site timezone) and operation: Revalidate, Revalidate if needed or Delete.
Processing
- Parallel processes (default 1, 1–8) — background workers optimising at once. 1 for shared hosting, 2 for a VPS, 4 for dedicated servers.
- Pause between pages (default 5 seconds, 0–60) — eases load on weak hosting.
- Worker time limit (default 570 seconds, 30–3600).
Browser and server caching
- Browser cache (default on, 365 days) — tells browsers to keep CSS, JS, fonts, images, PDF and video. Written to
.htaccesson Apache/LiteSpeed when you save; on Nginx include the generated snippet shown under the option. - Cache-Control for CDN (default on, 3600 seconds) — cached pages are sent with
public, max-age=0, s-maxage=3600so edge caches such as Cloudflare or Varnish can keep them while browsers always revalidate. - Conditional requests (default off) — send an ETag and answer
304 Not Modified.
Server’s cache
- Purge server caches (default on) — whenever TurboCache’s cache changes, also purge the layers it detects: Cloudflare (with credentials), LiteSpeed Cache, Nginx Helper, SiteGround, WP Engine, Kinsta, Pantheon, Cloudways Breeze, GoDaddy Managed WordPress, Varnish and a persistent object cache. The detected list is shown under the option.
- Cloudflare zone ID and Cloudflare API token — a token with the “Zone → Cache Purge” permission. Select Test to check it. Once saved, the token is never shown again: the field stays empty with a “Saved” note. Leave it blank to keep the saved token, type a new one to replace it, or tick Remove saved token to delete it.
Object cache
- Persistent object cache (default off) — installs a file-based
wp-content/object-cache.phpdrop-in that keeps options, terms and query results between requests, no Redis needed. Skip it if your host already provides Redis or Memcached; an existing object-cache drop-in from another plugin stays in charge. - Object lifetime (default 1 day) — for objects WordPress stores without an expiry.
- Memory-only groups — cache groups never written to disk, one per line. Core groups comment, counts, plugins and themes are built in.
Did this answer the question? No — open a support request