How would you choose among cookies, localStorage, sessionStorage, and IndexedDB for browser data?

Chooses browser storage by server transport, lifetime, capacity, query needs, sensitivity, synchronization, and offline behavior.

1Say itAnswer out loud first

2CompareCompare with Core answer

3RefineRefine with Stronger and Advanced

TL;DR

Cookies are small values the browser can send with matching HTTP requests, so they suit server sessions when configured securely. sessionStorage is scoped to a tab session, while localStorage persists for the origin and exposes a synchronous string API. IndexedDB is asynchronous and better for larger structured or offline data. I choose based on lifetime, size, access pattern, and security.

Full answer below

Practice focus

Practical storage judgment that keeps client persistence separate from trust and authorization.

Answer first

Answer path

Core answer first, then checkpoints toward a stronger answer.

Start
Core answer
Start here. This is the direct spoken answer to practice first.
Overview
The choice begins with who needs the data and how long it should live. No browser store turns client-controlled data into trusted state.
Cookies are small values the browser can send with matching HTTP requests, so they suit server sessions when configured securely. sessionStorage is scoped to a tab session, while localStorage persists for the origin and exposes a synchronous string API. IndexedDB is asynchronous and better for larger structured or offline data. I choose based on lifetime, size, access pattern, and security.
Checkpoint
Stronger answer
Optional upgrade with examples, trade-offs, and sharper phrasing.
I avoid placing sensitive bearer tokens in script-readable storage when an HttpOnly secure cookie session is available, while still handling CSRF for automatically sent credentials. Preferences may fit local storage; a recoverable draft may fit session storage; an offline catalog or queued work may justify IndexedDB. Every value remains untrusted when sent back to the server.

Review signals

Use these to catch weak phrasing, shallow reasoning, and risky claims.

Common mistakesCandidateCommon mistakesMistakes that weaken the answer or signal shallow understanding.Open details

Details

Choosing storage only by maximum capacity.
Treating local storage as a secure credential vault.
Trusting browser data because the application originally wrote it.
Ignoring schema versioning and quota failure.

How would you choose among cookies, localStorage, sessionStorage, and IndexedDB for browser data?

Practice focus

Answer path

Overview

Review signals

Follow-up prompts

Continue practice

Next in path

Go deeper

Skill areas

Human editorial direction

Was this drill useful?

Found this answer useful?