Storage & Application

Application Panel

Inspect, modify, and clear localStorage, sessionStorage, Cookies, and Service Worker caches for your application — mirroring the native Chrome Application tab.

Overview

Full Application State Management

The Application Panel gives you complete visibility and control over every piece of client-side state your application manages. This is essential for testing authentication flows, onboarding sequences, feature flags stored in local storage, and shopping cart persistence.

  • localStorage Viewer: Displays all key-value pairs in the application's local storage with formatted, readable values. Edit or delete individual entries.
  • sessionStorage Viewer: Shows session-scoped storage that clears when the tab closes — useful for testing session-based UI states.
  • Cookie Inspector: Lists all cookies set by the application, including their name, value, domain, path, expiry, and security flags. Per-device cookie clearing is supported.
  • Service Worker Status: Shows the status of any registered Service Workers (installing, waiting, active) and their scope URL.
  • Cache Storage Viewer: Lists the named caches managed by Service Workers and their cached URLs — essential for PWA debugging.
  • Clear All Storage: One-click nuclear option to clear all localStorage, sessionStorage, and cookies to simulate a fresh first-time user visit.
💡
Test onboarding flows instantly Use "Clear All Storage" to simulate a brand new user and test your entire onboarding experience end-to-end without needing to create a new account or open an incognito window.
ℹ️
Cross-origin note: Storage operations on the previewed application are relayed via postMessage to the Vispane proxy bridge. Ensure the proxy is active for full functionality.
Pro Tips
💡
Debug feature flags stored in localStorage Many apps store feature flags (e.g., {"betaFeatures": true}) in localStorage. Use the viewer to toggle these values and immediately see the UI response without modifying any code or environment configuration.
💡
Test "remember me" and session expiry Delete the session token cookie while logged in to test how your application handles an expired or missing session — does it gracefully redirect to login or break silently?