What is Per-Title Encoding?
Per-title encoding analyzes an individual video and constructs a bitrate and resolution ladder suited to its visual complexity. It replaces a fixed ladder applied uniformly to every title.
How Per-Title Encoding works
Per-title encoding measures the rate-distortion behavior of a particular source instead of applying a universal set of rungs. Trial encodes or content models estimate which combinations of resolution, bitrate, and codec settings deliver useful quality steps. The selected ladder is then packaged for adaptive playback like a conventional ladder, but its shape may differ from every other title. This optimization belongs between source analysis and large-scale encoding, and it must still respect device, network, and business constraints.
Key facts
- 1Low-motion animation and grainy live action can require very different bitrates at the same resolution and nominal quality, which fixed ladders cannot express well.
- 2Ladder construction must preserve monotonically useful choices; a higher-bitrate rendition that looks no better wastes storage, CDN bytes, and player options.
- 3Per-title analysis adds computation before final encoding, but its decisions can reduce downstream transfer when the catalog is viewed often enough.
When Per-Title Encoding matters
Use it when bandwidth efficiency justifies analyzing each source before encoding. A poorly selected quality target can remove useful renditions or spend extra bits without a meaningful visual benefit.
Common use cases for video
These examples cover video broadly, not specifically Per-Title Encoding.
- Preparing uploaded video for web, mobile, connected-TV, social, or editorial playback.
- Creating clips, thumbnails, captions, alternate aspect ratios, and adaptive renditions.
- Normalizing camera, screen-recording, and user-generated files into predictable outputs.
Working with video
This guidance covers video broadly, not just Per-Title Encoding.
A demuxer separates tracks from the container, decoders turn compressed streams into frames or samples, and filters apply spatial or temporal changes. Encoders compress the transformed tracks before a muxer writes the chosen output container.
Video compatibility is the product of codec, container, profile, level, frame rate, color, audio, and subtitles. Validate the complete output on target devices because a playable file on one decoder may fail or look different on another.
What you gain
- Standardized derivatives make diverse source files playable on target devices.
- A retained master can feed many resolutions, aspect ratios, codecs, and channels.
- Automated inspection and transformation make large upload volumes consistent.
What it costs
- More efficient codecs can lower bitrate at similar quality but usually cost more compute and may have narrower support.
- Higher resolutions and frame rates preserve more detail and motion while increasing processing and delivery requirements.
- Fast encoding settings improve throughput but can produce larger files or lower quality than slower analysis.
Before production
- 1Inspect codec, container, dimensions, frame rate, color, audio, and subtitle tracks.
- 2Test visual quality and playback support across the slowest and oldest target devices.
- 3Preserve a suitable master before applying lossy, destructive, or delivery-specific changes.