SVOD vs AVOD vs TVOD (and W2E): Monetization Models

SVOD (subscription video on demand) charges a recurring fee for a whole library. AVOD (ad-supported video on demand) is free to watch and paid for by ads. TVOD (transactional video on demand) charges per title, as a rental or a purchase. W2E, watch-to-earn, reverses the flow and rewards the viewer.

Those labels describe pricing, but each model also needs different machinery behind your player. TVOD needs a per-title ledger with timers, SVOD needs one live subscription check, and AVOD needs an ad-insertion method you pick early, because the two options behave very differently.

TL;DR:

• TVOD and SVOD both check whether a viewer may watch before you serve the video. TVOD checks per title, often against a rental clock, while SVOD checks one subscription status for the whole library.
• AVOD splits into server-side ad insertion (SSAI), which stitches ads into the stream, and client-side ad insertion (CSAI), where the player fetches ads itself.
• To compare CSAI against SSAI, start with who calls the ad server. SSAI resists ad blockers and plays without a stall, while CSAI keeps richer measurement and cacheable manifests. A hybrid, server-guided ad insertion (SGAI), aims to keep both.
• W2E pays the viewer instead of charging them, and its payout mechanics are not published.
• AIOZ Stream's docs list five monetization and reward options: SVOD, TVOD, AVOD, Tips and W2E.

Updated Oct 29, 2026: a new CSAI vs SSAI comparison covering ad blockers, playback, measurement, caching and fraud, plus SGAI and HLS interstitials, and a labelled diagram of the three insertion methods.

Updated Oct 19, 2026: new answer-first opening, a comparison table, question sections on TVOD and AVOD, the full model list in AIOZ Stream's docs (SVOD, TVOD, AVOD, Tips, W2E) and an analytics example.

SVOD vs AVOD vs TVOD at a glance

The table sets the four models side by side. The examples for the first three come from AIOZ Stream's own video on demand concepts page. All four sit on top of the same delivery pipeline, which our guide to how video on demand works walks through from upload to playback.

What does TVOD stand for?

TVOD stands for transactional video on demand. AIOZ Stream's docs define it as a model where users pay for individual pieces of content. That can be a rental available for a limited time or a purchase with permanent access. It suits viewers who want one film without committing to a subscription.

The engineering work sits in entitlement checking. On every playback request, you have to confirm that this viewer paid for this title and, for a rental, that the paid window is still open. Rentals usually run two clocks. Apple's TV app gives you 30 days to start a rental and then 48 hours to finish it once you press play, according to Apple Support. Your check has to evaluate both timers, and a rental can expire on the first one before the second ever starts.

SVOD: one check for the whole library

Subscription video on demand charges a recurring fee for unlimited access to a library, per the same docs page. Instead of a ledger per title, you check one entitlement: is the subscription active right now? A lapsed card, a canceled plan or a downgraded tier should cut access promptly, so SVOD services typically check status against a live source of truth near each playback request.

That single check makes SVOD easier to scale across a large catalog. It also helps caching: because the access decision does not depend on which title you request, the same segments can be cached and served to every subscriber. TVOD makes the decision per title and per viewer every time, even when the video bytes themselves are cacheable.

What does AVOD mean?

AVOD means ad-supported video on demand: viewers watch for free, and advertisements play during playback. YouTube, Peacock and Tubi are the docs' examples. The decision you face is how ads get into the stream, and there are two ways to do it.

Both start from markers in the video: per OTTVerse, the stream carries SCTE-35 markers that tell downstream systems where ad breaks go. With server-side ad insertion (SSAI), a server places the ad into the stream before it reaches the player, so the result looks like one continuous video. With client-side ad insertion (CSAI), the player does the work. When it reaches a cue point, it calls the ad server, pauses the content, plays the ad and then resumes.

For SSAI, your ads also have to match the content's renditions to splice in cleanly, which the bitrate ladder guide covers. The splice itself happens in the playlist structure described in the M3U8 article. The next section compares the two methods point by point.

CSAI vs SSAI compared: blockers, playback, measurement and caching

To compare CSAI against SSAI, start with one question: who calls the ad server? In CSAI your player makes that call. In SSAI a server component called a stitcher, or manifest manipulator, makes it for each viewer and rewrites the playlist so the ad looks like content. Almost every other difference follows from that choice.

Both methods use the same ad format. The ad server describes each ad in VAST (Video Ad Serving Template), the IAB Tech Lab's XML standard that lists the media file and the tracking URLs to call. The table below compares what changes for you, based on Fora Soft's SSAI vs CSAI guide unless another source is named.

Ad-blocking resistance

This is where SSAI wins most clearly. A CSAI player sends an explicit request to an ad domain, and a blocker only has to drop that request. With SSAI the ad segments come from the same host as the content, so a blocker cannot remove them without breaking playback. If a large share of your audience watches on desktop web, that gap shows up directly in filled impressions.

Measurement: who fires the beacon

In CSAI the device reports "ad started" and "ad completed" itself, so the ad server sees what the viewer saw. In SSAI the stitcher is the natural place to fire those beacons, but it only knows it sent bytes. It cannot tell whether the screen was on.

The industry fixed this in VAST 4.1 (November 2018). An ad-stitching service must forward the viewer's device IP and user agent in X-Device-IP and X-Device-User-Agent headers. Fora Soft adds that pairing SSAI with the Open Measurement SDK (OMID) lets a script in the player report real viewability.

Skip those steps and your numbers drift. Fora Soft cites a Pixalate benchmark from Q2 2024 that measured 110% higher invalid-traffic rates on SSAI connected-TV traffic than on non-SSAI traffic.

Caching and delivery cost

Targeting changes your delivery bill. To pick ads per viewer and cap repeats, the stitcher has to build a personalized playlist for each session, which is what dynamic ad insertion (DAI) means. A shared playlist can sit in a CDN edge cache for every viewer, but a per-session one cannot. If you are new to how that cache works, our guide to CDN edge caching for video covers hits, misses and origin load.

SGAI and HLS interstitials: the hybrid

Server-guided ad insertion (SGAI) splits the work. The server marks the break in a shared playlist, and the player fetches and plays the ad as a native break. On Apple devices this is HLS interstitials. Per Apple's HLS Interstitials guide, the playlist carries an EXT-X-DATERANGE tag with the class com.apple.hls.interstitial. That tag holds either an X-ASSET-URI or an X-ASSET-LIST, never both. A mid-roll looks like this (the ID, times and URL are examples):

#EXT-X-DATERANGE:ID="midroll-1",CLASS="com.apple.hls.interstitial",START-DATE="2026-07-01T12:00:15Z",DURATION=10.0,X-ASSET-URI="https://example.com/ads/ad-1.m3u8"

Because every viewer gets the same playlist, it stays cacheable, and the client-side fetch keeps measurement simple. Fora Soft reports that SGAI was standardized for DASH in ISO/IEC 23009-1:2026, the sixth edition of MPEG-DASH, published in July 2026.

Which should you pick?

Name the screen and the goal first, and the method follows. For connected TV, live events and FAST channels, SSAI is the safer default: breaks play without stalls and blockers cannot strip them. For web and mobile campaigns that need clicks or interactive ads, CSAI still fits. Many large services run both, and SGAI is the direction both are moving toward.

SVOD vs AVOD: what is the difference?

The difference is who pays and what you have to measure. With SVOD, the viewer pays and your revenue depends on keeping subscriptions active, while with AVOD, advertisers pay and revenue follows how many ads play and how much viewers watch. That puts playback analytics at the center of AVOD revenue.

Many services run both. AIOZ Stream's docs give Hulu as an example of a hybrid model, with ad-supported and ad-free subscription tiers. A title can also start as a TVOD rental and move into an SVOD library later. Combining models does not remove any of the machinery, so a hybrid tier still needs the SVOD status check plus an ad-insertion method.

Where W2E fits

Watch-to-earn is the only model of the four that pays the viewer instead of charging them. The W2E article covers what is documented. In short, W2E is a named AIOZ Stream option, and no payout rate, funding source or eligibility rule is published for it.

How AIOZ Stream handles it

AIOZ Stream's adaptive streaming page says "monetization and rewards (SVOD/TVOD/AVOD/Tips/W2E) are available without compromising mainstream usability." The same page says player and edge telemetry, plus on-chain proofs, are used to validate delivery and support transparent payouts. The QoE metrics page adds one ad detail: "Feed QoE and engagement into the ad-selection layer so revenue and experience grow together."

What the docs don't cover yet: AIOZ Stream documents no ad insertion of either kind (SSAI or CSAI), no rental or entitlement API for TVOD, how Tips work, or W2E payout terms. We checked all 47 pages in the docs sitemap on Oct 29, 2026.

The part you can use today is measurement. Whichever model you run, watch time and views drive the revenue math, and the Analytics API returns both. This request from the analytics reference sums watch time, in seconds, over a time range:

POST https://api.aiozstream.network/api/analytics/metrics/data/watch_time/sum

{ "from" : 1726001314 , "to" : 1726201314 }

You can narrow it with filter_by fields such as media_ids, countries and device_types. Next step: read the AIOZ Stream analytics docs.

Frequently Asked Questions

What is the difference between SVOD, AVOD and TVOD?
SVOD charges a recurring subscription for a whole library. AVOD is free to watch and paid for by ads. TVOD charges per title, as a rental or a purchase.

What does AVOD mean?
It stands for ad-supported video on demand: viewers watch for free, and ads play during playback. YouTube, Peacock and Tubi are common examples.

What does TVOD stand for?
Transactional video on demand, where viewers pay for one title at a time, either to rent it for a limited period or to buy it.

What is the core technical difference between TVOD and SVOD?
TVOD tracks entitlement per title, often with a rental clock that starts on first play. SVOD checks one subscription status for the whole library.

What is the difference between SSAI and CSAI?
SSAI places ads into the stream on the server, so playback looks continuous and there is no separate ad call to block. With CSAI, the player calls an ad server at each cue point, which allows richer ads but is easier to block.

How do you compare CSAI against SSAI on ad-blocking resistance?
SSAI resists ad blockers far better. Its ad segments come from the same host as the content, while a CSAI player makes a separate ad request that a blocker can drop.

Can SSAI ads be measured accurately?
Yes, if the stitcher forwards the device IP and user agent as VAST 4.1 requires and the player runs Open Measurement verification. Beacons fired blindly from the server tend to over-count.

What is SGAI?
Server-guided ad insertion: the server marks the break in a shared playlist and the player fetches the ad itself. Apple devices support it as HLS interstitials.

Which monetization models does AIOZ Stream list?
Five: SVOD, TVOD, AVOD, Tips and W2E, on its adaptive streaming concepts page.

Can a platform use more than one model at once?
Yes, hybrid tiers with and without ads, and TVOD windows before an SVOD release, are both common.

Related Reading

• What Is Video on Demand (VOD): the delivery mechanics under every model compared here
• Watch-to-Earn (W2E) on AIOZ Stream: What's Documented: the fourth model in depth
• How Video Segmentation and M3U8 Manifests Work: the playlist structure SSAI splices ads into
• How to Build a Video Bitrate Ladder: A Practical Guide: what an inserted ad has to match to splice in cleanly
• What Is a CDN Edge Node?: why per-viewer SSAI playlists cache worse than shared ones
• AIOZ Stream Pricing for Storage, Delivery and Transcoding: the cost side of whichever model you pick

References

• AIOZ Stream docs: Video on demand (VOD): TVOD, SVOD, AVOD and hybrid definitions and examples
• AIOZ Stream docs: Adaptive streaming: the SVOD/TVOD/AVOD/Tips/W2E list
• AIOZ Stream docs: QoE metrics: the ad-selection layer quote
• OTTVerse: CSAI vs SSAI: SCTE-35 markers, insertion workflows and ad-blocker behavior
• Fora Soft: SSAI vs CSAI: stitching, measurement, per-session caching, the Pixalate invalid-traffic figure and SGAI
• IAB Tech Lab: VAST 4.1: the device headers an ad-stitching service must send
• Apple: Getting Started with HLS Interstitials: the interstitial date-range class and asset attributes
• Apple Support: Rent movies from the Apple TV app: the 30-day and 48-hour rental windows