Frontend System Design · Lesson 61 of 86 · 4 min
Storing Auth Tokens: Cookies vs localStorage
This question is a filter. Your answer reveals whether you've shipped a secure app or just followed tutorials. Get it right, and you prove you understand web security fundamentals.
The Standard: Secure, HttpOnly Cookies
For storing authentication tokens, the correct answer is almost always a secure, HttpOnly cookie. This isn't just a best practice; it's a direct defense against the most common class of web vulnerability.
An HttpOnly cookie is inaccessible to JavaScript running in the browser. This is its entire purpose. If an attacker achieves Cross-Site Scripting (XSS) on your site, their malicious script cannot read the token from document.cookie. This single attribute prevents the most straightforward session hijacking attack.
The browser handles everything for you. Once set by the server, the browser automatically attaches the cookie to every subsequent request to the same origin. You don't write any code to manage it.
For a cookie to be secure, it needs three key attributes set by the server:
HttpOnly: Prevents JavaScript access. Non-negotiable for auth tokens.Secure: Ensures the cookie is only sent over HTTPS. Always use this in production.SameSite=LaxorSameSite=Strict: A critical defense against Cross-Site Request Forgery (CSRF).Laxis a sensible default for most web apps.
Why localStorage is a Footgun for Auth
Using localStorage for auth tokens is a common pattern in tutorials and bootcamps. It is also dangerously insecure.
Any data in localStorage is accessible via JavaScript. This means any XSS vulnerability on your page, including one injected through a third-party library, gives an attacker immediate access to the user's auth token. They can copy the token and use it to impersonate your user.
The trap: In an interview, never defend
localStoragefor auth tokens. Acknowledge its existence and risks, then pivot to the correct cookie-based solution. Arguing forlocalStoragesignals a lack of production security experience.
The diagram below shows exactly why. A script can read from localStorage, but the browser blocks it from reading an HttpOnly cookie.
The Implementation is Simpler Than You Think
A common misconception is that cookies are harder to work with in a Single Page Application (SPA). The opposite is true. With a secure cookie, the frontend auth code becomes trivial.
The server is responsible for setting the cookie on login.
// server.js (Node.js with Express)
// After validating credentials...
const sessionToken = 'your_generated_jwt_or_session_id';
res.cookie('session_token', sessionToken, {
httpOnly: true,
secure: process.env.NODE_ENV === 'production',
sameSite: 'Lax', // Or 'Strict'
maxAge: 24 * 60 * 60 * 1000, // 24 hours
path: '/',
});
res.status(200).json({ message: 'Login successful' });
The frontend only needs to include one option in its fetch calls to ensure the browser sends the cookie. That's it. You don't need to read, store, or attach the token manually.
// frontend.js (React/Vue/etc.)
async function fetchUserProfile() {
try {
const response = await fetch('/api/profile', {
// This tells the browser to send cookies with the request.
credentials: 'include',
});
if (response.ok) {
const user = await response.json();
console.log('User profile:', user);
} else {
// Handle 401 Unauthorized, etc.
console.error('Failed to fetch profile:', response.statusText);
}
} catch (error) {
console.error('Network error:', error);
}
}
There is no token management in your global state, no interceptors to add authorization headers, and no risk of a script stealing the token from memory or localStorage.
What About JWTs?
This is a common point of confusion. A JSON Web Token (JWT) is a token format. It is not a storage mechanism.
You can store a JWT in localStorage, which is insecure.
You can store a JWT in an HttpOnly cookie, which is secure.
The debate is not "JWTs vs. Cookies." The debate is "Where do you store the token?" The answer is in an HttpOnly cookie. Whether that token is a JWT or an opaque string is a separate architectural decision.
Handling CSRF with SameSite Cookies
While HttpOnly protects against XSS, the SameSite attribute is your primary defense against Cross-Site Request Forgery (CSRF).
A CSRF attack tricks a logged-in user's browser into making a malicious request to your site from another site. Since browsers used to send cookies automatically with any cross-site request, this could trigger state-changing actions (like changing a password or transferring funds) without the user's consent.
The SameSite attribute stops this:
SameSite=Strict: The browser will not send the cookie with any cross-site request, including a regular link click from another site. It's the most secure but can be disruptive to the user experience.SameSite=Lax: The browser sends the cookie on cross-site requests that result from top-level navigation (e.g., clicking a link), but not for requests initiated by scripts, iframes, or forms from another site. This is the modern browser default and provides a great balance of security and usability.
For auth tokens, SameSite=Lax is the recommended setting for most applications.
Try it
Open the developer tools on a site where you are logged in (e.g., GitHub, a banking site). Go to the Application/Storage tab and inspect the cookies for that domain. Find the main session or auth cookie. Check its attributes. Is it HttpOnly? Is it Secure? What is its SameSite policy? Can you articulate why the engineers chose those specific settings?
Next: We'll cover what you need to know about the PWA Manifest and Installability.
Lock it in — apply this lesson under interview conditions.