Review files, warnings and checksums

The file list

Each row is one project file. You see the file name and project name, the app that opens it, the size and the Checksum badge. Use Search files to find a file by name, project or app, and the App filter to show only one app’s files. The summary above the list counts all files, including those hidden by a filter.

File details

Select a file name to open its details on the right:

• App and Format — Bundlekeep recognises 54 project formats of the premium apps, its own backups included, for example Kerfwise Form Studio project or Flipline exposure sheet. A file without a known format shows Unrecognised format.
• Project name — the name stored inside the project.
• Size and Embedded data items — embedded items are pictures or other files stored inside the project, such as the photo of a Lumina project. They are part of the file and are backed up with it.
• Checksum and SHA-256 — see below.
• Source — Chosen file, Saved in the browser (with the store it came from), Example project, Received from another app or Built with the API.

Open Show the file content to look at the first part of the project text.

Warnings

A warning means that restoring this file alone will not bring everything back:

• Paperwell dossier without its document files. Paperwell keeps PDFs and scans separately. Keep the original documents, or save the dossier in Paperwell as a file that includes its documents and add that file.
• Reelcraft media files outside the project. Keep the original audio, video and image files.
• Keysmith project that keeps secrets. You chose to keep secrets in that Keysmith project. Encrypt the backup before you store or share it.
• Unrecognised format. Check which app opens the file before you rely on it.

Files with warnings are counted under With warnings. If a file says No known gaps in this file., everything it refers to is inside it.

Checksums

When a file is added, Bundlekeep computes its SHA-256 checksum, a 64-character fingerprint of the exact text. When you open the backup later, Bundlekeep computes it again:

• Verified — the file is byte for byte the one you added.
• Changed — the text is different. The backup file may have been damaged or edited. Do not rely on that file until you have checked it.
• No checksum — the file came from an older backup without checksums. Saving the backup file records one.

You can double-check a downloaded file yourself: Help › Related tools links to Hash & HMAC Calculator. Its SHA-256 must equal the value shown here.

A verified checksum proves the file is unchanged. It does not prove that a future version of the app still opens an old project, so test a restore now and then.

Next: Restore projects without overwriting anything.