Local saves, backups and recovery

Find a saved card

Open Saved cards to view named projects saved in the current browser. Open a card to edit it, duplicate it for a separate record, or download project JSON. A draft remains visibly unfinished even when its local save succeeded.

Another browser or device

There is no automatic cloud synchronization. A different browser can show no saved cards even when the original browser still has them. Move a complete project by downloading JSON from the original session and importing that file in the new one. A PDF or CSV copy does not restore every editable setting.

If a save fails

1. Keep the current tab open; the entered values remain in the editor.
2. Read the save status rather than assuming the attempted save succeeded.
3. Download project JSON to retain an editable copy.
4. Retry the local save when the browser allows it, or keep using the downloaded file.

Why storage can fail

A browser can disable storage or reject a write when its limits are reached. Private browsing and clearing site data can also affect how long a local copy remains available. The app should report a failed write without claiming “Saved to this browser”. Calculating and downloading a file should remain possible when persistence is unavailable.

Delete the intended copy

A delete action removes the named browser record you select. Review the project name before confirming. The most recent deletion can be undone for 60 seconds while the current page remains open. Deleting a local card does not remove exported files or copies already sent to someone else.

Before clearing site data

Download JSON backups for the cards you need to keep and verify a representative file. Clearing this site’s browser data removes local projects and preferences. The app cannot restore data that was cleared unless you retained a separate project file.

Sources and method

• WHATWG HTML: Web storageBrowser storage behavior and potential write failures.