Why does my Construct 3 save game fail with quota exceeded?

Browser localStorage caps at ~5-10MB per origin. Big saves hit the limit. Use IndexedDB (50MB+ typical) via the Local Storage plugin's IndexedDB option, or compress JSON before storing.

How to switch to IndexedDB?

Local Storage plugin properties → Storage Type = IndexedDB. Auto-uses IDB instead of localStorage. Same API surface, much larger quota.

JSON compression trick?

Save player array indices instead of full state; rebuild on load. Or stringify + LZ-string library if you must keep localStorage. JSON gzip via JS isn't built into Construct.

Fix: Construct 3 Save Exceeds localStorage Cap

Quick answer: Local Storage plugin → Storage Type = IndexedDB. ~50MB+ quota; same API as localStorage.

Save game with full level snapshots. Browser throws QuotaExceededError after a few saves. localStorage caps at 5-10MB.

The Fix

Local Storage object properties:
  Storage Type:         IndexedDB     // instead of LocalStorage
  Database Name:         my_game_save

// API unchanged: Set Item, Get Item, etc.

Event:
  System: Save Game
    Local Storage: Set item "save_slot_1" to JSONString.stringify(state)

IndexedDB is the modern persistent store. Construct's Local Storage plugin abstracts the difference; only the storage backend changes.

Verifying

Save 50MB of data: succeeds. localStorage variant: fails after ~5MB. Network tab shows IDB transactions.

“IndexedDB. Plenty of room.”

Related Issues

For loader layout, see loader. For Tap double, see tap.

IDB. Save grows.