This is post #6 of Frontend Interview Questions series. If you're looking to level up your preparation or stay updated in general, consider signing up on Frontend Camp.
Cookies, Local Storage, and Session Storage are all used to store data on the client side. These mechanisms are particularly useful for storing authentication tokens or client-only states, such as themes or personalized settings. All three storage types share the following characteristics:
- They store data as key-value pairs.
- All values are stored in string format. If a value is not a string, it is serialized before being stored.
- Data stored in these mechanisms is accessible to the client (except for HttpOnly cookies).
Cookies
Cookies cannot store large amounts of data; their storage is capped at approximately 4KB per domain. This limitation exists because cookies are automatically sent to the server with every request made by the browser. Storing excessive client-side data in cookies would increase the payload size, negatively impacting performance.
What kind of data should we store in Cookies?
Cookies are ideal for storing data that needs to be transmitted to the server, such as authentication tokens, session IDs, analytics IDs, and similar information. Additionally, cookies allow data sharing across different tabs or windows of the same domain or subdomain.
You can configure cookies using various flags to tweak their behavior or enforce security:
- HttpOnly ensures cookies are inaccessible via JavaScript on the client side, mitigating the risk of XSS attacks.
- maxAge/expires specifies an expiry date for the cookie. If no expiry date is set, the cookie is deleted when the browser is closed.
Want to learn more about cookie flags? Check out my LinkedIn post.
Unlike local storage and session storage, cookies can also be set (read: "added") by the server using the Set-Cookie header.
// Set a cookie for the key `token` that `expires` on 1st March 2025. document.cookie = 'token=a1-b2-c3; expires=Sat, 1 Mar 2025 23:59:59 GMT; path=/'; // Read all cookies. There's no way to read specific cookies using `document.cookie`. // You have to parse the string yourself. console.log(document.cookie); // token=a1-b2-c3 // Delete the cookie with the key `token` by setting an // expiry date in the past. The value doesn't matter. document.cookie = 'token=; expires=Thu, 01 Jan 1970 00:00:00 GMT; path=/';
Local storage
Unlike cookies, localStorage offers a significantly larger storage capacity of approximately 5MB per domain. This is because localStorage is designed for storing long-term data. It retains data even when the browser is closed, making it ideal for persistent client-side storage needs.
What kind of data should we store in localStorage then?
localStorage is best suited for storing data that is used only on the client side and does not need to be sent to the server with every request. Some examples are the theme of a website or products added in cart before a used has signed in.
Data stored in localStorage persists indefinitely until the user deletes it manually or the website clears it using JavaScript.
Similar to cookies, data in localStorage is accessible across all tabs or windows of the same origin, making it useful for sharing client-side state within a domain.
// Set a cookie for the key `token` that `expires` on 1st March 2025. document.cookie = 'token=a1-b2-c3; expires=Sat, 1 Mar 2025 23:59:59 GMT; path=/'; // Read all cookies. There's no way to read specific cookies using `document.cookie`. // You have to parse the string yourself. console.log(document.cookie); // token=a1-b2-c3 // Delete the cookie with the key `token` by setting an // expiry date in the past. The value doesn't matter. document.cookie = 'token=; expires=Thu, 01 Jan 1970 00:00:00 GMT; path=/';
Session storage
sessionStorage is used to store short-lived, client side data. Like localStorage, it provides a storage capacity of around 5MB per domain and shares the same API.
While both sessionStorage and localStorage share similar functionalities, they differ in two key aspects: Data persistence and Accessibility.
Unlike localStorage, sessionStorage does not retain data once the tab or browser is closed. Additionally, data stored in sessionStorage is isolated to the specific tab or window where it was created, meaning other tabs or windows from the same origin cannot access it.
What's the use case for sessionStorage then?
sessionStorage is ideal for storing data that is needed only for a single session. For instance, consider a user filling out a long form who accidentally refreshes the page. If the form data is stored in sessionStorage, it will persist through the refresh, allowing the user to continue without losing their progress.
However, it's important to note that this data will not be accessible in a different tab or once the tab is closed.
// Set a value in localStorage. localStorage.setItem('theme', 'dark'); // Get a value from localStorage. console.log(localStorage.getItem('theme')); // 'dark' // Remove a value from localStorage. localStorage.removeItem('theme'); // Clear all data in localStorage. localStorage.clear();
While cookies are automatically included in every request sent by the browser, data stored in localStorage or sessionStorage can be manually transmitted to the server by writing custom code.
Summary
- Cookies, localStorage and sessionStorage are used to store data on client side.
- Cookies are the only form of storage which can be set by the server too using Set-Cookie response header.
- Cookies are automatically sent to the server with every request.
- localStorage and sessionStorage have a significantly large storage(5MB) compared to the cookies(4KB). Both of these storages share the same API interface.
- Cookies have an expiry date, if not, they are cleared when the browser is closed.
- localStorage data persists indefinitely unless manually cleared by the user or the website itself.
- sessionStorage data is cleared after the session ends i.e. when the tab or the window is closed.
Like what you just read? Consider checking out Frontend Camp ✌️
The above is the detailed content of Cookies, Local storage and Session storage. For more information, please follow other related articles on the PHP Chinese website!

JavaScript core data types are consistent in browsers and Node.js, but are handled differently from the extra types. 1) The global object is window in the browser and global in Node.js. 2) Node.js' unique Buffer object, used to process binary data. 3) There are also differences in performance and time processing, and the code needs to be adjusted according to the environment.

JavaScriptusestwotypesofcomments:single-line(//)andmulti-line(//).1)Use//forquicknotesorsingle-lineexplanations.2)Use//forlongerexplanationsorcommentingoutblocksofcode.Commentsshouldexplainthe'why',notthe'what',andbeplacedabovetherelevantcodeforclari

The main difference between Python and JavaScript is the type system and application scenarios. 1. Python uses dynamic types, suitable for scientific computing and data analysis. 2. JavaScript adopts weak types and is widely used in front-end and full-stack development. The two have their own advantages in asynchronous programming and performance optimization, and should be decided according to project requirements when choosing.

Whether to choose Python or JavaScript depends on the project type: 1) Choose Python for data science and automation tasks; 2) Choose JavaScript for front-end and full-stack development. Python is favored for its powerful library in data processing and automation, while JavaScript is indispensable for its advantages in web interaction and full-stack development.

Python and JavaScript each have their own advantages, and the choice depends on project needs and personal preferences. 1. Python is easy to learn, with concise syntax, suitable for data science and back-end development, but has a slow execution speed. 2. JavaScript is everywhere in front-end development and has strong asynchronous programming capabilities. Node.js makes it suitable for full-stack development, but the syntax may be complex and error-prone.

JavaScriptisnotbuiltonCorC ;it'saninterpretedlanguagethatrunsonenginesoftenwritteninC .1)JavaScriptwasdesignedasalightweight,interpretedlanguageforwebbrowsers.2)EnginesevolvedfromsimpleinterpreterstoJITcompilers,typicallyinC ,improvingperformance.

JavaScript can be used for front-end and back-end development. The front-end enhances the user experience through DOM operations, and the back-end handles server tasks through Node.js. 1. Front-end example: Change the content of the web page text. 2. Backend example: Create a Node.js server.

Choosing Python or JavaScript should be based on career development, learning curve and ecosystem: 1) Career development: Python is suitable for data science and back-end development, while JavaScript is suitable for front-end and full-stack development. 2) Learning curve: Python syntax is concise and suitable for beginners; JavaScript syntax is flexible. 3) Ecosystem: Python has rich scientific computing libraries, and JavaScript has a powerful front-end framework.


Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

SublimeText3 Chinese version
Chinese version, very easy to use

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Linux new version
SublimeText3 Linux latest version

MantisBT
Mantis is an easy-to-deploy web-based defect tracking tool designed to aid in product defect tracking. It requires PHP, MySQL and a web server. Check out our demo and hosting services.

SAP NetWeaver Server Adapter for Eclipse
Integrate Eclipse with SAP NetWeaver application server.
