Inspect sessionStorage
View, edit, add, and delete every sessionStorage entry for this tab. Scoped to one tab and auto-cleared when the tab closes — ideal for transient draft state.
sessionStorage storage for this origin only · ~5 MB browser quota.
No sessionStorage entries
How to inspect sessionStorage
Each origin gets ~5 MB of sessionStorage. We list every key/value, let you edit in place, add new entries, and clear everything.
- 01
Browse keys
All entries listed alphabetically with size.
Inputs are treated as UTF-8 throughout the pipeline and validated client-side as you type — nothing dispatches until the value is well-formed.
browseinpututf-8client-sidevalidatedentries · textlist · setkey · value · size
loaded · parsedclient-side - 02
Edit value
Type a new value and click Save.
Each toggle re-computes through a memoised hook, so flipping options never resets your input and the UI stays snappy on large inputs.
editoptionslivememoisedtogglesedit · memoisedsave · livenew value
options set · memoisedlive - 03
Add entry
Use the new key/value box at top.
Randomness — where used — comes from
crypto.getRandomValues, neverMath.random. Heavy work sits inuseMemo.addcomputeinstantlocaldeterministicadd · instantk/v · computedkey + value
computed · instantinstant - 04
Export JSON
Copy all entries as a JSON object.
Copy writes through
navigator.clipboardand downloads use aBlob— zero network traffic. Same input plus same options always yield the same bytes.exportcopydownloadzero-networkreproducibleok · copiedready · copied{ key: value }shipped · ready to shipsuccess
Pro tips for everyday utilities
Reach for crypto.getRandomValues
Cryptographically random for IDs, tokens, salts. Math.random is for animation and games, not security.
Mock data with seeds
Faker-style libraries can be seeded so tests are reproducible. Embed the seed in the fixture file.
Reference cards beat memory
Cheatsheets for Vim, Git, Docker, Linux signals are faster than man pages when you’re mid-flow.
Browser APIs vary
Touch events, gamepads, and clipboard differ across vendors. Feature-detect before use.
Persist in the right place
localStorage for user preferences, sessionStorage for transient state, IndexedDB for structured data.
When to inspect sessionStorage
Debug state, clear stale data, audit.
Debug stale state
See what your app actually persists. Random values come from crypto.getRandomValues — cryptographically secure for tokens, salts, and session IDs. Math.random is deterministic enough for animations but predictable enough to be a security bug.
CSPRNG-backedOnboarding flows
Verify the first-run keys are written. Pair with hashids, ULID, or UUID v7 when you need both random and sortable — useful for primary keys, public-facing IDs, and event log ordering without a sequence column.
reproducibleMigration scripts
Spot legacy keys before deletion. Output is deterministic given the same seed, so fixtures and tests stay reproducible across CI runs and contributor machines. Embed the seed in the fixture file for full replay.
snappyPrivacy audit
Check what an unfamiliar site stores. Heavy work runs through useMemo so the UI stays snappy on large inputs. Same input + same options yields identical bytes — the kind of stability snapshot tests rely on.
feature-detectedClear cached login
Wipe a stuck auth state without DevTools. Storage tools persist to the right backend: localStorage for user preferences, sessionStorage for transient state, IndexedDB for structured data. Pick the right shelf and quota worries disappear.
deterministicQuota debugging
Confirm you're not near the 5 MB cap. Browser feature detection: clipboard, fullscreen, gamepad, and Web Bluetooth APIs gracefully fall back when unavailable. No surprise white screens on Safari or older Firefox.
production-readyFrequently asked questions
Something missing?
Tell us what you need. We ship the top requests every two weeks.