Storage for the web
summary
Recommendation: use IndexedDB and Cache Storage API for large client storage; both are asynchronous, available to windows and service workers, and throw a QuotaExceededError on overflow. Browsers vary: Firefox allows ~2 GB per origin, Safari ~1 GB and prompts, Chrome caps usable storage to about 60% of disk for each origin via an 80%/75% formula. Safari also evicts unused writable storage after seven days. Test quota failures by running Chrome on a small RAM disk (example 500 MB yields ~300 MB quota).
AI-written summary · about
chapters (8)
- 0:00Modern storage overview
- 1:17Storage APIs
- 2:23Browser storage limits
- 3:56Handling quota errors
- 5:33Eviction policies
- 7:33Safari eviction policies
- 8:15Testing and debugging
- 9:25Conclusion
related talks
32mThe hitchhiker's guide to client side persistent data storage
51mFront End Data
36mCaching strategies and their performance footprint
01h 00mOffline
45mThe perfect Service Worker. How to design it?
34mCargo Cult Web Performance Optimization
28mNever Wait for an API Again: Unlocking CacheStorage for Blazing Speed
41mThe Insecurity Caused By Trusting Your Client-Side Storage