All VAST error codes
202Trafficking errors · VAST 2.0+

VAST Error 202: Video player expecting different duration

The ad's duration violates what the placement allows — usually a creative longer than the slot's maximum.

Error 202 fires when the returned creative's duration doesn't satisfy the placement's constraints — a 60-second spot in a slot capped at 30, or an ad pod position with a strict per-ad limit.

It's most visible in CTV, where pod structures enforce duration rules strictly and reject non-compliant creatives outright.

Why error 202 happens

Creative exceeds the slot's max duration

The trafficked video is longer than the placement allows. Common when one creative is reused across placements with different caps.

Duration metadata doesn't match the file

The <Duration> element declares one length but the media file is longer. Strict players validate the declared value; some check the real file.

Pod rules in CTV

Ad pods allocate fixed time per position. A creative that fits the placement generally can still violate the specific pod slot it was assigned.

How to fix VAST error 202

  1. 1

    Check the declared duration against the placement cap

    Validate the tag and read the <Duration> element, then compare with the slot's spec. Fix whichever side is wrong.

  2. 2

    Verify the media file's real length

    Download the media file and confirm its actual duration matches the declared one — transcoding sometimes pads or trims files.

  3. 3

    Traffic duration-specific creatives

    Maintain 15s/30s cuts as separate creatives with duration targeting rather than relying on one master file.

Free VAST validator

Seeing error 202 on a live tag?

Paste the tag URL or XML — the validator resolves the full wrapper chain, validates the schema, downloads every media file, and shows exactly which stage fails.

Validate your VAST tag

VAST error 202 — frequently asked questions

Does a wrong <Duration> value matter if the file is fine?+

Yes. Players and SSP scanners use the declared duration for pod assembly and validation. A mismatch between declared and actual duration can trigger 202 or get the tag rejected upstream.

Why does the same creative play on web but fail in CTV with 202?+

CTV ad pods enforce duration budgets strictly because the break length is fixed. Web players are usually lenient about a few extra seconds.

Related error codes

Keep reading