Shot Delivery Preflight / Delivery spec checklist

Delivery QC

The VFX delivery spec checklist

Client delivery specs are precise on purpose: their ingest automation checks every field, and a single mismatch bounces the package. This is the checklist to run against your own delivery first.

Image sequences (EXR)

Frames and naming

QuickTimes

The package itself

Do it mechanically. Every item above is checkable from file headers and names - no pixels needed, no opinions involved. That is exactly what Shot Delivery Preflight automates: pick the spec, scan the folder, get a READY / NOT READY verdict with a fix list, in seconds.

FAQ

Why do specs ban lossy EXR compression?

VFX pulls are working material: they get comped, graded and re-rendered. Lossy compression (DWAA/DWAB, B44) bakes in loss that compounds through the pipeline, so masters and pulls are almost always required lossless - ZIP, PIZ or none.

What is the difference between the data window and display window?

The display window is the intended frame; the data window is where pixels actually exist (it can be larger for overscan or smaller for cropped renders). Specs that mention overscan constrain both - a mismatch is worth checking before upload.

Do I need to check every frame?

For header properties, sampling first/middle/last frames per sequence catches setting changes; for frame continuity you check every NAME (cheap) rather than every pixel. That combination is why a 100 GB delivery can preflight in seconds.

Run the check before the client does

Shot Delivery Preflight batch-checks EXR headers, naming and QuickTimes against the delivery spec in your browser - headers only, nothing uploads. 14-day free trial.

Try the example delivery →

Keep reading