I borrowed a friend's phone for an afternoon and opened the same H5 game he had been playing for three weeks. It greeted me like a first-time visitor: tutorial, starter pack, no settings. Nothing was corrupted. The browser had simply taken the space back.

That is the part most mobile web games are not built for. localStorage usually tops out around 5 MB per origin, and on Android that budget is shared with everything else the origin stores. On a 32 GB phone with a full camera roll, the system starts asking apps and browsers to release space, and IndexedDB buckets are fair game. The write does not fail loudly; setItem throws a QuotaExceededError that many builds never catch, so the game carries on as if the save worked.

I now check this on a short list of pages I keep for storage tests, and the results differ page by page. svip2 h5 kept its guest state across a tab close, while h5 g668 dropped back to a fresh session once the cache was cleared. That difference matters more than frame rate on a device with 4 GB of RAM.

The fixes are unglamorous. Ask for persistence with navigator.storage.persist(), put real save data in IndexedDB instead of one JSON blob in localStorage, and keep a small checksum copy behind so a half-written save can be detected on boot. It is also worth opening the pages you ship on a phone that is genuinely full: l777 and at866 are the two I use for a quick sanity check, and h5.idrgame is where the storage panel is easiest to read. A save that survives a nearly full phone is worth more than one that looks clean in a desktop profile.