A structural DCP pre-check, without uploading the package.
Your DCP stays on your machine. The browser checker reads its package XML and files locally, then reports structural and integrity problems before delivery.
Select the local DCP folder
The browser utility reads ASSETMAP, PKL, CPL, and referenced files directly from the folder you select. Nothing leaves your machine and nothing is uploaded.
Package pre-check
We parse the XML, follow ASSETMAP and CPL references, confirm files listed in the packing list are present, compare declared sizes, and optionally verify each asset's SHA-1 hash.
Plain-English report
You get a package-level pass/fail result with specific explanations for malformed XML, missing references, size mismatches, and failed hashes.
Resolve or escalate
Package errors can be returned to the filmmaker for a clean copy or repair. MXF essence, projection behavior, and full conformance require a separate review.
A reliable package check is the first gate, not the final projection test.
The current checker validates XML structure, package cross-references, file presence, declared sizes, and optional SHA-1 hashes. It does not decode MXF picture or sound essence, inspect channel mapping or subtitle rendering, or certify SMPTE Bv2.1 conformance. Encrypted packages are a paid add-on.
Package structures recognized
SMPTE namingInterop namingASSETMAP / PKL / CPLLocal SHA-1 verification
Full review remains separate
A clean package pre-check means the files are present, internally referenced, correctly sized, and hash-consistent. It is not a guarantee of cinema-server playback.
Most DCP failures aren't creative problems. They're plumbing problems.
A DCP should not be an adventure. A folder can look complete while containing broken XML, unresolved asset references, truncated copies, or files whose SHA-1 hashes no longer match the packing list. Those are package-level problems you can catch before delivery.
Start with a package pre-check
Run the local checker first to confirm the folder structure and file integrity before deciding whether you need deeper technical review.
You get a plain-English report
No jargon dump. We tell you what's wrong, why it matters, and what to do about it.
It costs nothing
The package check runs in your browser and needs no account. Nothing is uploaded, so there is nothing for us to charge you for.
Accessibility checks are the next thing we build.
Caption line length, descriptor presence, and declared accessibility tracks that turn out to be empty are the failures festivals catch latest and care about most. Today those are part of a paid engagement with a human reading the results. Automating them is the next build, and we would rather say that plainly than imply the software already does it.