Keep your practice history

Your times deserve a backup.

Rubik Cube Timer saves solves in this browser on this device. A downloaded JSON backup gives you a separate copy you can keep and later restore.

What “saved locally” means

Your sessions and solves live in the browser's IndexedDB storage for this website. Reloading the page normally keeps them. Another browser, profile, device or website address has its own storage and will not automatically show the same history.

Clearing site data, removing a browser profile or losing a device can remove your times. Private browsing may discard storage when the private session ends. Browsers can also limit or evict stored data. Local saving is convenient, but it is not a cloud backup.

Save a JSON backup

  1. Finish or cancel the active attempt.
  2. Open the timer's backup controls and choose the JSON backup download.
  3. Keep the downloaded file somewhere you can find again. A second location, such as your own backup drive, protects against device loss.
  4. Check that the file exists and has a recent date. Keep an earlier copy when saving a new one.

JSON is the restore format. It preserves the information needed to bring your Rubik Cube Timer sessions and recorded attempts back into the tool. Back up after an important session and before clearing browser data or changing devices.

Restore a backup

  1. Open Rubik Cube Timer in the browser where you want the history.
  2. If it already has important times, download a backup of those first.
  3. Choose the import control and select a Rubik Cube Timer JSON backup.
  4. Read the result message. Check the session names, solve counts and a few familiar times.

The importer checks the file before saving it and recognises repeated solve IDs to avoid duplicating the same backup's records. A renamed or manually edited file can still be invalid; the extension alone does not prove it is compatible. A failed import should leave existing data intact.

Only Rubik Cube Timer backups are supported by this import workflow. A file from another timer can use different fields, units or penalty rules. Do not assume it can be imported merely because it is JSON.

Use CSV for a spreadsheet

CSV export is useful for inspecting times in a spreadsheet or doing your own analysis. Keep the JSON version as well: the CSV is not a replacement for the restore backup and is not accepted by the JSON importer.

If your history is missing

If saving fails because browser storage is unavailable or full, keep the page open and try exporting your current history before clearing anything. Avoid repeatedly importing the same file while diagnosing a storage error.

Open your solve history Read how local data is used →