A mezzanine file is the high-quality source version of a video advertisement, supplied not to be played but to be re-encoded. Publishers, server-side ad insertion vendors and connected television platforms ingest it, run it through their own encoding pipelines and produce the versions they actually serve. The file itself almost never reaches a screen.

The reason it exists is generation loss. A 30-second spot delivered as one compressed MP4 was adequate when digital video meant a small player embedded in a web page. It is not adequate when the same spot sits between segments of 4K drama on a 65-inch television, encoded to match a bitrate ladder built for premium content. Transcoding an already-compressed delivery file produces visible artefacts. Transcoding from a near-lossless master does not.

Where the file sits in the transaction

The Video Ad Serving Template, or VAST, is the XML specification maintained by IAB Tech Lab that tells a player or a server which files to fetch and what to report. Its fourth version documented the ad-stitching sequence in which the mezzanine operates.

A publisher sends an ad request to its stitching service. The service calls the ad server, which returns a VAST document containing both ready-to-serve media files and a mezzanine. The service reads the creative identifier, checks whether it has transcoded that creative before, and if it has not, extracts the mezzanine and begins encoding. During that window the advertisement cannot run. VAST 4.0 assigned error code 407 to this state, describing a mezzanine downloaded for the first time, noting that the download may take several hours and that no advertisement serves until the file is downloaded and transcoded.

Once encoding completes, the transcoded set is cached against the creative identifier and reused. VAST 4.0 introduced the UniversalAdId element for that purpose, and according to the specification a creative changed in any way should carry a new identifier. IAB Tech Lab's CTV Programmatic Guide adds a fallback: where no mezzanine arrives, stitching vendors download the highest bitrate media file available and work from that.

The Mezzanine element

Inside a VAST document the file is declared as a Mezzanine node under MediaFiles, alongside the MediaFile elements carrying playable renditions. Its content is a URI in a CDATA block. VAST 4.0 declared it as a bare URI with no attributes at all. Version 4.1, released in November 2018, converted it into a complex type carrying delivery, type, width and height as required attributes, with codec, id and fileSize optional, and permitted more than one Mezzanine per creative. The delivery attribute accepts progressive or streaming; width and height take native pixel dimensions, or zero for audio.

Two further error codes bracket the element. Code 406 covers a mezzanine required but not provided; code 411 covers one provided but failing the required specification. In both cases the advertisement is not served. The distinction is deliberate: a schema can confirm that a URI is present, but nothing in the XML can confirm that the file behind it is a genuine master rather than an upscaled delivery copy.

Older versions were retrofitted. The VAST CTV Addendum published in July 2024 backported the element to VAST 2.0 and 3.x through an Extension node typed as mezzanine, paired with a CreativeId element so the file matches the right creative in a multi-creative tag. PPC Land also covered the draft that preceded it. The draft VAST 4.4 schema moves the other way, making delivery, width and height optional and leaving only type required, while adding a mediaType attribute defaulting to 2D.

Origin and evolution

The word is borrowed from post-production, where a mezzanine sits between the camera master and the distribution copies. Its arrival in advertising tracks the arrival of television-grade inventory. IAB published its first digital video ad format guidelines in 2008, updated them in 2015 as high-definition screens proliferated, and rewrote them in 2022 for cross-screen buying. VAST 4.0, released on January 21, 2016, gave the file a home in the tag, listed in the executive summary alongside ready-to-serve files, the UniversalAdId and new error codes.

IAB Tech Lab opened the 2022 update for public comment covering creative file submission, the mezzanine file, ready-to-serve files, and nonlinear and companion advertisements. Standardisation then moved to formats. The Ad Format Hero programme opened for submissions in October 2024, gathering more than 100 proposals, and six connected television formats reached public comment on December 11, 2025. Every one of those six format tables refers submission requirements back to the choice between ready-to-serve standards and a mezzanine file.

What the specifications ask for

The December 2025 draft carried the 2022 numbers largely intact. It recommended 50 Mbps variable bitrate for the original source, or 15 to 30 Mbps constant, in a .mov or .mp4 container at 1920 by 1080 or 1280 by 720, with 4:2:0 or 4:2:2 chroma subsampling, native frame rate, Apple ProRes preferred, and audio at 192 kbps AAC or PCM, 48 kHz stereo. No slate, no countdown leader, no bars, no tone.

Those numbers did not survive review. The revised draft removes the fixed bitrate and resolution figures entirely, replacing them with native resolution, native aspect ratio and native frame rate. It adds DNxHD and DNxHR alongside ProRes, names H.264 High Profile as the fallback where mezzanine codecs are unavailable, specifies bit depth for the first time at 8-bit minimum and 10-bit preferred, and sets colour space at Rec.709 for standard dynamic range. According to the revised text, advertisers are generally not expected to supply adaptive streaming packages, because platforms generate those from mezzanine or high-quality source files themselves.

Why the file matters commercially

Encoding takes time. Google's Ad Manager documentation states that if ingestion and transcoding are not performed before a dynamic ad insertion campaign launches, they occur on the first monetisable impression, converting a technical delay into a lost opportunity. Display and Video 360 guidance tells buyers to supply ready-to-serve versions at high, medium and low quality alongside a mezzanine, because the mezzanine needs encoding time while the others are immediately servable.

Live inventory sharpens the point. When Disney launched its live streaming advertising certification on January 7, 2025with Google Display and Video 360, The Trade Desk, Yahoo DSP and Magnite, one of three technical requirements was pre-ingestion of pre-approved creative. In a live break the decisioning window collapses to milliseconds, a compression examined in PPC Land's account of latency in live streaming. Nothing can be transcoded on demand.

The file also determines who bears the encoding cost. Microsoft's connected television specifications describe buyers uploading a single media file that Microsoft transcodes, while noting that some publishers require every rendition in a defined set and will not serve the line if one is missing.

Limitations and disputes

The obvious criticism is weight. A 30-second spot at 50 Mbps runs to roughly 190 MB, against about 19 MB for the same spot at 5 Mbps. The December 2025 draft argued at length that bitrate optimisation reduces data transfer and the energy that goes with it, while recommending mezzanine bitrates an order of magnitude above the delivery files it wanted lightened.

Compliance is uneven. The element is optional in every VAST schema that defines it, and the specification acknowledges that publishers requiring one may ignore a response that lacks it. Agencies without a true master sometimes supply a re-encoded H.264 delivery file labelled as a mezzanine, which passes validation and defeats the purpose. Error code 411 exists because the industry expected this.

Standardisation remains incomplete where it matters most. Within IAB Tech Lab's Live Event Ad Playbook, standardised pre-fetching and creative readiness have not been delivered, leaving transcoding latency to bilateral certification programmes. Publisher-specific requirements pull the same way: France's Alliance Digitale catalogued broadcaster-by-broadcaster format support because the promise of a single portable asset has not been met.

Distinguishing the mezzanine from adjacent terms

Ready-to-serve files are the transcoded renditions a player fetches and plays immediately. The revised guidelines define five tiers, from low resolution up to Ultra HD at 3840 by 2160, with H.264 target bitrates from 1.5 Mbps at the bottom to 15 to 30 Mbps at the top. A mezzanine is never one of these.

Adaptive bitrate renditions are segmented HLS or MPEG-DASH variants generated by the platform from a mezzanine or another high-quality source, indexed in a manifest and switched between mid-playback.

Camera masters sit upstream in post-production. A mezzanine is already delivery-oriented, trimmed to the exact advertisement duration with slate and bars removed.

Mezzanine capital, in corporate finance, describes debt subordinated to senior lending. The two usages share only the architectural metaphor.

Recent developments

The Ad Format Guidelines for Digital Video and CTV entered a second public comment round after the first closed on January 31, 2026, with feedback accepted until July 16, 2026 and the document moved onto IAB Tech Lab's GitHub. The revisions rewrote the mezzanine section and expanded ready-to-serve guidance from four tiers to five, adding 4K. The guidelines remain unfinalised as of September 2026.

Codec recommendations continue to move. The December 2025 draft named H.265, VP9 and AV1 as preferred over H.264 for delivery, and Meta's June 2026 disclosure that AV1 now runs on most mobile devices for real-time video added evidence from outside premium television. Identifier work advanced alongside, with UniversalAdId support added to the Open Measurement SDK in June 2025 and registry integrations under the Ad Creative ID Framework covering AD-ID, Clearcast, ARPP and Auditel. Format signalling reached the buy side when The Trade Desk gained direct pause advertisement supply as six format signals were finalised in July 2026.

The direction of travel is towards platforms doing more encoding and advertisers supplying less finished material.

Timeline

  • 2008: IAB publishes the first digital video ad format guidelines and VAST 1.0
  • 2015: The ad format guidelines are updated for high-definition screens
  • January 21, 2016: VAST 4.0 introduces the Mezzanine element, ready-to-serve file guidance, UniversalAdId and error codes 406, 407 and 411
  • April 2016: Corrections and clarifications are appended to VAST 4.0
  • November 2018: VAST 4.1 makes Mezzanine a complex type with delivery, type, width and height required, and allows multiple instances
  • June 2019: VAST 4.2 is released with SIMID support
  • March 31, 2022: IAB Tech Lab opens the digital video and connected television ad format guidelines for public comment
  • August 2022: The updated guidelines are released, setting mezzanine bitrate at 50 Mbps variable or 15 to 30 Mbps constant with Apple ProRes preferred
  • December 2022: VAST 4.3 is released
  • January 7, 2025: Disney's live streaming certification requires pre-ingestion of pre-approved creative
  • July 2024: The VAST CTV Addendum backports the mezzanine to VAST 2.0 and 3.x through an Extension node
  • December 11, 2025: The Ad Format Guidelines for Digital Video and CTV reach public comment with six connected television formats
  • January 31, 2026: The first public comment period closes
  • June 17, 2026: A revised draft replaces fixed mezzanine bitrate and resolution figures with native-source guidance and adds DNxHD and DNxHR
  • July 16, 2026: The second public comment period closes, with finalisation pending

Summary

Who. Advertisers and their agencies produce mezzanine files; ad servers reference them in VAST responses; publishers, server-side ad insertion vendors and connected television platforms consume and transcode them. IAB Tech Lab defines the element and the file specifications through VAST and the Ad Format Guidelines for Digital Video and CTV.

What. A raw, high-quality source video supplied alongside playable renditions, intended as the input to a platform's own encoding pipeline rather than for direct playback. It is declared in VAST as a Mezzanine node under MediaFiles, carrying a URI and attributes describing delivery method, MIME type and native dimensions.

When. The concept entered advertising with VAST 4.0 on January 21, 2016, gained mandatory attributes in VAST 4.1 in November 2018, reached older VAST versions through the July 2024 CTV Addendum, and had its file specifications rewritten in a revised draft that closed public comment on July 16, 2026.

Where. In connected television and premium streaming, where advertisements are transcoded into adaptive bitrate ladders matched to surrounding content, and in any workflow where a publisher rather than a buyer controls encoding.

Why. Encoding a delivery file a second time degrades it visibly against 4K content, and no single rendition suits every device. Supplying a master lets each platform generate what it needs, at the cost of file size, ingestion latency measured in hours, and a requirement the specifications can describe but cannot enforce.