Save data in the browser (part 2): LocalStorage, sessionStorage

Tram Ho

Unlike cookies, localStorage and sessionStorage are not sent to the server during each request. Many browers have at least 2 megabytes of data to store and configure them. The server cannot handle localStorage and sessionStorage via HTTP headers, everything via javascript.

Storage is associated with (domain / protocol / port triple), that is, different protocols or subdomains infer different storage objects, they can access data from each other.

Between localStorage and sessionStorage there are the same methods and properties:

  • setItem(key, value) – save key / value pairs
  • getItem(key) – get value by key.
  • removeItem(key) – remove the key / value pair.
  • clear() – delete everything.
  • key(index) – get the value of the corresponding key
  • length – the length of stored items.


Main features of localStorage :

  • All tabs and windows in the browser if the same source can share each other’s information.
  • Data has no time to exist, it remains after brower restart or OS reboot.

For example, when you run this code:

localStorage.setItem('test', 1);

Then close / reopen the browser or open another window with the previous page, you can get the value you just set:

alert(localStorage.getItem('test')); // 1

They must share the same source (domain / protocol / port), the path may be different.

access localStorage

We can use the getting / setting key:

This is allowed for historical reasons, and is mostly about the way things work, but is often not recommended, because:

  1. If the key is user-generated, it could be anything, like length or toString or another localStorage integration localStorage . In that case getItem/setItem works fine, while faild when localStorage :
  2. When there is a storage event , it activates when we modify the data. That event does not occur with access to localStorage . We will see that later in this section 😜 .

looping over keys

As we saw above, there are methods provided: get/set/remove by key, but do they actually receive all stored values?

Unfortunately, the storage object cannot be repeated.

To get key / value pairs we need to loop them over an array:

String only

Key and value must be string.


sessionStorage is used less than localStorage .

The properties and methods are the same, but it’s much more limited:

  • SessionStorage only exists in the current browser tab.
    • Another tab with the same page will have different storage capacity.
    • But it is shared between iframes in the same tab (assuming they come from the same origin).
  • Data exists when the page refreshes, but takes time when closing / opening tabs.

Take a look:

sessionStorage.setItem('test', 1);

After refreshing the page, you can get back the data:

alert( sessionStorage.getItem('test') ); // after refresh: 1

Storage event

When data is updated to sessionStorage or localStorage , the storage event triggered with the property:

  • key – changed ( null if .clear() is called)
  • oldValue – old value ( null if new keys are added)
  • newValue – new value ( null if key removed)
  • url – the url of the document where the update occurred

It is important: the event triggers on all window objects where the store is accessible, except for the object that caused it.

Imagine, you have two windows with the same website so localStorage is shared between them. You may want to open this page in two browser windows to check the code below. If both windows are listening for the window.onStorage event, each window will respond to updates that occurred in another window.

Thank you for reading. @@

Chia sẻ bài viết ngay

Nguồn bài viết : Viblo