Web Front-end
H5 Tutorial
What is the difference between localStorage and sessionStorage in HTML5?
What is the difference between localStorage and sessionStorage in HTML5?
The localStorage data is persisted and remains after the browser is closed until it is manually cleared; the sessionStorage is only valid for the current page session and disappears after closing the tab or window. 2. localStorage is shared between all tabs and windows in the same source; each tab of sessionStorage is independent and does not access each other. 3. localStorage is suitable for saving user preferences, offline cache, and long-term tokens; sessionStorage is suitable for temporarily storing form data, sensitive information, and other scenarios that do not require cross-session retention. 4. The API syntax of both are the same, and both support setItem, getItem, removeItem and clear methods. Therefore, if you need to keep data for a long time, you should use localStorage; if you only use the current session, you should select sessionStorage.

The main difference between localStorage and sessionStorage in HTML5 lies in their persistence and scope.

1. Data Persistence
localStorage : Data stored in
localStoragepersists even after the browser is closed. It remains available across browser sessions until it's explicitly cleared by the user or your code.-
sessionStorage : Data is only available for the duration of the page session. A session ends when the browser tab or window is closed. Refreshing the page doesn't affect
sessionStorage.
2. Scope and Accessibility
localStorage : Shared across all tabs and windows from the same origin (same protocol, domain, and port). If you set an item in one tab, it's accessible in another tab of the same site.
-
sessionStorage : Isolated to each tab or window. Even if you open the same website in two tabs, each tab has its own separate
sessionStorage. They can't access each other's data.
3. Use Cases
-
Use localStorage when you want to:
- Remember user preferences (like theme or language)
- Cache data for offline use
- Store login tokens that should survive page reloads
-
Use sessionStorage when you want to:
- Keep temporary data during a single browser session
- Store form data that shouldn't persist after the user leaves
- Handle sensitive info that shouldn't remain after the tab closes
4. API Usage (They Share the Same Syntax)
Both use the same methods:
// Save data localStorage.setItem('key', 'value'); sessionStorage.setItem('key', 'value'); // Retrieve data localStorage.getItem('key'); sessionStorage.getItem('key'); // Remove data localStorage.removeItem('key'); sessionStorage.removeItem('key'); // Clear all data localStorage.clear(); sessionStorage.clear();
So while the programming interface is identical, the behavior differences based on how long and where the data should be available.
Basically, if you need data to stick around, use localStorage . If it's only relevant during the current session or tab, go with sessionStorage .
The above is the detailed content of What is the difference between localStorage and sessionStorage in HTML5?. For more information, please follow other related articles on the PHP Chinese website!
Hot AI Tools
Undress AI Tool
Undress images for free
AI Clothes Remover
Online AI tool for removing clothes from photos.
Undresser.AI Undress
AI-powered app for creating realistic nude photos
ArtGPT
AI image generator for creative art from text prompts.
Stock Market GPT
AI powered investment research for smarter decisions
Hot Article
Popular tool
Notepad++7.3.1
Easy-to-use and free code editor
SublimeText3 Chinese version
Chinese version, very easy to use
Zend Studio 13.0.1
Powerful PHP integrated development environment
Dreamweaver CS6
Visual web development tools
SublimeText3 Mac version
God-level code editing software (SublimeText3)
Hot Topics
20519
7
13632
4
How to create a progress bar for file uploads in HTML5? (Progress tag)
Mar 06, 2026 am 02:22 AM
Why can't the tag directly display the upload progress? It is a read-only visual component. It does not listen to network requests and is not automatically bound to the upload process of XMLHttpRequest or fetch. If you put it in and don't update the value manually, it will always stop at 0%. What really drives it is the event monitoring in the upload logic you write yourself. A common mistake is to only monitor onload (upload completed) but miss upload.onprogress. XMLHttpRequest (not fetch) must be used to obtain real-time upload progress, because fetch does not expose the max attribute of the event in the upload phase and must be set to the file size (file.size
How to create a tooltip using only HTML5? (Title attribute)
Mar 06, 2026 am 12:23 AM
The title attribute is not a tooltip component, but an accessibility prompt mechanism implemented by the browser. The behavior, style, and interaction are uncontrollable and are only suitable for simple scenarios such as pure information supplement.
How to center an image vertically in HTML5? (Layout techniques)
Mar 07, 2026 am 02:05 AM
Flexbox is the most stable for centered images. The key is to set display:flex and align-items:center in the parent container and specify the height; using place-items:center for Grid is more concise; absolute positioning requires top:50% with transform:translateY(-50%); vertical-align is invalid for block-level centering.
How to create a simple offline web app with HTML5? (Application Cache)
Mar 06, 2026 am 02:16 AM
ApplicationCache has been completely abandoned and will be removed from Chrome 61, Firefox 72, and Safari 11.1. ServiceWorker must be used instead; the latter requires HTTPS, manual registration and cache control, and the path, scope, and life cycle must match exactly.
How to create a contact form with validation in HTML5? (Required attribute)
Mar 06, 2026 am 02:06 AM
required only verifies that it is not empty, not the format; type="email" or pattern must be used together; native verification is only triggered when submitting, not real-time; checkbox/radio/select/textarea has special behavior; the server must re-verify and clean empty values.
How to create a collapsible details section in HTML5? (Summary tag)
Mar 06, 2026 am 02:25 AM
Use and implement native folding area. HTML5 natively supports folding and expansion. It can work without JS. It is a container and a click area. The browser adds a small triangle by default. Click it to expand/collapse the content. A common mistake is to write a closing tag (for example), which must have a start and end tag, and must be the first child element of , otherwise the folding logic will fail. The default is the collapsed state; add the open attribute to expand it by default: you can put text, icons, and even text inside, but don't nest another one - some browsers have inconsistent behavior and do not support IE. Edge79, Chrome12, Firefox49, and Safari6 have good support.
How to use the dialog element for modals in HTML5? (Native popups)
Mar 06, 2026 am 01:26 AM
The element does not render by default, does not occupy the layout, and is not recognized by screen readers. It must explicitly set the open attribute or call showModal()/show() to activate; to close, you need to call close(), click mask or press Esc to monitor manually; the old version of Safari needs to be polyfilled or downgraded; form submission will not automatically close and must be intercepted and manually controlled.
How to preload video or audio content in HTML5? (Preload attribute)
Mar 06, 2026 am 01:59 AM
What are the values of the preload attribute, and what are their effects? The preload of HTML5 is a suggestive attribute. The browser is not forced to comply with it, but it will affect the initial resource loading strategy. It has only three legal values: auto, metadata, none. auto: It is recommended that the browser downloads the entire media file (including audio and video data) as soon as possible, which is suitable for scenarios where users are likely to play it, such as carousel videos on the homepage; but it will waste bandwidth, especially on mobile terminals or under weak networks. metadata: only prefetch meta information such as duration, size, frame rate, cover image, etc., without loading the actual audio and video frames, which is a safe choice in most cases none: explicitly tell the browser "don't load it yet" and wait until the user triggers playback (such as clicking) before starting it





