VAST 4 Video Delivery: What Brands Need Beyond an MP4

A finished MP4 can be perfectly watchable and still be unready for advertising. If a media team will upload the file manually to one known placement, that may be acceptable. If the campaign must move across publishers, connected TV environments or programmatic supply, the buying question changes: can every system identify, transcode, track and verify the creative without an emergency rebuild?

Amazon Ads made that distinction more consequential on September 2, 2026. Amazon DSP now supports VAST 4.0 through 4.3 on third-party publisher inventory worldwide and returns the highest version a publisher's player can handle. Publishers that use VAST 2 or 3 remain supported. Amazon-operated inventory—including Stores and Fire TV—still accepts VAST 2 or 3 creatives. “Amazon” therefore does not describe one technical route; third-party supply and Amazon-operated inventory can require different delivery paths inside the same media plan.

The update is not a new video codec. It is a reason to stop treating the final export as the whole deliverable.

Start with the layer distinction

IAB Tech Lab defines VAST as a universal XML schema for serving ads to digital video players. It carries instructions and metadata: where media lives, which events are tracked, and which verification or interactive resources accompany the ad. MP4, WebM and adaptive streams are media files that the player actually loads.

There is no production command called “export a VAST 4 MP4.” A production partner prepares traceable media assets. An ad server or creative technology partner packages those assets, identifiers, tracking and rules into a VAST response. The publisher's player then executes the highest compatible path.

IAB Tech Lab's CTV programmatic guidance explains the asset consequence. Server-side ad insertion needs a high-quality mezzanine file that can be transcoded for the destination, plus files that are ready to play. VAST 4.x calls for either an adaptive ready-to-serve stream or at least three quality levels. A Universal Ad ID helps the same creative remain identifiable as it crosses systems.

Buy a portable delivery package, not a lone export

1. A trustworthy mezzanine master

The mezzanine is a high-quality source for downstream encoding, not the lightweight file shown to the viewer. The scope should state resolution, frame rate, color space, audio, duration and aspect ratio, plus whether clean, captioned and textless variants exist. A file downloaded from a social platform is not a master.

2. Ready-to-serve renditions

Provide high, medium and low quality versions, or an adaptive stream confirmed by the media and publisher teams. The content and duration should remain consistent while bitrate, encoding and resolution may differ. Publisher specifications still control the final acceptance test; VAST 4 does not erase placement-level requirements.

3. A stable creative identity

The asset manifest should map creative ID, version, language, market, duration, aspect ratio, rights window and approval owner. Ad registration and trafficking teams may own Universal Ad ID, but production still has to prevent two different cuts from masquerading under similar filenames. This mapping is what turns creative history into reusable operational data.

4. Separate verification and interactive resources

VAST 4 separates playable media from verification and interactive code. If a campaign includes measurement vendors, interactive end cards, captions, companion assets or fallbacks, list the owner, supported environment and failure behavior for each. The core video must remain usable when a player cannot execute an optional component.

5. An inventory compatibility and QA record

Maintain a matrix for inventory family, supported VAST version, accepted files, tracking capability, test result and fallback. Amazon's announcement shows why “Amazon” is not a useful row by itself: VAST 4 is available on third-party publisher supply, while Stores and Fire TV remain on VAST 2 or 3.

Assign three owners before production locks

The production partner owns story, picture, sound, masters, renditions and the asset manifest. The ad server or creative technology team owns tag generation, tracking configuration and creative-ID mapping. Media and ad operations own inventory confirmation, player capability, publisher specifications, test traffic and fallback decisions.

None of those roles should silently assume that another team will close the gap. When the media plan is not final, production should at least preserve a transcodable master and explicit version history. When inventory is known, media operations should deliver the specification matrix before the picture lock. If agents or automated tools will deploy the assets, ONCE's creative operating contract for ad agents explains how to preserve approval and rollback controls.

Compare cost per verified placement family

The cheapest shoot or the smallest file count is not necessarily the lowest-cost delivery. Use a project-specific denominator instead:

Cost per verified placement family = (production + encoding/adaptation + ad-serving setup + verification/QA) ÷ placement families successfully verified

A placement family shares technical requirements and fallback logic. This is not an industry benchmark and it does not replace a media budget. It exposes deferred work. A low quote that includes one MP4 can become expensive when every new publisher triggers a search for the master, a fresh encode, a version reconciliation and another QA cycle.

When one MP4 is still a rational choice

A single-file handoff is reasonable only when all five conditions are true: the placement is known and singular; direct manual upload is accepted; no cross-system creative identity is required; no third-party verification or interaction is needed; and the brand accepts that a future inventory change may require new work.

Move to the portable package when any of these appears: multiple publishers, CTV, server-side insertion, multi-market version management or cross-channel measurement. Amazon DSP's VAST 4 support does not manufacture missing masters or identifiers. It makes compatible third-party inventory easier to address; the brand can only benefit if its delivery assets are ready before trafficking begins.

Change the brief from “how many videos?” to “which routes must work?”

Before the next production quote, ask production, media and ad operations to answer four questions together: Which inventory families are in scope? Who generates the VAST tags? Who owns creative identity and version mapping? Who tests and signs off every delivery route?

The procurement shift is precise. A production company does not need to become an ad-server developer. It does need to deliver media that can be reliably used by those systems and traced by the people operating them. For brands expanding into global programmatic video and CTV, that distinction affects launch speed, rework cost and measurement credibility.