How to Fix Chrome IndexedDB and Local Storage Issues

When a web app in Chrome says its storage is full, loses data, or breaks after an update, the data it keeps in your browser (IndexedDB or Local Storage) is often the cause. The fix is to delete that one site’s stored data, either for one database in DevTools or for the whole site. Deleting it can remove anything the site has not saved to its own servers, so read step 1 first.

1. Before you delete anything

If a site keeps your data on its own servers, deleting the copy in your browser is safe: the site downloads it again. If it keeps your data only in the browser, for example an app you use offline, export it from the site’s own settings first, if it offers that.

2. Delete one site’s IndexedDB database in DevTools

  1. Open the site in Chrome.
  2. Open DevTools: F12 or Ctrl + Shift + I on Windows and Linux, Cmd + Option + I on a Mac (Google’s shortcut list). New to DevTools? See DevTools basics.
  3. Click the Application tab.
  4. Expand IndexedDB and select the database.
  5. Click Delete database, then reload the page.

3. Clear all of one site’s storage

To remove IndexedDB, Local Storage and the site’s other stored data together:

  1. In DevTools, on the Application tab, open the Clear storage pane.
  2. Make sure the IndexedDB checkbox is on.
  3. Click Clear site data, then reload the page.

To fix a single Local Storage value instead, go to Application > Storage, expand Local Storage, click the site and delete the key (Google’s Local Storage guide).

4. Clear site data for every site

If you don’t know which site is the problem, or you aren’t comfortable with DevTools, delete all site data. Google’s Delete browsing data help says the Cookies and other site data box removes Web Storage and Indexed Database data as well as cookies.

  1. Select More (⋮) > Delete browsing data.
  2. Choose a time range such as All time.
  3. Select Cookies and other site data, then Delete data.

Our clear browsing data guide explains the other boxes.

“Quota exceeded” errors: how much Chrome lets a site store

From Google’s Storage for the web guide on web.dev:

StorageLimit in Chrome
All sites togetherUp to 80% of total disk space
One site (origin)Up to 60% of total disk space
Local StorageAbout 5MB, strings only

These limits come from the total size of your disk, not from how much space is free: Google says Chrome always reports 60% of the disk size to a site. Clearing site data you no longer need, as in steps 2 to 4, makes room within the limit. If the drive itself is nearly full, see Chrome using too much disk space. Google also notes that Chrome gives sites much less storage in Incognito.

If you build the site, call navigator.storage.estimate() (the StorageManager API) to see how much quota is left before writing large amounts of data. To check usage across sites, open chrome://quota-internals.

Frequently asked questions

What decides how much a site can store?

The total size of your disk. Google says a site can use up to 60% of it and all sites together up to 80%. Clearing data a site no longer needs frees room within that limit.