# TABLE OF CONTENTS - [Executive Summary](#execsummary) - [Audience](#audience) - [Linear, Nonlinear & Companion Ads](#linearnonlinearcompanion) - [Digital Video Placement Types](#digitalvideo) - [CTV Ad Porfolio](#ctvportfolio) - [Linear Ad Format Guidelines](#linear) - [Pause Ad](#pause) - [Menu Ad](#menu) - [Squeezeback](#squeezeback) - [Overlay](#overlay) - [In Scene Ad](#inscene) - [Screen Saver Ad](#screensaver) - [Interactivity](#interactivity) - [QR Codes](#qrcodes) - [Video Ad Submission Guidelines](#submissionguidelines) - [Encoding Ready-to-Serve Files](#encoding) - [General Video Settings](#generalvideo) - [Ready-To-Serve Video Ads](#readytoserve) - [The Mezzanine File](#mezzanine) - [Linear Ad File Format Recommendations](#linearrecommendations) - [Video Companion Ad Guidelines](#videocompanion) - [Audio Guidelines](#audio) - [Ad Delivery Notes](#addelivery) # Executive Summary Originally intended to establish a baseline for in-stream video ad formats and creative submission requirements, the 2008 Guidelines helped digital video establish a foothold in the marketplace. In an update in 2015, consideration was given to the increasing need for high-quality video, especially as high definition screens of all sizes and capabilities enter the marketplace. The 2022 update accommodated high-quality video needs for cross-screen video advertising in mobile, desktop, and connected TV (CTV). File submission recommendations detail “ready-to-serve” files for streaming, progressive download, and adaptive bitrate streaming formats. Providing the high quality source, or mezzanine file is also vital in CTV so that the publisher may transcode the file best suited to the environment into which it will serve. This 2025 update establishes six new CTV creative formats. It describes the consumer experience, file types, sizes, and interactivity best practices. These guidelines are intended to help the market scale these new ad formats through standardization. ## Audience Publishers should use these guidelines as a resource for providing creative submission requirements for video ads. Video Ad developers should use this document as a reference for baseline ad development specifications. Creative agencies, studios and video ad technologists, as well as video ad-serving partners should use this document as a reference for digital video ad specifications. # Linear, Nonlinear & Companion Ads We break digital video ads down into two different formats: linear and nonlinear. Either format may include a “companion” ad that displays outside the player, less common in mobile and CTV while fairly typical in web. Linear video ads are video formatted ads that interrupt streaming video content much like a TV commercial. They can play before (pre-roll), during (mid-roll), or after (post-roll) the streaming content. Linear ad formats can be accompanied by a companion ad, or they can include an interactive component. Nonlinear video ads are typically served on top of (overlay) the video content. Traditionally, these ads are simple images but increasingly, especially in CTV, they can be a video or animated media. The ad runs concurrently with the streaming content so the user sees the ad while also viewing the content without interruption. Ideally, the nonlinear video ad is small enough to allow a relatively unobstructed view of the content. Nonlinear video ads can be delivered as text, static images, interactive rich media, or as video overlays. Typically, a nonlinear video ad developer can take advantage of the medium and use the small overlay as an invitation for consumers to further engage with a more robust set of interactions. As with Linear ads, nonlinear ads can be served with companion ads where applicable. Companion ads are ads that are served along with linear or nonlinear ads in the form of text, static image display ads, rich media, or skins that wrap around the video experience. These ads come in a number of sizes and shapes and typically run alongside, or surrounding, the video player. The primary purpose of the companion ad is to offer sustained visibility of the sponsor throughout the streaming video experience. Digital video companion ads are always served with a master ad, which is either the linear or nonlinear ad. Companion ads, that are not served as end cards, are not available on CTV. Recently, there has been an increase in newer formats that allow minimal disruption to content. Unlike linear ads, these formats do not interrupt content, allowing for a more seamless user experience. The following image illustrates where these ads might fit along the timeline of the streaming video content. ![Image with sample ads across streaming timeline](/assets/timeline.png) ## Digital Video Placement Types When considering the consumer experiences for digital video, the inventory is categorized into placement types that are enumerated in the OpenRTB specification. The ‘plcmt’ attribute is sent as a part of the video object in OpenRTB. The details of the ‘plcmt’ types are enumerated in AdCOM . Detailed examples of the implementations can be found in the Implementation Guide. ## CTV Ad Portfolio The ad formats that follow are part of the CTV Ad Portfolio. While these ads can be served to web video and mobile, the descriptions focus on ad service to a connected TV. - Linear Ad - Pause Ad - Menu Ad - Squeezeback - Overlay - In Scene Ads - Screensaver Ad It is understood that this list is not comprehensive of all CTV experiences. Specifically, it does not further define the linear ad format guidelines, meaning, executions that involve a slot in a pod in-stream. Many unique experiences can be done within a slot in an adbreak, and the details of submission guidelines are well-known for these video assets. The new additions, Pause, Menu, Squeezeback, Overlay, In Scene, and Screensaver are those which happen outside of the traditional commercial break, where more detailed standardization is needed for growth. ## Linear Ad Format Guidelines The following linear ad format guidelines outline the minimum considerations for linear ad development. Publishers may offer other ad formats and specifications that extend these recommendations. Please check with the publisher for specific requirements. | Linear Ad Property | Guidelines | |---|---| |Insertion Point | Pre-roll, mid-roll, post-roll. | |Maximum ad display duration Duration should be exact, but the transcoding process may produce slight variations within no more than 1 second. | Ad duration should be one of the following: 6 seconds, 15 seconds, 20 seconds, 30 seconds. Interactive ads should be 15-30 seconds for the compulsory portion of the ad, but may continue indefinitely upon viewer interaction. Other durations commonly accepted: Short-form creative (aka “bumper”, 3-10 seconds in length) 60 second spots (ran sparingly and usually as post-roll or during extended mid-roll ad slots). | |Long “info-mercial” ad | Duration can range from 1-5 minutes, or longer depending on placement, skip options, and objective. Considerations for info-mercial ads: Skip option recommended (check with publisher) Controls for ffw, rw, pause, etc. recommended, especially if skip option omitted (check with publisher on technical feasibility) | |Engagement Event| Both the video window and companion ad may offer interaction controls with links to the advertiser site. For interactive ads, engagement controls may extend ad duration, initiate interactive ad, or take the user to the advertiser’s site. Technology: check with publisher, ad serving platform on tech used to manage interactions. Mobile: click might be a gesture such as a swipe CTV: click happens with remote or game system controller. Check with the publisher on limited “clickability.” | |Controls | Options for player controls to be available during ad play should be negotiated prior to campaign start (for example: no fast forward during ad play). If the ad is skippable, skip controls and time delay should be negotiated prior to campaign start. For interactive ads, call to action should be clearly labeled. Viewer-initiated portion must provide a close control to allow the viewer to exit at any time. If the extended portion of the ad includes any expandable media, a collapse button must also be provided. Check with the publisher on the technological handling of these controls.| |Dimensions | Preferred aspect ratio is 16:9 (formatted for HD screens) Ultra-wide aspect ratio 21:9 is less common but may increase as more TVs and monitors of this size enter the market. Viewer-initiated portion may fill the video viewing pane or may extend beyond viewing pane if publisher allows.| ## Pause Ad Format Guidelines A pause ad is an ad present in streaming video content that the consumer has requested. While there may be other content surrounding the player, the video content must be the focus of the user’s visit. It should remain the primary content on the page and the only video player in-view. | Pause Ad Property | Guidelines | |---|---| |Initiation | Viewer Initiated: program is paused by viewer. | |Creative Type | Display / Static, Video / Animated | |Creative Size | Fullscreen: 1920 x 1080, Partial Screen: 600 x 600 | |Aspect Ratio | Fullscreen: 16:9, Partial Screen: 1:1 | |Ad Submission Requirements | See Video Format Submission Guidelines for options based on ready-to-serve standards vs mezzanine file. If Display/Static, the file size should be under 350kB.| |Sound | The default execution does not require audio. | |Placement | This execution could be full Screen or partial screen in the pause experience. | |Interactive Components | Optional interactive support may include QR codes and or interactivity via the controls on the tv remote. See more details on standards for interactivity in the Interactivity section below. | |Duration & Exit | The ad experience may end under any of the following: Viewer Initiated: Dismiss message, Resume content, Power off TV, App exited, Device Initiated:, Screen Saver kicks in, Device timing out/shutting off. Some pause ads may refresh, or the same ad may remain on screen for the duration of the experience. Videos may autoplay. The seller would signal any refresh rates or autoplay behavior in the bid request.| ## Menu Ad Format Guidelines A menu ad is an ad unit that appears within the user interface (UI) of the TV or streaming platform. These are typically ads integrated into the home screen or in the content navigation menu, rather than during video playback. | Menu Ad Property | Guidelines | |---|---| |Initiation | The ad may load when the smart TV is turned on, or when the user navigates to the specific menu where the ad is hosted. | |Creative Type | Display / Static, Video / Animated | |Creative Size | The size is variable, we have provided aspect ratios for scalability.| |Aspect Ratio | Headline Banner 2:3, 3.88:1, 4:1, 6:5, 16:9 , In Menu Tile 16:9 or 3:9 | |Ad Submission Requirements | See Video Format Submission Guidelines for options based on ready-to-serve standards vs mezzanine file. If Display/Static, the file size should be under 350kB.| |Sound | The default execution does not require audio. | |Placement | Headline Banner - These are featured across an entire horizontal row, often the top of the navigation, but in some cases in between rows of tiles. In Menu Tiles - These can appear anywhere within the navigational UI. | |Interactive Components | Optional interactive support may include QR codes and or interactivity via the controls on the tv remote. See more details on standards for interactivity in the Interactivity section below. | |Duration & Exit |The duration of time the creative is on screen can depend on viewer or device behaviors. The ad experience may end under any of the following: Viewer Initiated: Navigate away from menu, Power off TV, App exited, Device Initiated: Screen Saver kicks in, Device timing out/shutting off. Some menu ads are part of navigable slides that a user scrolls through. Some may have fixed duration and/or refresh rates. Additionally, videos may autoplay, or may require additional engagement. These features would be described by the seller in the bid request. | ## Squeezeback Ad Format Guidelines Ads Alongside or Adjacent to Content, also known as L-Shape Ads & Double Box, are ads that occur during program content and outside of the traditional ad break. The program content is resized to allow for placement of an ad on the screen. In a squeezeback, none of the content is covered by the ad, instead it shares screen space with the ad. This is the major distinction between squeezeback and overlay. | Squeezeback Ad Property | Guidelines | |---|---| |Initiation | These ads are not user initiated, they appear around the content while it continues to play. The size of the content is reduced from full screen to accommodate space for the ad. The content reduction should take between 1 and 2 seconds. | |Creative Type | Display / Static, Video / Animated, For scaling purposes, it is assumed that the squeezeback assets are provided in an underlay format. This means that the full screen 1920 x 1080 branded advertisement is provided with a cutout for the content placement.| |Creative Size | L-Shape - The content will take up 60% of the 1920 x 1080 screen. The content squeezes to the upper left or upper right, and the ad experience is across the bottom of the screen and vertical right bar. Frame - The content will take up 60% of the 1920 x 1080 screen. The content squeezes into the center the ad experience surrounds the content. Double Box Video - Each box (the content and the ad) will take up 25% of the 1920 x 1080 screen. The content squeezes back to the center left, and the ad squeezes to the center right. Double Box Video + Background : Each box (content and the ad) will take up 25% of the 1920 x 1080 screen. The content squeezes back to the center left, and the ad squeezes to the center right. The advertiser also brands/takes over the background between the double boxes of video. | |Aspect Ratio | 16:9 | |Ad Submission Requirements | See Video Format Submission Guidelines for options based on ready-to-serve standards vs mezzanine file. If Display/Static, the file size should be under 350kB.| |Sound | The default execution does not require audio. The publisher will signal in the bid request if audio is required. For example audio is usually requested when there is a lull in sports content and the squeeze back becomes the user’s focus. | |Placement | L Shape - This format generally takes an “L” shape around the outside of the content. The content squeezes to the upper left or upper right and the ad experience is across the bottom of the screen and the vertical right bar. Frame - This format squeezes the content to the center of the frame and the ad experience surrounds it. Double Box Video - The content squeezes back to the left, a second matching size box is presented on the right. Double Box Video + Background - The content squeezes back to the left, a second matching size box is presented on the right. The advertiser also brands/takes over the background between the double boxes of video. | |Interactive Components | Optional interactive support may include QR codes and or interactivity via the controls on the tv remote. See more details on standards for interactivity in the Interactivity section below. | |Duration & Exit | When the ad ends, the content returns to full screen. These ads can be variable in length. The minimum duration is 10 seconds. Duration will be signaled in the bid request. | ## Overlay Ad Format Guidelines Overlay Ads over content are non-linear ads occurring during program content and outside of the traditional ad break. The ad format places ad creatives over top of the program content, often as a banner or picture in picture execution. Overlay Ads may have user interaction with the remote control or scanning a QR code that is part of the ad creative. | Overlay Ad Property | Guidelines | |---|---| |Initiation | These ads are not user initiated and they appear over the content while it continues to play. The size of the content is not reduced, the ad covers some portion of the programming. | |Creative Type | Display / Static, Video / Animated | |Creative Size | Corner Overlay - The creative takes up 25% of a 1920 x 1080 screen. It is generally presented in one of the four corners of the screen, over content as it continues to play. It is possible for the creative to appear to cover less than 25% of the screen, and not adhere to a square shape if formatted for transparency. Lower Third Overlay - The creative takes up 30% of the bottom of a 1920 x 1080 screen. It appears over content as it continues to play. It is possible for the creative to appear to cover less than 30% of the screen, and not adhere to a square shape if formatted for transparency. | |Aspect Ratio | 16:9 | |Ad Submission Requirements | See Video Format Submission Guidelines for options based on ready-to-serve standards vs mezzanine file. If Display/Static, the file size should be under 350kB.| |Sound | The default execution does not require audio. | |Placement | Over content while the content continues to play on the majority of the screen. | |Interactive Components | Optional interactive support may include QR codes and or interactivity via the controls on the tv remote. See more details on standards for interactivity in the Interactivity section below. | |Duration & Exit | When the ad ends, the ad creative is no longer visible over the content. These ads can be variable in length, minimum duration is 10 seconds. Duration will be signaled in the bid request. | ## In Scene Ad Format Guidelines In Scene Ads are a form of advertising that integrates branded elements directly within the content itself, rather than appearing as separate pre-roll, mid-roll, overlay, or display formats. In Scene Advertising is composited into the video content and blends the brand naturally into the scene, environment, or storyline, ensuring contextual relevance and viewer immersion without interrupting the user experience. In-scene ads typically consist of product placements or virtual out of home insertions. At this time, the standardization focuses on the out of home insertions. | In Scene Ad Property | Guidelines | |---|---| |Initiation | These ads are not user initiated and they appear within the content while it continues to play. The size of the content is not reduced, the ad is composited within the programming, but it appears to the user as if it were naturally within the scene. The brand asset is composited into the environment so that the viewing experience remains uninterrupted. | |Creative Type | Static Image (jpg, png, gif), Video/Animated, 3D / CGI Asset is supported by some partners, but requires direct communication for assets. | |Creative Size | 9:16 – 1080w x 1920h, 4:3 – 1280w x 960h, 16:9 – 1920w x 1080h, Poster – 840w x 400h, Bulletin – 1400w x 400h | |Aspect Ratio | 9:16 – 1080w x 1920h, 4:3 – 1280w x 960h, 16:9 – 1920w x 1080h, Poster – 840w x 400h, Bulletin – 1400w x 400h | |Ad Submission Requirements | See Video Format Submission Guidelines for options based on ready-to-serve standards vs mezzanine file. If Display/Static, the file size should be under 350kB.| |Sound | None. | |Placement | These ads are usually billboards in the scene content (e.g. a car is driving down the road and sees a billboard in the city). The billboard is filled with the branded content. | |Interactive Components | No interactivity, as this type of ad is closer to a brand placement. It’s meant to not appear to the viewer as an ad. | |Duration & Exit | When the ad ends, the ad creative is no longer visible within the content. These ads can be variable in length, minimum duration is 3 seconds for Brand Exposure Duration. | ## Screensaver Ad Format Guidelines Screen Saver Ads are similar to Pause Ads but where Pause Ads are viewer-initiated ad experiences, Screen Saver Ads are OS/App initiated ad experiences. | Screensaver Ad Property | Guidelines | |---|---| |Initiation | This ad format begins after a defined period of inactivity on the device. | |Creative Type | Display / Static, Video / Animated | |Creative Size | 1920 x 1080 | |Aspect Ratio | 16:9 | |Ad Submission Requirements | See Video Format Submission Guidelines for options based on ready-to-serve standards vs mezzanine file. If Display/Static, the file size should be under 350kB.| |Sound | The default execution does not require audio. | |Placement | Full screen ad. | |Interactive Components | Optional interactive support may include QR codes and or interactivity via the controls on the tv remote. See more details on standards for interactivity in the Interactivity section below. | |Duration & Exit | The ad experience may end under any of the following: Viewer Initiated: Dismiss message, Resume content, Power off TV, App exited, Device Initiated: Device timing out/shutting off, Some screen saver ads may refresh. Videos may autoplay. The seller would signal any refresh rates or autoplay behavior in the bid request. | ## Secure Interactivity Most CTV formats above have optional capabilities for interactivity. Some examples of interactivity include: shoppable ads, “choose your advertisement” experiences, interactive polling within the ad, full screen expansions, autoplay videos/gifs, and more. VMAP standard enables video content owners to overlay advertising onto content when they don’t control the video player or the content distribution outlet. This can include secure interactive ads if the inserted ad is SIMID-based (VAST 4.2 or above). To take advantage of robust secure interactivity features without the need for installing and supporting proprietary software from each individual ad vendor, we recommend the use of SIMID. In July 2024, the IAB Tech Lab published its VAST Addendum which makes it easy for publishers to upgrade their VAST 2.x or VAST 3.x environments to support the current version of VAST, including SIMID for interactivity, ACIF for ad IDs, and other benefits. ## QR Codes QR codes are a common form of interactivity in CTV ads. QR code behavior is part of the interactive experience and does not impact the underlying video file format or encoding specifications. There are generally two ways that the QR code ends up on the screen: The advertiser burns the QR code into their existing creative. This means that the QR code is pre-embedded within the full video creative prior to being trafficked. The sellers receiving said file would play the .mp4 as received. The sell-side manages the QR code generation dynamically. In this case, the advertiser has already selected where the QR code will go on their creative, but they haven’t done the generation and inserted it into the creative. When this is handled by the sell-side, it allows for sell-side application of tracking parameters over various dimensions. When assembly is done this way, the advertiser must send a scan url with the video file. QR codes can also be made dynamic in a SIMID-based interactive environment. For example a different QR code can appear in the ad depending on the location of the consumer (e.g. to direct them specifically to a local car dealer website). In addition, the URL embedded in the QR code can be changed dynamically in real time, for example to append info to the URL identifying where the scan came from (e.g. the device ID, session ID, geolocation, etc.) - and therefore enable the advertiser to associate the scan with the specific ad. # Video Ad Submission Guidelines The following guidelines facilitate ad portability and development for ad creative files. Beginning with VAST 4.0, support was added for multiple "ready-to-serve" files along with a "mezzanine" source file. Ready-to-serve files can be, for example, four independent files with separate quality specifications for progressive download, or as a single adaptive streaming file using four specified quality levels. Details on the file submission guidelines in the following sections are designed as a starting point to improve cross-industry workflows. However, quality specifications may differ from publisher to publisher. Be sure to check with publishers on specific submission requirements for ad creative. These guidelines are organized to distinguish between media asset requirements (e.g., encoding and file formats), delivery mechanisms (e.g., VAST), and runtime behaviors (e.g., playback, secure interactivity, and measurement). Understanding these layers helps ensure consistent implementation across platforms and environments. ## Encoding Ready-to-Serve Files This section focuses on media asset preparation for playback. Ready-to-serve video files are pre-encoded assets designed for immediate playback across digital video environments, including Connected TV (CTV) and Online Video (OLV). These files enable platforms and players to select the most appropriate version of an ad based on device capabilities, screen resolution, and network conditions. To support consistent playback, Advertisers are encouraged to provide multiple ready-to-serve renditions at different resolutions and bitrates. These renditions allow for flexible delivery across a range of environments, from bandwidth-constrained mobile devices to high-quality CTV experiences. ### Rendition Strategy Advertisers are encouraged to provide a set of video renditions that: - Cover targeted resolution tiers (e.g., SD, HD, Full HD, and where applicable, Ultra HD) - Align with standard streaming bitrate profiles - Maintain consistent visual quality across renditions In most cases: - Three to four renditions are sufficient for broad compatibility - Additional renditions or special encoding procedures may be required by specific platforms Players or platforms are responsible for selecting the appropriate rendition during playback. ### Bitrate and Encoding Guidance Bitrate selection should be based on: - Resolution and frame rate - Content complexity (e.g., motion, animation, scene changes) - Encoding quality and configuration - Target playback environment Bitrate requirements are not linear and may vary significantly across content types and delivery platforms. Formula-based approaches (e.g., bits-per-pixel calculations) are not recommended. Advertisers are encouraged to follow commonly accepted bitrate ranges (see table below) and confirm platform-specific requirements where applicable. ### Environment Considerations #### CTV Environments - Typically use adaptive bitrate (ABR) streaming and server-side ad insertion (SSAI) - May re-encode ads to align with platform-specific encoding ladders - Benefit from higher bitrate renditions to maintain visual consistency with content #### OLV / Web Environments - Often rely on progressive MP4 playback or platform transcoding - May favor lower bitrates for efficient delivery - Typically use a smaller set of renditions #### Units and Terminology - Bitrate is measured in bits per second (kbps, Mbps) - File size is measured in bytes (kB, MB), where 1 byte = 8 bits ## General Video Settings | Video Setting | Specification | | --- | --- | |Progressive Download Format | MPEG-4 (MP4) for progressive download. Produce high, medium and low versions of each asset, allowing the publisher or player to select the appropriate version for the environment. When encoding an MP4 for progressive streaming, use the “web-optimized” setting. This improves streaming performance by placing the MOOV atom at the start of the file. | |Adaptive Streaming Format | Adaptive streaming protocols such as HTTP Live Streaming (HLS) and MPEG-DASH are commonly used in CTV and premium video environments. These protocols deliver video as segmented media at multiple bitrates, allowing the player to dynamically adjust quality based on network and device conditions. In most cases, advertisers are not expected to provide adaptive streaming packages (e.g., HLS or DASH manifests). Instead, platforms (e.g., publisher or SSAI systems) generate these formats from mezzanine or high-quality source files as part of their encoding workflows. When required, advertisers are encouraged to confirm adaptive streaming specifications directly with the publisher or platform. Adaptive streaming workflows typically rely on encoding ladders derived from mezzanine or high-quality source assets, reinforcing the importance of providing high-quality input files. | |Video Codec | Required: H.264 (AVC), High Profile Optional: H.265 (HEVC). VP9, or AV1 when supported (primarily CTV environments) HEVC and AV1 are more commonly associated with CTV environments, while VP9 is frequently used in browser-based and online video environments. |Aspect Ratio | Use the native aspect ratio of the source content or creative. Aspect ratio considerations affect playback and rendering behavior and are independent of encoding format or delivery signaling. Common formats include: 16:9 (primary format for CTV and OLV video), 1:1 and 9:16 (used in certain digital and mobile placements), Cinematic formats (e.g., 2.39:1) for film-based content, 4:3 for legacy or archival content. Guidance: Provide creatives in aspect ratios that match the intended placement or platform requirements. Maintain original aspect ratios and avoid stretching or distortion. When necessary, platforms may apply letterboxing or pillarboxing to preserve presentation. | Note: MP4 files with H.264 video and AAC-LC audio represent the only format that can be assumed to be universally supported across all video advertising environments. Players and platforms supporting other formats should share those specifics directly. ## Ready-To-Serve Video Ads While the mezzanine file is used for encoding video to fit programming needs, the encoding process takes time. Providing multiple ready-to-serve renditions aligned to common streaming bitrate profiles enables players and platforms to select the most appropriate asset for the viewer's device and network conditions. The following specifications define encoding and format characteristics for video assets. Playback behavior and delivery logic may vary by platform.
Attribute Low Resolution (≤480p) Standard Definition (480p-576p) High Definition (720p) Full HD (1080P) Ultra HD (4K) (2160p)
16:9 - Horizontal, 9:16 - Vertical (Primary) 640x360 854x480, 960x540 1280x720 1920x1080 3840x2160
1:1 Square 360x360 480x480 720x720 1080x1080 2160x2160
2.39:1 (Cinematic/Wide) 640x268 854x360 1280x536 1920x804 3840x1608
Video Target Bitrate (H.264) 1.5– 3 Mbps 2– 4 Mbps 2– 5 Mbps 4– 10 Mbps 15– 30 Mbps
Lower end of ranges typically applies to OLV/web/mobile environments. Upper end of ranges typically applies to CTV environments. Actual bitrates vary based on motion, frame rate, and encoder quality. SSAI/CTV environments typically align to ABR ladders. Publishers may require specific bitrate caps or ranges. Required Codec: MP4 container with H.264 (AVC), High Profile Optional Codec: H.265 (HEVC), VP9 or AV1 where supported (more common in CTV environments)
H.264 Profile Level High 3.0 High 3.1 High 3.1-4.0 High 4.0 (≤ 30fps), 4.2 (≤ 60fps) High 5.0-5.1
Video Frame Rate 23.976, 24, 25, 29.97, 30, 50, 59.94, 60 fps Guidance: Maintain the native frame rate of the source content. Both fractional (e.g., 29.97, 59.94) and integer (e.g., 30, 60) frame rates are supported. Integer frame rates may simplify certain digital workflows, but conversion from fractional rates should be avoided unless required by the target platform.
Video Color Space SDR (Default): Rec.709, 4:2:0 HDR (Optional): HDR10 (PQ / Rec.2020), HLG (primarily CTV environments)
Video Interlacing Progressive only (no interlacing)
Leaders (Slate) No slate, countdown, or black frames before/after ad content
Audio Codec Required: AAC-LC Optional: Dolby Digital / Dolby Digital+( 5.1, primarily CTV environments)
Audio Bitrate Stereo: 128 - 192 kbps Surround (optional): 256 - 384 kbps (Dolby Digital+)
Audio Channel Default: Stereo (2.0) Optional: 5.1 surround (primarily CTV environments)
Audio Sample Rate 48 kHz (preferred), 44.1 kHz (acceptable)
Audio Levels US: -24 LKFS ±2 (ATSC A/85), EU: -23 LUFS ±1 (EBU R128), Peak: ≤ -6 dBTP
4:3 aspect ratio content is common in legacy and archival video libraries. However, ad creatives are typically produced in 16:9 and rendered independently of content aspect ratio. Platforms are responsible for managing aspect ratio differences between content and ad creatives during playback. ## The Mezzanine File The mezzanine file is a high-quality source asset used by platforms to generate delivery-ready renditions aligned to their encoding workflows. Unlike ready-to-serve files, the mezzanine file is not intended for direct playback in most environments, but instead serves as the input for downstream encoding workflows. Providing a mezzanine file enables platforms to produce optimized renditions that align with their encoding standards and streaming requirements. Mezzanine files are part of the media asset layer and are used by platforms to generate delivery-ready renditions aligned to their encoding workflows. They do not directly control playback behavior or user interaction. ### Role in CTV and Streaming Workflows In CTV and premium streaming environments: - Ads are frequently transcoded into adaptive bitrate (ABR) formats - Encoding pipelines align ad quality with primary content - Platform-specific encoding ladders are applied Without a high-quality mezzanine file: - Ads may be encoded from lower-quality sources - Visual quality may degrade - Playback may appear inconsistent with surrounding content Providing a mezzanine file ensures that ads can be encoded using the same standards as the content they accompany. ### Relationship to Ready-to-Serve Files - Ready-to-serve files are used for immediate playback - Mezzanine files are used for platform-side encoding In some workflows: - Platforms may use ready-to-serve files directly - In others, mezzanine files are preferred or required Advertisers are encouraged to provide both where supported. ### Recommended Mezzanine Specifications | Setting | Recommendation | |---| ---| |Container | .mov (preferred), .mp4 | |Video Codec | Apple ProRes (preferred), DNxHD/DNxHR | |Alternative Codec | H.264 High Profile (if mezzanine codecs unavailable)| |Bit Depth | 8-bit minimum, 10-bit preferred| |Resolution | Native resolution (no upscaling)| |Aspect Ratio | Native aspect ratio| |Frame Rate| Native frame rate| |Color Space| Rec.709 (SDR), HDR optional | |Scan Type| Progressive only| |Audio Format| PCM preferred| |Audio Channels| Stereo (2.0), optional 5.1| |Sample Rate| 48 kHz | |Leaders / Slate| Not permitted | ## Linear Ad File Format Recommendations Linear video ads are delivered across a range of environments, including Connected TV (CTV), Online Video (OLV), and mobile platforms. To support consistent playback and interoperability across these environments, ad creatives should be provided in formats that are widely supported and compatible with standard video players and ad delivery systems. ### Baseline Format for Interoperability For maximum compatibility across platforms, advertisers are encouraged to provide video files using: - Container: MP4 (.mp4) - Video Codec: H.264 (AVC), High Profile - Audio Codec: AAC-LC This combination represents the most broadly supported format across: - CTV devices and applications - Web browsers and OLV environments - Mobile operating systems Providing assets in this format ensures that ads can be played directly or processed by downstream systems without requiring additional conversion. ### Additional Format Considerations While the MP4/H.264 format is the required baseline, additional formats may be provided where supported and/or required by the target platform. - HEVC (H.265) and AV1 may be used in environments that support these codecs, particularly in CTV workflows - Use of these formats should be confirmed with platforms prior to delivery - Alternative formats should be provided in addition to, not instead of, the baseline MP4/H.264 file Providing additional formats can improve efficiency or quality in supported environments but should not be assumed to be universally compatible. ### Relationship to Mezzanine and Ready-to-Serve Files Linear ad delivery may involve multiple asset types: - Ready-to-serve files are used for immediate playback in OLV and some CTV environments - Mezzanine files may be used by platforms to generate optimized renditions for adaptive streaming and SSAI workflows When supported, advertisers are encouraged to provide: - A set of ready-to-serve renditions for immediate playback - A high-quality mezzanine file for downstream encoding Platforms may choose to: - Serve ready-to-serve assets directly - Transcode mezzanine files to align with their encoding pipelines ### Streaming and Delivery Considerations Video delivery environments may use different playback methods, including: - Progressive download (commonly used in OLV and web environments) - Adaptive bitrate (ABR) streaming (commonly used in CTV and premium video platforms) In most cases: - Advertisers are not expected to provide adaptive streaming packages (e.g., HLS or DASH manifests) - Platforms generate these formats from mezzanine or high-quality source files Advertisers are encouraged to confirm platform-specific delivery requirements where applicable. ### Compatibility and Playback To ensure consistent playback across environments: - Use widely supported codecs and containers (MP4 + H.264 + AAC-LC) - Avoid reliance on platform-specific or proprietary formats unless specifically required/requested - Ensure files are properly encoded for streaming (e.g., optimized for progressive playback where applicable) These recommendations address file format compatibility. For delivery signaling and execution, refer to the Ad Delivery Notes section. For interactive behavior, refer to the Secure Interactivity section. Additional encoding settings (e.g., bitrate, resolution, frame rate) should align with the guidance provided in the Ready-to-Serve Video Ads section. ## Video Companion Ad Guidelines Both linear and nonlinear ads have the option to be served with a companion ad. Companion ads are display ads in the form of text, static image, rich media, or skins that wrap around the video experience. Companion ads come in a number of sizes and may require some coordination for appropriate placement. The primary purpose for the companion ad is to offer sustained visibility of the sponsor throughout the streaming video experience and to leave behind a reminder after the linear or nonlinear component has been completed. The following companion ad format guidelines outline the minimum considerations for companion ad development. Publishers may offer other formats and specifications that extend these recommendations. Please check with publisher for specific requirements. |Property | Specification | | --- | --- | |Content | Since companion ads are displayed with video content and ads, companions should not contain any video or audio. | |Dimensions | Companion ad dimensions should fit publisher display placement dimensions, but common sizes offered are: 300x250, 468x60, 300x100, 728x90, 300x60 | |File Size | 200 kB for most ads but check IAB Creative Display Guidelines for appropriate file size | |Audio | No audio allowed in companion ad unit.| Best practices for HTML Companion assets Data minimisation in HTML assets is an essential practice for reducing the electricity consumption of digital campaigns. Every extra line of code, unused script, or uncompressed image adds weight to the file and increases the amount of data transferred when a page or banner loads. By optimising HTML structure, compressing resources, and removing redundant tracking or animation scripts, brands can significantly reduce loading times and energy consumption across servers, networks, and user devices. Techniques such as lazy loading, minification, and efficient caching not only improve electricity consumption but also enhance user experience by making pages faster and smoother. In short, a lighter and cleaner HTML codebase supports both performance, electricity consumption and lower greenhouse gas emissions. ## Audio Guidelines A sudden spike in volume during ad playback can interfere with the user experience and negatively affect users’ perception of brands. Broadcast networks are required to adhere to the Commercial Advertisement Loudness Mitigation (CALM) act. A similar bill has been introduced to streaming services in California as of drafting in 2026. Ad agencies can aid the industry in this effort by normalizing ad volume levels to avoid any spikes within the ad. Some publishers and their SSAI partners won’t allow an ad to play until they’ve ensured that the ad’s volume has been normalized. As a best practice, peak levels should not exceed -6 db true peak. ## Accessibility Guidelines All ads should adhere to local regulations and best practices for audio, visual and interactive accessibility. Resources and recommendations can be found in the Web Content Accessibility Guidelines. ## Efficiency and Sustainability Considerations Efficient encoding practices can contribute to reduced data transfer and improved playback performance across devices and network conditions. While overall energy consumption in video playback is largely driven by end-user devices, optimizing bitrate and file size can contribute to more efficient use of network and infrastructure resources at scale. Advertisers are encouraged to balance visual quality with efficient encoding practices appropriate for the target environment, avoiding unnecessarily high bitrates that do not provide meaningful improvements in perceived quality. ## Ad Delivery Notes The mechanism for ad delivery is out of scope for this document but should be a consideration in the development process. When the ad will be served using an ad server, the most widely accepted delivery mechanism in digital video is the Video Ad Serving Template (VAST). Not as widely adopted in CTV, VAST implementations for CTV support are expected to increase as programmatic buys and cross-screen campaigns continue to grow. VAST provides details about the ad to the video player in a way that enables ad portability and consistent tracking from system to system. In version 4.x, a single VAST tag identifies all four file versions outlined in this document necessary for smooth ad playback experience. It also enables the delivery of other ad components such as companion ads, ad pods, back-up images, and any interactive elements, including tracking elements that help measure impressions. VAST defines how ad metadata and media files are communicated between systems. It does not define the encoding characteristics of the video assets themselves, which are covered in the Video Ad Submission Guidelines section. When a VAST response includes multiple media files of different resolutions and bitrates, the video player should intelligently select the most appropriate version based on the viewer’s screen size, device, and connection. Choosing the highest bitrate by default is unnecessary and wasteful, as it increases data transfer and energy use without improving perceived quality on smaller screens. By adapting playback dynamically — for example, using a lower bitrate on mobile devices — advertisers can maintain a consistent user experience while significantly reducing bandwidth consumption. Delivery decisions at the player level are a key factor for more sustainable digital advertising. In addition to VAST, the Safe Interactive Media Interface Definition (SIMID) may be used. Wrapping an interactive ad in SIMID enables safe and transparent interaction between the ad and the player. See the Secure Interactivity section for more details. For more dynamic ad portability, verify whether the publishers you work with accept VAST and that your ad server can serve your ads using VAST. When using SIMID for interactive ads, verify which publishers can accept SIMID. In addition to verifying VAST and SIMID support, request publisher requirements that are as specific as possible.