KV storage provides a simple, asynchronous key/value store with a modern API. Additionally, it allows easy creation of isolated storage areas beyond the default one. KV storage is layered on top of IndexedDB, storing its data in a specific database, so the developer can fall back to using IndexedDB directly when necessary.

Motivation

As explained in Mozilla's 2012 article, "There is no simple solution for local storage", the web today has no good key/value store. Local storage itself is synchronous, leading to performance issues and cross-window synchronization problems. Developers often use it anyway, leading to subpar web experiences. Other developers use libraries like localForage or idb-keyval to get around this problem. We've taken inspiration from their work to build KV storage.

Demo

Documentation

Specification

Specification link


Specification being incubated in a Community Group

Status in Chromium

Blink>Storage


No longer pursuing (tracking bug)

Consensus & Standardization

After a feature ships in Chrome, the values listed here are not guaranteed to be up to date.

Owner

Intent to Prototype url

Intent to Prototype thread

Search tags

local storage, async local storage, kv storage, lapi, lapis, layered api, layered apis, indexeddb,

Last updated on 2021-06-15