Updated October 2026: per-title services compared (AWS MediaConvert, Mux, Bitmovin, Brightcove), AV1 at 30% of Netflix streaming and the AV2 1.0 release, corrected Netflix, Bitmovin and Brightcove figures, new FAQ.

Per-title encoding is a video encoding method that builds a custom bitrate ladder for each video from that video's own rate–quality curve, instead of reusing one fixed ladder for the whole catalogue. Per-scene (shot-based) encoding goes further and sets the bitrate shot by shot inside one title. Both aim at the same thing: the same perceived quality for fewer bits, which on simple content means a much smaller CDN bill.

Why this matters

If you stream video to viewers, the bitrate ladder you choose decides three things at the same time: how much your content delivery network bill is each month, how clean the picture looks at every connection speed, and how fast your player can recover from a network drop. A fixed ladder copied from Apple’s HLS authoring specification overspends on simple content like webinars and underspends on busy content like sports — both bad outcomes. Product managers and founders need to understand this trade-off because the savings are large: AWS measured 29–30% smaller ladders on its own test titles (2020), and Bitmovin reports up to 87% on the top rendition of simple 4K content (2023) — on a large catalogue that is real budget. Engineers need it because the algorithms inside per-title encoding draw on convex-hull math, machine learning, and quality metrics like VMAF in ways the old fixed-ladder mental model never required.

What a Bitrate Ladder Actually Is

Before we get to "per-title", let's make sure we mean the same thing by "ladder". In adaptive streaming — the technology that lets your phone drop from HD to SD when the train enters a tunnel — the service offers the same video at several quality levels in parallel. Each level has a resolution (like 1920×1080 pixels) and an average bitrate (like 5 megabits per second, written 5 Mbps). The full set of (resolution, bitrate) pairs is the bitrate ladder. The player walks up and down this ladder during playback, picking the highest level the current bandwidth can sustain. Think of the ladder like menu sizes at a coffee shop: same product, different sizes, and the customer picks based on what they can drink right now.

The Apple HLS Authoring Specification, which most engineers still treat as the default starting point, recommends roughly nine to twelve rungs for H.264 video — values like 145 kbps at 416×234, 1 Mbps at 768×432, 4.5 Mbps at 1280×720, and 7.8 Mbps at 1920×1080. Apple itself notes these are "initial encoding targets" and that bitrates should be evaluated against specific content, but in practice many video pipelines ship those numbers verbatim. That is the fixed ladder. It does not know whether your input is a cartoon, a Champions League final, or a static slide presentation — and it spends the same bits on all three. To size a starting ladder for your own content before going per-title, use our bitrate ladder calculator.

Fixed ladder against a per-title ladder on one rate-quality curve. The chart plots quality in VMAF from 50 to 100 against bitrate from 0 to 8 Mbps; the curve rises steeply and then flattens, and a dashed horizontal line marks the VMAF 95 target. A green dot sits where the curve first touches the target, labelled 3.2 Mbps reaches VMAF 95. A grey square sits further right at 6.0 Mbps, labelled 6.0 Mbps adds 2.7 VMAF points. Below the chart two strips share the same bitrate axis: the fixed ladder, 7 rungs from 0.145 to 7.8 Mbps, drawn as grey squares spread across the full width; the per-title ladder, 5 rungs from 0.3 to 3.2 Mbps, drawn as green circles that stop at 3.2. The closing line reads: same VMAF 95, the fixed ladder spends 6.0 Mbps and the per-title ladder 3.2 Mbps, which is 47% fewer bits per view on this title and two top rungs nobody needs. Figure 1. A fixed ladder picks the same rungs for every video. A per-title ladder picks rungs along the actual rate–quality curve of this video, so simple content uses fewer bits and complex content uses more.

The Idea Behind Per-Title Encoding

Per-title encoding throws out the fixed ladder and computes a new one for every video you ingest. The high-level recipe, published by Netflix in a 2015 engineering post that triggered the entire industry, is three steps. First, encode the title at several resolutions and several quality settings, so you get a cloud of (resolution, bitrate, quality) points. Second, draw the curve that connects the best of those points — the highest quality reachable for any given bitrate. That curve is called the convex hull, and it is the mathematical frontier of "you cannot do better than this with this encoder on this content". Third, place your ladder rungs along that curve at the bitrates your audience actually uses.

The quality score in step two is rarely raw peak signal-to-noise ratio, called PSNR, because PSNR correlates poorly with what humans see. Most modern pipelines use Video Multi-method Assessment Fusion, abbreviated VMAF — a metric Netflix open-sourced in 2016 that scores videos on a 0–100 perceptual scale; a top-rung target around VMAF 93–95 is a common industry rule of thumb for premium content, not a standard. (For a deeper dive, see our article on quality metrics.)

Why does the convex hull matter? Because for a given title, encoding 1080p at 1.5 Mbps may produce a worse-looking picture than encoding 720p at 1.5 Mbps. The extra pixels at 1080p cost bits that the encoder has to take away from the parts that humans actually notice, like edges and faces. The convex hull tells you which resolution wins at each bitrate. For a quiet animation that may mean 1080p starts winning at 1.2 Mbps; for a fast hockey match it may not win until 5 Mbps.

Rate-quality curves for 480p, 720p and 1080p on one title, with the convex hull drawn over them. Quality in VMAF from 50 to 100 runs up the left, bitrate from 0 to 10 Mbps along the bottom. The light blue dashed 480p curve rises first and flattens at VMAF 88. The orange dotted 720p curve overtakes it and flattens at about 95.5. The green dash-dotted 1080p curve starts lowest, climbs steepest and ends highest, near 99. A thick navy line traces the outer envelope of all three and carries five round ladder rungs at roughly 0.5, 1.6, 2.6, 4.4 and 7.4 Mbps; where the envelope follows a resolution, it covers that curve. Two vertical dashed markers at 1.2 Mbps and 3.2 Mbps split the chart into three bands, labelled along the top: 480p wins below 1.2 Mbps, 720p between 1.2 and 3.2, 1080p above 3.2. Figure 2. Each resolution gives its own rate–quality curve. The outer envelope of all curves — the convex hull — is the best the encoder can do for this title. Ladder rungs are picked along that envelope.

Math of the Bitrate Savings

Take a typical 90-minute feature with a fixed-ladder 1080p rung at 6 Mbps. The total payload for one viewer watching all the way through is:

size = bitrate × time
     = 6 Mbps × 5,400 seconds
     = 32,400 megabits
     = 4,050 megabytes
     ≈ 4.05 GB

Now suppose per-title analysis discovers that this particular title — say a dialogue-heavy drama — can hit the same VMAF 95 at 3.2 Mbps. The new payload is:

size_new = 3.2 Mbps × 5,400 s
         = 17,280 Mb
         = 2,160 MB
         ≈ 2.16 GB

That is a 47% reduction in egress bandwidth for that title. If your content delivery network charges 1 cent per gigabyte and the title gets 5 million views per year, the savings are:

savings = (4.05 − 2.16) GB × 5,000,000 views × $0.01/GB
        = $94,500 per year per title

That arithmetic — multiply the per-view delta by the view count by the unit cost — is the entire business case for per-title encoding in one expression. It also explains why the savings are concentrated in your most-watched titles: optimisation buys you the same percentage on every title, but the dollar value tracks views. For the full CDN, storage and compute cost model of an OTT catalogue, see per-title encoding economics.

Where Per-Title Falls Short — and Per-Scene Begins

Per-title makes a single ladder for the whole title, which means every part of the video pays the same per-second bit rate. That works for content where complexity is roughly uniform — a news bulletin, a webinar, a sitcom with steady camera work. It works less well for content with big complexity swings: a thriller that alternates between dark interior dialogue and a chase scene, or a sports stream that cuts from a wide pitch to a close-up of grass.

In a thriller, the dialogue scene needs maybe 1.5 Mbps to look perfect because there is almost no motion and the camera is locked off. The chase scene needs 8 Mbps to avoid blocking on the fast pans and tight crops. A per-title ladder picks one bitrate, say 4 Mbps, that splits the difference — dialogue overspends by 2.5 Mbps and the chase underspends by 4 Mbps and shows artefacts. The viewer's eye fixes on the artefacts, not the savings on the dialogue.

Per-scene encoding (also called shot-based encoding or content-adaptive encoding) fixes that by splitting the title into shots and computing a fresh ladder for each shot. A "shot" is a single continuous camera capture; shots in scripted TV and film typically last only a few seconds, so a 60-minute drama contains several hundred shots. Netflix's Dynamic Optimizer, which it deployed in production in 2018, encodes each of those shots at several quality points, runs a Lagrangian optimisation across the whole title to pick the per-shot quality that minimises total bits for a target average VMAF, and stitches them back together. In its 2018 Dynamic Optimizer post, Netflix reported about 17.1% average bitrate savings for VP9 at equal quality (HVMAF) against the best fixed-QP encode of the whole sequence — 22.5% when measured with PSNR — and 28–38% gains on shorter test clips across H.264, HEVC and VP9. Quiet shots drop to lower resolutions and busier shots claim back the saved bits.

Per-title encoding against per-scene encoding over six shots of the same title, as two bar charts stacked one above the other on a shared 0 to 8 Mbps scale. The upper chart, per-title encoding, is one bitrate for the whole title: six equal blue bars at 4.0 Mbps each. The lower chart, per-scene encoding, gives every shot its own ladder: shot 1 dialogue 1.5 Mbps, shot 2 wide shot 3.0, shot 3 action 6.5, shot 4 dialogue 1.8, shot 5 chase 7.0, shot 6 outro 2.0, with a dashed line across them at the 3.6 Mbps average. The closing line reads: average 3.6 Mbps against a flat 4.0 Mbps is 10% fewer bits, and the bits move from the four quiet shots to the two busy ones. Figure 3. Per-title gives the whole video one bitrate. Per-scene profiles each shot and reassigns bits from the easy shots to the hard shots without changing the perceived overall quality.

A Common Mistake: Cutting on GOP Boundaries Only

A pitfall every engineer hits the first time they try per-scene encoding: shots must start on group-of-pictures (GOP) boundaries so that the player can switch ladder rungs cleanly. (For background, see the GOP structure article.) If your scene detector finds a shot boundary in the middle of a closed GOP, you have two bad choices: split the GOP and accept a decoding glitch, or move the shot boundary to the next keyframe and lose some of the optimisation. The fix used by Netflix, Bitmovin, and Mux is to force a keyframe at every detected shot boundary in the analysis pass. That makes shots a little less compressible — each shot now starts with a more expensive I-frame — but the loss from extra keyframes is far smaller than the gain from per-shot adaptation.

How the Algorithms Actually Run

There are three practical implementation styles in 2026, sorted by complexity:

Brute-Force Test Encodes (the original Netflix method)

For each title, encode it at every (resolution, bitrate) combination of interest — for example five resolutions times eight bitrates equals forty test encodes — and measure VMAF on each. Build the convex hull from those forty points, pick the ladder rungs that hit your target VMAF range, and discard the rest. This is the most accurate method because it directly measures what the encoder will produce. It is also the most expensive: those forty test encodes are an order of magnitude more compute than producing one final encode, so the analysis pass alone can cost more than a fixed-ladder pipeline produces. Netflix can afford this because the resulting bits are served to more than 325 million paid memberships (Netflix Q4 2025 results, January 2026); the per-view amortisation makes the cost trivial.

Lookahead-Plus-Single-Encode (Bitmovin / classical CAE)

Take a fast first-pass analysis of the file — maybe one fifth-the-speed encode at the source resolution, or a constant-rate-factor (CRF) probe — collect statistics like motion energy, spatial complexity, and noise level, and feed those statistics into a model that predicts the convex hull without running every combination. The model can be hand-tuned (early CAE systems) or trained on a benchmark dataset (modern systems). Output is the same ladder shape as brute force but produced in roughly one extra encode's worth of compute. Bitmovin’s own tests (blog, 2023, updated April 2026) report 22.7% bitrate savings with higher VMAF on a 4K title against a static ladder, and up to 87% on the top rendition of low-complexity 4K content in HEVC.

Neural-Network Inference (Mux instant per-title, ML-CAE)

Pass the source through a convolutional neural network whose output is the ladder directly — no test encodes, no probe pass, just inference on raw frames. Training data is the brute-force ladder for tens of thousands of clips; the network learns the mapping from "what the content looks like" to "what the ladder should be". Inference time is milliseconds, which is what makes this approach feasible for live streams where you do not have a fast-encoder probe budget. Mux publicly describes this approach as the basis for its instant per-title pipeline. Accuracy is slightly below brute force on out-of-distribution content but the speed difference is six orders of magnitude.

Method Analysis cost Live-friendly Typical bitrate saving vs fixed Where it shines
Brute-force test encodes 10–40× a single encode No 20–50% Premium VOD catalogues with high view counts
Lookahead + CAE model ~1.2–1.5× a single encode Borderline (chunked live) 20–40% Mid-size VOD libraries; live with several-second latency
Neural-network inference Milliseconds Yes 15–35% Live streams; UGC; very large libraries

The analysis-cost and saving ranges in this table are our 2026 working estimates, combined from the vendor reports cited here and our own test encodes; your catalogue will land somewhere inside them, so measure on 10–20 of your own clips before you commit.

For a deeper look at the encoders that sit downstream of any of these methods, see our rate control article and the FFmpeg cheat sheet.

Context-Aware Encoding: One More Dimension

Per-title and per-scene both look at the content. Brightcove's Yuriy Reznik, who originally pushed the term, made the case in 2017 that you should also look at the context — the population of devices, screens, and networks the title will be delivered to. If 80% of your viewers are on mobile and never see anything above 720p, the 4K and 1440p rungs of your ladder are wasted CDN warm-up storage. If your audience is concentrated in a region with median bandwidth around 4 Mbps, putting two ladder rungs at 8 and 12 Mbps just feeds the small fraction with fibre at the cost of redundant encodes.

Context-aware encoding (CAE) takes the per-title or per-scene ladder and prunes / shifts it based on audience analytics: drop rungs no one watches, push other rungs up or down to land at the modal bandwidth, and re-target VMAF based on screen size. Measured gains depend on the signals you feed in. In a 2023 SMPTE paper, Reznik and colleagues at Brightcove added one more signal to CAE — detecting the true resolution of upscaled sources — and cut bandwidth by about 9.4% and storage by about 11.3% on average, and by up to 27–28% for some content categories, at unchanged SSIM. The cost is operational: you need playback analytics flowing back into the encoding pipeline, and you need to re-encode when audience composition shifts.

Live Streaming Changes the Game

Per-title was invented for video-on-demand, where the file sits on disk and you can spend an hour analysing it. Live changes three constraints at once: there is no full file to analyse, latency budgets are in the order of seconds, and the content can pivot between calm and chaotic in one shot (think a half-time interview cutting back to the pitch). Three adaptations have emerged in production:

Chunk-level adaptation. Bitmovin, Mux, and AWS Elemental MediaLive all support chunk-level rate control where the ladder is fixed at stream start but each segment's encoder targets a slightly different bitrate based on a short lookahead. Savings are typically 5–15%.

Audience-adaptive encoding. Mux runs a model that watches incoming player telemetry and gradually shifts the ladder while the stream is live — rungs no one is selecting get pulled or replaced. This is closer to CAE than per-title.

Online per-scene encoding (OPSE). Academic work by the ATHENA Christian Doppler Laboratory in 2022 demonstrated online per-scene encoding for live HLS: a trained model predicts the bitrate–resolution pairs of each incoming scene on the fly instead of running test encodes. The authors report bitrate savings of up to 48.88% in some scenes at the same VMAF as the reference HLS ladder, with no noticeable added latency.

For low-latency formats — LL-HLS or WebRTC — the lookahead budget shrinks below a second, so most production systems today fall back to a careful audience-adaptive fixed ladder with per-stream tuning rather than full per-scene optimisation.

Decision ladder for choosing a per-title encoding method in 2026, walked from the top; the first yes picks the method and the last row is the default. Question one: live stream, latency under 2 seconds? Yes leads to an audience-adaptive ladder, a fixed ladder pruned by player telemetry with chunk-level tuning, saving 5 to 15%. No drops to question two: live stream with a few seconds of latency? Yes leads to neural-network inference, where an ML model predicts the ladder straight from the source frames, saving 15 to 35%. No drops to question three: VOD above 100,000 views a year? Yes leads to brute-force test encodes, encoding every resolution and bitrate pair and measuring VMAF, at 10 to 40 times the analysis cost and saving 20 to 50%. No drops to the default row, VOD and everything else, which leads to lookahead plus a CAE model, where one probe pass feeds a trained convex-hull model at 1.2 to 1.5 times the cost, saving 20 to 40%. A panel below the tree reads: in every branch, layer context-aware encoding on top, pruning the rungs no audience selects and re-targeting VMAF by screen, noting that the size of that saving depends on your audience data and should be measured before and after. Figure 4. Which per-title method to run. Walk the questions from the top: the first one you answer yes to is your method, and context-aware pruning goes on top of whichever you pick.

What Changed in 2025–2026

The method has not changed; the codecs and the tooling around it have. Four developments matter for anyone building a ladder today.

  • AV1 went mainstream. Netflix reported in December 2025 that AV1 powers about 30% of its streaming, with AV1 sessions using about one-third less bandwidth than AVC and HEVC sessions and 45% fewer buffering interruptions. A per-title ladder is built per codec: the AV1 convex hull sits to the left of the H.264 hull, so the same VMAF target lands on fewer bits and often fewer rungs.
  • Film grain stopped inflating the top rung. Netflix productized AV1 film grain synthesis in July 2025: grain is removed before encoding and re-synthesised in the decoder. If you run per-title on grainy film content, build the hull with grain synthesis on, or you will over-provision the top rungs.
  • AV2 1.0 shipped. The Alliance for Open Media released AV2 in June 2026 and says it delivers about 30% better compression than AV1 on objective metrics (AOMedia, July 2026). Hardware decoders follow software, so in 2026–2027 AV2 is a lab codec for most services, not a delivery rung.
  • Per-title became a setting. AWS, Mux, Bitmovin and Brightcove all ship it as a managed option, so the build-or-buy question below is now the first decision, not the last.

Per-Title Encoding Services and Quality Tools in 2026

If you do not want to build the convex-hull pipeline yourself, a managed encoder will build the ladder for you; if you do, FFmpeg plus libvmaf is the standard toolkit. The table compares what each option actually controls and what its vendor has published.

Option How it builds the ladder What you control Published numbers
AWS Elemental MediaConvert — Automated ABR Analyses each source and builds its ladder on QVBR rate control, dropping redundant rungs Maximum renditions, minimum and maximum bitrate 29–30% smaller ladders on AWS test titles, up to 40% less storage; no extra charge on Professional-tier VOD jobs (AWS, 2020)
Mux Video An AI model measures content complexity and picks the ladder per asset Quality level: basic, plus or premium Premium priced at 1.5× plus; up to 2160p on demand, 1080p live (Mux, October 2024)
Bitmovin Per-Title Complexity analysis per asset; drops rungs above about 45 dB PSNR, where extra bits add no visible quality Per-codec configuration, bitrate bounds, rung count 22.7% savings on a 4K example; up to 87% on the top rendition of simple 4K content (Bitmovin, 2023)
Brightcove Context-Aware Encoding Content analysis plus audience device and network statistics Audience data feeding the optimiser True-resolution detection: about 9.4% less bandwidth, 11.3% less storage (SMPTE, 2023)
Build your own: FFmpeg + libvmaf You run the test-encode grid, score it with VMAF and walk the convex hull Everything: codecs, grid, quality target, pruning rules Cost is compute; pays back when view counts are high

To evaluate a per-title encoding platform, run the same five checks on each candidate: encode 10–20 of your own clips and compare bitrate at equal VMAF against your current ladder; confirm per-title works for every codec you ship (H.264, HEVC, AV1), not just H.264; check whether it works for live or only VOD; price the analysis pass, not just the per-minute encode; and for live channels ask for compute or power per channel at your ladder, because that is what scales your bill. Whichever service you pick, keep your own VMAF measurement in the loop so the vendor’s quality claim is not the only one you have.

Frequently Asked Questions

What is per-title encoding?

Per-title encoding builds a custom bitrate ladder for each video from its own rate–quality curve instead of reusing one fixed ladder. Simple content gets fewer, cheaper rungs; complex content gets the bits it needs.

What is a bitrate ladder?

A bitrate ladder is the set of (resolution, bitrate) pairs an adaptive stream offers, for example 1080p at 6 Mbps down to 234p at 145 kbps. The player switches between rungs as the viewer’s bandwidth changes.

What is the difference between per-title and per-scene encoding?

Per-title picks one ladder for the whole video. Per-scene (shot-based) encoding gives every shot its own bitrate target, so quiet shots spend fewer bits and busy shots get more at the same overall quality.

How do developers handle per-title bitrate ladders without ballooning CDN costs?

They build each ladder from the title’s convex hull, cap the top rung where the quality curve flattens (often around VMAF 93–95), prune rungs their audience never selects, and spend expensive analysis only on titles whose view count pays it back.

How do video APIs pick a bitrate ladder for a live stream?

Live has no full file to analyse, so APIs either predict the ladder from the first frames with a trained model, fix the ladder at stream start and tune bitrate per chunk, or prune rungs from player telemetry while the stream runs.

Is there a rule of thumb for live sports ladders?

Sports is the hardest case for per-title savings: high motion keeps the top rung near a fixed ladder’s bitrate, so the savings come from the middle rungs and from pruning rungs your audience’s devices and networks never select.

Which per-title encoding service should I use?

AWS MediaConvert Automated ABR is the default if you already run on AWS; Mux suits teams that want an API with one quality setting; Bitmovin gives the most per-codec control; a self-built FFmpeg and VMAF pipeline wins only at high view counts.

↓ Free download: Smart Bitrate Ladder ChecklistOne-page A4 reference with the per-title and per-scene decision flow, the test-encode grid for a brute-force convex hull, the ladder-pruning rules for context-aware encoding, and the three live-streaming variants.

Where Fora Soft Fits In

We build video and audio streaming software and the encoding pipelines behind it: OTT and internet TV catalogues that need to keep CDN costs predictable, conferencing platforms that fight for every millisecond of bandwidth, e-learning systems where lecture content varies from slide capture to camera-and-whiteboard, and surveillance and telemedicine products where bandwidth is paid for by the client. When the ladder is the problem, our custom video processing development team builds the test-encode grid, the VMAF gate and the convex-hull step into your transcoding pipeline, and for catalogue products our OTT and IPTV platform development team ships per-title ladders together with multi-DRM and the player. In every one of those verticals, the right per-title or per-scene strategy is a different shape. A lecture platform can run brute-force per-title overnight on each upload because lectures rarely watch live. A live sports OTT product needs neural-inference per-title plus context-aware pruning. A telemedicine app needs context-aware only — the content is uniform but the network varies. Picking the right combination is one of the design decisions we walk every new project through.

Video Encoding: A Complete Guide to Video Compression - book cover

The book

Video Encoding: A Complete Guide to Video Compression — From Pixels and Color to H.264, HEVC, AV1, Quality Metrics, and AI

Every point on the convex hull above is one encode, scored by one metric, hit by one rate-control mode — and a ladder is only as trustworthy as those three. The book spends 1,522 pages on them: the encoder stages that shape the rate–quality curve in the first place, then rate control, GOP structure and the quality metrics you need to prove a cheaper ladder does not look cheaper. Written by Nikolay Sapunov, CEO at Fora Soft.

Read it on Amazon →Kindle & paperback · Fora Soft Video Engineering Handbook

Still shipping the ladder from the Apple spec?

Send us a sample of your catalogue, your player telemetry and your CDN bill, and we will tell you what a per-title or per-scene ladder saves on it, what the analysis costs to run, and which of the three methods fits your latency budget — 250+ video products shipped since 2005.

Book a 30-min call →WhatsApp →Email us →

See our case studies

References

  1. Netflix Technology Blog. Per-Title Encode Optimization (2015). netflixtechblog.com/per-title-encode-optimization-7e99442b62a2. Accessed 2026-05-17.
  2. Netflix Technology Blog. Dynamic Optimizer — a perceptual video encoding optimization framework (2018). netflixtechblog.com/dynamic-optimizer-a-perceptual-video-encoding-optimization-framework-e19f1e3a277f. Accessed 2026-10-29.
  3. Netflix Technology Blog. Optimized shot-based encodes: Now Streaming! (2018). netflixtechblog.com/optimized-shot-based-encodes-now-streaming-4b9464204830. Accessed 2026-05-17.
  4. Apple Developer. HTTP Live Streaming (HLS) Authoring Specification for Apple Devices. developer.apple.com/documentation/http-live-streaming/hls-authoring-specification-for-apple-devices. Accessed 2026-05-17.
  5. Reznik, Y. Context-Aware Encoding and 5G — DASH-IF Workshop 2019. dashif.org/docs/workshop-2019/03-Reznik-DASH-IF-workshop-2019-CAE.pdf.
  6. Reznik, Y. Improving Context-Aware Encoding by Adaptation to "True" Audience — SMPTE MTS 2023. reznik.org/papers/SMPTE_MTS2023_Improving_Context_Aware_Encoding.pdf. Accessed 2026-10-29.
  7. Mux Engineering. Instant Per-Title Encoding. mux.com/blog/instant-per-title-encoding. Accessed 2026-05-17.
  8. Bitmovin. Per-Title Encoding service page. bitmovin.com/encoding-service/per-title-encoding. Accessed 2026-05-17.
  9. Bitmovin. Cut your storage and CDN bills in half with Per-Title Encoding. bitmovin.com/blog/per-title-encoding-savings. Accessed 2026-10-29.
  10. ATHENA Christian Doppler Laboratory. OPSE: Online Per-Scene Encoding for Adaptive HTTP Live Streaming (2022). athena.itec.aau.at/2022/05/opse-online-per-scene-encoding-for-adaptive-http-live-streaming/. Accessed 2026-10-29.
  11. Netflix Technology Blog. AV1 — Now Powering 30% of Netflix Streaming (December 2025). Summary at tvtechnology.com. Accessed 2026-10-29.
  12. Alliance for Open Media. AV2: What the Final Specification Means for Implementers (July 2026). aomedia.org. Accessed 2026-10-29.
  13. AWS for M&E Blog. Introducing Automated ABR configuration in AWS Elemental MediaConvert (2020). aws.amazon.com/blogs/media. Accessed 2026-10-29.
  14. Mux. One size does not fit all: introducing premium video quality for Mux Video (October 2024). mux.com/blog. Accessed 2026-10-29.
  15. Bitmovin. Per-Title Encoding Overview (developer docs). developer.bitmovin.com/encoding/docs/per-title-encoding. Accessed 2026-10-29.
  16. Convex Hull Prediction Methods for Bitrate Ladder Construction: Design, Evaluation, and Comparison — ACM TOMM (2025). DOI 10.1145/3723006; open preprint: arxiv.org/abs/2310.15163. Accessed 2026-10-29.
  17. Zabrovskiy, A. et al. FAUST: Fast Per-Scene Encoding Using Entropy-Based Scene Detection and Machine Learning. fruct.org/publications/volume-30/fruct30/files/Zab.pdf.