VAST Error Codes
When a video ad fails, the player calls the tag's error address with a three-digit code. Here is what each code means, why it happens and how to fix it.
How VAST error codes work
A VAST tag can hold one or more <Error> addresses. When something goes wrong, the player replaces the [ERRORCODE] macro in them with a code and calls them, so the ad server learns what happened:
<Error><![CDATA[https://ads.example.com/error?code=[ERRORCODE]]]></Error>The first digit tells the family: 1xx the XML, 2xx the ad doesn’t fit the player, 3xx wrappers and requests, 4xx the video ad, 5xx overlays, 6xx companions, 9xx everything else. Not every player uses every code: many report only the common ones, and some send 900 for anything.
1xx: the VAST XML itself
100 XML parsing error
VAST 2.0+
The player received something it can’t read as XML: a broken tag, an HTML page, JSON, or an empty answer.
Common causes
- The ad server returned an error page (HTML) or a login page instead of VAST.
- Characters such as
&in URLs outside a<![CDATA[ ]]>block. - The answer was cut off (timeout on the server side) or starts with spaces or a byte-order mark before
<?xml.
How to fix it
- Open the tag address in a browser and check the answer starts with
<?xmlor<VAST. - Wrap every URL in
<![CDATA[ ]]>. - Run it through the VAST Tag Tester: it shows the line and column of the first XML error.
101 VAST schema validation error
VAST 2.0+
The XML is readable but doesn’t follow the VAST structure: a required element is missing or in the wrong place.
Common causes
- An
<InLine>ad without<AdSystem>,<AdTitle>,<Impression>or<Creatives>. - A
<Linear>without<Duration>or<MediaFiles>. - Elements from another format, or misspelled element names (VAST is case-sensitive).
How to fix it
- Compare the tag with the IAB samples for its version and add the missing elements.
- Check the spelling and case of every element and attribute.
102 VAST version of response not supported
VAST 2.0+
The version attribute of <VAST> is one the player doesn’t handle.
Common causes
- A VAST 4.x answer sent to an old player that only reads VAST 2 or 3.
- A missing or misspelled
versionattribute.
How to fix it
- Ask the ad server for a version the player supports (many have a setting per tag).
- Make sure
<VAST version="…">is present.
2xx: the ad doesn't fit the player
200 Trafficking error: the player can't show this type of ad
VAST 2.0+
The ad is valid, but of a kind the player wasn’t set up for, such as an overlay where a video ad was expected.
Common causes
- The campaign was set up for the wrong placement (overlay versus video).
- A VPAID or interactive ad sent to a player that doesn’t run them.
How to fix it
- Check the creative type matches the placement in the ad server.
201 Player expecting different linearity
VAST 2.0+
The player asked for a video ad (linear) and got an overlay (non-linear), or the reverse.
Common causes
- A non-linear ad sent to a pre-roll slot, or a video ad sent to an overlay slot.
How to fix it
- Match the creative to the slot:
<Linear>for pre-, mid- and post-rolls,<NonLinearAds>for overlays.
202 Player expecting different duration
VAST 2.0+
The ad is longer (or shorter) than the slot allows.
Common causes
- A 30-second ad sent to a slot limited to 15 seconds.
- A
<Duration>that doesn’t match the real length of the video file.
How to fix it
- Set the duration limits in the ad server, and make
<Duration>match the file.
203 Player expecting different size
VAST 2.0+
The ad’s size doesn’t fit the player, usually an overlay wider than the video.
Common causes
- A 728×90 overlay in a player narrower than 728 pixels.
How to fix it
- Offer several sizes, or use
scalableandmaintainAspectRatio.
204 Ad category was required but not provided
VAST 4.1+
The publisher only accepts ads that declare a <Category>, and this one doesn’t.
Common causes
- Brand-safety rules on the publisher side.
How to fix it
- Add
<Category authority="…">to the inline ad.
205 Ad category blocked by a wrapper
VAST 4.1+
A wrapper listed blocked categories (<BlockedAdCategories>) and the final ad belongs to one of them.
Common causes
- An advertiser category the publisher or an exchange doesn’t allow.
How to fix it
- Check the categories on both sides; nothing to fix in the player.
206 Ad break shortened, ad not served
VAST 4.1+
The ad break became shorter than planned (for example in live TV), so this ad no longer fits.
Common causes
- Live streams where the break is cut short.
How to fix it
- Normal in live streaming; send shorter ads if it happens often.
3xx: wrappers and the ad request
300 General wrapper error
VAST 2.0+
Something went wrong while following a wrapper (a VAST that points to another VAST), with no more specific code.
Common causes
- A wrapper without
<VASTAdTagURI>, or with an address that isn’t a URL. - A next step that answers with something other than VAST.
How to fix it
- Test the tag in the VAST Tag Tester: it follows every step and shows which one fails.
301 Wrapper request failed or timed out
VAST 2.0+
The player couldn’t get the next VAST in the chain: it timed out, the address is wrong, or the browser blocked the answer.
Common causes
- The server didn’t answer in time (players often wait 5 to 8 seconds; Fluid Player waits 5 by default).
- The next server doesn’t send CORS headers, so the browser hides its answer from the player.
- An
http://address on anhttps://page (blocked as mixed content). - A wrong or expired address in
<VASTAdTagURI>.
How to fix it
- Open the address in a browser to see if it answers at all.
- Ask the ad server to send
Access-Control-Allow-Originwith your site’s origin, andAccess-Control-Allow-Credentials: truefor players that send cookies (Fluid Player does). - Use
https://everywhere.
Fluid Player: Fluid Player stops after vastOptions.vastTimeout (5,000 ms by default) per request.
302 Wrapper limit reached
VAST 2.0+
The chain of wrappers is longer than the player accepts.
Common causes
- Too many resellers between the publisher and the advertiser.
- A loop: a wrapper that ends up pointing back to itself.
How to fix it
- Shorten the chain or raise the player’s limit; IAB recommends players accept at least 5 steps.
Fluid Player: Fluid Player follows 3 wrappers by default: raise it with vastOptions.maxAllowedVastTagRedirects.
303 No ad after one or more wrappers
VAST 2.0+
The chain worked, but the last ad server answered with an empty VAST: it had no ad to show.
Common causes
- No fill: no campaign matched this request (country, device, time of day, frequency cap, floor price).
- A test from a place the campaign doesn’t target, for example an office outside the target country.
- Missing macros (page URL, consent string) that the demand side needs to bid.
How to fix it
- Normal some of the time with third-party demand; check the fill rate rather than one request.
- Retry, or test with targeting that matches the campaign.
304 Ad didn't display in time
VAST 4.1+
An inline ad was received but couldn’t start playing within the time limit.
Common causes
- A very large or slow media file, or a slow interactive unit.
How to fix it
- Serve smaller, progressive MP4 files from a fast CDN.
4xx: the video ad (linear)
400 General linear (video ad) error
VAST 2.0+
The player couldn’t show the video ad, without a more specific reason.
Common causes
- The video file failed to decode or play.
How to fix it
- Check the media files in the VAST Tag Tester: type, codec, size and whether this browser plays them.
401 Media file not found
VAST 2.0+
The video file’s address answered with an error (404 or similar).
Common causes
- A deleted or moved file, or an expired signed URL.
How to fix it
- Open the
<MediaFile>address in a browser and update it.
402 Media file timed out
VAST 2.0+
The video file took too long to start loading.
Common causes
- A slow server, a very large file, or a network problem.
How to fix it
- Host the files on a CDN and offer smaller versions (for example 720p under 2 Mbps).
403 No supported media file
VAST 2.0+
None of the <MediaFile> entries is a format this player and browser can play.
Common causes
- Only formats the browser can’t play, such as WebM in older Safari or HEVC in browsers without it.
- Only VPAID (JavaScript) files for a player that doesn’t run VPAID.
- A missing or wrong
typeattribute (it must be likevideo/mp4).
How to fix it
- Always include an H.264/AAC MP4 with
type="video/mp4". - Offer a plain video file next to any VPAID one.
Fluid Player: Fluid Player reports 403 when no media file has a type the browser can play.
405 Problem displaying the media file
VAST 2.0+
The file was found and in a supported format, but couldn’t be played (corrupt, wrong codec inside, unsupported profile).
Common causes
- A file whose content doesn’t match its declared type or codec.
- A high profile or 10-bit video the device can’t decode.
How to fix it
- Re-encode to H.264 High or Main profile, 8-bit, AAC audio.
406 Mezzanine required but not provided
VAST 4.1+
The player (usually server-side ad insertion for TV) needs a high-quality <Mezzanine> file to transcode, and the ad has none.
Common causes
- A CTV or SSAI placement with a web-only creative.
How to fix it
- Add a
<Mezzanine>file to the creative.
407 Mezzanine being downloaded
VAST 4.1+
The mezzanine file is being transcoded for the first time, so the ad isn’t ready yet.
Common causes
- The first time a new creative is requested by a server-side ad insertion system.
How to fix it
- Nothing to do: it plays on later requests.
408 Conditional ad rejected
VAST 4.1+
The player rejected an ad marked as conditional (conditionalAd="true"). Deprecated in VAST 4.2.
Common causes
- A conditional (often VPAID) ad in a player that doesn’t accept them.
How to fix it
- Remove the conditional ad or the attribute.
409 Interactive unit not executed
VAST 4.1+
The <InteractiveCreativeFile> (SIMID or VPAID) wasn’t run, while the video itself may have played.
Common causes
- A player or device that doesn’t run interactive units.
How to fix it
- Make the video work without the interactive part, or target players that support SIMID.
410 Verification unit not executed
VAST 4.1+
A measurement script from <AdVerifications> (Open Measurement) wasn’t run.
Common causes
- A player without the Open Measurement SDK, or a vendor the publisher doesn’t allow.
How to fix it
- Expected in players without Open Measurement; check with the verification vendor.
411 Mezzanine doesn't meet the specification
VAST 4.1+
The mezzanine file exists but isn’t good enough (size, bitrate, format) for transcoding.
Common causes
- A low-quality file declared as mezzanine.
How to fix it
- Provide a high-quality master file as described by the platform.
5xx: overlays (non-linear ads)
500 General overlay (non-linear) error
VAST 2.0+
The player couldn’t show an overlay ad.
Common causes
- An overlay without a usable resource, or one that failed to load.
How to fix it
- Check the
<NonLinear>resource address and type.
Fluid Player: Fluid Player reports 500 when an overlay’s image fails to load.
501 Overlay doesn't fit the player
VAST 2.0+
The overlay is bigger than the space available in the player.
Common causes
- A wide banner in a small or mobile player.
How to fix it
- Provide smaller sizes, or set
scalable="true".
502 Overlay resource not loaded
VAST 2.0+
The overlay’s image or page couldn’t be downloaded.
Common causes
- A broken image address, or an
http://image on anhttps://page.
How to fix it
- Open the resource address in a browser; use
https://.
503 No supported overlay resource
VAST 2.0+
None of the overlay’s resources is a type the player can show.
Common causes
- Only
<HTMLResource>or<IFrameResource>for a player that only shows images.
How to fix it
- Add a
<StaticResource>image (JPEG, PNG or GIF).
Fluid Player: Fluid Player reports 503 when an overlay’s image type isn’t one it shows.
6xx: companion ads
600 General companion ad error
VAST 2.0+
A companion (a banner shown next to the player) couldn’t be shown.
Common causes
- The page has no companion slot, or the companion failed to load.
How to fix it
- Check the page has a slot of the companion’s size.
601 Companion doesn't fit its slot
VAST 2.0+
The companion is bigger than the space the page offers for it.
Common causes
- A 300×250 companion for a 300×60 slot.
How to fix it
- Provide a companion for each slot size.
602 Required companion not shown
VAST 2.0+
The ad says its companions are required (required="all" or "any") and the player couldn’t show them, so it skipped the ad.
Common causes
- No companion slot on the page.
How to fix it
- Make companions optional, or add the slot to the page.
603 Companion resource not loaded
VAST 2.0+
The companion’s image or page couldn’t be downloaded.
Common causes
- A broken or
http://resource address.
How to fix it
- Open the resource in a browser; use
https://.
604 No supported companion resource
VAST 2.0+
None of the companion’s resources is a type the player can show.
Common causes
- Only HTML or iframe resources for a player that shows only images.
How to fix it
- Add a
<StaticResource>image.
9xx: undefined, VPAID and interactive
900 Undefined error
VAST 2.0+
Something went wrong that doesn’t match any other code.
Common causes
- Often a playback failure the player couldn’t classify: the video stopped, or an unexpected answer.
How to fix it
- Test the tag in the VAST Tag Tester and look at the first error in its checks and event log.
Fluid Player: Fluid Player reports 900 when the tag holds neither a video ad nor an overlay it can play.
901 General VPAID error
VAST 2.0+
A VPAID ad (JavaScript) failed: it didn’t load, didn’t answer in time, or reported an error itself.
Common causes
- VPAID scripts blocked by the page’s security policy or an ad blocker.
- A VPAID unit that doesn’t start within the player’s time limit.
- VPAID is deprecated: many players and devices no longer run it.
How to fix it
- Offer a plain video file next to the VPAID one, or move to SIMID and Open Measurement.
Fluid Player: Fluid Player runs VPAID only with vastOptions.allowVPAID: true and reports 901 when it fails.
902 General interactive creative error
VAST 4.1+
The <InteractiveCreativeFile> (usually SIMID) failed.
Common causes
- A script error in the interactive unit, or a player that doesn’t support it.
How to fix it
- Test the interactive unit separately; the video should still play without it.
Questions
Which VAST errors are the most common?
My tag has no <Error> element. Is that a problem?
<Error> with [ERRORCODE] in its address so your ad server can count failures by reason.What are codes like 1009 or 1012?
Did the codes change in VAST 4?
More free tools
SRT to VTT Converter
Convert SRT subtitles to WebVTT for HTML5 video. Fixes broken accents, checks for errors and previews the result in Fluid Player.
VTT to SRT Converter
Convert WebVTT subtitles to SRT for YouTube, video editors and media players. Keeps positions, checks for errors and previews the result.
HLS & DASH Stream Tester
Play an .m3u8 or .mpd stream, check its quality levels and codecs, and find out why it doesn't play, CORS errors included.
VAST Tag Tester & Validator
Paste a VAST tag or its XML: follow every wrapper, find what's wrong in plain words and play the ad in Fluid Player.
Player Builder
Set up Fluid Player visually, with video ads, subtitles and your colors, and copy ready-to-use code.