Best practices for pristine videos

To enable Image and Video Manager to deliver the best quality derivative videos to your customers, we recommend that your original pristine videos have certain characteristics. Please note that these are only general guidelines.

Container format

  • High-quality videos in web-compatible progressive download formats such as MP4 or MOV.

  • Formats such as HLS or MPEG-DASH are not supported for streaming.

Upon failover or until the video is optimized, the pristine video will be delivered to end users (unless a placeholder video is being used). For this reason, the video must already be in a web-compatible format.

Codec

  • High-quality videos in h264 format.

Quality

  • High quality and high bit-rate videos.

  • Keep in mind the file size limitation of 256 MB.

Image and Video Manager performs video optimization as an offline process. The first request for any video URL will serve the pristine video and queue the video for processing. Subsequent requests will also serve the pristine video until derivative video processing is complete. As an alternative, you can configure a placeholder video that will play until the offline process is complete.

Dimensions (resolution)

  • Videos dimensions of 1920x1080 or less.

  • If you know the largest video dimensions you will deliver to end users, use those exact dimensions for your pristine videos (there is no advantage to a pristine video with a width of 10,000 px if you will never display videos at widths greater than 1920 px).

  • 4K video is not supported.

  • The maximum total pixel area that is supported is 3,686,400 pixels. Videos with a pixel area greater than this will not be optimized.

File size

  • Less than 256 MB.

Length

  • 5 minutes or less.

Video and audio streams

  • Provide video containers with a single video (and optionally a single audio track).

  • All other streams will be removed when generating a derivative video.

Closed captions

  • Use mov_text Streams within a video container persist in derivative videos to preserve closed captions.

  • 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).


Did this page help you?