Token Storage Options Overview
You'll learn how to compare four common storage methods for authentication tokens and understand their security tradeoffs.
The Storage Challenge
When your frontend receives a JWT or session token, you need somewhere to keep it between requests. Think of it like storing a keycard after checking into a hotel—you could put it in your pocket (memory), your wallet (sessionStorage), leave it in your car (localStorage), or have the front desk hold it (cookies). Each option has different security and convenience implications.
The Four Main Options
localStorage
Persists across browser sessions and tabs. Convenient but vulnerable to XSS attacks—any malicious script can read it. Data survives page refreshes and closing the browser.
sessionStorage
Similar to localStorage but cleared when the browser tab closes. Still vulnerable to XSS but has a shorter lifetime. Good for single-session workflows.
Cookies (HTTP-Only)
Sent automatically with every request. When marked HttpOnly, JavaScript cannot access them, making them immune to XSS. However, they're vulnerable to CSRF attacks unless additional protections are used.
Memory (JavaScript Variables)
Store tokens in your application's runtime memory (like a plain JavaScript variable or React state). Most secure against XSS and CSRF because the token never persists anywhere accessible. The downside? Lost on page refresh.
Security vs Convenience Tradeoff
Most secure (but inconvenient): Memory → you need token refresh mechanisms
Balanced security: HTTP-Only cookies → automatic but needs CSRF protection
Convenient (but risky): sessionStorage/localStorage → easy but XSS-vulnerable
Key Takeaway: No storage option is perfect—HTTP-Only cookies with CSRF tokens offer the best balance for most web apps, while memory storage provides maximum security at the cost of user experience.