What Is VMAP? Video Multiple Ad Playlist

VMAP (Video Multiple Ad Playlist) is an IAB Tech Lab XML standard that schedules ad breaks for a video session. It answers when breaks should occur, how long they should run, and which ad tags to call for each break. It does not carry the creatives themselves. Those still arrive through VAST responses that fill each scheduled slot.

In VOD or session-based streaming, VMAP is how an ad server hands a player or SSAI service a full break plan up front. Live FAST channels usually cue breaks differently, with SCTE-35 markers in the stream. Knowing which layer does which job keeps debugging honest when fill or timing fails.

What problem does VMAP solve?

Without a break schedule, every player or inserter has to invent timing rules: mid-roll at minute 10, pre-roll on start, and so on. That creates inconsistent load across apps and weak measurement.

VMAP centralizes the plan:

1. Break timing. Offsets or position types (pre-roll, mid-roll, post-roll) define when each break starts.
2. Break length. Each break declares how much ad time to fill.
3. Ad source pointers. Each break points at a VAST tag (or a chain) that will supply creatives when the break fires.
4. Tracking hooks. The playlist can carry break-level tracking so systems know when a planned break was attempted.

The player or SSAI engine reads the VMAP once (or refreshes it), then executes the plan as playback progresses.

Conceptually, a VMAP document is a list of ad breaks. Each break has a timing rule, an optional duration, and one or more ad sources (usually VAST URLs). Extensions can add vendor-specific rules, but the core contract stays the same: schedule first, creatives second.

VMAP vs VAST vs SCTE-35: who does what?

These three names get mixed together. They sit on different layers.

In one sentence: VMAP plans the breaks, VAST fills them, SCTE-35 cues live linear opportunities.

A VOD title might ship with a VMAP that says "pre-roll, then a mid-roll at 00:12:00 for 90 seconds." When each break arrives, the inserter calls VAST. It stitches the ads via SSAI.

A live FAST channel usually does not depend on a per-viewer VMAP for break timing. The playout schedule decides pods. SCTE-35 cue-out and cue-in markers carry those decisions into the HLS manifest. SSAI still uses VAST to fill each pod. For how pods are structured once a break exists, see what is ad podding.

When do FAST operators actually see VMAP?

Many independent FAST operators never open a VMAP file. The platform owns break policy, cue insertion, and ad calls. You still meet the concept when:

• You integrate a third-party ad server that returns VMAP for on-demand or catch-up sessions
• A buyer or ad-ops partner asks whether your stack "supports VMAP"
• You debug a hybrid product that mixes linear FAST with VOD episodes

On Vidiyo, linear monetization is schedule-driven SSAI: playout inserts markers, SSAI fills pods with VAST, beacons report delivery. You configure break policy in channel settings rather than authoring VMAP by hand. If you also ship VOD, session ad plans may still use VMAP-style scheduling on the demand side. The important product truth is the split of duties above, not a claim that every FAST view starts with a VMAP document.

If a partner questionnaire asks "Do you support VMAP?", answer with the product surface you actually run. Linear FAST with SCTE-35 cueing and VAST fill is a complete monetization path. Session VMAP support is a separate integration question for VOD or hybrid apps. Collapsing those answers into a single yes often creates false expectations in ad-ops reviews.

What breaks when the layers are confused?

Common failure modes:

• Treating VMAP as the creative. Empty breaks when the VAST tags inside the playlist fail or time out.
• Ignoring duration contracts. A VMAP break of 120 seconds filled with 45 seconds of ads leaves dead air unless the inserter backfills or shortens the window.
• Expecting VMAP to cue live linear. If your live stream has no SCTE-35 (or equivalent) markers, a VOD-style playlist cannot magically invent splice points in the HLS timeline.
• Long wrapper chains under each break. Each VAST hop adds latency. Prefetch helps when the stack supports it; see SSAI ad prefetch.

When fill looks wrong, ask which layer failed: schedule, cue, VAST decision, or stitch. That triage is faster than blaming "SSAI" as a single black box.

A short debug order that works in practice:

1. Confirm the break was planned (VMAP offset or linear schedule / SCTE-35 cue).
2. Confirm the VAST tag returned playable media within the break duration.
3. Confirm the HLS playlist shows ad segments between cue-out and cue-in.
4. Confirm beacons fired for the creatives that actually played.

Skip step 1 and you will "fix" VAST when the schedule never asked for a break. Skip step 3 and you will blame demand when the stitch never landed.

Quick answers

What is VMAP? It is an IAB XML playlist that schedules ad breaks for a video session and points each break at a VAST tag for fill.

Does VMAP replace VAST? No. VMAP schedules breaks. VAST still describes the ads that fill those breaks.

Do live FAST channels use VMAP for cueing? Usually no. Live linear breaks are typically signaled with SCTE-35 (or similar) markers from playout. VAST still fills the pod.

Do I need to write VMAP myself on Vidiyo? Not for linear FAST. You set break policy; the platform handles cues and VAST fill. VMAP matters more when you integrate session-based or VOD ad plans with an external ad server.

Official references

• IAB Tech Lab VMAP: iabtechlab.com
• Launch on Vidiyo instead of applying platform-by-platform: start creating

Cite this page

Vidiyo, "What Is VMAP? Video Multiple Ad Playlist", vidiyo.com/learn/what-is-vmap.

What's next

• What is SSAI? Server-side ad insertion
• What is a VAST tag?
• What is ad podding?
• What is SCTE-35? Ad break signaling
• Designing ad breaks for FAST channels