Xenon Post
Xenon Post — Tools & Reference

DCP — Digital Cinema Package

The Digital Cinema Package is the universal format for theatrical exhibition. Understanding how DCPs work — and in particular, how the 4K versus 2K decision affects quality across different projection systems — saves independent filmmakers from delivering the wrong thing to the wrong screen.

01 — What is a DCP?

A DCP — Digital Cinema Package — is the standardised format for distributing films to cinemas worldwide. It replaced 35mm film prints as the primary theatrical distribution medium from around 2006 onwards, and today virtually every commercial cinema operates a digital cinema server that plays DCPs. The format is defined by SMPTE standards (principally ST 428) and administered by the Digital Cinema Initiatives (DCI) — a joint venture of the major Hollywood studios.

Structurally, a DCP is a folder of files: JPEG 2000-encoded video in MXF containers, uncompressed PCM audio, XML metadata (a Composition Playlist, a Packing List, and an ASSETMAP), and optionally subtitle files. The structure is closely related to IMF — they share the same CPL, PKL, and ASSETMAP concepts, the same MXF container, and the same JPEG 2000 video codec. The key differences are the target use case (theatrical exhibition versus streaming mastering) and the DCI-specific colour encoding and encryption requirements.

DCP
Theatrical distribution
Delivered to cinemas on hard drive or via satellite. Encrypted with venue-specific KDMs for theatrical release. Decoded by a Digital Cinema Server and projected through a DCI-compliant projector calibrated to DCI-P3.
IMF
Streaming mastering
Delivered to streaming platforms for ingestion and transcoding. Not encrypted in the same way; PKL hash integrity is the primary security. A DCP is typically created from an IMF package for simultaneous theatrical and streaming releases.

A DCP is not a file you can open in QuickTime Player or a standard media player. It requires either a real Digital Cinema Server, a DCP playback application (DCP-o-matic Player, EasyDCP Player), or a projector with built-in DCP decoding. This is worth noting for independent filmmakers who may want to verify their DCP before delivery — a validation playback on appropriate software is essential.

02 — 4K vs 2K: the critical decision

This is the most consequential technical decision for independent filmmakers creating a DCP — and the one most often misunderstood. The intuition that “4K is better than 2K” does not translate cleanly to the cinema context, because the result depends not just on the DCP resolution but on the projection system at the venue.

What the projectors actually are

Digital cinema projectors fall into two categories by resolution. 2K projectors — the dominant type in most cinemas worldwide, including the majority of Australian multiplex and independent cinema screens — have a native resolution of 2048 × 1080 pixels. 4K projectors are found in premium large-format (PLF) screens, IMAX digital halls, and higher-end multiplex auditoriums. 4K projectors are meaningfully less common than 2K, particularly in regional and independent venues.

4K PROJECTOR
Premium / PLF screens
2K PROJECTOR
Majority of cinema screens worldwide
4K DCP
Best quality

Full native resolution rendered end-to-end. Ideal — when confirmed 4K venue.

Avoid

Many 2K servers reject 4K DCPs outright. Those that play them downscale in real-time — lower quality than a native 2K DCP.

2K DCP
Acceptable

Projector upscales to fill 4K panel. Imperceptible quality difference from native 4K DCP in practice.

Recommended

Full native quality. Compatible with the majority of cinema screens worldwide.

DEFAULT FOR INDEPENDENT RELEASE
Fig. 1 — The four projection scenarios. A 4K DCP on a 2K projector is the worst outcome: most 2K servers reject 4K DCPs entirely, and those that play them perform a real-time hardware downscale that is lower quality than a post-production 2K encode. A 2K DCP is compatible everywhere.

Why a 4K DCP on a 2K projector is a problem

When a 4K DCP is ingested by a 2K Digital Cinema Server, one of two things happens. Either the server rejects the DCP entirely — many 2K servers cannot read 4K packages — or the server decodes the 4K JPEG 2000 frames and downscales them to 2K in real time, then sends 2K frames to the projector. That real-time downscale is performed by the server’s processing hardware under the time constraints of live playback. It is generally lower quality than the downscale that a post-production tool like DaVinci Resolve can produce — one that works at any speed, with a high-quality algorithm, on the full frame.

There is also a bitrate consideration. The DCI specification allows a maximum video bitrate of 250 Mbps for both 2K and 4K DCPs. A 2K DCP at 250 Mbps has roughly four times more compressed data per pixel than a 4K DCP at the same bitrate. In practice, both are visually lossless at typical operating bitrates, but the principle holds: a native 2K encode at DCI bitrates will be a sharper, cleaner representation of 2K-resolution content than a 4K encode of the same content that is then hardware-downscaled to 2K for projection.

Why a 2K DCP on a 4K projector is fine

When a 2K DCP is played on a 4K projector, the server outputs 2K frames and the projector’s internal processing upscales to fill the 4K panel. This is not the same as a post-production upscale — it happens at the projector level — but in practice the difference between a 2K DCP upscaled to 4K and a native 4K DCP is imperceptible from a cinema seat at normal viewing distance. The resolution of human vision at typical cinema viewing distances means the additional pixels of a 4K DCP over a quality 2K DCP are rarely visible.

For independent theatrical releases and festival submissions: deliver a 2K DCP as your standard package. It is universally compatible, guaranteed to ingest on any server, and produces full native quality on the majority of screens worldwide. Create a 4K DCP only when you have confirmed, in writing, that the specific venue has a 4K-capable server and projector and has specifically requested 4K.

When 4K is the right choice

A 4K DCP is appropriate when you have confirmed you are delivering to a verified 4K venue — typically a PLF screen at a major multiplex, a Dolby Cinema hall, or a purpose-built 4K screening room. It is also appropriate if your source material was acquired in genuine 4K resolution (on an ARRI ALEXA 35, Sony VENICE 2, RED MONSTRO, or equivalent) and the grade has been completed at 4K resolution. Delivering a 4K DCP from a 2K source — or upscaling a 2K grade to 4K for the DCP — produces no quality improvement and simply creates a larger, less compatible file.

ScenarioRecommended DCPReason
Festival circuit — venues unknown2KCompatibility is paramount; you cannot know the server capabilities at every venue in advance
Independent theatrical — regional and art-house screens2KThe majority of these venues run 2K servers; 4K DCPs may be rejected outright
Multiplex release — mix of 2K and 4K screens2K (primary) + 4K on requestDeliver 2K as the standard; create 4K only for confirmed 4K screens
Premium large-format (PLF) or Dolby Cinema screen4KThese venues have 4K-capable servers and projectors; 4K DCP maximises quality
Source acquired and graded at 2K or lower2K alwaysA 4K DCP from a 2K source offers no quality improvement and introduces compatibility risk
Source acquired and graded at genuine 4K4K (if venue confirmed)Full benefit of 4K acquisition is realised only on a 4K projector with a 4K DCP

03 — Aspect ratios and container formats

The DCI specification defines a set of standard pixel containers. These are not the same as the aspect ratios of the content — they are the outer boundaries of the picture data. The cinema’s screen masking system (motorised panels at the edges of the screen) adjusts to frame the active picture area within the container.

Scope2.39 : 1
4096 × 1716
2048 × 858 (2K)
CinemaScope / anamorphic
Flat1.85 : 1
3996 × 2160
1998 × 1080 (2K)
Standard theatrical / 16:9 source
Full container1.90 : 1
4096 × 2160
2048 × 1080 (2K)
Defines DCI boundary
Fig. 2 — DCI container formats at representative proportions. Scope (2.39:1) is the widest; its letterbox zones at top and bottom are masked by the screen. Flat (1.85:1) has a near-identical height to the full container but is slightly narrower. The full container boundary is rarely used directly.

Scope (2.39:1)

Scope is used for films shot in the CinemaScope or anamorphic wide-screen aesthetic — or any film with a 2.39:1 aspect ratio. In a 4K DCP, the scope container is 4096 × 1716 pixels; in 2K it is 2048 × 858. The unused top and bottom of the 4096 × 2160 full container are filled with black and masked by the cinema’s screen masking. The cinema must be set to “scope masking” before a scope DCP can be shown — this is a physical change to the screen, not just a software setting. Communicate the format to the venue well in advance.

Flat (1.85:1)

Flat is the standard format for most drama, documentary, and commercial feature content that was not shot in a wider anamorphic ratio. The flat container is 3996 × 2160 (4K) or 1998 × 1080 (2K) — occupying the full height of the DCI frame boundary with a very slightly reduced width (50 pixels less on each side of the full 4096). That thin sliver is masked by the cinema’s screen panels and is imperceptible in the auditorium. Content shot and finished at 1.85:1 fills the flat container exactly.

What about 16:9 content?

16:9 (1.778:1) is narrower than flat and is not a DCI standard container. Independent filmmakers shooting on standard cameras — iPhones, DSLRs, most digital cinema cameras in their default mode — end up with 16:9 footage. The correct delivery is a flat DCP with the 16:9 image centred within the 1.85:1 container, leaving thin black pillar bars on each side (about 18 pixels wide each at 2K). These bars are imperceptible from a cinema seat and are the cleanest approach — no cropping of the intended frame is required.

A scope DCP played without scope masking, or a flat DCP played without the correct flat masking, will appear with the wrong aspect ratio — either with visible black bars or with the image stretched. Always confirm with the cinema technician that they know the format of your DCP and that the correct masking is set before the screening begins.

04 — Colour: DCI-P3 and XYZ encoding

Cinema colour is defined by the DCI specification as DCI-P3 — the same P3 colour primaries used in streaming delivery, but with a different white point. DCI-P3 uses the DCI white point (approximately CIE xy: 0.314, 0.351 — roughly 6300 K), which is slightly warmer and yellower than the D65 white point used in broadcast, streaming, and Display P3. The difference is subtle but visible: a monitor calibrated to D65 (Display P3) will appear slightly cooler than a DCI-calibrated cinema projector.

Inside the DCP, the video data is not stored as DCI-P3 RGB. It is encoded in CIE XYZ colour space with a 2.6 gamma transfer function (written as X’Y’Z’ in the specification). The cinema projector decodes the XYZ values and its internal colour management converts to DCI-P3 for projection. DCP creation tools (DaVinci Resolve, EasyDCP) handle the P3-to-XYZ conversion automatically — you work in P3 and the tool writes XYZ to the DCP.

Grading for cinema vs broadcast

A grade completed for Rec.709 broadcast delivery will not look correct in a cinema. The DCI white point shift means that neutral whites will appear slightly warm, and the wider P3 gamut means that saturated colours — particularly greens and reds — can be rendered more vividly than the Rec.709 grade intended. For any theatrical release, a dedicated cinema grade on a DCI-P3-calibrated monitor is strongly recommended.

If a separate cinema grade is not possible, content can be delivered in a DCP from a Rec.709 grade with an automatic colour space transform (CST) applied on export. This avoids the white point mismatch but may not produce optimal results in highly saturated scenes. Note in the delivery paperwork that the DCP was created from a Rec.709 master so the cinema technician is aware.

DCI-P3 has roughly 26% more colour volume than Rec.709. A film graded with the intention of a cinema release should be graded on a DCI-P3 calibrated display from the start — retrofitting a cinema grade from a Rec.709 deliverable after the grade is locked is less satisfying than having graded to the larger gamut from the beginning.

05 — Audio in a DCP

DCP audio is uncompressed PCM stored in MXF containers at 24-bit depth and either 48 kHz or 96 kHz sample rate. Up to 16 audio channels can be carried in a DCP, though the standard theatrical configuration is 5.1 surround (six channels: L, R, C, LFE, Ls, Rs), with 7.1 configurations (adding Lss and Rss for side surround) increasingly common in larger venues.

Cinema loudness: no LUFS target

Unlike streaming and broadcast delivery, cinema audio does not have an integrated LUFS loudness target. The cinema is a calibrated acoustic environment: the room’s sound system is set to a reference level defined by the DCI specification — 85 dB SPL at the mixing position when a 1 kHz sine wave at the system’s reference level (0 dBFS in some configurations, or at a standardised fader position) is played. A film mix created at a calibrated cinema mixing stage will play at the correct level in any DCI-calibrated cinema.

The practical consequence for independent filmmakers is significant. A stereo mix or a mix created in a non-calibrated studio environment will not sound correct in a cinema. The bass extension of a proper 5.1 LFE channel, the rear surround depth, and the level calibration are all set for the cinema acoustic — and a mix that has not been made for that environment will either sound too quiet (if the mix was normalised for streaming) or too loud and distorted (if it was not attenuated correctly).

Channel configChannelsMappingNotes
5.16L · R · C · LFE · Ls · RsStandard theatrical — required for most theatrical releases
7.18L · R · C · LFE · Lss · Rss · Ls · RsAvailable in larger auditoria; side and rear surround separation
Stereo (Lo/Ro)2L · RAcceptable for short films and smaller festival venues; not recommended for theatrical
HI / VI+2Hearing Impaired · Visually ImpairedOptional accessibility tracks; increasingly expected for theatrical release in Australia

For Australian theatrical releases — even short runs or one-off festival screenings — a 5.1 mix mastered at a calibrated cinema stage is the professional standard. If budget constrains this, a stereo Lo/Ro mix can be delivered; it will be routed to the left and right speakers only in most cinema processors, which is workable for intimate screenings but will not fill a large auditorium appropriately. Agree the audio format with the venue in advance.

06 — Subtitles in a DCP

DCP subtitles can be delivered in two forms: XML timed text (SMPTE Timed Text, similar in concept to IMSC) or PNG bitmaps with associated timing XML. XML timed text is rendered by the cinema server at playback using the embedded font; PNG subtitles are pre-rendered at the source resolution and displayed as images. PNG subtitles are more predictable in appearance across different server brands but are larger files and less flexible. XML subtitles are more common for English-language films with occasional foreign-language subtitles.

Subtitles in a DCP are open — they appear on screen for all audience members when enabled in the CPL. There is no closed-caption equivalent for the main picture in standard DCP; hearing-impaired (HI) audio tracks and separate assistive listening systems handle accessibility. For foreign-language films or films with passages of non-English dialogue, subtitles are embedded in the DCP and are always visible.

07 — Encryption and KDMs

Theatrical DCPs are encrypted using AES-128 encryption. Without the correct KDM (Key Delivery Message), the DCP cannot be played on any server. The KDM is generated from the cinema’s server certificate — a unique cryptographic identity embedded in the hardware at manufacture — and is valid only for that specific server, for a specific DCP, during a specific date range. Sending a KDM to a cinema is as important as sending the DCP itself.

KDM logistics

Obtaining KDMs requires knowing each venue’s server certificate in advance. Cinema chains maintain certificate databases; independent venues may need to supply their certificate by request. KDM management services (provided by specialist post houses, theatrical distributors, and some DCP creation tools) handle this process and can generate KDMs on short notice. For a wide release across many venues, a theatrical distributor handles KDM management as part of their service.

KDMs have a validity window — a start date and an end date. If a KDM expires mid-run, the DCP will stop playing. When ordering KDMs for a theatrical season, build in a margin: request validity from two days before the first scheduled screening to two days after the last, and keep a record of every KDM issued.

Unencrypted DCPs

For festival submissions, press screenings, and distributor review, an unencrypted DCP removes the KDM logistics entirely — any server can play it without a key. Unencrypted DCPs are standard practice for festival submissions and short film screenings. They carry a piracy risk for theatrical release of commercial features, but for independent films and short films the practical risk is low. Most DCP creation tools (including DaVinci Resolve) can create both encrypted and unencrypted versions.

Always confirm with each venue whether they need an encrypted DCP with a KDM or an unencrypted DCP. Sending an encrypted DCP to a venue that expected an unencrypted one — or sending the wrong KDM, or a KDM for the wrong server — means the DCP cannot play. For independent releases with limited technical support at the venue, an unencrypted DCP is often the more reliable choice.

08 — Creating a DCP

DaVinci Resolve Studio

DaVinci Resolve Studio (the paid version) is the most accessible tool for creating DCPs. Since version 16, Resolve can export DCP packages directly — both 2K and 4K, scope and flat, encrypted and unencrypted. The workflow is: complete the grade with Resolve Color Management enabled and the output colour space set to DCI-P3 (or let Resolve apply the P3-to-XYZ conversion automatically), then export via File → Export → DCP.

Resolve handles the JPEG 2000 encoding, MXF wrapping, CPL and PKL generation, and XYZ colour encoding automatically. For straightforward single-language theatrical deliverables, Resolve’s DCP export is technically sufficient. For complex packages requiring encrypted KDM distribution to multiple venues, a specialist DCP distribution service or dedicated tool is more practical.

Other tools

ToolTypeNotes
DaVinci Resolve StudioPaid (included with Studio licence)Best option for most independent filmmakers; handles complete DCP creation from grade to package
EasyDCPPaidIndustry-standard tool with advanced options; handles KDM generation; used in many post facilities
DCP-o-maticFree / open sourceCreates valid DCPs from most source formats including ProRes; limited colour management tools; good for straightforward jobs
OpenDCPFree / open sourceCommand-line based; technically capable but requires more technical knowledge
DCP-o-matic PlayerFree / open sourcePlayback and validation only; essential for verifying a DCP before delivery

Validation before delivery

Play the entire DCP back in DCP-o-matic Player or a comparable application before delivering it to any venue. Watch the full programme — not just a few minutes — with particular attention to audio sync at scene cuts, subtitle timing, and any black frames or picture artefacts at reel boundaries. A DCP that passes software playback validation is much less likely to fail at a cinema server, though software players and real servers do not always behave identically. For high-stakes screenings (festivals, premieres, theatrical openings), arrange a technical check at the venue on the actual server before the public screening.

The most common cause of a failed cinema screening is not a technical problem with the DCP — it is logistics: a missing KDM, a KDM for the wrong server, a KDM that hasn’t arrived yet, or a DCP that didn’t transfer correctly. Deliver the DCP to the venue at least 48 hours before the screening. Confirm receipt, confirm the KDM is loaded (if encrypted), and ask the projectionist to ingest and verify the DCP on their server — not just confirm the files arrived.

09 — Delivering the DCP

Digital upload has become the preferred delivery method for independent DCP delivery, and for good reason: no physical shipping cost, no risk of a drive being lost or arriving late, and the ability to resend instantly if something goes wrong. Many festivals and independent cinemas now accept — or actively prefer — digital delivery, and cinema chains are progressively rolling out secure ingest portals for exactly this purpose.

Digital delivery

DCPs uploaded digitally are transferred as a compressed archive or via a managed file transfer service directly to the cinema’s ingest system. The cinema server then ingests the DCP from internal storage in the same way it would from a physical drive. Common digital delivery methods include upload portals operated by the cinema or distributor, Aspera-based transfers used by larger chains, and services such as DCP Transfer, Cinedrop, and similar platforms built specifically for DCP logistics. Always confirm with the venue which method they accept and what format — a plain ZIP of the DCP folder is the most universally handled.

For festival submissions, many platforms (Filmfreeway, Festival Scope, and others) now have DCP ingest workflows or direct screener options. Check whether the festival wants a DCP specifically or whether a ProRes or H.264 screener is acceptable for the selection round — DCPs are typically required only for the screening itself, not for the initial assessment.

Digital delivery makes last-minute corrections far more manageable. If a DCP has an error — a wrong audio track, a missing subtitle file, a KDM for the wrong server — you can upload a corrected version without arranging a courier. Build this into how you think about delivery timelines: digital doesn’t mean you can leave it until the last minute, but it does mean that fixing a problem doesn’t take another 24 hours of shipping.

Hard drive delivery

Some venues — particularly smaller independent cinemas and regional screens — still require or prefer delivery on a physical drive. When this is the case, format the drive as exFAT, which is readable by Windows, macOS, and most Linux-based cinema servers without additional drivers. Avoid macOS HFS+ and Windows NTFS — not all servers can mount these without extra configuration. The DCP folder must sit at the root of the drive; do not nest it inside additional folders.

ParameterRequirement
Preferred methodDigital upload where the venue supports it — faster, no shipping risk, easy to correct
Hard drive formatexFAT (recommended, universal); ext2/ext3 accepted by Linux servers; confirm with venue
Folder locationDCP folder at the root of the drive or archive — not nested inside additional folders
Drive interfaceUSB 3.0 minimum; some servers accept eSATA
Delivery lead time48 hours minimum before screening; 72+ hours for theatrical runs; longer for hard drive shipping
KDM deliveryBy email to the venue technical contact — separate from the DCP, before the screening window opens
IMF & Streaming Delivery →Colour Science & Management →Aspect Ratios & Delivery →