Dolby Vision & Dolby Atmos Delivery Requirements - Prime Video Tech Docs

Dolby Vision & Dolby Atmos Delivery Requirements

Last updated 2026-07-24

Important: This page covers requirements specific to Dolby Vision and Dolby Atmos deliveries. All other delivery requirements — including general video specifications, general audio specifications, timed text, and MMC field details — follow the standard Prime Video specifications outlined in Video Central. Please refer to the Video requirements, Audio specifications, and MMC asset manifest pages for complete technical requirements.

Before delivering Dolby content: Partners must contact their Prime Video Partner Operations Manager before initiating any Dolby Vision or Dolby Atmos deliveries. Prime Video requires a test delivery phase to validate content and delivery workflow before accepting production deliveries. This advance coordination ensures:

  • Content meets all Dolby Vision and Dolby Atmos specifications
  • Delivery workflows are properly configured and tested
  • Any technical questions or concerns are addressed upfront
  • Production deliveries proceed smoothly without delays

Overview

Prime Video supports delivery of HDR mezzanine video files with Dolby Vision and Dolby Atmos audio to provide customers with enhanced viewing experiences. This page outlines the technical requirements and delivery specifications for content mastered in Dolby Vision and Dolby Atmos formats.

Dolby Vision provides dynamic shot-by-shot optimization to enhance brightness, contrast, and color, while Dolby Atmos delivers immersive audio with object-based sound positioning. Together, these technologies create a premium viewing experience for Prime Video customers on compatible devices.

Dolby Vision Delivery Formats

Supported delivery format: Two-mezzanine delivery

Partners must deliver two distinct video masters:

  • One UHD SDR mezzanine file (standard dynamic range)
  • One Apple ProRes 4444 XQ or ProRes 4444 UHD HDR mezzanine with Dolby Vision sidecar XML metadata

How Prime Video Uses Your Delivery

Delivered Videos: ProRes 4444 XQ/4444 with sidecar Dolby Vision XML + SDR

  • SDR Source: Original SDR file
  • HDR10 Source: HDR base layer (PQ)
  • Dolby Vision Source: HDR base layer (PQ) + Dolby Vision XML

By delivering both SDR and Dolby Vision HDR sources, you maintain creative control over how your content appears across different display capabilities while Prime Video derives the HDR10 variant from your Dolby Vision master.


Dolby Vision Technical Specifications

Video File Specifications (ProRes 4444 XQ / Prores 4444)

Resolution and aspect ratio:

  • Canvas aspect ratio must be 1.77 (3840x2160 - UHD)
  • Image aspect ratio must be one of: 4:3, 1.66:1, 16:9, 1.85:1, 2:1, 2.20:1, 2.35:1, 2.39:1, 2.40:1
  • Video deliverables must not be anamorphic

Frame rate and scan type:

  • Frame rate must be constant and one of: 23.976, 24, 25, 29.97, 30
  • Variable frame rate sources will be rejected
  • Scan type must be Progressive

Color Encoding Primaries:

  • Video codec: ProRes 4444 XQ or ProRes 4444
  • Container: MOV
  • Color Encoding Primaries: Rec. 2020 or DCI-P3
  • White point and color primaries: ITU-R BT.2020 or D65 P3
  • Color range and chroma: Full range 12-bit RGB/YUV color @ 4:4:4 with no chroma subsampling
  • Average bit rate: At least 250 Mbps

Audio requirements:

  • Video source must contain embedded audio tracks
  • All audio tracks must be in the same language
  • Audio duration and video duration must match exactly

Dolby Vision Sidecar XML Specifications

A separate Dolby Vision sidecar XML file must be delivered alongside the ProRes video source.

Metadata requirements:

  • CM version must be either 2.9 or 4.0
  • Dolby Vision XML version: 2.0.5 for CM 2.9, or 4.0.2 or 5.1.0 for CM 4.0
  • Master Monitor: 1000 nit, 2000 nit, or 4000 nit - P3 D65
  • Color Encoding Primaries: Rec. 2020
  • Target trim metadata must be present: Level 2 metadata for CM 2.9, or Level 2 or Level 8 metadata for CM 4.0. Target Trim ID1 - SDR 100 Nit Rec 709 is required (Level 8 metadata)
  • Electro Optical Transfer Function (EOTF) must be ST.2084 (PQ)
  • Mastering volume metadata must contain ST.2086 – non-zero MaxFALL and MaxCLL values must be present as L6 Dolby Vision Metadata
  • Aspect ratio/Output Blanking (L5) is required and must match image for entire show if static, or per shot/scene if dynamic

Required metadata elements:

  • HDR static metadata including mastering display details: RGB primaries, white point, peak brightness, and minimum brightness
  • Non-zero Level 6 metadata, including MaxCLL and MaxFALL values
  • Global or Level 5 metadata (if aspect ratio changes across duration)
  • Canvas, image aspect ratio, and frame rate must be consistent with the video source

SDR Mezzanine Specifications

The SDR mezzanine must conform to standard Prime Video UHD specifications:

  • Resolution: 3840x2160 (UHD)
  • Format: ProRes 422 HQ, MOV
  • Minimum bit rate: 250 Mbps
  • Color space: Rec. 709
  • Chroma subsampling: 4:2:2
  • Chroma bit depth: 10-bit
  • Frame rate (constant): Must match Dolby Vision source
  • Scan type: Progressive only

Critical requirement: Conformance and runtime of SDR and HDR sources must be identical. The only acceptable difference between the SDR and Dolby Vision mezzanine file is the colorspace. The following must match exactly:

  • Frame rate
  • Runtime duration
  • Scene/shot boundaries

Not Supported in Dolby Vision

  • Trailers
  • Dubcard asset presentations


Dolby Atmos Technical Specifications

Audio Format Requirements

Dolby Atmos must be delivered in Broadcast Wave Format Audio Definition Model (BWF ADM) format:

  • Container: BWF-RF64 (.wav)
  • Codec: DOLBY-ATMOS-ADMBWF
  • Format: ADM BWF (BWAV) - a broadcast WAV file containing Atmos metadata
  • All audio tracks: 24-bit LPCM audio at 48kHz
  • Maximum individual audio tracks: 128
  • Object count cannot exceed 118
  • Beds count cannot exceed 10

Matching non-Atmos Audio Requirement

For any Dolby Atmos audio source delivered, there must be a non-Atmos audio source with matching locale and subtype that includes a 5.1 surround mix. This baseline audio ensures compatibility across all playback devices.

Multiple Audio Asset Requirement

A title must include additional audio assets beyond a single Atmos track. It must have at least one other separate audio asset delivered different than the OV language.
Single language titles must be delivered with one of the following configurations:

  • Option 1: One Atmos audio source with matching 5.1 audio source per spec, and one 5.1 audio source of a different type (e.g. Audio Description or a different language).
  • Option 2: Two (or more) Atmos audio sources of different types, both with a matching 5.1 audio source per spec.

Audio Consistency Requirement

  • Audio duration must be within [-2, +2] second duration difference compared to main content video duration
  • All Dolby Atmos audio sources for a program must have the same bed channel configuration and mastering frame rate
  • Music and Effects (M&E), MOS, silent tracks, and commentary tracks must be removed from Dolby Atmos audio sources
  • Main content video source must not contain Dolby Atmos audio as embedded audio
  • Dolby Atmos descriptive audio requires a corresponding non-Atmos descriptive audio baseline for successful encoding

MMC specification requirements

Dolby Vision Source Specification

For ProRes 4444 XQ/4444 delivery with sidecar XML, partners must include two separate inventory track files:

  • Video track - References the ProRes HDR video file
  • Ancillary track - References the Dolby Vision sidecar XML

Ancillary track requirements:

  • Type must be enhancement
  • SubType must be DolbyVision
  • BaseTrackReference must point to the ProRes video track ID
  • ColorTransformMetadata/ColorVolumeTransform must be DolbyVision
  • ColorTransformMetadata/ApplicationIdentifier must be 1 with ApplicationVersion="0" attribute

Dolby Atmos MMC Specification

Codec specification:

  • Codec must specify DOLBY-ATMOS-ADMBWF under AudioTrackID
  • Type must specify BWF-RF64 under ContainerReference
  • Atmos filename referenced in ContainerLocation

Can’t find what you’re looking for?

Contact us


Internal Server error! Please try again
Your session has expired

Please sign in to continue

Sign In
edit