b2KIT

IndexedDB Browser

Browse IndexedDB databases, object stores, and records with search, filtering, and export capabilities.

Tested tool guide Tested browser tools Checked August 16, 2026

What IndexedDB Browser does and how it behaves

IndexedDB Browser shows the IndexedDB databases available to this page's browser storage context and organizes them by database, object store, and record. After choosing a store, you can inspect stored keys and values, narrow the record list with search and filtering, and export data for separate review. Its scope is the part most often misread. This is not a cross-site replacement for browser developer tools: IndexedDB is isolated by origin, so a database created under another scheme, host, or port is not automatically visible here, even when it exists elsewhere in the same browser profile.

How the result is produced

1

Database and store hierarchy

The navigation follows IndexedDB's containment model: a database owns named object stores, and each store owns records addressed by primary keys. Opening one level sets the context for the next, so a record result is meaningful only when its database and object store are identified. Store names are local to a database; two databases can use the same name for unrelated collections of records.

2

Filtering and export scope

Within the chosen object store, the search and filter controls reduce the records shown, and the export control produces a separate representation of the available data. Searching, filtering, and exporting do not edit or delete the IndexedDB records being inspected. These operations run inside the browser, so store contents are not uploaded merely to be viewed or exported. Confirm the database and store context before creating the export.

Good uses

  • Verify that an offline-first web application wrote the expected IndexedDB record to a cache, pending-action queue, or local working set after a test action.
  • Locate a record by a known key, identifier, or visible value when an object store has become too crowded to inspect one row at a time.
  • Export records from a reproducible test state for a bug report, or compare the accessible data left by two versions of the same web application.

Limits and checks

  • The database list reflects the current browser storage context, not every IndexedDB database on the device. Origin, browser profile, private browsing, and storage partitioning can change what is visible.
  • IndexedDB keys are typed. The numeric key 7 and the string key "7" are different keys, even if a compact record display makes their printed forms look similar.
  • Do not assume an export is a complete restoration package. Confirm whether it preserves database version, object-store definitions, primary keys, key paths or generators, indexes, and stored value types.

Common questions

Can it inspect the IndexedDB database of any website in my browser?

No. Web content is normally restricted to IndexedDB associated with its own origin and storage context. Opening this viewer beside another site does not grant access to that site's stores, and sharing a host name is not enough if the scheme or port differs. Inspect the target site's storage with that page's browser developer tools, or use an export the site provides.

Is the export a complete backup I can restore later?

Not necessarily. IndexedDB records can contain values supported by the structured clone model, while a portable export format may represent some types differently and may or may not include schema details. Check the exported artifact for primary keys, store definitions, indexes, version information, and the value types you need before deleting or rebuilding the source database.

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