Browser Storage Cleaner🔒 100% local
Clear localStorage/cookies. Privacy-first, no server uploads, no tracking.
Related Tools
Classifies the browser storage keys you paste in, one name and size per line, and sorts them into three risk classes: safe to clear, will sign you out, and destructive. About a dozen name patterns are matched, from _ga and auth tokens through service-worker caches to autosave drafts, and the output ends with the DevTools commands for the class you are clearing. It never touches your browser's storage, because no page can read another origin's keys; the work is done on the text you supply.
How to use it
- On the site you care about, open DevTools, Application, Storage, and copy the key names, or run the localStorage dump command shown in the help output.
- Paste one entry per line as name: size, where the size is plain bytes or suffixed with kb or mb.
- Press Process, then deal with anything tagged DANGER before running any clear command.
Worked example
_ga: 64
auth_token: 512becomesEntries analysed: 2 Total size: 576 B
Safe to clear: 1 (64 B)
Will sign you out / lose state: 1 (512 B)
Destructive - export first: 0 (0 B)Reproduced by running the tool's classification and formatting code in Node. The real third line uses an em dash; a hyphen is shown here.
sw-cache-v3: 2MB
draft-note: 1200becomesBreakdown:
[CLEAR OK] sw-cache-v3 2.00 MB Cache (service worker / assets)
[DANGER ] draft-note 1.2 KB Unsaved work / autosavedraft-note is DANGER because draft, autosave and recovery keys can hold the only copy of typed text.
When to use it
- Before pressing clear site data on a site you use, to see whether something in there is worth exporting first.
- Auditing which keys on a site belong to third-party measurement and which are real session state.
- Working out why a web app serves a stale version: a service-worker cache key in the safe class is the usual answer.
- Explaining to a colleague which keys they can clear without being signed out.
What it does not do
- It does not clear, read or measure anything. No key is deleted and no storage is inspected; sizes are the numbers you typed.
- Matching is on the key name, so a key called prefs that holds a session token is classified as a UI preference. Read the value, not just the name.
- Anything outside the known patterns, such as a UUID or an app-specific prefix, is tagged CAUTION by default and left to your judgement.
- Sessions held in HttpOnly cookies are invisible to JavaScript, so a pasted cookie list is always an incomplete picture of who is signed in.
- Lines without a numeric size are skipped and listed at the end, so a plain list of key names produces no entries at all.