Browsers expose two key-value stores to every web page: localStorage (persistent) and sessionStorage (per-tab). Sites use them for preferences, auth tokens and — frequently — third-party analytics identifiers. This inspector lists every key the current page can read, shows its size, lets you search and delete entries, and flags keys that match common tracker patterns. It is a quick privacy and debugging aid.
How it works
JavaScript can read window.localStorage and window.sessionStorage only for its own origin — the browser’s same-origin policy forbids reading another site’s storage. So this tool reports the storage belonging to this page. It iterates every key, records the value length in bytes, and tests the key name against a list of well-known tracker prefixes (_ga, _gid, _fbp, _hjid, amplitude, mp_, and similar).
Tips
- To audit a different website’s storage, open that site and use its DevTools Application/Storage panel — no in-page script can cross origins.
- Deleting an auth or session key here logs you out of this page; clear with care.
- A flagged key is a heuristic signal. Confirm by checking the value and the site’s privacy policy before drawing conclusions.
Notes
All reads and writes happen locally in your browser. Nothing is transmitted to any server, and clearing a store cannot be undone.