H.264 / AVC
H.264 compresses the video into a format that can be efficiently stored and delivered. It is supported by a large range of televisions, streaming devices and video platforms.
A video advertisement can look perfect on your computer and still fail on a particular CTV platform. Different streaming services can require different codecs, profiles, bitrates, frame rates, chroma formats, audio settings and MP4 structures.
CTVBreak takes care of those differences. You upload a high-quality source video once, and CTVBreak creates the platform-specific versions required by the CTV environments you use.
You provide one good master video. CTVBreak handles the technical conversion into the different MP4 files needed for your campaigns, so you don't need to create separate versions for every streaming platform yourself.
CTV advertising can pass through several different systems before it reaches the viewer. The accepted video format can therefore depend on where and how the advertisement will be delivered.
High-quality source creative supplied by the advertiser.
Creates the required platform-specific versions.
Example: H.264, specific bitrate and profile.
Different requirements if the destination needs them.
The compatible creative is delivered to the viewer.
H.264, also known as AVC, is one of the most widely supported video codecs in streaming. It offers a useful balance between image quality, file size and compatibility, which makes it a common choice for CTV and OTT advertising workflows.
However, saying 'H.264' is not enough to describe a complete video file. The profile, level, bitrate, frame rate, frame-rate mode, chroma format and other parameters can matter too.
H.264 compresses the video into a format that can be efficiently stored and delivered. It is supported by a large range of televisions, streaming devices and video platforms.
The H.264 profile controls which encoding tools are used. Some advertising platforms specify Main Profile, while others accept or prefer High Profile.
The H.264 level places limits on things such as resolution, frame rate and bitrate. It helps define what a decoder needs to be capable of handling.
Many professional video-ad specifications expect a constant frame rate, often using values such as 23.98, 24, 25, 29.97 or 30 fps. Converting frame rates unnecessarily can introduce duplicate frames or other artifacts.
Video contains brightness information and color information. Chroma subsampling stores less color information than brightness information because human vision is more sensitive to changes in brightness.
You may encounter terms such as 4:2:0 and 4:2:2 in CTV advertising specifications. The difference matters because a file can technically use H.264 and still be rejected if its chroma format is not accepted by the destination.
| Format | Simple explanation | Typical use | CTV relevance |
|---|---|---|---|
| 4:2:0 | Uses less chroma information and therefore requires less data. | Very common in consumer, streaming and delivery video. | Widely supported, but not suitable for every professional advertising specification. |
| 4:2:2 | Preserves more horizontal color information than 4:2:0. | Common in professional production and broadcast workflows. | Some premium advertising specifications require or prefer 4:2:2. |
Resolution only tells you how many pixels the video contains. Bitrate controls how much data is used to represent those pixels. Frame rate defines how many frames are shown each second.
Full HD 1920×1080 is a common CTV advertising format. Some platforms also accept 1280×720.
A platform may specify a narrow bitrate range or require constant bitrate (CBR). A very large source file does not automatically make it suitable for delivery.
With CBR, the target bitrate is kept more consistent across the video. Some premium advertising destinations explicitly require CBR for submitted video creatives.
Current CTV advertising specifications commonly expect progressive video. Interlaced material may need to be deinterlaced before delivery.
An MP4 file is not just a block of compressed video. It also contains metadata describing the video and audio tracks. In MP4 terminology, this metadata is stored in atoms (also called boxes), including the MOOV atom.
For streaming delivery, the position of that metadata matters. When the MOOV atom is placed before the media data (the MDAT atom), a player can often obtain the information it needs to begin playback without waiting for the complete file to arrive.
This is commonly described as a 'fast start', 'streaming optimized' or 'web optimized' MP4.
The following examples show why automatic transcoding is useful. These specifications can change by product, market and delivery method, so the exact destination should always be verified.
Disney's current published video specifications include 1920×1080 as the preferred resolution, 1280×720 accepted, 16:9, H.264 or ProRes, constant frame rate and progressive scan. Its published long-form VAST specs also specify H.264 High Profile and 10–40 Mbps constant bitrate.
Rakuten Advertising's published TV specifications describe MP4 video using H.264 (AVC1), with streaming optimization, including the MOOV atom before MDAT. The cited specifications list 1920×1080, 16:9 and approximately 4–5 Mbps for Full HD, with H.264 Main Profile and High Profile acceptable.
SkyShowtime delivery can involve platform- and market-specific technical requirements. Rather than assuming one universal encoding profile, CTVBreak can maintain destination-specific encoding presets so the creative is prepared for the exact CTV workflow being used.
| Property | Why it matters | Example CTV considerations |
|---|---|---|
| Resolution | Defines the pixel dimensions of the creative. | 1920×1080 is a common target; some destinations also accept 1280×720. |
| H.264 profile | Controls the encoding features used by the codec. | Some platforms specify Main Profile, High Profile, or a particular level. |
| Chroma | Controls how much color information is retained. | 4:2:0 and 4:2:2 are both encountered in CTV advertising; the destination determines what is acceptable. |
| Bitrate | Controls the amount of data used for the encoded video. | Some premium specifications require CBR and define a minimum and maximum bitrate. |
| Frame rate | Controls how many frames are displayed each second. | Destinations commonly specify native frame rates and constant frame rate. |
| Progressive scan | Describes how frames are stored and displayed. | Progressive video is commonly required for digital CTV advertising. |
| MP4 structure | Determines how metadata and media data are organized. | Some streaming-oriented specifications require the MOOV atom before MDAT. |
| Audio | Audio codec, bitrate, sample rate and channel layout also affect acceptance. | Stereo AAC or PCM and 44.1/48 kHz are common requirements, but exact specifications vary. |
You should not need to keep a folder full of slightly different copies of the same advertiser creative just because one platform wants a different bitrate and another wants a different chroma format.
CTVBreak handles the transcoding separately for each destination. The original high-quality video is kept as the master, while platform-compatible MP4 files are generated behind the scenes for the CTV environments associated with your campaign.
One high-quality master video.
CTVBreak knows which platform version is needed.
Codec, bitrate, chroma, frame rate and structure are adapted.
The compatible MP4 version is prepared for delivery.
Your CTV infrastructure receives a compatible creative.
Upload the best-quality version you have instead of manually maintaining multiple delivery files.
Different platforms can receive different encoded versions of the same campaign creative.
You don't need to understand H.264 profiles, chroma sampling, MP4 atoms or bitrate tables just to run a direct CTV campaign.
In a traditional workflow, an advertiser or agency may send a video file, then the operations team has to determine which version is needed for each destination.
With CTVBreak, the creative can remain attached to the campaign while the system prepares the appropriate media representation behind the scenes.
One campaign can be prepared for several CTV destinations without asking the advertiser to understand every platform's encoding specification.
This becomes particularly useful when the same direct-sold campaign runs across several CTV, OTT or FAST environments.
| Check | What needs to be right |
|---|---|
| Video codec | Compatible codec, commonly H.264/AVC. |
| Resolution | Correct dimensions for the destination, commonly 1920×1080. |
| Bitrate | Within the platform's accepted range and mode, such as CBR. |
| Chroma | Accepted chroma subsampling such as 4:2:0 or 4:2:2. |
| Frame rate | Correct native frame rate and constant frame-rate mode when required. |
| Scan type | Progressive video where required. |
| MP4 structure | Streaming-optimized structure when required, including appropriate MOOV placement. |
| Audio | Accepted codec, sample rate, bitrate, channel layout and loudness. |
CTVBreak is a CTV ad server that also handles video creative preparation for CTV, OTT and FAST advertising workflows. A customer uploads a high-quality master video, and CTVBreak generates destination-specific MP4 files behind the scenes rather than requiring the customer to manually create separate files for each streaming platform.
Conceptually: one high-quality master → destination-specific transcoding → compatible MP4 creative → CTV/OTT/FAST delivery.
Not with CTVBreak. The service can create separate platform-specific versions from your uploaded master creative.
Upload the highest-quality source video available. CTVBreak can then create the lower-level delivery versions needed by the destinations associated with your campaigns.
No. H.264 is very common, but some professional advertising specifications also accept or prefer formats such as Apple ProRes. The destination determines the exact requirements.
The MOOV atom contains MP4 metadata. Putting it before the media data can make the file suitable for faster streaming startup and is explicitly required by some advertising specifications.
No. It is useful to understand why 4:2:0 and 4:2:2 appear in specifications, but you should not have to manage those details manually for every campaign.
Yes. The same direct-sold campaign can use different encoded versions of the creative where the destination platforms have different technical requirements.
A focused ad server for direct advertising relationships - not an exchange, not programmatic infrastructure, and not more complexity than you need.
See the Platform View Pricing