b2KIT

Local Storage Viewer

Browse, search, edit, and export localStorage and sessionStorage data with JSON formatting support.

Tested tool guide Tested browser tools Checked August 16, 2026

What Local Storage Viewer does and how it behaves

Local Storage Viewer exposes the key-value records available through localStorage and sessionStorage to the page hosting the viewer. It lets you switch between the stores, search displayed entries, inspect JSON-shaped strings in a readable form, edit stored data, and export a snapshot. The important boundary is origin isolation: opening this viewer does not grant access to storage belonging to an unrelated website. Web Storage values are also always strings, even when a value contains valid JSON or looks like a number, boolean, or object.

How the result is produced

1

Selecting and reading storage

Choosing localStorage or sessionStorage changes which browser Storage object is inspected. Every entry consists of a string key and a string value. Search narrows the displayed records. When a stored string is valid JSON, JSON formatting can expose its object or array structure for inspection. Plain text and malformed JSON remain strings rather than becoming structured data.

2

Editing and exporting

Saving an edited value writes a string for its key in the selected storage area. Export captures a point-in-time copy of the storage data available to the viewer. Inspection, editing, formatting, and export happen in the browser, so storage contents are not uploaded. Displaying formatted JSON does not convert Web Storage into an object database or assign native data types.

Good uses

  • Check whether a same-origin page saved a theme, feature flag, draft, or serialized preference under the expected localStorage key.
  • Inspect sessionStorage after navigating from another same-origin page in the same tab, especially when the equivalent page in a second tab behaves differently.
  • Export a storage snapshot before correcting a malformed JSON settings value or testing how a same-origin page responds to an edited stored flag.

Limits and checks

  • The viewer cannot cross the browser's same-origin boundary. Storage associated with a different scheme, host, or effective port is not part of the storage area it can inspect.
  • Pretty-printed JSON can look like typed application data, but the underlying value is still a string. The viewer cannot determine whether an application expects that string to follow a particular schema.
  • sessionStorage is scoped by both origin and top-level browsing context, so another tab may contain different entries. An export is only a snapshot and may become outdated as pages change storage.

Common questions

Can this viewer inspect localStorage from any website?

No. Browser origin rules limit the viewer to storage exposed to its own document. An origin is based on scheme, host, and port, so data from https://example.com is unavailable to a viewer hosted at another origin. To inspect another site's Web Storage, use a context operating on that exact origin, such as the developer tools attached to that site.

Does JSON formatting change the stored value?

No. localStorage and sessionStorage store strings. Formatting presents valid JSON with readable structure; it does not change the saved value unless you explicitly save an edit. JSON whitespace may be insignificant when parsed, but it remains part of the raw stored string. An application that compares raw text can therefore notice whitespace-only edits.

References and verification

The behavioral notes were checked against the browser implementation. Standards and primary references below define the relevant format, formula, or platform behavior.

Related Tools