Storage limits on Chrome browser

by

Update May 2020: Chrome now lets an origin use 60% of the storage device’s space (Real nitty gritty: “storage device” is the partition containing the chrome profile directory). Updated article here https://web.dev/storage-for-the-web/#how-much

The rule of thumb is 6% (edit 2015-Jul: was 10%) of the available space on the user’s hard drive, less if your origin is using websql, appcache or the filesystem api. The MDN doc mentioning 5mb was outdated and has been updated. The gory details about the current policy are here: https://developer.chrome.com/apps/offline_storage

Note some annoying subtleties:

  1. There is no PERSISTENT storage for indexeddb, only the stuff in the link above about TEMPORARY applies.
  2. Once your origin exhausts its share of the pool,indexeddb transactions will unhelpfully abort with no real indication why. As of now the only way to determine that lack of quota is the cause is to use queryUsageAndQuota to check how much space is left. Hopefully a future version of chrome will soon properly fill out IDBTransaction.error in these cases. Edit: chrome 26 now properly fills out IDBTransaction.error with QuotaExceededError.
  3. There is currently no API to request more storage space for indexeddb.

More Related Contents:

  1. In IndexedDB, is there a way to make a sorted compound query?
  2. Storing Image Data for offline web application (client-side storage database)
  3. Maximum item size in IndexedDB
  4. IndexedDB view all Databases and Object Stores
  5. How to delete indexedDB?
  6. How to create multiple object stores in IndexedDB
  7. How to access Google Chrome’s IndexedDB/LevelDB files?

Leave a Comment