A NonLinear creative needs a renderable resource
InLine <NonLinear> must contain at least one StaticResource, IFrameResource, or HTMLResource
Short answer
A <NonLinear> creative is not valid on its own. It must contain a StaticResource, IFrameResource, or HTMLResource so the player has an actual overlay asset to render.
Like companions, `<NonLinear>` creatives inside an `<InLine>` must include at least one renderable resource element.
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. Required-field failures usually stop validation early because the platform cannot determine the basic shape of the ad, the creative metadata, or the mandatory tracking payload. Affected scope: VAST 2.0 and later (all versions).
How to fix
Add <StaticResource>, <IFrameResource>, or <HTMLResource> inside each <NonLinear> element.
Invalid
<NonLinear width="480" height="70">
<!-- no StaticResource, IFrameResource, or HTMLResource -->
</NonLinear>Valid
<NonLinear width="480" height="70">
<StaticResource creativeType="image/png">
<![CDATA[https://cdn.example.com/overlay.png]]>
</StaticResource>
</NonLinear>VAST-2.0-nonlinear-resource and other issues instantly.Validate a tag →