i like your humor

yes. I'm storing an entire game's json in mine

Hi. Based on my personal experience (by using the error-testing-error-testing mode :), I discovered that IndexedDB in Chrome Desktop can get up to 50 MB of maximum disk space and for Chrome Mobile they can be up to 5 MB. You must considered that this values can be different depending the Chrome versión installed on the user's device. In both cases, if your webapp exceed the maximum allowed, Chrome will prompt to the user for allowing more space in disk for this webapp. But I can't discover the way that GChrome uses this query by the user. By the way, I think an answer by the Chrome Team will be most acqurate and welcome to us! BR!

​ Cameron Brown Thanks for your recomendation. I work with since 2012 with all kind of local storage types included on Chrome/Chromium and in those time the storage limits was very very different to actually. After many years without using it, I discover again they limits are much more bigger. And beyond to inspect the limits established in documentation or in the same web browser tools, I think do a real test is the best way to know. by the way the testing that I do, is inserting real data and forcing on those databases scale to the limit.

​@Charls Dicken ​ thanks for the tip. Times has changed. 8 years ago the capacity for Local Storage on mobile devices (my specialty) was 5 MB and the same amount of MB for IndexedDB and WebSQL. Today, the maximum capacity are different for both of them.

It varies based on browser implementations. Firefox has 2G and Chrome has 80% of your hard disk capacity.

@@elgs1980 Is it 2 GB now a days?

Yes, welcome to ES3-world. And also, let's pretend async/await doesn't exist.

I'm back i forgot lmao xd

LOL!!!!! I know right!?!

I don't see how IndexedDB is any more gross than the other alternatives to store data client side.