What Is Browser Cache Inspector?
Browser Cache Inspector is a free online tool by TechnSols that shows the locally cached resources of the current site, in one clear overview. It lists the named caches in Cache Storage, the files each cache holds, and the size of every cache, so you can see what the site saved for offline use.
Cached files are the reason a site can load fast, work offline, and still show yesterday’s version after an update. A service worker saves the app shell, the images, and the scripts, and serves them again without asking the server. When a new version goes live and the old files keep appearing, the cache is the usual suspect, yet the browser never shows what is inside it. This inspector opens the caches and lists their contents, using the same Cache API that service workers use to store and read files.
One honest limit applies, and the tool states it plainly: it shows Cache Storage only, because raw HTTP cache entries are not listable from a page, and no website tool can read them. The Local Storage Inspector covers a different store, the saved keys and values, while this tool covers the saved files. Together they show the two halves of what a site keeps. Everything runs in your browser, and nothing is uploaded anywhere.
How To Use Browser Cache Inspector?
Using the inspector takes less than a minute. There is no software to install and no account to make. Open the tool on the site you want to check, read the overview, and open any cache to see its files. If a stored value is the problem instead of a file, the Session Storage Viewer lists every entry saved for this tab session.
Step 1: Open The Cache Overview
Load the tool on the website you want to inspect. The overview lists every named cache for the site, with the number of files and the total size of each one. The biggest cache stands out right away, and a cache with an old name often holds the old version of the site.
Step 2: Open A Named Cache
Read the files listed under each cache name. Each entry shows its URL and its estimated size, so you can tell whether the cache holds the current scripts, the old images, or files from a version that should be gone. Lists are capped at the first 100 entries of a cache, and the tool says so when the cap applies. Long lists stay readable, with the largest files easy to spot.
Step 3: Check Sizes And Save The Report
Read the size of each cache against the grand total for the site, then press Copy Summary or Download Report to keep the list as text. The inspector never deletes a cache, so to clear a stale one, use the browser developer tools Cache Storage panel or the site settings, then press Refresh here to confirm it is gone.
The whole check is quick because the tool reads the caches directly, with no scan and no waiting. If a cookie is the stale item rather than a cached file, the Cookie Viewer lists every cookie for the site in the same way.
Why Inspect Browser Cache Online?
Cache problems look like site problems, because the page that loads is the cached one, not the live one. A fixed bug still appears, a new price never shows, and a changed logo stays old, all while the server is serving the right files. Hard refreshing helps sometimes, but it never shows what was cached or why it stayed. An inspector shows the files, their sizes, and their cache names, so the cause is visible instead of guessed. The Service Worker Caching guide explains how service worker caches differ from the HTTP cache, and why both exist.
Find The Cache Serving Old Files
When a site will not update, the old files live in a named cache that the service worker keeps serving. The overview shows the cache names and their contents, so the stale cache can be found and cleared in the developer tools, instead of clearing everything and losing the good caches with it. If the server headers are the cause, the HTTP Header Checker shows the cache headers the server sends.
See Which Files A Site Saved Offline
Apps that work offline save their files on purpose, and knowing which files were saved proves the offline setup works. The cache list shows the app shell, the scripts, and the images the worker stored, so a missing file stands out at once. This is the fastest way to confirm an offline app is ready before it is needed.
Free Space Taken By Stale Caches
Old caches grow quietly, especially on sites that deploy often and leave a new cache behind each time. Each old cache holds a full copy of the site, and several of them can take real space on a small device. The size column shows exactly how much each cache holds, so you know which stale caches to clear in the browser settings and how much room each one holds.
What Can You Do With Browser Cache Inspector?
The inspector fits any job where cached files need checking, cleaning, or proving. These are the jobs it handles best.
Fix A Page That Will Not Update
A page that shows the old version after a deploy is almost always served from a stale cache. Open the inspector, find the cache with the old file names, clear it in the developer tools, and reload the page. The fresh files arrive from the server, and the fix takes seconds. If the browser itself lacks a feature the new page needs, the Browser Feature Detector lists what this browser supports.
Check What An Offline App Cached
Before trusting an offline app on a flight or in a dead zone, check that its files are actually cached. The cache list shows every file the service worker saved, so a missing script or image can be fixed before the trip. A full cache list is proof the app will open with no network at all.
Prove A New Version Went Live
After a deploy, the cache list proves the new files arrived. Compare the file names and sizes in the cache with the new build, and any old file still listed is a file that needs clearing in the developer tools. This check settles arguments about whether the new version is live, with evidence instead of opinion. If a third party script is the stale file, the Third Party Script Inspector lists the scripts a page loads.
Quality And Settings
The inspector lists every named cache in Cache Storage for the current site, with the files and sizes inside each one. Entry sizes are estimates read from the stored response, and a few entries may show size unknown. Press Refresh to re-read the caches after a change. There is nothing to configure before the first check, because the overview is the whole tool.
- One overview for every named cache on the current site.
- File list for each cache, with URL and size per entry.
- Total size per cache, with a grand total for the site.
- First 100 entries per cache, with the cap stated plainly.
- Copy Summary and Download Report buttons for the whole list.
The overview shows only the caches of the site it is open on, because the browser keeps each origin separate. If a cached image is broken rather than stale, the Broken Image Checker finds every broken image on a page.
How Browser Cache Inspector Works
The tool runs entirely in your browser and asks the browser itself for the data. It calls the Cache Storage API to list the named caches, then opens each cache and lists its stored requests with their estimated sizes, up to 100 entries per cache. Nothing is sent to a server, and no copy of your cached files is kept. If a page logs errors while its caches are read, the Website Error Log Viewer shows the errors a page produces.
Two honest limits are worth knowing. First, the tool shows Cache Storage only, because raw HTTP cache entries are not listable from a page, and the browser gives no API to read them. Second, the tool can only see the caches of the site it is open on, because the browser keeps each origin separate, so it cannot inspect another site from this page.
Cache sizes also change as the site is used, because the service worker adds files on each visit and old caches may be deleted by the site itself. Cache names often carry a version, so a new deploy leaves a new cache beside the old one, and the old name in the list is the clue that stale files remain. The same caches appear in the browser developer tools, under Cache Storage, where entries can be deleted one by one. The overview shows the live state at the moment you open it, which is why a cache that was stale yesterday may already be gone today. Re-run the check after a deploy, and the list will match the current build.
Privacy
Everything you inspect stays in your browser. Browser Cache Inspector runs on your own computer, and nothing you do is uploaded to a server, stored, or shared with anyone. No file is ever uploaded, and the tool does its job and shows the answer, and that is all it does.
Because no account is needed, there is no name, email, or history tied to what you do. Closing the tab ends the session, and the browser clears the inspection from memory. That is the same protection on every tool here: your work stays yours, and nothing about it is kept, shared, or sold.
Tips
A few habits make Browser Cache Inspector work smoother, whether this is your first cache check or your five hundredth.
- Clear one stale cache at a time in the developer tools, then reload the page.
- Check the cache list right after every deploy.
- Look for old cache names from earlier versions.
- Note the biggest cache before you clear anything.
- Open the inspector on the exact page that looks stale.
When the cache list matches the current build, and nothing old remains, the check is done. If a site also collects personal data worth reviewing, the Privacy Risk Assessment Tool reviews what the site collects and how risky it is.
More Tools For The Same Job
These tools handle the same kinds of jobs: browser data, storage, caches, and checking what a site keeps.
- Local Storage Inspector: shows every key and value saved in localStorage.
- Session Storage Viewer: lists all entries saved for the current tab session.
- Cookie Viewer: lists every cookie set by the current site.
- HTTP Header Checker: shows the headers a server sends for any URL.
- Browser Feature Detector: checks which web features this browser supports.
- Third Party Script Inspector: lists the third party scripts a page loads.
- Broken Image Checker: finds every broken image on a page.
- Website Error Log Viewer: shows the errors a page produces.
- Privacy Risk Assessment Tool: reviews what a site collects and scores the risk.
- HTTP Request Header Viewer: shows the headers this browser sends with a request.
FAQ
Common questions about inspecting browser cache online, answered plainly.
Is Browser Cache Inspector By TechnSols Free?
Yes, Browser Cache Inspector by TechnSols is completely free to use, with no account, no sign-up, and no usage limit. You can inspect caches as often as you like, and everything runs in your browser, so nothing is uploaded or stored anywhere.
What Caches Does It Show?
It shows the named caches in Cache Storage for the current site, with every stored request and its size. Each cache lists the files the service worker saved, so you can see what the site kept for offline use and how much room it takes.
Why Can It Not List HTTP Cache?
The raw HTTP cache is private to the browser and has no API for a page to read, so no website tool can list its entries. The inspector shows Cache Storage instead, which is the cache service workers control. That is the cache a site can actually manage and clear.
Can I Delete A Cache With It?
No. The inspector is read-only and never deletes a cache or an entry, so a check cannot wipe an offline app by accident. To delete one cache, use the developer tools Cache Storage panel or the browser site settings, then press Refresh here to confirm the cache is gone.
Does Clearing A Cache Log Me Out?
Clearing a cache removes saved files, not logins, because logins live in cookies or storage, not in Cache Storage. The site may load slower once while it fetches fresh files, but your session stays signed in. Clear cookies separately if you want to sign out.
Open the overview, read the cache names, and clear only the stale ones in the browser settings. A site with clean caches loads the current version every time, and leaves no old files behind to confuse the next visit.