VAST Tag Tester & Validator

Paste a VAST tag address or its XML. The tester follows every wrapper, checks each step against the VAST specification and plays the ad in Fluid Player, with every event it reports.

Runs in your browser · Tracking never sent: Runs in your browser: your tag isn't sent to us, only to the ad servers in it. Tracking is never sent.

Ad

Paste a VAST tag above and click Test tag.

Or try a sample:

Version
–
Ad
–
Ad server
–
Wrappers
–
Duration
–
Skip
–
Media files
–
Tracking URLs
–
Load time
–

Problems in the ad that plays, with the VAST error code a player would report.

  • Results appear here after a test.

How to test a VAST tag

  1. Paste the tag

    Copy the VAST tag address from your ad server or ad network (or the VAST XML itself) and click Test tag. VMAP playlists work too.

  2. Read the result

    Every wrapper is followed and checked, step by step. Problems come in plain words, with the VAST error code a player would report.

  3. Watch it play

    The ad plays in Fluid Player and each event it reports shows up as it happens: impression, quartiles, clicks, skip. Tracking is listed, never sent.

What the tester checks

The checks follow the IAB VAST 2.0 to 4.3 and VMAP 1.0 specifications, plus what players actually do with them.

  • The request

    Whether each ad server answers, how fast, and why it doesn’t: CORS, HTTP errors, timeouts, http:// addresses on https:// pages, web pages or JSON instead of VAST.

  • The XML

    Broken XML with its line and column, missing required elements (AdSystem, AdTitle, Impression, Duration, MediaFiles…), times and offsets in the wrong format, misspelled events.

  • Wrappers

    Every step of the chain with its ad server, chains longer than players follow, loops, followAdditionalWrappers, allowMultipleAds, and empty answers (error 303).

  • Media files

    Type, codec, size, bitrate, whether this browser plays each one, its real picture size and length, and which one Fluid Player picks.

  • Tracking and macros

    Every tracking address of the chain by event, standard and non-standard macros, ad-server macros left unfilled, error addresses without [ERRORCODE].

  • VAST 4 and more

    UniversalAdId, AdServingId, ad pods, companions, icons, Open Measurement verification, SIMID and VPAID files (listed, never run).

Fix CORS on your ad server

A web player requests the VAST with JavaScript, so the browser only hands over the answer if the ad server says the page’s site may read it. Every server of the wrapper chain must send these headers on its VAST answers.

HTTP
Access-Control-Allow-Origin: https://www.example.com
Access-Control-Allow-Credentials: true
Vary: Origin
  • Echo the page’s origin (the request’s Origin header), not *: Fluid Player requests VAST with cookies (credentials), and browsers refuse * together with credentials.
  • This tester sends no cookies, so a server answering * passes here and still fails in Fluid Player: check the header itself (curl -sI -H "Origin: https://www.example.com" <tag address>).
  • Vary: Origin stops a CDN from serving one site’s answer to another.
  • Media files don’t need CORS to play in a <video> tag, but tracking pixels and VAST answers do.

VAST tag not playing?

  • Every ad server in the chain sends Access-Control-Allow-Origin (the tester names the one that doesn’t).
  • Everything is on https://: the tag, every wrapper, the media files and the tracking.
  • There’s an H.264 MP4 media file with type="video/mp4".
  • The chain has no more wrappers than your player follows (3 in Fluid Player by default).
  • The campaign targets where you test from: an empty answer (303) usually means no campaign matched.
  • Ad-server macros (%%CACHEBUSTER%%, ${…}) were replaced before the tag reached the player.

Questions

Is my tag sent to you?

No. The tester runs in your browser: it requests the tag straight from the ad servers, as a player on your site would. Nothing goes through our servers and nothing is stored. A share link keeps the tag after a #, a part of the link that browsers never send to a server. The tester sends no cookies.

Does testing count impressions or clicks?

No. The tester never sends tracking: Fluid Player plays a copy of the ad whose tracking addresses are replaced by placeholders, so the log shows each event and its addresses without calling them. Your campaign stats stay clean. The VAST requests themselves do reach the ad servers, as any ad request would, and some count them as requests.

Why does my tag return no ad (error 303)?

The chain worked, but the last ad server had nothing to show. Usually no campaign matched: wrong country, device, time of day, a frequency cap already reached, or a floor price too high. It’s normal with third-party demand some of the time. Test again, or from a place the campaign targets. See error 303.

Why does my tag work in Google's IMA inspector but not here?

The two players differ. The most common reasons: the IMA SDK follows more wrappers than Fluid Player’s default of 3; one ad server answers Google’s domains with CORS headers but not others; the ad is VPAID, which the IMA inspector runs and this page doesn’t. The checks say which one it is.

What does the CORS error mean?

The ad server answered, but without the header that lets other sites read the answer, so the browser hides it from the player. The fix is on the ad server: send Access-Control-Allow-Origin (see Fix CORS above). A player on your own site meets the same error, so it’s worth fixing. With Fluid Player, the header must name your site’s origin and come with Access-Control-Allow-Credentials: true: Fluid Player sends cookies with VAST requests, and * doesn’t work with cookies.

Can I test VPAID or SIMID ads?

The tester reads them and checks the XML, but doesn’t run them: they’re third-party JavaScript, which this page never runs. VPAID is deprecated and many players and devices no longer play it. Offer an MP4 media file next to it, and use SIMID and Open Measurement for interactivity and measurement.

Does it test VMAP?

Yes. Paste a VMAP playlist: the tester reads every ad break, resolves each break’s VAST and plays the breaks as Fluid Player ad rolls (pre-roll, mid-rolls, post-roll). Fluid Player has no VMAP support of its own, so the code under the tester lists the breaks as Fluid Player ad rolls.

Which VAST versions does it support?

VAST 2.0, 3.0, 4.0, 4.1, 4.2 and 4.3, and VMAP 1.0. The checks follow each version’s rules: for example UniversalAdId is required from VAST 4.0, AdServingId from 4.1.

How do I play this tag on my site?

Copy the code under the tester: Fluid Player loads the tag, follows the wrappers and sends the tracking itself. See advertisements (opens in a new tab) in the Fluid Player documentation for every option: mid-rolls, overlays, skip button, ad text.

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.

  • Player Builder

    Set up Fluid Player visually, with video ads, subtitles and your colors, and copy ready-to-use code.