framecache.
A small utility for the open web

Know what
stays fresh.

Less guesswork between a request and a response. Unpack cache policies for images, media, and everything in between.

Inspect a cache policy

No account. No requests sent. Just the headers.

RESPONSE / 001Fresh
cache-controlpublic, max-age=3600
Ready to reuse01:00:00
A LITTLE CLARITY. A FASTER NEXT REQUEST.
01 /

Read the policy

Turn compact response headers into useful, plain-language signals.

02 /

Check the clock

Compare freshness lifetime with response age, in one place.

03 /

Keep it local

Your input stays in this tab. Nothing is uploaded or fetched.

THE WORKBENCH

A policy, made readable.

How to read the results
INPUTHTTP response headers

Paste the value, or the full Cache-Control header line.

Use the response Age value for a quick snapshot. See notes for exact timing.

Try:
READOUTFresh

Freshness remaining

58 min
120s elapsed3,600s lifetime

This shared cache can reuse the response while it stays fresh.

Effective directive
max-age=3600
Stale allowance
60s, while revalidating
Storage
Permitted by this policy

Policy estimate only. Other headers and cache rules can affect reuse.

A HANDY REFERENCE

Headers are small.
The details matter.

Freshness, storage, and validation are different questions. Our field notes explain the directives, their limits, and what to check next.

Read the field notes