How it works
Verify before you deliver.
Bundvera answers two questions: is everything ready to hand over, and did everything arrive intact? Here is exactly what happens on each side.
On the sender’s computer
- Drop the delivery folder. Usually the folder that holds your Premiere project and its media. Bundvera asks for nothing else: no account, no upload.
- Choose a depth. Quick Preflight for a fast structural check, Deep Verification when you’re ready to hand over.
- Bundvera lists every file, reads the media references of any Premiere Pro project in the folder (experimental), and checks names that won’t survive a move between macOS and Windows.
- Review the issues. Each one says what happened, why it matters, which file is affected, what to do, and whether it stops the delivery from being marked ready.
- Fix and check again. Relink or copy the missing media, rename problem files, then run the check again.
- Save the manifest and the receipt. After Deep Verification, Bundvera saves a manifest for the recipient’s software and a PDF or HTML receipt for people.
- Send the folder and the manifest with whatever you already use.
Quick Preflight or Deep Verification
Both modes report the same structural problems. Only Deep Verification reads the contents of every file, so only Deep Verification can produce a manifest the recipient can verify against.
| What it does | Quick Preflight | Deep Verification |
|---|---|---|
| Lists every file and its size | Yes | Yes |
| Reads Premiere Pro media references (experimental) | Yes | Yes |
| Flags media missing from the folder or stored outside it | Yes | Yes |
| Flags names that break on Windows or across Mac volumes | Yes | Yes |
| Reports files and folders it can’t read | Yes | Yes |
| Computes a SHA-256 fingerprint of every byte | No | Yes |
| Saves a manifest the recipient can verify against | No | Yes |
| Produces a PDF or HTML receipt | No | Yes |
| Time it takes | Usually seconds: file contents aren’t read | Roughly the time it takes to read the whole project from its drive |
What the statuses mean
Bundvera keeps five statuses apart. A check that couldn’t be performed is never shown as a check that passed.
| Status | Meaning | Example |
|---|---|---|
| PASS | The check ran to completion and found no problem. | Every file listed in the manifest is present and byte-identical. |
| FAIL | A confirmed problem. | Media the Premiere project uses is missing from the folder; a received file differs from the manifest. |
| REVIEW | Something needs your judgement before you send or accept. | A file name Windows won’t accept; extra files in a received folder; a Premiere project saved by an unverified version. |
| UNSUPPORTED | Bundvera can’t perform this check for this format or configuration. | Fonts and plugins; dependencies inside After Effects or DaVinci Resolve projects. |
| INCOMPLETE | The check could not finish. | A drive was disconnected or the scan was cancelled. Nothing is reported as missing until a scan completes. |
What’s in a manifest
The manifest is a small, versioned JSON file named <name>.bundvera-manifest.json. It is what the recipient’s copy of Bundvera compares against.
It contains
- The path of every file relative to the delivery folder, its size and its SHA-256 fingerprint
- A verification ID, the date and time, and the Bundvera version that created it
- The checks that were performed, the issues recorded at the sender (such as a missing dependency) and the overall result
- An integrity digest that detects damage or casual editing of the manifest
It never contains
- File contents, passwords or tokens
- The location of the folder on your computer
- A digital signature: it doesn’t prove who created it
Preparing a delivery copy
Instead of copying files by hand, you can ask Bundvera to prepare the delivery:
- It copies the scanned project into a new folder you choose, keeping the folder structure.
- It never moves, modifies or deletes the originals, and it refuses to overwrite existing files.
- It re-hashes every copy and compares it with the original’s fingerprint.
- If you cancel, it can resume later without copying finished files again.
Media that can’t or shouldn’t be packaged, such as licensed fonts and plugins, stays your responsibility. Bundvera doesn’t collect them.
On the recipient’s computer
- Open Bundvera and choose to verify a received delivery. Verifying is free.
- Pick the manifest and the folder you received.
- Bundvera recomputes the SHA-256 fingerprint of every file and compares it with the manifest.
- Read the result. Missing and modified files are a FAIL. Extra files and files renamed only by capitalisation need REVIEW. If a drive disconnects, the result is INCOMPLETE rather than a guess. The sender’s recorded warnings stay visible.
- Export a report to send back to the sender if something needs fixing.
What a pass proves
A pass proves that every file listed in the manifest is present and byte-identical to what the sender scanned. It doesn’t prove that the project opens or renders, that fonts, effects and plugins are installed, or who created the manifest. Open the project in your editing app to confirm it works.