Premium apps

Project Backup Verifier

Check a Bundlekeep backup file by file and get a restore checklist.

Paste a .bundlekeep.json backup, or upload the file below.

Used instead of the pasted text when given.

More options

Exact file name from the backup; the tool returns that project file for download.

Try an example: Verify the workshop example backup · Extract the circuit from a backup · Spot a changed file

More about this tool

How it works

Open a Bundlekeep backup: the tool recomputes the SHA-256 checksum of every project file, lists what each file is and what it leaves out, writes a restore checklist per app and can extract one project file for download.

  • Validates the Bundlekeep format (version 1), unique file names, JSON content and the limits of 200 files, 10 MB per file and 50 MB in total.
  • Recomputes SHA-256 for each file and compares it with the checksum recorded when the file was added: verified (identical), changed (different) or no checksum (older backups).
  • Recognises the app and format of each file and lists the same warnings as the Project File Identifier (documents or media outside the file, kept secrets, unknown format).
  • The restore checklist groups files by app with workspace links. Restoring means downloading a file and opening it in its app; nothing is written into an app.

Sources

Part of Bundlekeep

How to use the Project Backup Verifier

Check every file of a Bundlekeep backup against its checksum, see what each file is and get a restore checklist.

What it is for

A backup is only useful if it is intact when you need it. The Project Backup Verifier opens a Bundlekeep backup and checks each project file against the SHA-256 checksum that was recorded when the file was added. It also tells you which app opens each file, warns about parts that live outside a project, and writes a restore checklist grouped by app.

Use it for regular checks of stored backups — monthly from a script, for example — or to pull a single project out of a backup without opening the workspace. Give the exact file name in File to extract and the result contains that file as a download.

The verifier does not repair files, and a verified checksum does not promise that a future app version still opens an old project.

Worked example

The first example verifies the "Workshop backup" from the Bundlekeep templates. The tool answered: "Checked 4 files: 4 verified, 0 without a checksum."

Worked example
FileAppBytesChecksum
base-cabinet-600.kerfwise.jsonKerfwise413Verified
led-with-series-resistor.ohmforge.jsonOhmforge2,580Verified
3-station-line.twinworks.jsonTwinworks6,237Verified
name-tag.threadsmith.jsonThreadsmith1,446Verified

Together that is 10,676 bytes from 4 apps, and the callout confirmed that every file matches its checksum. The restore checklist starts with "# Restore checklist: Workshop backup" and lists one section per app with a link to its workspace.

The third example adds a single space inside the cabinet project. Its size becomes 414 bytes and the result changes to "Checked 4 files: 1 file changed since it was added", with the cabinet marked "Changed" and a warning not to rely on it until you have checked it. One space is enough — that is the point of a checksum.

How to read the result

  • Verified means the file is byte for byte the one that was added. Changed means the text differs. No checksum appears for files from backups made before checksums existed; saving the backup again in the workspace adds them.
  • Apps and the table show what you would get back, and where to open it.
  • The restore checklist (Markdown) has one tick box per file, the format and project name, and every warning.
  • Download appears when you asked to extract a file.

Tips and common mistakes

  • Upload the backup file instead of pasting it when it is larger than a few megabytes; the file field accepts up to 55 MB.
  • The extract name must match exactly, including the extension, for example led-with-series-resistor.ohmforge.json.
  • A "Changed" file is not necessarily lost. Compare it with another copy of the backup before you delete anything.
  • Keep at least two copies of important backups and verify both.
  • The workspace performs the same check whenever you open a backup, entirely in your browser.

FAQ

What does a changed checksum mean?

The file's text is different from when it was added — a damaged download, a sync conflict or a manual edit.

Can it verify backups made by the first Bundlekeep release?

Yes. Those files have no checksums yet, so they are reported as "No checksum" rather than verified.

Is the backup stored on the server?

No. It is read to answer the request; only an extracted file is kept as a download for about two hours.

How do I restore from the checklist?

Download each file, open its app with the link in the checklist and use the app's command for opening a project file.

Guide last updated:

For scripts and AI agents

  • JSON API: POST https://bundlekeepbackupverifier.usefulweb.app/api/v1/calculate (same calculation as this page)
  • Interface description: OpenAPI 3.1 · AI guide: llms.txt
  • MCP server (Streamable HTTP): https://bundlekeepbackupverifier.usefulweb.app/mcp · tool name bundlekeep_backup_verifier
Example request
curl -s -X POST https://bundlekeepbackupverifier.usefulweb.app/api/v1/calculate \
  -H 'content-type: application/json' \
  -d '{}'
Feedback · ideas & bug reports welcome