chrome-ext-storagelisted

# Chrome Extension Storage Chrome extensions have four storage areas plus IndexedDB. Each serves a different purpose with different lifecycles, quotas, and trade-offs. Choose based on data size, persistence needs, and cross-device requirements. ## Storage Selection Guide | Mechanism | Best For | Capacity | Lifecycle | |-----------|----------|----------|-----------| | `storage.session` | Hot state, temporary variables | 10 MB (in-memory) | Clears on browser close | | `storage.local` | Device settings, cached data | 10 MB (expandable) | Persists until extension removed | | `storage.sync` | User preferences across devices | 100 KB total | Syncs across Chrome instances | | `storage.managed` | Enterprise-pushed config | Read-only | Set by IT admin policy | | IndexedDB | Large datasets, binary data | ~80% disk | Persists until extension removed | ## When to Use What **`storage.session`** — In-memory state that must be fast but doesn't need to survive browser restart. Service worker volatile cache. Authentication tokens for the current session. **`storage.local`** — Default choice for most extension data. Settings, cached API responses, user data that stays on one device. Use `unlimitedStorage` permission to remove the 10 MB cap. **`storage.sync`** — Small user preferences that should follow the user across devices. Subject to strict quotas: 8 KB per item, 512 items max, 1,800 writes/hour. **IndexedDB** — Large datasets, binary data (images, model weights, video metadata), o