Your files stay on your device

Browser cache policy builder

Set Cache-Control rules per resource type, watch a timeline simulate browser and CDN freshness over your chosen horizon, catch contradictory directives, and copy Nginx, Apache, IIS, or Express config.

Simulate over

Add a rule per resource type, pick one to simulate, and the timeline shows when a stored response is fresh, stale while revalidating, salvageable on origin failure, or back at the origin.

Freshness follows RFC 9111: a browser lives on max-age, a shared cache prefers s-maxage, and no-cache means revalidate every use rather than do not cache. The simulation models one stored response. It says nothing about cache eviction, quota pressure, or Vary negotiation, and it cannot see what your servers actually send; paste a deployed header into the HTTP header parser to check the real thing.

Policy rules

Rule 1

Resource type

MatchFile extensions, or path prefixes starting with /

Cache-ControlEditable; picking a type refills a sensible start

Rule 2

Resource type

MatchFile extensions, or path prefixes starting with /

Cache-ControlEditable; picking a type refills a sensible start

Rule 3

Resource type

MatchFile extensions, or path prefixes starting with /

Cache-ControlEditable; picking a type refills a sensible start

Rule 4

Resource type

MatchFile extensions, or path prefixes starting with /

Cache-ControlEditable; picking a type refills a sensible start

More settings

API responses contain per-user dataShared caches must not store them

Simulate rule

4 of at most 12 rules. Rule ids are internal labels up to 64 characters.

All web & auth tools

Was this tool useful?

Browser cache policy builder

More web & auth tools