Cloudflare is launching Workers Cache, a regionally tiered cache that sits directly in front of Cloudflare Workers entrypoints. Enabled with a single Wrangler config line, it uses standard HTTP Cache-Control headers and Cache-Tag headers for configuration and invalidation. Key features include: automatic tiered caching (lower + upper tier) across Cloudflare's global network, stale-while-revalidate support so users never wait on cache refreshes, Vary header support for content negotiation, per-entrypoint cache control within a single Worker, and multi-tenant-safe cache keys via ctx.props. Cache hits skip Worker execution entirely, saving CPU billing. The feature composes with Smart Placement, Durable Objects, and service bindings, enabling architectures where a gateway Worker runs near the user while a cached backend Worker runs near the data. Astro already has built-in integration; other framework integrations are in progress. Available now on all plans at no additional cost beyond standard request rates.
Table of contents
Why server-rendered apps need a cache in frontstale-while-revalidate is the part that makes it feel instantOne URL, many representations: Vary worksThis is your Worker's cache, not your zone'sTwo tiers, every Worker, no configurationRun your app near the user and near the dataMulti-tenant by default, with ctx.propsA cache between every Worker entrypointFirst-class support in your frameworkSee your cache on the same dashboard as your WorkerBillingWhat's nextTry it114.6K Impressions4 Comments