Session Storage Inspector Panel

WHAT IT DOES

This script provides a full-featured inspector for browser storage on any webpage. It displays all key-value pairs stored in sessionStorage and localStorage, organized by storage type. You can search for specific keys or values, view the raw value of each key, add new key-value pairs, edit existing ones, and delete individual entries. A "Clear Session" button clears all sessionStorage items for the current domain, and a "Clear Local" button clears all localStorage items. The panel shows the total storage size used, helping you understand how much space your data is consuming. The storage view updates dynamically as changes are made, either by the script or by other tabs/windows.

WHERE IT RUNS

The script runs on all websites (*://*/*), making it truly universal. It works on any page that uses browser storage—single-page apps, traditional websites, and more. It supports both desktop and mobile views.

HOW TO USE

After installation, the settings panel appears on the left side of the screen with the gear emoji (⚙️). Open the panel to configure the script:

- The "Enable storage inspector" toggle enables or disables the inspector.

- Use the search input to filter keys and values in the storage lists.

- Click the "Show raw values" toggle to display the full value of each key (or truncated view).

- Click "+ Add Key" to add a new key-value pair to either sessionStorage or localStorage.

- Click the ✎ (edit) button next to any key to modify its value.

- Click the ✕ (delete) button next to any key to remove it.

- Click "Clear Session" to remove all sessionStorage items.

- Click "Clear Local" to remove all localStorage items.

- Click "Refresh storage" to manually reload the storage view.

The storage list appears in the panel, showing keys, values, and item size.

TECHNICAL SECTION — REAL MECHANISM

The script accesses the browser's sessionStorage and localStorage objects directly using JavaScript. It iterates through each storage object using the length property and key() method to retrieve all key-value pairs. The size of each item is calculated using new Blob([key + value]).size. The data is displayed in a scrollable list with search filtering applied client-side. When a user edits or deletes an item, the script uses storage.setItem(), storage.removeItem(), or storage.clear() to modify the storage. The panel updates by re-rendering the entire list. A storage event listener is attached to window to detect changes made from other tabs or windows, triggering a re-render. The search filter is applied by checking if the search string appears in either the key or the value (case-insensitive). The showRaw toggle controls whether the full value is displayed or truncated to 50 characters.

THE PANEL

The settings panel is built with BotGentz's BGPanel component. It is draggable via its header, allowing you to reposition it anywhere on the screen. The panel snaps to the left edge by default but can be moved freely. Click the gear emoji to collapse the panel into a small bubble, and click the bubble to expand it again. The panel remembers its position per page session. Press the Escape key to quickly close or minimize the panel. The panel includes a status flash bar that provides visual feedback when settings are changed or actions are performed. All settings save automatically via GM_setValue.

PLEASE NOTE

This script requires the free BotGentz browser extension to run. It does not function as a standalone Chrome extension and does not use chrome.* APIs. The script accesses and modifies browser storage—use caution when editing or deleting data, as some websites rely on this data for functionality. The script does not modify storage for other domains. The storage size calculation is approximate. The script stores only your preferences via GM_setValue. No data is sent externally—all processing is performed locally in your browser. The script never reads or writes password fields, hidden inputs, or file inputs. All DOM operations use safe methods (style properties, textContent, appendChild) and never use innerHTML.