Cookies, localStorage, and IndexedDB: Where State Belongs
Compare cookies, Web Storage, and IndexedDB by scope, network exposure, capacity, and eviction, then choose where each piece of state should live.
The Knowledge Hub is for education, comparisons, and commentary. The docs center is for setup, reference, validation, and responsible-use material.
Start with these guides to explore the tag before browsing the full list.
Separate scraping cookies, localStorage, IndexedDB and sessionStorage across runs. Check restored client state without confusing it with a valid server session.
How cookies carry session and consent state, why cookies added after page creation can miss the first request, and how to load a separate cookie set per identity at launch.
Additional guides with this tag.
Compare cookies, Web Storage, and IndexedDB by scope, network exposure, capacity, and eviction, then choose where each piece of state should live.
How an embedded document checks and requests unpartitioned cookie access, what user mediation and support mean, and how to design a fallback when access is denied.
Use the Cookie Store API for asynchronous cookie work, reason about change events and service-worker visibility, and keep origin and privacy boundaries explicit.
Understand the Partitioned cookie attribute, its top-level-site key, and how to design safe embedded sessions without confusing CHIPS with storage access.
Learn what browser site-data clearing removes, what survives, and how sign-out and account switching should protect application sessions.
How top-level site context separates embedded browser state, what application flows can change, and how to test partitioned storage responsibly.
Load a profile, keep the signals you just read about consistent inside the browser, and confirm the result on your own machine before a rollout.