Developer

Browser Storage Viewer

Inspect script-visible cookies (document.cookie), localStorage, and sessionStorage for this origin in one place. Search, copy values, and export JSON — read-only, with no data sent to DroidXP. Use it next to the Local Storage Manager when you need to edit localStorage.

Ad placement — top banner
Cookies: only names/values exposed to JavaScript via document.cookie are listed. HttpOnly cookies (common for session tokens) are hidden from scripts — use browser DevTools → Application → Cookies for the full set.
Name Value (preview) Approx. size Actions
Key Value (preview) Approx. size Actions
Key Value (preview) Approx. size Actions
Ad placement — mid rectangle

What does this viewer show?

Three separate stores, all scoped to the current origin (scheme + host + port):

  • Cookies — parsed from document.cookie. This is the JavaScript-visible subset of cookies for the current document path; attributes like HttpOnly, Secure, SameSite, and exact path are not exposed here.
  • localStorage — persistent key–value strings until cleared by the user or your code.
  • sessionStorage — per-tab; cleared when the tab is closed (unless restored by the browser).

Why are some cookies missing?

Cookies marked HttpOnly cannot be read by JavaScript — they still appear in DevTools → Application → Cookies, but not in document.cookie. First-party vs third-party rules and SameSite also affect what the browser sends and what scripts can read.

Read-only by design

This page is a viewer: it does not set or delete cookies (which would require specific paths and attributes). To edit localStorage in depth, use DroidXP’s Local Storage Manager or your browser’s DevTools.

Exports

Export active tab downloads a JSON object of name/key → value for the visible tab. Export all includes cookies, localStorage, and sessionStorage plus origin and timestamp — useful for auditing your own dev environment (never share exports that contain secrets).

How to use this tool

  1. Step 1: Open the tab you care about (Cookies, localStorage, or sessionStorage).
  2. Step 2: Use search to narrow rows; click Copy value to copy the full string.
  3. Step 3: Refresh after your app writes storage; export JSON if you need a snapshot.

Frequently Asked Questions

Does DroidXP upload my storage?

No. Everything is read in your browser with the Web Storage API and document.cookie. Nothing is transmitted to DroidXP.

Why don’t I see HttpOnly cookies?

Browsers intentionally hide them from JavaScript. Use DevTools → Application → Cookies to inspect headers, paths, and flags for the full picture.

Why is sessionStorage empty?

It is isolated per tab. If you opened this tool in a fresh tab, only keys written in this tab appear. Your app’s storage may live in another tab or window.

How is this different from Local Storage Manager?

The Storage Viewer combines cookies + both storages in a read-only dashboard. Local Storage Manager focuses on editing, importing, and clearing localStorage only.

Can I trust the size column?

It is a rough estimate (UTF‑16 length × 2). Use it for comparisons, not exact quota accounting.

Why does “Export all” include empty objects?

If a storage API is blocked or empty, the export still lists that section with whatever keys were readable — often an empty object.

Are third-party cookies shown?

Only cookies visible to document.cookie on this page’s origin. Embedded third-party frames have their own storage and are not merged here.

Is it safe to paste exports into chat or tickets?

Treat exports like secrets if they contain tokens. Redact before sharing; prefer synthetic data for bug reports.

Ad placement — sidebar 300×600