
Cloudflare launches Workers Cache to cut CPU work for edge apps
Cloudflare Workers Cache adds a tiered cache in front of Worker entrypoints to reduce CPU work for edge apps.
Cloudflare has launched Workers Cache, a new caching layer designed specifically for applications where a Cloudflare Worker is the origin rather than a small script in front of a separate origin server. The company says the feature is available now for every Worker on any plan and can be enabled from Wrangler with a short cache configuration block.
The change is aimed at a common problem in server-rendered edge applications: every page request can invoke application code even when the result is identical to a recent response. With Workers Cache enabled, Cloudflare checks a regional, tiered cache before running the Worker. A cache hit returns the stored response directly, while a miss runs the Worker once and can store the cacheable response for later requests. That means hot pages and API reads can avoid CPU time while still being generated by application code when needed.
Why it matters
Cloudflare's announcement frames the release as a shift from zone-level CDN rules toward a cache owned by the Worker itself. Developers control behavior with standard HTTP headers such as Cache-Control, including stale-while-revalidate, and can purge cached responses by tag or path prefix from Worker code. The company also says the cache is tiered across its network by default, so a request in one region can populate an upper tier that later helps serve traffic from other locations without re-running the Worker.
The most notable developer feature is that the cache can sit in front of more than just a public Worker URL. Cloudflare says Workers Cache applies to Worker entrypoints, service bindings and internal calls through ctx.exports, giving teams a way to cache expensive parts of an application while keeping gateways, authentication checks and routing code uncached. For multi-tenant applications, the company says ctx.props can become part of the cache key so responses for different users or tenants remain isolated.
- Cloudflare says Workers Cache is available now through Wrangler for Workers on any plan.
- Astro has first-class support through its Cloudflare adapter, with other framework integrations in progress.
- The system supports standard content negotiation through the
Varyheader and programmatic cache invalidation.
The release gives Cloudflare a more integrated answer to incremental static rendering and edge-side API caching. Developers still need to set correct cache headers and avoid caching private data accidentally, but the new model reduces the need to bolt on separate CDN rules for applications already built around Workers.
Sources
Cover photo by Brett Sayles on Pexels, used under the Pexels License.
CyberOGZ Team






Comments (0)
Leave a Comment