Inspect and edit localStorage for this origin (this site’s hostname and scheme): list keys, search, add or update values, delete entries, export JSON, or import JSON (merge or replace). All operations run in your browser — nothing is sent to DroidXP servers.
| Key | Value (preview) | Approx. size | Actions |
|---|
localStorage is a browser key–value store scoped to an origin (scheme + host + port). Values are strings (objects are usually stored as JSON text).
Data persists until the user clears site data or your code removes it — unlike sessionStorage, it survives tab closes.
Browsers enforce a per-origin quota (often several MB; exact rules vary). Saving may throw QuotaExceededError. In private or strict modes,
localStorage can be unavailable or cleared when the session ends.
Data is not encrypted — any script on the same origin can read it. Do not store secrets or tokens without additional protection. This page does not upload your data; still follow your team’s policy when using browser dev tools on sensitive apps.
No. Read/write happens only in your browser via the Web Storage API. No storage payload is sent to DroidXP.
Storage is isolated per origin. This page only sees keys for droidxp.com (or your local host) when you open this tool here — not other domains.
No — this tool targets localStorage only. SessionStorage is per-tab and separate; use DevTools or a dedicated session tool if you need it.
A single JSON object whose keys are strings and values are stringified (or primitives coerced to strings). Arrays at the root are not supported.
It runs localStorage.clear() first, then writes every key from the file. Keys that exist only in the browser are removed. Confirm before using it.
The origin’s storage is full. Remove large entries, export and trim data, or ask users to free disk space. Some browsers let you inspect usage in Storage settings.
We estimate from string lengths (UTF‑16 code units × 2). The real on-disk footprint is implementation-dependent and may differ.
This is a debugging aid. For production apps, use your framework’s devtools, automated tests, and server-side persistence — not manual edits to live user storage.