vastlint

VPAID-type-invalid

VPAID <MediaFile> type must be application/javascript or application/x-javascript

ErrorAttributesIAB VPAID 2.0 §3.1

A element with has an unexpected attribute. VPAID 2.0 requires the to be (or the older variant ). Values like , , or an empty string are not valid for VPAID and will cause the ad unit to fail to initialise in all players.

Why this matters in production

Treat this as a hard compatibility failure. A VPAID rule that rises to error level is usually the difference between a runnable creative and a blank slot. Attribute rules are where VPAID integrations break most often. The unit may be present, but a wrong type, casing, or dimension value prevents correct initialization.

How to fix

Set type="application/javascript" on VPAID <MediaFile> elements. Note that migrating to SIMID requires changing this to type="text/html" on <InteractiveCreativeFile>.

Invalid

<MediaFile delivery="progressive" type="text/javascript"
           apiFramework="VPAID" width="1280" height="720">
  <![CDATA[https://example.com/vpaid.js]]>
</MediaFile>

Valid

<MediaFile delivery="progressive" type="application/javascript"
           apiFramework="VPAID" width="1280" height="720">
  <![CDATA[https://example.com/vpaid.js]]>
</MediaFile>
Check your VAST tag for VPAID-type-invalid and other issues instantly.Validate a tag →

Other Attributes rules

VPAID-apiframework-casingapiFramework value is not the canonical "VPAID" (wrong case)VPAID-width-height-missingVPAID <MediaFile> missing width or height attribute
← All VPAID rulesSIMID rules (migration target) →