<!-- This article pertains to video-on-demand (VOD) content. For live content, see ?? -->

When you upload a media file [through your dashboard](πŸ”—ο»Ώ), JWP prepares the media file to be shared and streamed through a conversion and encoding process. The information below describes how and why JWP converts and encodes media files.

## Media Scaling

Upscaling and downscaling allow media to conform to different viewing situations. Upscaling re-sizes lower-resolution content to fit a broader range of screen sizes, while downscaling allows content from one source to play on different displays in their native resolution.

Because upscaling tends to result in a loss of resolution or picture quality, JWP will only downscale an output rendition. For example, if an uploaded video has a 720p resolution, JWP will not create a 1080p rendition. The highest output resolution will be 720p.

<br /> <hr />

## Media Output Formats

JWP creates the following encoded renditions in MP4 containers by default:

<table> <thead> <tr> <th><strong>Resolution</strong></th> <th><strong>Profile</strong></th> <th><strong>Level</strong></th> <th><strong>B-frames Enabled</strong></th> <th><strong>Audio Codec</strong></th> </tr> </thead> <tbody> <tr> <td><strong>1080p</strong></td> <td>H.264 High&nbsp;</td> <td>4.0</td> <td>Yes</td> <td>AAC audio</td> </tr> <tr> <td><strong>720p</strong></td> <td>H.264 Main&nbsp;</td> <td>4.1</td> <td>Yes</td> <td>AAC audio</td> </tr> <tr> <td><strong>540p</strong></td> <td>H.264 Main&nbsp;</td> <td>3.1</td> <td>Yes</td> <td>AAC audio</td> </tr> <tr> <td><strong>360p</strong></td> <td>H.264 Main&nbsp;</td> <td>3.0</td> <td>Yes</td> <td>AAC audio</td> </tr> <tr> <td><strong>270p</strong></td> <td>H.264 Baseline&nbsp;</td> <td>3.0</td> <td>No</td> <td>AAC audio</td> </tr> <tr> <td><strong>180p</strong></td> <td>H.264 Baseline&nbsp;</td> <td>2.1</td> <td>No</td> <td>AAC audio</td> </tr> </tbody> </table>

<br />

JWP also creates the following adaptive streaming outputs:

<table> <thead> <tr> <th>Properties <em>without</em> DRM enabled</th> <th>Properties <em>with</em> DRM enabled</th> </tr> </thead> <tbody> <tr> <td><strong>HLS</strong>: <ul> <li>H.264 video</li> <li>AAC audio</li> <li>In-manifest WebVTT subtitles*</li> <li>HLS Trickplay (I-Frame and JPEG variants)*</li> <li><a href="https://developer.apple.com/documentation/http_live_streaming/about_the_ext-x-version_tag" target="_blank" rel="noopener">EXT-X-VERSION:3 compatible</a></li> </ul> </td> <td><strong>MPEG-DASH</strong>: <ul> <li>H.264 video</li> <li>AAC audio</li> <li>AES-128 Common Encryption</li> <li>Widevine and PlayReady DRM variants</li> </ul> <strong>HLS</strong>: <ul> <li>H.264 video and AAC audio</li> <li>FairPlay Streaming DRM</li> <li><a href="https://developer.apple.com/documentation/http_live_streaming/about_the_ext-x-version_tag" target="_blank" rel="noopener">EXT-X-VERSION:1 compatible</a></li> </ul> </td> </tr> </tbody> </table>

<sup>\*</sup> requires enablement by JWP Support representative

<br /> <hr />

## Bitrate Caps

JWP uses [capped CRF encoding](πŸ”—ο»Ώ) to create media renditions and determine the bitrate cap for each rendition. A proprietary algorithm determines the optimal peak bitrate for the content. This approach makes the most efficient use of available bits in the rendition.

This bitrate cap prevents the encoded media stream from exceeding a peak bitrate. If the content is not complex (such as media with little fast movement or fine detail), the output may render under the cap, but never over.

For example, an encoded rendition with a bitrate cap of 1,000 Kbps might have an effective bitrate of 600 Kbps but never 1,100 Kbps.

<br /> <hr />

## Audio Channels

By default, JWP matches the number of audio channels in the upload. If an uploaded video has 5.1 channel audio, JWP will create both stereo and 5.1 renditions.

<br />

<!-- Removes the automatic page-to-page navigation at the bottom of the page -->

<style> .rm-Pagination { display: none; } </style>