Build MediaConvert job template configurations with HLS/DASH outputs, codec settings, and adaptive bitrate profiles.
Build MediaConvert job template configurations with HLS/DASH outputs, codec settings, and adaptive bitrate profiles.
Required Fields
NameSettings.OutputGroupsSettings.InputsOutput will appear here...The builder validates that Name, Settings.OutputGroups, and Settings.Inputs all resolve before accepting the JSON as a valid CreateJobTemplate request, the fields MediaConvert needs to know the template's name and what transcoding pipeline it defines; it can't verify the referenced S3 input/output URIs are reachable or that the codec settings are internally consistent for the target output group type, those are checked only when an actual job is submitted using the template.
Build a MediaConvert job template defining multi-bitrate HLS output (separate 1080p and 720p renditions in one OutputGroup) with QVBR (Quality-Defined Variable Bitrate) rate control, which targets a consistent visual quality level rather than a fixed bitrate, letting simpler scenes use fewer bits and complex scenes use more, generally producing better quality-per-byte than a fixed CBR/VBR bitrate target for the same average file size. AccelerationSettings with Mode PREFERRED opts into MediaConvert's accelerated transcoding for compatible job types (faster processing on eligible content), but it's not universally applicable, MediaConvert automatically falls back to standard processing for content/settings combinations that don't support acceleration, so PREFERRED isn't a guarantee every job actually runs accelerated.
QVBR generally produces better perceptual quality-per-byte than CBR for the same average bitrate, but don't assume it's a drop-in replacement if you have a hard, strict file-size or bandwidth-budget requirement, MaxBitrate is a ceiling, not the actual guaranteed output rate.
Don't rely on AccelerationSettings PREFERRED to guarantee a specific transcoding speed for capacity planning, since fallback to standard processing is automatic and silent, budget processing time assuming standard speed unless you've specifically verified your content/settings combination is acceleration-eligible.
A well-designed adaptive bitrate ladder (multiple renditions at sensibly-spaced bitrates) matters more for actual viewer experience than any single rendition's specific settings, review the full Outputs ladder holistically rather than optimizing one rendition's QVBR level in isolation.
No, that's the fundamental tradeoff of QVBR versus CBR: QVBR targets a consistent perceptual quality level (via QvbrQualityLevel) and lets bitrate (and therefore file size) vary based on scene complexity, a static talking-head scene uses far fewer bits than an action sequence with lots of motion. MaxBitrate caps the ceiling, but actual average bitrate and file size depend on the content itself, not a fixed target the way CBR would guarantee.
No, PREFERRED means MediaConvert will use accelerated transcoding when the specific job's settings and input are eligible, but it automatically and transparently falls back to standard processing for anything that isn't eligible (certain codec/setting combinations aren't supported for acceleration). It's a preference, not a guarantee, don't assume every job using this template necessarily gets the faster, accelerated processing path.
Yes, adding another entry to the Outputs array within the same OutputGroup is additive, existing renditions and their settings aren't affected by adding a new one alongside them. This is the standard way to add a lower-bandwidth fallback rendition for viewers on poor network connections without disrupting the existing adaptive bitrate ladder.
Was this tool helpful?
Disclaimer: This tool runs entirely in your browser. No data is sent to our servers. Always verify outputs before using them in production. AWS, Azure, and GCP are trademarks of their respective owners.