vastadtechtroubleshootingdeveloper

VAST Tag Not Playing? How to Debug It Step by Step

July 2, 2026 · 5 min read

When a VAST tag doesn't play, the problem lives in one of four places: the tag URL, the wrapper chain, the XML, or the media files. Work through them in that order and you will find it. A validator does the first three checks for you in one run.

Debug It In One Pass

Start here

Use VAST Ad Validator

Paste the tag URL or XML. It follows every redirect, validates the XML, downloads each media file, and flags CORS, codec, and MIME problems.

Debug your tag

Quick steps

How To Debug A Silent VAST Tag

Request the tag URL directly

If it returns an error status or an empty document, the problem is upstream — see the wrapper trace.

Check the wrapper chain

Slow or dead hops cause timeouts (error 301) before the player ever sees an ad. The validator shows per-hop latency.

Validate the XML

Schema errors, a missing Impression, or a bad Duration make players discard the response quietly.

Check the media files

The most common silent failure: the XML is fine but every MediaFile is unplayable — missing CORS headers, unsupported codec, or a dead URL.

The usual suspects

Missing CORS headers on the media CDN. Browsers block the file and the player shows nothing. The validator checks CORS on every file.
Codec the player can't decode — HEVC or VP9 files fail on older devices while the declared MIME type says video/mp4. The validator reports the real codec, not the declared one.
HTTP resources on an HTTPS page — mixed content is blocked silently.
Unreplaced macros in the tag URL, so the ad server rejects the request.
A wrapper chain deeper than 5 hops — many players give up (error 302).

When the tag validates but still won't play on your site

Then the tag is healthy and the problem is your player integration: check the player console for errors, confirm the ad container is visible and sized, and confirm autoplay policy (muted autoplay only in most browsers).