Cache-Control Builder

Build HTTP Cache-Control headers visually and inspect TTL directives.

Environment Presets

Directives configuration

no-storeNever store response in any cache. Overrides other directives.

no-cacheMust revalidate stale responses with the origin server before serving.

publicAllows responses to be stored by shared caches (CDNs, edge proxies).

privateResponse is user-specific. Block shared caches/CDNs from storing.

must-revalidateOnce stale, cache cannot serve response without server confirmation.

proxy-revalidateLike must-revalidate but strictly applies to shared/proxy caches.

immutableResponse body is immutable. Never validate with server within max-age.

max-age

s-maxage

stale-while-revalidate

stale-if-error

Directives Count2 directives

Cache ScopePublic

Max-Age TTL1d

RevalidationNo

Live Preview

Full HTTP Header

Cache-Control: public, max-age=86400

Value Only

public, max-age=86400

Example HTTP Response

HTTP/1.1 200 OK
Content-Type: text/html; charset=utf-8
Cache-Control: public, max-age=86400

Cache-Control Builder — generate HTTP cache directives interactively

The Cache-Control HTTP header controls how browsers, CDNs, and proxy caches store your responses. The most common directives are max-age (how long in seconds a cached response is fresh), no-store (never cache at all — for sensitive data), and no-cache (always revalidate before serving). Use public to allow CDN caching and private for user-specific responses. The immutable directive is ideal for content-hashed static assets — it prevents browsers from issuing conditional revalidation requests during the max-age window, giving you the fastest possible cache performance.

Private & free — this tool runs entirely in your browser.