VAST-4.4-nonlinear-mediafiles-empty
<NonLinear> <MediaFiles> contains no renderable or interactive asset
Short answer
The <NonLinear> declares a <MediaFiles> container but it holds no <MediaFile> and no <InteractiveCreativeFile>, and the creative has no static resource either. There is nothing for the player to render in the pause, overlay, or squeezeback slot.
Why this matters in production
This rule is usually a delivery blocker. Many players, SDKs, and ad servers will discard the response or skip the affected creative once this condition is hit. The CTV Ad Portfolio standardises Pause, Screensaver, Overlay, Squeezeback and In-Scene ads, which ran for years on bespoke per-publisher integrations. These rules cover the VAST side of that contract: the NonLinear MediaFiles delivery model, the AdCOM signals round-tripped into Extensions so stitchers can validate the experience without the bid object, and the QR code block. The signaling guidance is final; the VAST 4.4 schema that accompanies it is still a working-group draft, so anything sourced only from the schema is reported as a warning or a note. Affected scope: All VAST versions.
VAST-4.4-nonlinear-mediafiles-empty and other issues instantly.Open the VAST tag validator →