Why this matters
The bitrate ladder is the single biggest lever you have on streaming cost, perceived quality, and start-up time. A bad ladder pays the egress bill three times: in pixels nobody can see, in rebuffers from rungs that are too sparse, and in encoder hours spent on renditions nobody picks. Product, finance, and engineering all meet the ladder through three signals — bandwidth cost per viewer, complaints about quality, and time-to-first-frame — but most teams build their first ladder by copy-pasting Apple's reference table and never revisiting it. This calculator gives any team a content-aware starting point in under a minute, and the article below explains every rule the calculator applies so you can defend the numbers to your CTO.
How a bitrate ladder works, in one paragraph
A bitrate ladder is a list of pre-encoded versions of the same video, each at a different combination of resolution and bitrate. The list lives inside the manifest — the small text file the player downloads first. For HTTP Live Streaming, abbreviated HLS, the manifest is a multi-variant playlist with the extension .m3u8; the controlling document is Internet Engineering Task Force standard RFC 8216, §4.3.4.2. For Dynamic Adaptive Streaming over HTTP, abbreviated DASH, the manifest is the Media Presentation Description with the extension .mpd; the controlling document is ISO/IEC 23009-1:2022. Each entry in either manifest is a rung, and each rung carries a bitrate, a resolution, a codec, a frame rate, and an audio variant association. The player picks one rung at a time and switches as the network changes. That is the whole shape; everything below is about how to choose the numbers.
Use the calculator. The rest of this article explains why it gives you the answers it does.
Figure 1. The ladder is the menu. The encoder builds it once; the packager publishes it; every player picks rungs from the same list according to its own measured network.
The five rules every bitrate ladder must respect
The calculator encodes five rules. Three of them survive from Apple's 2014 fixed-ladder thinking; two come from Netflix's 2015 per-title work and the 2026 multi-codec consensus.
Rule 1 — Geometric spacing, not equal spacing
Adjacent rungs are spaced by a multiplicative factor, not by an additive step. A jump from 400 kbps to 600 kbps is a 50% increase a viewer can see; a jump from 4,000 kbps to 4,200 kbps is a 5% step that mostly wastes encoder time. The widely-used target ratio is between 1.4× and 1.7× between adjacent rungs. Apple's reference ladder in §2.7 of the HLS Authoring Specification (revision 2025-09) sits at roughly 1.5× between most steps, with two tight pairs near 1080p where the platform wants extra resolution to switch between under load.
The math is two lines:
ratio = adjacent_bitrate_high / adjacent_bitrate_low
1.4 ≤ ratio ≤ 1.7 for adjacent rungs
This calculator uses logarithmic interpolation between the top rung's base bitrate and the lowest rung's base bitrate to pick intermediate resolutions whose base bitrates fall close to the target geometric points. The result is a ladder that descends smoothly enough for adaptive bitrate algorithms to switch one rung at a time without jolting the viewer.
Rule 2 — Resolution moves with bitrate
A 400 kbps stream at 1920×1080 looks worse than a 400 kbps stream at 640×360, because the encoder is asked to spread its bit budget over too many pixels. There is a "knee" above which adding pixels stops adding visible quality at a given bitrate. The classic fix is to cluster two or three rungs at the top resolution, then drop resolution at the bottom — at 540p, 432p, 360p, and below.
This calculator respects that knee. It never gives you a top rung at the source resolution and a near-floor rung at the same resolution — those rungs would compress to the same picture quality, wasting one slot.
Rule 3 — Codec efficiency is multiplicative
H.264, abbreviated AVC, is the universal floor — every device made since 2008 can decode it. But for the same picture quality, HEVC (H.265) ships at roughly 55% of H.264's bitrate, AV1 at roughly 42%, and VP9 at roughly 65%. The numbers vary by content type and by encoder preset, but the Bitmovin 2026 codec study and the Netflix BD-rate work published 2024–2025 converge on those ratios for production presets.
The calculator multiplies the H.264 base bitrate by the codec efficiency factor:
codec_efficiency_h264 = 1.00
codec_efficiency_hevc = 0.55
codec_efficiency_av1 = 0.42
codec_efficiency_vp9 = 0.65
bitrate(codec) = bitrate(h264_reference) × codec_efficiency(codec)
A 1080p H.264 top rung at 5,000 kbps becomes a 1080p AV1 top rung at roughly 2,100 kbps with comparable VMAF — the perceptual quality metric Netflix open-sourced in 2015 and the industry adopted as the consensus visual-quality measure.
Rule 4 — Content complexity scales the whole ladder
A static cartoon and a fast-action sports broadcast both look acceptable at 2,000 kbps with completely different settings. The cartoon barely needs 1,000 kbps; the sports stream needs 3,500 kbps to avoid blocking. Netflix's 2015 Per-Title Encode Optimization paper made this the industry's foundational insight: build a ladder per title, not per platform. The 2018 Dynamic Optimizer paper extended that to a per-shot level, cutting another 10–15% bandwidth at the same VMAF.
The calculator approximates that work with a content-complexity multiplier:
| Content class | Multiplier | Examples |
|---|---|---|
| Easy | 0.70× | Animation, slideshow lectures, talking-head, low-motion screencasts |
| Standard | 1.00× | Drama, news, documentary, mid-motion VOD |
| Hard | 1.25× | Sports, action, esports, music with strobe lighting |
| Extreme | 1.45× | 4K HDR sports, dense particle motion, premium concert film |
Rule 5 — Frame rate and dynamic range have their own costs
Sixty frames per second roughly doubles the encoder's work compared to thirty. The bitrate per rung does not double — modern encoders compress temporal redundancy well — but it lifts by a factor of about 1.4×. The exact number depends on encoder preset and content; the calculator applies 1.4× for 60 fps and 1.35× for 50 fps.
High dynamic range adds another premium. HDR10 (10-bit, BT.2020 colour, PQ transfer) lifts bitrate by about 15% on the top two rungs, where bright highlights and dark shadows need the extra precision; Dolby Vision adds about 20%. The calculator only applies the HDR multiplier on the top two rungs because the lower rungs are too compressed for the HDR difference to be visible.
How the calculator builds your ladder, step by step
The algorithm runs four passes per recompute. Each pass is small enough to do by hand on a piece of paper, which is why the calculator stays predictable instead of becoming a black box.
Pass 1 — Pick the resolution set. The calculator filters its internal table of reference resolutions to those at or below your source. A 1080p source returns the subset {1080p, 720p, 540p, 432p, 360p, 270p, 234p}; a 4K source extends the same table up.
Pass 2 — Choose the number of rungs. VOD ships 9 by default; live with low-latency ships 6; real-time WebRTC ships 4; user-generated content ships 4. These numbers come from the 2025 Bitmovin Video Developer Report (167 developers, 34 countries), which lists the median rung count per workflow. The calculator then picks rungs from the resolution set so that adjacent base bitrates fall close to a geometric progression between the top and bottom rungs.
Pass 3 — Apply the multipliers. Each chosen rung's base bitrate is multiplied by codec efficiency, content complexity, frame-rate factor, and (for the top two rungs) the HDR factor. The result is rounded to the nearest 25 kbps so the manifest reads cleanly.
Pass 4 — Reshape for the audience profile. A mobile-dominant audience pushes the calculator to lift the bottom two rungs by 10% — cellular networks need a stronger floor — and to cap the top rung at 1080p. A broadband-only audience drops the bottom two rungs entirely. A living-room over-the-top audience pushes the ladder top-heavy because TVs pin to the highest available rung.
The result lands in a sortable table with seven columns: rung index, resolution, video kbps, total kbps (video plus audio), frame rate, codec string, and a one-line use hint.
A worked example: 1080p VOD drama on a global audience
Pick a typical mid-tier streaming service. The codec is H.264 (you still need the universal fallback), the source is 1080p, the frame rate is 30, the content is "standard" drama, the workflow is VOD, the audience is global, the dynamic range is standard, the audio is 128 kbps stereo AAC.
Plug those into the calculator. It returns nine rungs.
| Rung | Resolution | Video kbps | Total kbps | Use |
|---|---|---|---|---|
| 1 | 1080p (1920×1080) | 5,000 | 5,128 | Top — fibre |
| 2 | 1080p (1920×1080) | 3,200 | 3,328 | Main 1080p |
| 3 | 720p (1280×720) | 2,400 | 2,528 | Good Wi-Fi |
| 4 | 720p (1280×720) | 1,500 | 1,628 | Wi-Fi |
| 5 | 540p (960×540) | 1,400 | 1,528 | 4G LTE |
| 6 | 432p (768×432) | 725 | 853 | 4G cell |
| 7 | 360p (640×360) | 450 | 578 | 3G / 4G floor |
| 8 | 270p (480×270) | 275 | 403 | Slow cellular |
| 9 | 234p (416×234) | 175 | 303 | Mobile fallback |
Now switch the codec to AV1, the content to "hard" (action sports), and the dynamic range to HDR10. The top rung lands at about 3,000 kbps for 1080p — a 40% drop from the H.264 number, even with the sports multiplier and the HDR premium. That is the production economic argument for AV1 in one row of a table.
The math of the egress bill
The calculator's summary panel shows you the egress cost for one viewer-hour at the top rung. The arithmetic:
top_rung_total_kbps = 5,128
bytes_per_second = 5,128 × 1000 / 8 = 641,000
bytes_per_hour = 641,000 × 3600 = 2.31 × 10⁹
gigabytes_per_hour = 2.31 × 10⁹ / (1024 × 1024 × 1024) = 2.15 GB
cost_per_hour = 2.15 × $0.008 = $0.017
A platform with one million daily active viewers averaging ninety minutes a day, half on the top rung, pays roughly:
1,000,000 × 90/60 × 0.5 × $0.017 = $12,750 per day = $4.65 million per year
That is one rung of one ladder for one codec. Multiply by two codecs (H.264 + HEVC, or H.264 + AV1), and the bandwidth bill is real money. The calculator's reference rate of $0.008 per gigabyte is a 2026 mid-tier commit price; high-volume customers pay $0.003–$0.005, and short-tail customers pay $0.020+. Substitute your own number.
Figure 2. The same 1080p VOD ladder, three codecs. The top rung is the headline number; the catalogue bill is the area under each curve.
The outputs you can paste into production
The calculator emits four downloadable artefacts per recompute.
HLS multi-variant playlist. A complete .m3u8 with one #EXT-X-STREAM-INF line per rung, the right RESOLUTION, BANDWIDTH, AVERAGE-BANDWIDTH, FRAME-RATE, and CODECS attributes, and a single audio rendition group. Paste it into your origin's manifest path, and a stock player picks it up. The format follows RFC 8216, §4.3.4.2.
DASH MPD skeleton. A bare SegmentTemplate paths; the skeleton is the rendition declarations only.
FFmpeg command per rung. A copy-pasteable command for each rung that runs the right encoder (libx264, libx265, libsvtav1, libvpx-vp9), the right scale filter, the right keyframe interval (2 × fps, the production default for HLS and DASH), and the right buffer sizes. Use it for one-off encodes; for catalogue work, drive the same parameters through your transcoding cluster (AWS MediaConvert, Mux, Bitmovin, or your in-house pipeline).
JSON dump. The whole ladder, plus your input parameters and a timestamp, as a single JSON object. Useful for piping into a config-as-code workflow or for auditing what a stakeholder used at decision time.
The HLS playlist and DASH MPD are both browser-downloadable from the calculator panel; the JSON works for any automation pipeline.
A common pitfall: trusting the calculator over your own VMAF run
This calculator is a strong starting point, not a substitute for measuring quality against your own content. The codec efficiency multipliers — 0.55, 0.42, 0.65 — are industry averages on production presets, and they will be wrong for your titles by ±10% in either direction depending on encoder version, preset, content mix, and source quality. If a 5% mistake on the top rung costs your platform $200,000 a year, run a VMAF measurement on twenty representative titles before you ship.
The 2025 Mux Halfpipe paper makes this point explicitly: a single static ladder, even a content-aware one built by a calculator, leaves 5–15% bandwidth on the table compared to a real per-title encode that scores VMAF against the actual frames. Use this calculator to size your ladder. Use a per-title encoder to ship it.
Where Fora Soft fits in
Fora Soft has built video streaming, OTT, conferencing, e-learning, telemedicine, surveillance, and live commerce platforms since 2005. Every one of those workloads ships a bitrate ladder, and every one of them benefits from a ladder shaped to its content, not borrowed from another platform's docs. We use this calculator at the scoping stage to set first-encode parameters with a client, then move to per-title encoding once the platform's content profile is stable. The decision points are the same on every project: how many rungs the audience profile actually needs, which codec to add second, and where the per-title work pays back its encoder cost.
What to read next
- Bitrate ladders: classic Netflix ladder, per-title, per-shot — the deep dive on the methodology this calculator approximates.
- Adaptive bitrate streaming explained — what the player does with the rungs at runtime.
- HLS in depth: m3u8, segments, multi-variant playlists — the manifest format the calculator emits.
Talk to us / See our work / Download
- Talk to a streaming engineer — scope your ladder against your real content, not a calculator average.
- See our case studies — OTT, telemedicine, conferencing, e-learning, surveillance projects shipped since 2005.
- Download the Bitrate Ladder Quick-Reference Card — a one-page printable summary of the five rules, the codec multipliers, and the recommended rung counts per workflow.
References
- Apple Inc. HLS Authoring Specification for Apple Devices, revision 2025-09. Apple Developer Documentation. https://developer.apple.com/documentation/http-live-streaming/hls-authoring-specification-for-apple-devices — base ladder in §2.7; codec/profile recommendations in §1; HEVC-specific in §1.7.
- IETF. RFC 8216: HTTP Live Streaming, August 2017. https://www.rfc-editor.org/rfc/rfc8216 — multi-variant playlist format, §4.3.4.2; rendition group definitions, §4.3.4.1.
- ISO/IEC 23009-1:2022. Dynamic Adaptive Streaming over HTTP (DASH) — Part 1: Media presentation description and segment formats, fifth edition. International Organization for Standardization. — MPD schema and Representation element.
- Netflix Technology Blog. Per-Title Encode Optimization, 14 December 2015. https://netflixtechblog.com/per-title-encode-optimization-7e99442b62a2 — the 2015 paper that started content-aware ladders; 20% bandwidth savings at matched VMAF.
- Netflix Technology Blog. Dynamic Optimizer — A Perceptual Video Encoding Optimization Framework, March 2018. — per-shot extension; additional 10–15% savings on top of per-title.
- Katsavounidis, I. et al. "Convex Hull Prediction Methods for Bitrate Ladder Construction: Design, Evaluation, and Comparison." ACM Transactions on Multimedia Computing, Communications, and Applications, 2025. https://dl.acm.org/doi/10.1145/3723006 — academic survey of convex-hull methods.
- Mux. Instant Per-Title Encoding and Per-Title Encoding @ Scale, December 2025. https://www.mux.com/blog/instant-per-title-encoding — Halfpipe neural-network model; millisecond per-title decisions.
- Bitmovin. Video Developer Report 2025, surveying 167 developers across 34 countries. — multi-codec adoption, median rung counts per workflow, top cost-cutting strategies.
- DASH Industry Forum. DASH-IF Interoperability Guidelines for DASH-IF Implementations v5, 2024–2025. https://dashif.org/guidelines/ — Representation construction, bandwidth attribute semantics, switching set conventions.
- Streaming Learning Center. Comparing H.264, HEVC, VP9, and AV1 in SBE: From BD-Rate to Contextual ROI, 2026. https://streaminglearningcenter.com/articles/comparing-h-264-hevc-vp9-and-av1-in-sbe-from-bd-rate-to-contextual-roi.html — codec efficiency numbers consistent with the calculator's multipliers.
- AOMedia. AV1 Bitstream and Decoding Process Specification, version 1.0.0 errata 1, 2019. https://aomediacodec.github.io/av1-spec/ — codec string format
av01.*. - VMAF GitHub. Video Multi-Method Assessment Fusion. https://github.com/Netflix/vmaf — open-source perceptual quality metric used for ladder validation.
