DeviceTry Storage Inspector
Inventory every localStorage key DeviceTry owns, export it, and clear it with a verified result.
This origin's localStorage keys only
DeviceTry Privacy & Data Inspector
Every localStorage key this site owns — view, export or wipe
document.cookie can see for this site — HttpOnly cookies are invisible to any page.How to Test
- •Read the owned-key table: each DeviceTry key is listed with what it holds, its size, and whether it is currently stored.
- •Individual test results and saved guided inspections are counted separately, so you can see which is using space.
- •Export Backup whenever either count is above zero — it downloads a versioned JSON file of exactly the data listed here.
- •Clear Owned Data asks for confirmation, removes only the registered keys, and re-reads the store to verify each one is gone.
Browser Limitations
- •Clearing cannot be undone.
- •Only DeviceTry's own localStorage keys are removed. Cookies, IndexedDB, Cache Storage, service-worker caches and other origins are not touched, and the cookie figure shown is only what document.cookie can see.
Troubleshooting Tips
- •If the page says storage is unavailable rather than empty, your browser is blocking site data for this origin — allow it in the address-bar settings and reload.
- •If a deletion reports a partial failure, reload and try again; the table shows which key survived.
About the DeviceTry Storage Inspector
The DeviceTry Storage Inspector lists every localStorage key DeviceTry itself writes — individual test history, saved guided inspections, rerun-comparison values and your theme choice — with the byte size of each and whether it is currently stored. The inventory comes from a fixed registry of owned keys, so the deletion target is a known list rather than a name pattern that might match something this site never wrote.
The two record counts are shown separately because they are separate things: individual test results accumulate as you use the tools, while guided inspections only appear when you save a report. Export is available whenever either is present — test history on its own is worth keeping — and produces a versioned JSON file containing exactly the data on this page. Clearing asks for confirmation, removes the registered keys, then re-reads the store so the result can state what was verified rather than what was intended.
Tips before you clear
- Export first if you might want the history back — deletion is permanent and there is no server-side copy, because none exists.
- A page that says storage is unavailable is reporting a blocked store, not an empty one. In that state nothing can be inspected, exported or deleted.
- Clearing resets your theme choice to the default; that is the only preference affected, and the tools themselves keep working.
- The cookie figure shown counts only what document.cookie can see for this site. HttpOnly cookies are invisible to any page, so it is a floor, not a total.
Common questions
The page says storage is unavailable rather than empty
Your browser is blocking site data for this origin — common in private windows and hardened profiles. Allow cookies/site data for this site in the address-bar settings, then reload.
Test history will not save
The same site-data block prevents writes. Allow storage for this origin and reload; the testers save to localStorage exactly like every other part of the site.
Clearing reported a partial failure
The page lists which key survived or threw, and deliberately does not claim a clean wipe. Reload and try again; if it persists, the browser is likely enforcing a storage policy on that key.
There are other localStorage keys I did not expect
They are listed so nothing is hidden from you, but they are not part of the DeviceTry registry, so this page neither claims nor deletes them. Clearing them is a browser site-data setting, not this page’s job.
FAQ
What exactly does “Clear Owned Data” delete?
Only the keys in DeviceTry’s owned registry: test history, saved guided inspections, rerun-comparison values and the theme choice. The page verifies afterwards and reports any key it could not remove.
Does it clear cookies, IndexedDB or the cache?
No — and it does not claim to. Those are separate browser surfaces, managed in your browser’s site-data settings. This page only reads localStorage keys the site owns, and only counts the cookies a page can see.
Is any of this stored data uploaded?
No. It all lives in this browser for this site, and it is never transmitted. Export is a download you initiate; clearing removes it from your device and nowhere else, because it exists nowhere else.
Will clearing log me out or break the site?
There are no accounts here. After clearing you lose your history and inspections, and your theme reverts to the default — the tools themselves work exactly as before.
What does the backup file contain?
A versioned JSON document with a format marker, an export timestamp, an explicit scope statement, your test history entries, your saved inspections, the comparison store and your theme preference — nothing from any other site.