The localStorage viewer shows the keys this site has saved in your browser's localStorage and sessionStorage, with JSON values pretty-printed. Search keys and values, edit or delete them, add new ones, and export or import everything as JSON. It's also a hands-on way to see how web storage works — browsers only let a page see its own site's storage, so for other sites the page explains how to use DevTools. Nothing leaves your browser.
| Storage | Lifetime | Size | Sent to server |
|---|---|---|---|
| localStorage | Until cleared | ~5 MB | No |
| sessionStorage | Until the tab closes | ~5 MB | No |
| Cookies | Set by expiry | ~4 KB each | Yes, with requests |
| IndexedDB | Until cleared | Large, quota-based | No |
No. Browsers only allow a page to read storage for its own site. Open DevTools on the other site (F12 → Application → Storage) instead.
localStorage persists until cleared; sessionStorage is per tab and is cleared when the tab closes.
About 5 MB per site in most browsers. Values are stored as strings.
They're stored with JSON.stringify to save space; the viewer pretty-prints them again for reading.
No. Storage is read and changed only in your browser.
localStorage and sessionStorage are key/value stores of strings scoped to an origin — protocol, host and port. The browser only gives a page access to its own origin's storage, so this viewer lists what toolsnests.com has stored in this browser; to inspect another site you use DevTools on that site. Keys are read with Storage.key(i) and getItem, sorted and filterable. Values that parse as a JSON object or array are pretty-printed for editing and written back compactly with JSON.stringify; other values are stored as typed. Size is estimated as UTF-16 (two bytes per character of key and value) against the roughly 5 MB per-origin limit most browsers apply; a write that exceeds it throws QuotaExceededError, which is shown rather than lost. Export produces a JSON object of all keys; import accepts the same shape and stringifies non-string values. Access is wrapped in try/catch because storage can be disabled or throw in private modes.