3 VOD library storage is the long-lived home for everything a broadcaster or streaming service offers on demand: films, series, catch-up programs, archive titles and the many versions of each that different devices and markets need. Unlike live channels, the library grows steadily for years. Every new title adds a high-quality master and often a stack of streaming renditions, and old titles are rarely removed. Where that library lives determines streaming costs, how quickly new services can be launched and how much control the broadcaster keeps over its own content. This article covers what a VOD library contains, the storage options broadcasters choose between and the factors that decide the right home: cost, performance, rights, residency and resilience. For the delivery side, see our hub on video origin server storage. What a VOD library contains A typical library includes several layers: Mezzanine files: high-quality masters, often in professional codecs, used to create every delivery version. Streaming renditions: encoded versions at multiple bitrates and resolutions, packaged for HLS, DASH or other formats. Audio tracks, subtitles and captions in multiple languages. Artwork and metadata used by catalogs and recommendation engines. Market-specific versions, such as edits for different regions or compliance requirements. Mezzanine files are large but accessed infrequently; renditions are smaller per file but numerous and read whenever CDN caches miss. Storing both on the same tier is rarely optimal. The storage options Public cloud object storage Cloud storage makes it easy to integrate with cloud transcoding and delivery services and avoids running infrastructure. Costs to weigh include ongoing storage charges as the library grows, request charges for segment reads and data transfer charges when content leaves the cloud to CDNs or other facilities. For large libraries with heavy origin traffic, those charges can be significant. Moving a multi-petabyte library out later also takes time and money. On-premises object storage Many broadcasters keep their library on object storage in their own data centers or colocation facilities. Costs are predictable, there are no per-request or egress charges between the library and on-premises origins or CDN interconnects, and content stays under the broadcaster’s control. It requires capacity planning and operations. Hybrid A common pattern keeps the master library on premises and uses cloud services for burst transcoding, specific markets or disaster recovery copies. Another keeps renditions in the cloud close to a cloud-based delivery chain while masters stay on premises. Open interfaces such as S3 make hybrid designs workable. Tape and deep archive Older or rarely used masters may live on tape or deep archive tiers, with the understanding that restoring them takes hours or days. This works for preservation but not for titles that need to be repackaged quickly. Factors that decide where the library lives Origin traffic and delivery architecture If origins and CDNs pull frequently from the library, keeping it close to the delivery chain reduces latency and transfer costs. On-premises libraries feeding on-premises origins avoid egress fees; cloud libraries suit cloud-based delivery. Library size and growth Small libraries can live almost anywhere. Libraries of several petabytes growing every year make cost per terabyte and transfer charges decisive. Model costs over five years, not one. Rights and territorial restrictions Content licenses often restrict where content may be stored and delivered. A broadcaster may hold rights only for certain territories and must ensure the library and its copies respect those limits. Data residency and sovereignty Public broadcasters in Europe and elsewhere often prefer, or are required, to keep content and associated data within national borders. National cloud or on-premises storage in-country simplifies compliance. In markets such as Japan, France and Germany, local infrastructure is commonly favored for both regulatory and strategic reasons. Repackaging and new services New devices, formats and partners mean the library is repeatedly re-encoded and repackaged. Fast access to mezzanine files, whether on premises or in the cloud, keeps launches quick. Resilience The library is a core business asset. It should survive hardware failure and site loss, which means erasure coding within a site and copies at a second location, possibly in a different form such as tape or cloud. Tiering the library A practical tiering model: Performance tier for live, new releases and the most popular renditions, often fronted by origin caches. Capacity tier on object storage for the full library of renditions and recent mezzanine files. Archive tier for older masters and preservation copies. Movement between tiers can be automated based on age or access, though many broadcasters keep all renditions on one scalable object tier and rely on CDNs for hot content. Mezzanine vs renditions: store once or store all? Storing every rendition and package for every title multiplies capacity. Just-in-time packaging lets broadcasters store fewer renditions and package on request, trading storage for compute. Some go further and transcode on demand for rarely watched titles. The right balance depends on viewing patterns: popular titles benefit from pre-built renditions; the long tail may be cheaper to generate when needed. Cost modeling Compare options on cost per terabyte per year, including: Storage capacity and protection overhead. Request and data transfer charges for expected origin traffic. Hardware, facilities and operations for on-premises options. Copies for resilience. Migration and exit costs. A useful exercise is to calculate the total for the current library and for the library in five years under each option. Metadata and rights data belong with the library A library is only usable if the system knows what each file is. Titles, episodes, versions, languages, rights windows, territories and technical properties all live in metadata, usually held by a media asset manager or content management system. When designing library storage, decide where metadata is mastered, how it links to files and how it is backed up. Losing metadata can make a perfectly intact library almost impossible to use. Object storage can hold metadata alongside objects as tags or attributes, which helps with search and lifecycle rules, but the authoritative catalog typically remains in the asset management system. Supporting partners and syndication Libraries increasingly feed third parties: other platforms, international distributors, airlines and hospitality providers. Each delivery needs specific versions and packages. Keeping masters on fast, scalable storage with S3 access makes it easier to automate partner deliveries without manual file transfers. Track which partner received which version, and when, so rights and reporting stay accurate. Migrating an existing library Libraries often need to move, for example from aging NAS to object storage, or from cloud back on premises. Plan for transfer time at petabyte scale, verification of every file, metadata and rights information, and a period of dual operation while origins switch. Moving masters and renditions separately can simplify the process. Security for the library Unreleased content and high-value titles are targets for piracy and ransomware. Protect the library with restricted access credentials for each workflow, encryption, audit logging and immutable copies of masters so they cannot be encrypted or deleted by an attacker. Checklist: VOD library storage Inventory mezzanine files, renditions, subtitles, artwork and metadata. Measure library size, growth and origin traffic. Map rights and territorial restrictions. Confirm data residency requirements per market. Compare cloud, on-premises and hybrid on five-year cost, including transfer charges. Decide on pre-packaged, just-in-time or hybrid packaging. Tier content by access and value. Protect the library across sites. Plan migration paths and exit costs. Putting it together A VOD library should live where it can feed delivery efficiently, grow affordably and stay within rights and residency rules. For many broadcasters with large libraries and on-premises or interconnected delivery, scalable object storage in their own facilities offers predictable cost and control, with cloud used for burst work or specific markets. Smaller or fully cloud-native services may keep everything in the cloud. Model five-year costs including transfer charges, respect territorial and residency limits and keep the masters where they can be repackaged quickly. Frequently asked questions Should a broadcaster store its VOD library in the cloud? It depends on library size, origin traffic, delivery architecture, residency and cost. Large libraries with heavy origin traffic often find on-premises or hybrid storage more economical. What is a mezzanine file? A high-quality master used as the source for creating streaming renditions and other delivery versions. Do broadcasters need to store every rendition? Not necessarily. Just-in-time packaging and on-demand transcoding can reduce stored renditions, trading storage for compute. How do rights affect where content is stored? Licenses may restrict storage and delivery to specific territories, so the library and its copies must respect those limits. How should a VOD library be protected? With erasure coding within a site and copies at a second location, possibly on a different medium. Further reading Video origin server storage Cloud DVR storage Media nearline archives Media asset managers on object storage Cloud repatriation strategy
