DCP vs. IMF vs. Network Delivery Specs

What's the Difference Between DCP, IMF, and Network Delivery Specs?

A DCP is a theatrical playback package built to run on cinema projectors. An IMF is a studio-grade, component-based master built for a streamer or broadcaster used to generate every other downstream version of a film or show. A network delivery spec is the platform-specific rulebook, covering resolution, audio configuration, and QC thresholds, that governs whether either package gets accepted. Each has a unique part to play in the delivery process, and none of the three is interchangeable.

‍

What Is a DCP Used For?

A Digital Cinema Package is the file format that plays back on a commercial cinema server. It's what's required any time a project screens theatrically, whether that's a festival premiere, a one-night theatrical release, or even a private screening room.

A DCP is built from a Digital Cinema Distribution Master, typically a DPX or TIFF image sequence, and packaged using JPEG 2000 image encoding, uncompressed audio, and XML metadata inside a defined folder structure that cinema servers are built to read. Many theatrical DCPs are also encrypted and require a Key Delivery Message, or KDM, to unlock playback on a specific server for a specific date range. Similar to IMF packages, DCPs cannot simply be 'exported' from your favorite NLE, but must be built with dedicated software.

‍

How Is an IMF Different From a DCP?

An IMF, or Interoperable Master Format, is not a playback format. It is a component-based master package: image, audio, subtitle, caption, and metadata assets stored as separate files and assembled into a finished version through a Composition Playlist, or CPL. Streamers like Netflix require delivery as an IMF package generated directly from an intermediate mezzanine asset, like a ProRes HQ video file, in the highest available resolution. Internally, the studio uses that structure to assemble every regional, language, and platform-specific version a title needs, without building a separate flattened master for each one.

The practical difference from a DCP is structural. A DCP is a finished package meant to be projected as delivered. If something needs to change, theatrical delivery typically handles it through a Version File, or VF, that references the original package (the OV) and replaces only specific reels or elements; the VF won't play without the OV present on the server. IMF works on the same principle at a finer grain, since its Composition Playlist can point to a single replaced audio track, subtitle file, or textless video component without touching anything else.

‍

What Varies Across Network and Streamer Delivery Specs?

Every platform maintains its own version of a similar checklist, but the specs differ by network:

• Video resolution and color space (UHD versus HD, Rec. 709 versus Rec. 2020, etc)
• Frame rate and wrapper format (23.98 versus 24, MXF versus ProRes, or platform-specific containers)
• Audio configuration and channel mapping (stereo, 5.1, Dolby Atmos or Immersive Audio)
• Loudness targets and true peak ceilings
• Caption, subtitle, and dubbing requirements
• Branding and ident placement, or explicit instructions to deliver without

None of these are purely cosmetic details. A title can be creatively locked and still fail delivery on a mismatched audio channel map or an unapproved wrapper.

‍