Asset Filename Cache Busting Checker
Compare manifest hashes and filenames; flag changed content with unchanged cache keys.
A clear result starts here
Add your input or try the worked example.
Using Asset Filename Cache Busting Checker
Compare manifest hashes and filenames; flag changed content with unchanged cache keys.
- Use Try example to explore asset filename cache busting checker, or enter your own asset history csv / json.
- Review the input format and the scope note before processing.
- Choose Review input and inspect the result, including any review flags or unsupported cases.
- Use the relevant download buttons to keep your result. CSV and report JSON preserve the available findings; original files are not changed.
Example
Asset history CSV / JSON: old_url,new_url,old_hash,new_hash,cache_control /app.js,/app.js,aaa,bbb,max-age=31536000 /style.v1.css,/style.v2.css,ccc,ddd,immutable /logo.png,/logo.png,eee,eee,max-age=3600
Questions & answers
What does Asset Filename Cache Busting Checker do?
Compare manifest hashes and filenames; flag changed content with unchanged cache keys.
What input does this tool support?
Asset history CSV / JSON: Columns: old_url,new_url,old_hash,new_hash,cache_control
What should I check before using the result?
Checks supplied content hashes and cache keys. Actual browser/CDN behavior also depends on validators, purge rules and deployment headers.
Can I keep or share the result?
Yes. Use the result-specific downloads, CSV where available and report JSON. Downloads can contain your supplied information, so review the content before sharing. Processing runs in this browser; public pages also include the site’s approved advertising and optional analytics.
Help improve this tool
Report a problem or suggest an improvement
Describe the issue without pasting private tool input. Feedback goes to our admin inbox.
