Experiencing troubles with Chrome’s IndexedDB and Local Storage can hinder your browsing experience. This guide will help you understand the different types of storage in Chrome, diagnose issues, and apply effective solutions across various platforms.
Quick Fixes to Try First
- Restart Chrome and try accessing the site again.
- Clear cache and cookies via More > Delete browsing data. The cookies option also deletes site storage such as IndexedDB, so you may be signed out of sites.
- Ensure Chrome is updated to the latest version (
chrome://settings/help). Our guide to updating Chrome covers every device. - Disable unnecessary extensions that might interfere with storage.
Understanding Chrome Storage Types and Quotas
Chrome uses several storage types to enhance user experience, including IndexedDB and Local Storage. IndexedDB is a low-level API for storing significant amounts of structured data, while Local Storage is a simple key-value store for smaller amounts of data.
| Storage Type | Use Case | Quota |
|---|---|---|
| IndexedDB | Large datasets, complex queries | Shared quota: one site can use up to 60% of total disk space, and Chrome up to 80% in all |
| Local Storage | Small key-value pairs | About 5MB, strings only |
The limits come from Google’s storage guide on web.dev.
Clearing IndexedDB Data for Specific Sites
Clearing IndexedDB data can solve many issues related to corrupted databases or outdated information.
- Open Chrome and navigate to the site in question.
- Press F12 (Windows/Linux) or Cmd + Option + I (Mac) to open Developer Tools.
- Go to the Application tab.
- Under Storage, expand IndexedDB and select the database.
- Click Delete database. To remove all of the site’s storage at once, use Clear site data instead (Google’s DevTools guide).
- Refresh the page to apply changes.
Fixing Storage Quota Exceeded Errors
Encountering a “storage quota exceeded” error can be frustrating. Here’s how to address it:
- Check the current usage by visiting
chrome://quota-internals. - Free up space by clearing unnecessary data:
- Select More > Delete browsing data.
- Select the cookies box and Cached images and files.
- Click Delete data.
- If you build the site, use the StorageManager API (
navigator.storage.estimate()) to check how much quota is left before writing large amounts of data.
chrome://quota-internals page when a quota error comes back.Inspecting Storage in DevTools Application Panel
Chrome DevTools is a powerful tool for inspecting and managing storage.
- Open Developer Tools using F12 (Windows/Linux) or Cmd + Option + I (Mac).
- Navigate to the Application tab.
- Under Storage, inspect IndexedDB, Local Storage, and other relevant data.
- Analyze storage usage and remove unwanted data as needed.
Recovering from Corrupted IndexedDB Databases
Corrupted databases can disrupt functionality. Here’s how to attempt recovery:
- If the site keeps your data on its own servers, deleting the local copy is safe. If it doesn’t, export your data from the site’s own settings first, if it offers that. DevTools has no export button for IndexedDB.
- Delete the corrupted database as described in the “Clearing IndexedDB Data” section.
- Reload the site and let it rebuild the database, or import your exported data.
Frequently Asked Questions
What causes Chrome IndexedDB errors?
IndexedDB errors can be caused by corrupted data, storage quota limits, or browser settings affecting storage access.
How do I know if my Chrome storage is full?
Visit chrome://quota-internals to view detailed storage usage, or open DevTools > Application > Storage for one site.
Can clearing cookies fix storage issues?
Yes. In Chrome’s delete browsing data dialog, the cookies option also removes site data such as IndexedDB and Local Storage, which frees space. It also signs you out of sites.
Is there a way to increase Chrome’s storage quota?
Not directly. Chrome bases the quota on your disk size, so freeing disk space on your computer and clearing unused site data are the practical options.
Why is my Local Storage not working?
Local Storage issues can stem from browser settings, corrupted data, or reaching its limit of about 5MB.