Blendpipe homeSend a brief
Menu

CTV ad specs: one master file, many publisher requirements

CTV ad specs differ by publisher. Build one ProRes master, then MP4 renditions, a VAST tag and an Ad-ID that pass DV360, Hulu, Roku and NBCU checks.

Reader question
What files does a connected TV campaign need, and how do you build one master that passes every publisher's spec?
A rolled sheet of dough on a floured wooden counter has been cut into several shapes by metal cookie cutters, and the cutter still pressed into the dough is drawn in steel blue with a bold black outline.

A connected TV (CTV) campaign needs a set of files, not one: a high-quality master, an MP4 mezzanine at 1920 x 1080 and at least 15 Mbps, smaller MP4 renditions at the bitrates each publisher names, a VAST tag without VPAID or wrapping, and a creative ID such as an Ad-ID that travels with every copy. The way to pass every publisher’s check is to finish one progressive master at 23.976 or 29.97 fps with a full mix at -24 LKFS, derive every other file from it, and test each rendition against the sheet attached to the media buy. Specs differ by publisher, so the master is the only file you build once.

This guide works outward from that master. It uses the AICP file deliverable specification for the master; the help pages of Google Display & Video 360 (DV360), The Trade Desk and Microsoft Invest for the publisher renditions; and IAB Tech Lab’s VAST standard for the tag. Every figure was checked on the publisher’s or standards body’s own page in November 2026. Spec pages change without notice, so treat the numbers as a map of the territory and the publisher’s current sheet as the ruling document.

What files does a CTV campaign need?

A CTV buy needs a master for archive and broadcast, a mezzanine MP4 for server-side insertion, a ladder of ready-to-serve MP4s, a VAST tag, a creative ID and, where the plan includes them, captions. Each item feeds a different system downstream, and a missing one usually stops the line from serving rather than lowering its quality.

Connected TV here means ads that play on a television set through an internet connection: streaming apps on smart TVs, plug-in sticks, set-top boxes and game consoles. The files behave differently from social video in three ways. Most CTV ads cannot be clicked. Many are stitched into the program stream on a server rather than called by the app. And most publishers re-encode what you send, so they ask for a large, clean source file rather than a small finished one.

Item What it is Who asks for it
Broadcast master Apple ProRes 422 HQ QuickTime with a 5-second slate and 2 seconds of black, per the AICP spec TV networks and stations that take file delivery, and your own archive
Digital master The same picture and mix with no slate or black, progressive scan The source for every encode below
Mezzanine MP4 1920 x 1080, 15,000 to 30,000 kbps DV360, The Trade Desk, NBCU, Hulu and server-side insertion systems
Ready-to-serve renditions High, medium and low quality MP4 files Publishers that play files directly; VAST 4 asks for three quality levels or an adaptive stream
VAST tag The XML response that tells a player or stitching service where the files are Every third-party-served CTV line
Creative ID The Ad-ID code on the slate, in the file name and in the VAST tag Networks, ad servers and stitching services
Captions An embedded caption track or a sidecar file Varies by destination

Two terms carry most of the weight. A mezzanine file is, in DV360’s words, “a raw source file of the highest possible quality” that is “too large to be served directly”, so server-side ad insertion platforms “will usually dynamically extract the quality necessary to encode the appropriate versions for different environments” (Display & Video 360 Help, “Connected TV creatives”). DV360 adds that the mezzanine “requires time to go through an encoding process”, which matters for launch dates. Server-side ad insertion (SSAI, also called ad stitching) means a service joins the ad to the program on a server, so the TV receives one continuous stream. IAB Tech Lab describes that flow step by step in VAST 4.3, and it explains why the mezzanine and the creative ID matter so much later in this guide.

Why is there no single CTV spec?

There is no single CTV spec because each publisher sets its own file rules, and the buying platforms check only some of them. DV360’s help page lists publisher-specific guidelines for 12 publishers, from Discovery+ to Univision, and tells advertisers to “work directly with the publisher” for any it does not list. Microsoft Invest warns that its CTV requirements “may change at any time depending upon the publisher’s needs”.

The layers stack like this:

  1. The publisher (Hulu, NBCU, Roku, Netflix and the rest) decides what its players and stitching systems accept.
  2. The buying or selling platform (a demand-side platform such as DV360 or The Trade Desk, or a sell-side platform such as Microsoft Invest) runs automated checks on file type, resolution and bitrate and flags creatives that would not serve.
  3. The ad server that hosts third-party creatives builds the VAST tag and the encodes it points to.
  4. Your production files have to satisfy all three.

The checks at layer 2 are partial. DV360 says it performs “a limited set of checks” on file type, video resolution and bitrate, warns that “some publishers have their own creative detection systems that detect violations”, and recommends pre-auditing creatives with publishers. The Trade Desk’s creative specifications say that requirements “such as bitrates” vary “drastically by publisher” and ask advertisers to check individual publisher specs before submitting. A green tick in the platform is a good sign, not a sign-off.

A practical rule follows. The spec that governs a file is the one attached to the insertion order or deal for that publisher, with the date you received it. Generic guidance, including this article, tells you where the lines usually fall. When the two disagree, the publisher’s sheet wins.

Some things do hold across the documents we checked. MP4 is the serving format everywhere (a few publishers also take a MOV upload), 1920 x 1080 is the size of the top-quality file, audio is 48 kHz, the frame rate is a constant 23.976 or 29.97 fps in North America, and VPAID is out. Build those into the master and most of the remaining work is encoding.

Start from the master: the AICP broadcast spec

The safest master for a campaign that runs on both linear TV and CTV is the one in the AICP’s North American file deliverable specification: Apple ProRes 422 HQ, 1920 x 1080, 4:2:2, with a 5-second slate, 2 seconds of black and a full mix at -24 LKFS. The spec dates from February 2018 and, according to the document, was endorsed by the ANA, the 4A’s, NABA/DPP and IAB Tech Lab “to align the industry on a common deliverable” (AICP, File Deliverable Specifications).

AICP HD element Requirement
Codec Apple ProRes 422 HQ, 4:2:2 sampling
Raster and frame rate 1920 x 1080 progressive at 23.976; 1920 x 1080 interlaced at 29.97 (top field first); or 1280 x 720 progressive at 59.94
Layout 5 seconds of slate, 2 seconds of black, then the content, “NO extra frames”
Slate Ad-ID or other content identifier, with “H” for high definition
Title safe 90% within the 4 x 3 center area, or 90% of the 16 x 9 area if specifically noted (SMPTE RP 2046-2)
Timecode Non-drop frame
Audio PCM, 48 kHz, 24-bit; stereo on channels 1 and 2, or 5.1 as 8 mono channels with the stereo mix on 7 and 8
Loudness -24 LKFS on the full mix, true peak below -2 dB, per ATSC A/85:2013; the first 7 seconds are excluded from the measurement
File name The Ad-ID with “H” and the extension, for example ABCD0001000H.mov
Captions (optional) An embedded QuickTime caption track at 29.97 fps

The document also says AICP was working with industry groups on a specification “that will supersede this one”. As of November 2026 the 2018 PDF is still the version AICP serves at its published address, and we found no newer edition. If a network sends its own sheet, that sheet governs.

Which frame rate should the master use?

Choose 23.976 or 29.97 before the shoot and keep it through finishing. DV360 and The Trade Desk both list 23.98 or 29.97 fps for every CTV rendition, DV360 adds 25 fps for PAL countries, and both forbid duplicate frames. Both also rule out telecine, which they define as converting footage from its source rate “by inserting a duplicate frame every fourth frame, or by blending or interlacing every third frame together”. A 24 fps animation conformed to 29.97 by pulldown fails that rule, so animation and 3D renders should be made at the project rate from the start.

At 23.976, timecode counts 24 frames per second, so a 30-second spot holds 720 frames and its last frame is 00:00:29:23. At 29.97 it holds 900 frames. The frame and timecode calculator converts between frames, timecode and real time at either rate.

Why the CTV master must be progressive

AICP’s 29.97 option is interlaced 1080i, and CTV sheets reject interlacing. DV360’s best practices tell advertisers to avoid interlacing, The Trade Desk lists “No telecine, interlacing, or duplicate frames”, and the Netflix section of Microsoft Invest requires a progressive scan. A project finished at 23.976 progressive can feed both destinations from one master. A project finished at 29.97 needs a progressive digital master for CTV beside the interlaced broadcast file, which is one more file to check and archive.

Slate, black and file names

The slate and the 2 seconds of black belong to the broadcast master only. Publisher sheets ask for exact durations (Hulu takes 15 or 30 seconds, ESPN 15 or 30), so a rendition that still carries 7 seconds of slate and black fails a 30-second duration check. Export the digital master from the same timeline without them, and keep the Ad-ID in the file name of every copy, so anyone handling a file can tie it back to the registry entry.

How do you get from the master to the renditions?

You get from the master to the renditions by encoding down a ladder: one mezzanine MP4 inside the publisher’s top bitrate band, then high, medium and low files sized to each publisher’s bands. Every encode should come from the master, not from another encode, so quality losses do not stack.

  1. Lock picture and mix. Any change after this point means a new creative ID and a new set of encodes.
  2. Export the broadcast master to the AICP layout if any network or station is on the plan.
  3. Export the digital master from the same timeline without slate or black, progressive, at the project frame rate.
  4. Encode the mezzanine MP4 at 1920 x 1080, inside 15,000 to 30,000 kbps, with audio at 192 kbps or more at 48 kHz.
  5. Encode the ready-to-serve renditions to each publisher’s bands, sharing a file between publishers only where both bands allow it.
  6. Measure every file for duration, frame rate, bitrate, loudness and true peak before it leaves post.
  7. Host or traffic the files, then read the platform’s eligibility report for each publisher.

The ladders that DV360 and The Trade Desk publish disagree on what “high quality” means:

Rendition DV360 The Trade Desk
Mezzanine 15,000 to 30,000 kbps; 1920 x 1080 preferred 1920 x 1080; 15,000 to 30,000 kbps; up to 10 GB
High 1,500 to 2,500 kbps at 720p; 2,500 to 3,500 kbps at 1080p 1920 x 1080; 4,000 to 6,500 kbps
Medium 700 to 1,500 kbps (SD) 1280 x 720; 1,200 to 3,500 kbps
Low 500 to 700 kbps 1280 x 720; 500 to 1,200 kbps
Audio 192 kbps, 48 kHz 192 kbps minimum, 48 kHz
Frame rate 23.98 or 29.97 (25 for PAL countries) 23.98 or 29.97

A 1080p “high” file at 3,000 kbps meets DV360’s band and misses The Trade Desk’s. Neither ladder is wrong; each describes what its own platform expects. The mezzanine is the rung they agree on, which is why it is the file to get right first. DV360 asks for “at least one MP4 asset with a bitrate of 15 Mbps or higher”, and The Trade Desk states that the mezzanine “requires a 1920 × 1080 resolution with a video bitrate of at least 15,000 kbps or higher”. The Trade Desk adds that it does not upscale or stretch uploads, so the best file you have is the one to send.

From one master to every CTV fileFlow diagram. A locked edit and mix produces a broadcast master in ProRes 422 HQ with a slate, which goes to TV networks with the Ad-ID on the slate. The same edit produces a digital master with no slate, progressive. The digital master is encoded into an MP4 mezzanine at 1920 by 1080 and at least 15 Mbps, and into high, medium and low ready-to-serve MP4 files. Both kinds of MP4 are listed in a VAST tag whose UniversalAdId carries the same Ad-ID, and the tag goes to CTV publishers and stitching services, which run eligibility checks. Locked edit and mix one picture, one mix Broadcast master ProRes 422 HQ, slate TV networks Ad-ID on the slate Digital master no slate, progressive MP4 mezzanine 1920 x 1080, 15+ Mbps Ready-to-serve MP4s high, medium, low VAST tag UniversalAdId: Ad-ID CTV publishers eligibility checks
Every file comes from one locked edit and mix; only the broadcast master carries a slate. / Sources: AICP File Deliverable Specifications (February 2018); Display & Video 360 Help, "Connected TV creatives"; IAB Tech Lab, VAST 4.3; all checked November 2026.

File sizes: the arithmetic behind upload limits

File size is bitrate times duration divided by 8, because there are 8 bits in a byte. A 30-second mezzanine at 15 Mbps is 15 x 30 / 8 = 56.25 MB; at 30 Mbps it is 112.5 MB. Add the audio: 192 kbps for 30 seconds is 0.192 x 30 / 8 = 0.72 MB. Both fit easily under the 1 GB maximum DV360 sets for creatives it hosts.

The Trade Desk’s spec document gives the example “30 seconds x 15,000 kbps = 450 MB or 0.45 GB”. That figure is in megabits: 450 megabits is 56.25 megabytes. The difference matters when a team budgets storage or transfer time, so check which unit a sheet means before anyone plans around it.

The ProRes master is far larger. Apple’s ProRes white paper (April 2022) lists ProRes 422 HQ at about 176 Mbps for 1920 x 1080 at 24p and about 220 Mbps at 29.97. A broadcast master holding 37 seconds of picture (5 of slate, 2 of black, 30 of spot) at 176 Mbps is 176 x 37 / 8 = 814 MB; at 220 Mbps it is 220 x 37 / 8 = 1,017.5 MB, just over 1 GB. That is why masters go to networks by file transfer and MP4s go to ad servers. The file size and bitrate calculator runs this arithmetic against any upload limit.

Example (fictional). Kestrin, an invented home-heating brand, buys a CTV flight on Hulu, NBCU and Roku through a sell-side platform that applies the Microsoft Invest rules for third-party creatives, with a 30-second spot and a 15-second cutdown. For each length the team plans:

  • one mezzanine MP4 at 1920 x 1080 and 20,000 kbps, which meets Hulu’s rule (15,000 to 30,000 kbps) and NBCU’s mezzanine rule (the same band at 1920 x 1080);
  • one NBCU high file at 1280 x 720 and 4,000 kbps (band 3,250 to 5,000);
  • one Roku high file at 1,800 kbps (band 1,200 to 2,100), because the Roku and NBCU high bands do not overlap;
  • one medium file at 960 x 540 and 1,100 kbps, inside both NBCU’s medium band (1,000 to 1,500) and Roku’s (700 to 1,200);
  • one low file at 640 x 360 and 400 kbps, inside both NBCU’s low band (340 to 460) and Roku’s (360 to 500).

That is 5 encodes per length, 10 for the two lengths, plus two digital masters. NBCU rejects a creative that sends more than four files, so the NBCU tag carries exactly the mezzanine, the NBCU high file and the shared medium and low files; a Roku tag carries the Roku high file and the shared medium and low files; and a Hulu tag carries the mezzanine, the one file inside Hulu’s band. Three tags per length, six in all. The 30-second mezzanine weighs 20 x 30 / 8 = 75 MB of video plus 0.72 MB of audio at 192 kbps, about 75.7 MB. Every name, bitrate and count in this box is an illustration.

What do the big publishers require?

The big publishers agree on MP4 and 16:9 and disagree on almost everything else: durations, how many files, and the bitrate bands. The table below collects the rules Microsoft Invest publishes for five CTV publishers. It is a snapshot of one platform’s documentation (DV360 and The Trade Desk link to their own lists), so read it as an example of how far the rules spread, not as the sheet for your buy.

PublisherFiles requiredBitrate (kbps)ResolutionDurationsOther rules
HuluAt least one MP4 or MOV15,000 to 30,000960 x 720, 1280 x 720, 1440 x 1080 or 1920 x 108015 or 30 sSame rules for hosted files
RokuThree MP4s: high, medium, low1,200 to 2,100; 700 to 1,200; 360 to 500No set resolution6 to 60 s16:9 only; a hosted file needs 2,100 or more
ESPNTwo MP4s: high, low2,000 to 5,000; under 1,5001280 x 720 or 1920 x 1080 (low also 640 x 360)15 or 30 sHosted file at 2,000 or more
NBCUExactly four MP4s: mezzanine, high, medium, low15,000 to 30,000; 3,250 to 5,000; 1,000 to 1,500; 340 to 4601920 x 1080; 720 x 480, 1280 x 720 or 1920 x 1080; 640 x 480 or 960 x 540; 640 x 360 or 416 x 2346, 15, 30, 45 or 60 sMore than four files is rejected
Netflix (hosted)One MOV (ProRes preferred) or MP4 (H.264)MOV above 80,000 at 1080p; H.264 above 12,000 at 1080p1280 x 720 or 1920 x 1080, progressive10, 15, 20, 30 or 60 sNo QR codes; one video and one stereo audio track at 48 kHz; durations within 500 ms
Third-party creative rules, except where marked hosted. Publishers change these rules; use the sheet attached to your buy. / Source: Microsoft Invest, "Creative CTV guidelines and specifications", checked November 2026.

Several rules in that table decide production choices rather than encoding choices:

  • Durations are exact. Hulu and ESPN take only 15 or 30 seconds. NBCU takes 6, 15, 30, 45 or 60. Netflix takes 10, 15, 20, 30 or 60. Roku accepts anything from 6 to 60. A 20-second edit runs on Netflix and Roku and nowhere else in the table.
  • File counts are fixed. NBCU requires all four renditions and rejects a creative that sends more. Roku requires three. A missing rendition “will prevent the line from serving”, in Microsoft’s words.
  • The landscape frame is assumed. Roku states 16:9; the resolution lists of the others are all landscape. Google Ads Help says the same of YouTube’s 30-second non-skippable CTV format: “Video assets must be horizontal. Square or vertical assets will not be able to run.”
  • Content rules sit inside the spec. Microsoft’s Netflix section notes that Netflix “does not allow QR codes in their creatives”. A QR code end card built for one publisher needs a clean alternate for another.

Durations: why a 20-second edit can strand a flight

Lengths are set in the edit, weeks before trafficking, and no encoding setting can fix a length a publisher does not accept. If the plan includes Hulu or ESPN, every CTV length has to be 15 or 30 seconds. If a brand wants a 20 or a 45, the deliverable matrix should show which publishers can run it before the script is timed.

Exact also means exact at the frame level. A :30 at 23.976 is 720 frames, which runs 30.03 seconds of wall-clock time; at 29.97 it is 900 frames, also 30.03 seconds. Ask each publisher which measure its validator uses and what tolerance it allows, and write the answer into the spec sheet for the job.

Turning the matrix into a deliverable list

Build the list per length, then per publisher group:

  1. List every publisher on the plan and the sheet for each, with its date.
  2. For each length, write the bands each publisher requires for each rung.
  3. Merge rungs where bands overlap, as the Kestrin example does for the medium and low files.
  4. Count the encodes, then the tags (one tag for each set of files a publisher will accept).
  5. Add masters, captions and any clean alternates (no QR code, no click prompt).

The count belongs in the deliverable matrix beside the cutdowns, aspect ratios and languages. Campaign versioning describes how that matrix is built and how each file is named to it.

VAST tags, VPAID and wrappers: what CTV players accept

CTV players accept a plain VAST tag that points to MP4 files; most do not accept VPAID, MRAID or wrapped tags. VAST (Video Ad Serving Template) is IAB Tech Lab’s XML standard for telling a video player which ad to play, where its files are and which tracking calls to fire.

The platform documents agree on the essentials:

  • DV360 recommends VAST 2.0, says VAST 3.0 and 4.0 are supported “but scale is more limited”, and states that VPAID, MRAID and tag wrapping “aren’t supported on most Connected TV devices”. It also requires MP4 and SSL-compliant creatives.
  • The Trade Desk accepts third-party CTV creatives as VAST tags only, says VPAID tags are not supported on CTV, and notes that VAST 3.0 and 4.0 “are typically less scalable”. It separates a standard VAST tag that happens to include a VPAID component from a VPAID wrapper, which is the thing that fails.
  • IAB Tech Lab lists VPAID as “Deprecated, replaced with SIMID”, the interface for interactive ads introduced with VAST 4.2. On its VAST page, the newest version is VAST 4.3, released December 2022. A VAST Addendum for CTV dated July 2024 adds support for ad registration through the Ad Creative ID Framework (ACIF) and covers higher-resolution creative for large screens, and IAB says these features reach VAST 2.x and 3.x through the addendum as well.

Two production consequences follow. First, interactivity belongs in units a publisher sells as interactive, not in the tag. Second, a CTV ad has no click. The Trade Desk says plainly that “CTV devices do not support the ability to click through to a landing page.” The call to action has to work by eye and ear: a short web address on screen long enough to read from a sofa, the same address in the voiceover, and a QR code only where the publisher allows one.

The Trade Desk also recommends one tag for each creative media asset rather than rotating several creatives through one tag. That keeps reporting clean, and it pairs with the creative ID rules below: one creative, one code, one tag.

How does the Ad-ID follow the file into the stream?

The Ad-ID code is printed on the slate, used as the file name and carried inside the VAST tag, so every system that touches the ad can match it to the same registry record. Ad-ID is the US ad registry run by a company of the American Association of Advertising Agencies and the Association of National Advertisers, and it compares its codes to a product barcode: they identify the ad and link it to metadata such as title, length and product.

The format is fixed (AD-ID, “How it works”):

  • 11 characters for standard-definition ads and 12 characters for high-definition or 3D ads.
  • A 4-character prefix licensed to a specific advertiser, then a 7-character code.
  • An “H” or “D” at the end where there is a specific media definition, which is why the AICP’s HD file name example reads ABCD0001000H.

In VAST 4.x the same code goes into the UniversalAdId element, which IAB Tech Lab makes required for linear ads, with an idRegistry attribute naming the registry. The VAST 4.3 example pairs idRegistry="ad-id.org" with the 12-character code CNPA0484000H. VAST 4.2 and later allow more than one UniversalAdId, so a spot registered in two countries can carry both codes.

The ID matters most in server-side insertion. VAST 4.3 sets out the flow:

  1. The publisher asks the stitching service for an ad.
  2. The stitching service requests a VAST tag from the ad server.
  3. The ad server returns a tag with a mezzanine file and ready-to-serve files.
  4. If the creative ID is new to the system, the service extracts and transcodes the mezzanine. In that case “the ad is skipped and the next available ad is played instead”, and VAST error code 407 is sent.
  5. If the ID matches an ad already transcoded, the service uses the stored version.
  6. The ad is stitched into the content stream.

Two working rules come out of that sequence. VAST 4.3 says that “if the ad creative is changed in any way, it should be served with a new creative identifier”, so a corrected super or a remixed track needs a new Ad-ID, not just a new file with the old name. And because a new creative is skipped the first time it arrives, tags should be live before the flight starts, so the first transcode does not cost impressions on launch day. The same code also anchors the network review of the spot’s content, which is covered in getting a TV commercial cleared.

Picture, sound and caption checks before the files leave

Most CTV rejections are technical and visible in a file report: wrong duration, wrong bitrate, interlacing, duplicate frames, mismatched audio and video lengths, or loudness away from the target. Each is cheaper to catch in post than in the platform, where a rejection can arrive days into the flight.

Picture

  • Constant frame rate at the project rate, with no telecine, interlacing or duplicate frames (DV360, The Trade Desk).
  • Progressive scan for every CTV file (the Netflix rules in Microsoft Invest; DV360’s frame quality guidance).
  • Title safe. AICP asks for 90% of the 4 x 3 center area unless the 16 x 9 area is specifically noted. Supers, legal lines and the web address belong inside it, sized to be read at television distance.
  • Resolution exactly as listed for each rung, with 1920 x 1080 for the mezzanine.

Sound

  • Track layout. The Netflix rules require one video track and one audio track, 2-channel stereo at 48 kHz, PCM preferred or AAC-LC at 192 kbps or more.
  • Duration match. The same rules require audio and video durations to be identical within 500 ms. A mix bounced with a tail of room tone fails that check.
  • Loudness. AICP specifies -24 LKFS measured on the full mix with true peak below -2 dB, and The Trade Desk’s CTV best practices ask advertisers to “ensure that the loudness of audio averages -24 LKFS”. Streaming publishers can set other targets, and the law treats broadcast and streaming differently. The companion article on loudness for TV and streaming ads separates the numbers that are law from the ones that are publisher practice.

Captions

AICP treats captions as optional and, where they are supplied, wants an embedded QuickTime caption track at 29.97 fps; it notes that 23.98 fps tracks were not supported. The first caption should “pop-on” after one second of content or “paint-on” after four frames. VAST 4.x adds a ClosedCaptionFiles element for sidecar caption files. Whether a spot needs captions at all, and which format to deliver, is the subject of the companion article on captions and audio description for video ads.

Approval and eligibility checks before launch

Many CTV publishers review creatives before they serve, and the buying platforms show part of that status inside the campaign. Build the review into the schedule rather than treating it as a formality on launch day.

  • DV360 shows a “Connected TV publisher eligibility” column on the line item. Netflix creatives are sent for approval automatically when an active line item targets a Netflix deal. Disney’s real-time ad exchange (DRAX) needs approval before serving, and an appeal returns the creative to “PENDING” for a new audit. For one type of fixed-terms programmatic deal sold through FreeWheel, the publisher must approve creatives before bid requests start.
  • Microsoft Invest shows a “View CTV Eligibility” section at upload, with “More Details” listing which requirements to adjust.
  • The Trade Desk runs a Go-Live Check when an ad group with at least one private contract is activated, and creatives running through FreeWheel need publisher verification, shown as the Supply Vendor Audit Status.

None of these technical checks replaces the standards review that decides whether the content may air, which looks at claims, supers and disclaimers rather than bitrates. Plan for both, and keep the technical files ready early enough that a rejected rendition can be re-encoded without moving the flight.

Questions to send the media team before the edit

The answers to these questions change the edit and the encode list, so ask them while the script is still being timed:

  1. Which publishers, apps and exchanges are on the plan, and will each buy run through a DSP, a sell-side platform or a direct insertion order?
  2. Will the creative be hosted by the buying platform or served by a third-party ad server, and which VAST version will the tag use?
  3. Which lengths does each publisher accept, and does any of them want a length the edit does not yet include?
  4. Which bitrate bands and file counts apply to each rung, and is there a written sheet with a date?
  5. Does any publisher forbid QR codes, prompts to click, or particular end card content?
  6. Who holds the Ad-ID prefix, and who registers each new code when the creative changes?
  7. How long does each publisher’s approval take, and who receives a rejection notice?

YouTube is a separate case: DV360 notes that YouTube inventory has its own CTV specifications, so a plan that mixes YouTube and other streaming apps needs both sets of answers.

The QC list for ad operations

Run this list on every file before trafficking, and record the result beside the file name.

  1. The governing spec sheet for each publisher is on file, with the date received.
  2. The length matches a duration the publisher accepts, counted in frames at the project rate.
  3. No slate or black remains in any digital file; the broadcast master has exactly 5 seconds of slate and 2 of black.
  4. Frame rate is 23.976 or 29.97 (25 where PAL applies), constant and progressive, with no duplicate frames.
  5. The mezzanine is 1920 x 1080 and inside the publisher’s 15,000 to 30,000 kbps band.
  6. Each ready-to-serve file sits inside its own band, and each tag carries exactly the number of files its publisher requires.
  7. Audio is 48 kHz stereo, at 192 kbps or more where AAC is used, and matches the video duration within the publisher’s tolerance.
  8. Loudness and true peak are measured on the full mix against the target in the sheet.
  9. Supers, legal lines and the web address sit inside title safe and are readable at television distance.
  10. No QR code or click prompt appears in versions for publishers that do not allow them.
  11. The Ad-ID is on the slate, in every file name and in the VAST UniversalAdId, and any change to the creative has a new code.
  12. The tag is plain VAST with no VPAID wrapper, and every media URL is served over SSL.
  13. The platform’s eligibility report is clear for every publisher, or each flag has an answer.
  14. Captions, where planned, are in the format the destination takes.
  15. Tags are live before the flight starts, so stitching services can transcode new creatives in advance.

The delivery specs checklist holds the general version of this list for every destination, not only CTV.

What to do next

Ask your media agency or each publisher for its current CTV sheet before the edit is timed, not after picture lock. Choose the project frame rate and the lengths with those sheets in hand, and write the rendition ladder into the deliverable matrix so the encodes, tags and checks are counted in the schedule. The deliverables page shows what a full handover contains, and a Blendpipe production plan lists the masters, encodes and checks for each placement before work starts. If a CTV flight is coming up, you can send a brief with the publisher list and the sheets attached.