What is Indexeddb Viewer
The IndexedDB Viewer is a client-side tool that lists all IndexedDB databases stored by the current origin in the browser. It uses the IndexedDB.databases() API (available in Chrome, Edge, and Opera) to enumerate database names, displaying each one as a clickable list item. IndexedDB is the browser's most powerful client-side storage API, supporting structured data, indexes, transactions, and much larger storage quotas than localStorage (typically hundreds of MB to several GB). However, unlike localStorage, there is no built-in browser UI that lists all databases across origins. This viewer fills that gap by providing a quick inventory of what IndexedDB databases exist, which is useful for debugging: you can verify that your application created the expected databases, check for orphaned databases from previous development sessions, and confirm database cleanup after logout. Note that the databases() API is not available in all browsers — Firefox and Safari may show an empty list even when databases exist.
How to Use Indexeddb Viewer
- Step 1: Open the IndexedDB Viewer. The tool automatically queries the IndexedDB.databases() API on load.
- Step 2: Review the list of database names displayed. Each database is shown as a separate entry with its name.
- Step 3: If no databases are found, the tool displays a message. This could mean either no IndexedDB databases exist for this origin, or the browser does not support the databases() API.
- Step 4: To inspect database contents, use the browser DevTools Application tab — this tool provides the high-level inventory, not record-level browsing.
Why Use Indexeddb Viewer
IndexedDB is commonly used by web applications for offline data storage, caching API responses, storing user-generated content, and implementing service worker caches. Over time, these databases accumulate and can consume significant storage space. The IndexedDB Viewer provides a quick way to audit what databases exist without navigating to DevTools. It is particularly useful when: debugging an application that stores data in IndexedDB and you need to confirm the database was created; cleaning up after development by identifying databases that can be deleted; auditing third-party scripts that may have created databases in your origin; and verifying that database deletion logic works correctly after user logout.
Privacy & Security
This tool runs entirely in your browser — no data ever leaves your device. There is no server round-trip, no upload, no logging, and no account required. Your input is processed locally using client-side JavaScript and is never stored, transmitted, or accessible to anyone else. When you close the tab, everything disappears.
Frequently Asked Questions
Why is the database list empty?
<p>Two possible reasons: (1) No IndexedDB databases exist for this origin, or (2) the browser does not support the databases() API. Firefox and Safari have limited support — use Chrome or Edge for accurate results.</p>
Can this tool delete databases?
<p>No. This tool is read-only — it lists database names. To delete databases, use the DevTools Application tab or call indexedDB.deleteDatabase() from the console.</p>
Does this show database sizes?
<p>The databases() API returns names and versions but not sizes. For storage usage, check the browser DevTools or the Storage Manager API (navigator.storage.estimate()).</p>
Can I view the data inside each database?
<p>No. The databases() API only returns names and versions. To view records, indexes, and object stores, use the browser DevTools Application tab with IndexedDB expanded.</p>
Why does Safari show no databases?
<p>Safari has limited support for the databases() API. It may not enumerate databases even when they exist. Use Chrome or Edge for reliable database enumeration.</p>