Live to VoD is a built-in capability of Play, available from the Standard Feature Plan (currently Limited Availability).
It is available for both standard and premium processing.

Before we go into the details of how to use it, let's make sure we use the same language ...
Live to VoD allows to convert a live content into streamable VOD assets.
Once created, VoD assets have an unique identifier used to access the content, and their own lifecyle uncorrelated to the live content.

Overview

The live to VoD workflow is illustrated below. It includes:

• A configuration step used to gather VoD assets into "Collections". This step can be done prior to the actual live to VoD processing or during the "Publish" step.
• Four steps that implement the live to VoD process till the user delivery

• By default, recordings are retained in the system for seven days.
• Live-to-VoD processing, including codec, resolution, bitrate, packaging (HLS, DASH), and DRM capabilities, is identical to that used for Live content.
• VoD assets are created from recordings and published to collections. After publication, they can be streamed using ABR delivery.
• VoD assets are currently available for streaming only and cannot be downloaded as files (e.g., MP4). Support for file-based delivery is a candidate evolution.
• VoD assets do not expire and remain available until explicitly deleted.

Live to VoD menu

When Live to VoD is available for your organization, a "Live2VOD" choice is available in the left menu of the UI.
It has 2 tabs: Recorders and Asset Collections.
The next sections describe how to use them.

Creating Recorders

Creating recorders enables to record live content that will later be used as a source to extract VoD.
A recorder is defined by:

• An input
• A transcoding ladder

Optionally, you may

• Change the default recorder name
• Activate the Autopublish to a selected collection to automate this action. This means that all VoD that will be later extracted from this recorder will automatically be sent to the selected collection.

Once created, the recorder starts to record immediately.
The recorder records the same content as delivered for live. Particularly, If the source is missing, the recorded content will be either black, or fallback image depending on the input configuration

The recorder produces recordings that will be the source of future VoD assets.
Recordings are kept for 7 days in the system by default (system setting).

Extracting Assets from Recordings

VoD Assets are generated by extraction from recordings.
To generate a VoD Asset, the following information are required

• Start and End time
• Asset name

An existing matching recording for the selected start and end time must exist to generate the VoD Asset.
The extraction is aligned on segments. The extraction is performed on the closest segment before the requested start date, and after the requested end date.

Publishing to collection

Collections can be used to regroup various assets for business purposes but a single collection for all can be used if not required.

Once the extraction is done, the next step is to publish the extracted VoD asset to a collection.
This results in storing the VoD asset in a dedicated storage, where assets have their own lifecycle, disregards the recorder they originate from.

Until an asset is published, it appears in the "Unpublished asset" list:

To publish it, you need to assign a Collection. This action can be done per asset or as a bulk action for several assets:

You can select an existing Collection, or create a new one as target Collection:

Once published, the asset appears in the Collection:

Delivery endpoint

Like for live delivery, VoD Assets are delivered to users via endpoints.
Endpoints are defined by

• A collection
• A selected packaging configuration

This results in a templated URL to access VoD Assets belonging to that collection.

You can also export all assets URI in a CSV file:

A specific asset can be streamed using the URI.

Updated on: 16/10/2026