How to deliver video on demand through a CDN

Cache HLS and DASH segments and progressive files at Cloud CDN, use Origin Shield, and keep packaging at your encoder.

VOD is a cache problem dressed as a media problem. Segments and files are large, popular and identical. The encoder should package once. Cloud CDN should repeat the result on 200+ Tbps.

You deliver, you do not have to transcode

Cloud CDN does not replace your packager. It caches HLS/DASH segments and progressive files, including 4K-ready playback, and shields origin storage from concurrent viewers.

Playlists versus segments

Media playlists change more often than segments. Give segments long TTLs. Keep playlist TTLs short enough for the product, and purge when a title is replaced.

Protect premium titles

Token authentication can gate URLs so a cached object is still not anonymously shareable. HTTPS is not a licence check by itself.

The same CDN as the website

Application assets and VOD can share the network. They usually should not share cache keys or bypass rules. Use path policy.

Continue on Aptranet

Frequently Asked Questions

Do you transcode?

No. Packaging stays at origin or your encoder. Cloud CDN caches and delivers the output.

What about live?

Live uses short TTLs and the same shield idea. See the live streaming post.

Can I use progressive MP4?

Yes. Large-file optimisation applies. Range requests are part of that path.