Autosave & Restore — Crash Recovery for GrapesJS

Your users will close the tab. Their laptop will die. The browser will crash.

GrapesJS keeps the project in memory. If nothing saved it, an hour of work is gone — and the person who lost it blames your editor, not their battery.

Autosave & Restore adds a local safety net underneath whatever storage you already use. Every change is written to IndexedDB in the background. When the editor opens and finds a newer local snapshot than the loaded project, it offers to bring it back.

What you get

• Background autosave to IndexedDB, debounced — no lag while typing
• Version history: the last 20 snapshots with timestamps, component count and size
• Restore any version in one click — and undo the restore if it was the wrong one
• Recovery banner on load when unsaved work is detected
• Ctrl/Cmd+S to snapshot on demand
• Graceful quota handling: oldest snapshots drop, the editor never breaks

Works alongside your storage, not instead of it

This is a local layer on top ofStorageManager, not a replacement. It saves project state (getProjectData), so a restored session comes back editable — components, styles, pages, everything. Your remote save keeps working exactly as configured.

Built for

Anyone shipping GrapesJS to end users. The support ticket "I lost my page" is the one you can stop receiving.

GrapesJS 0.21–0.23. Buy once, all future updates included.