What Delivery Actually Means
You spent months finishing your film. Now comes a step nobody warns you about: handing it over in the precise technical format the festival, platform, or distributor demands. Get it wrong and your masterpiece bounces at the door. Delivery is the unglamorous last mile that decides whether your film is ever seen.
Every guide to making a film ends when the film is done. But "done" isn't the finish line — delivery is, and it's the step that quietly kills more indie films' chances than any creative problem. Here's the reality: a festival, a streaming platform, a broadcaster, or a distributor doesn't want "your film." They want your film in an exact technical package — a specific format, resolution, frame rate, codec, audio configuration, with specific accompanying files — and if you hand them anything else, they reject it, or at best send it back with a list of fixes while your deadline burns. This isn't bureaucracy for its own sake; their playback systems and pipelines physically require these formats to work. So the mindset shift for this whole course is that delivery is a technical translation problem, not a creative one: your job is to take your beautiful finished film and repackage it into whatever precise shape each destination requires. It's unglamorous, it's fiddly, and it's absolutely essential — because a film nobody can play is a film nobody sees.
Why delivery trips people up
The reasons this step catches filmmakers off guard:
- It's invisible until it isn't. Nobody talks about delivery while you're shooting and editing, so it hits you as a surprise at the exact moment you're exhausted and out of money — the worst time to learn a new technical skill.
- Every destination is different. A cinema wants a DCP; a festival might want a DCP or a screener; a streamer wants a specific master and files; a broadcaster wants yet another package. There's no single "export" that works everywhere.
- The specs are unforgiving. Wrong frame rate, wrong color space, wrong loudness, a missing file — any one can trigger a rejection. Delivery is pass/fail, and the standards are precise.
- It's often a hard deadline. Festival delivery dates are fixed and strict. Miss the technical spec and miss the deadline, and your acceptance can evaporate. Delivery problems become existential fast.
- It feels like a foreign language. DCP, mezzanine, ProRes, KDM, IMF, loudness, dual-mono — the vocabulary alone is intimidating. But it's learnable, and this course teaches it plainly.
The right mindset going in
The single most valuable thing you can do about delivery is plan for it early instead of scrambling at the end. The filmmakers who deliver smoothly aren't technical geniuses — they're the ones who found out the delivery requirements before they finished, so their edit, color, and sound were built to produce the right masters from the start. The ones who suffer are the ones who "finished" the film and only then asked "wait, how do I actually send this to the festival?" — and discovered their project was the wrong frame rate, or they never made a proper master, or the loudness is wrong for broadcast. So carry two principles through this course. First, know your destination's specs before you lock anything: read the delivery requirements of the festivals and platforms you're targeting the way you'd read a recipe before cooking, because they dictate technical choices upstream. Second, make a proper high-quality master first, then derive everything from it — because a clean master is the source you'll repackage into a DCP, a screener, a streaming file, or a broadcast package, and if the master is right, every delivery is just a translation. That's the roadmap of everything ahead: we'll build up from what a master is, through codecs and specs, into the DCP itself and how to make and test one, then subtitles and accessibility, and finally the specific packages festivals, streamers, and broadcasters demand — closing with a checklist and archive. None of it is as scary as the jargon suggests. Delivery is just the craft of handing your film over correctly, and learning it is the difference between a film that gets played and a film that gets bounced. Let's start with the foundation everything else derives from: your master file, next.
My first festival acceptance nearly became a rejection. I'd finished the film, celebrated, then read the delivery email: DCP required, specific frame rate, specific audio config, due in twelve days. I had no master, didn't know what a DCP was, and my project was the wrong frame rate for their spec. I spent those twelve days in a panic learning what should have taken a calm afternoon months earlier. We made the deadline by luck. Now the first thing I do on any film is read the delivery specs of where I want it to go — before I lock a single frame. Delivery isn't the end of the work. It's part of it.
Run your finished film through Distribution Readiness — check your masters, deliverables, and specs against what festivals and platforms require, so you catch problems before a rejection letter does.