Best Practices for Pristine Videos
Image and Video Manager can simplify your workflow by reducing the number of derivative videos needed.
To make sure each end-user receives the best-quality derivative version you should use a higher-quality pristine (or original) video. To take full advantage of Image and Video Manager optimizations, we created these best practices for video format, quality, resolution, file size, and container details.
Please keep in mind that these are general guidelines.
- We recommend providing high-quality videos in web-compatible progressive download formats. Mp4 or mov formats are typically used.
- Keep in mind, that upon failover or until the video is optimized (unless using the placeholder video), the pristine video will be delivered to end users. For this reason it is essential that the video is already in a web-compatible format.
- We recommend high-quality videos in h264.
- We recommend providing high quality and high bitrate videos while keeping in mind file
size limitations (maximum of 256 MB). This lets Image and Video Manager optimize in the
best way.Note: Image and Video Manager performs video optimization in an offline process. The first request for any video URL will either serve the pristine video (and queue the video for processing). Subsequent requests will also serve the pristine video until the derivative video processing is complete. You can optionally configure a placeholder video URL to play until the offline process is complete.
- In general, we recommend pristine videos with dimensions of 1920x1080 or smaller.
- If you happen to know the largest dimension you will deliver to end users, we suggest
using those exact dimensions as your pristine dimensions. Tip: You should use logical dimensions. For example, there's no point in providing a 10,000 px by 10,000 px pristine when the largest dimension image you would ever serve is only 1920 px wide.Note: 4K video is not supported as input. The maximum total pixel area input that is accepted is 3,686,400 pixels.
- Input videos must be 256 MB or less.
- Input videos must be 5 minutes or less.
Video and Audio Streams
- We recommend that you provide video containers with a single video (and optionally a single audio track).
- All other streams will be removed when generating a derivative video.
- mov_text Streams - Mov_text streams within a video container are persisted in derivative videos (to preserve closed captions).
- WebVTT - We recommend that you use WebVTT for text files for greater flexibility in multi language support and for more efficient workflows. HTML5 player supports WebVTT files as do many other video players.