Back up a time card saved in your browser

Know where the saved card lives

A card saved in the browser belongs to that browser’s storage for this site. Opening another browser or device does not automatically bring it along. There is no account-based synchronization in MinuteFolio, so a familiar page on another device can legitimately show an empty saved-card list.

Why a local save can be unavailable

Browser storage is subject to the browser’s controls and limits. A user can clear site data, storage can be disabled, and a write can fail when space is unavailable. The Web Storage specification explicitly allows a failed write to report a quota error. A truthful interface must distinguish a successful save from an open but unsaved card.

Do not close the tab merely because a save attempt was made. Read the result. If the browser could not save, keep the current session open while you download a backup or retry.

Download the full editable backup

Use a project JSON file when you want to reopen the complete card, including settings and unfinished records. CSV serves spreadsheet data and PDF serves a readable copy; neither should be mistaken for the full editable backup. Keep the versioned JSON file intact and in a location you can find again.

Check a backup before relying on it

1. Download project JSON after the changes you want to retain.
2. Keep the original open until the browser has saved the file.
3. Reopen the file as a separate project and compare the period and key records.
4. Keep the original file if an import reports a version or validation problem.

Deletion and downloaded files are separate

Deleting a named browser card does not delete a file already downloaded. Clearing site data does not recall a copy sent to another person. Decide which copies you intend to retain, and review private notes before sharing any of them.

A backup habit can stay simple: save locally during editing, and download JSON before switching devices, clearing browser data or closing work you cannot easily recreate. The purpose is a recoverable record, not a claim that browser storage is guaranteed forever.

Sources and method

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