Key takeaways
- A bitrate ladder is the set of renditions, each a resolution and bitrate pair, encoded from one source video so a player can switch quality as bandwidth changes.
- A fixed ladder reuses the same rungs for every video. A per-title ladder fits the rungs to each video’s complexity, a method Netflix described in 2015.
- Apple’s HLS authoring specification recommends a default variant near 2,000 kbit/s average bitrate and identical aspect ratios across all video variants.
- In Cloudinary, sp_auto generates an HLS or DASH adaptive stream from a single uploaded video.
What Is a Bitrate Ladder?
A bitrate ladder is the set of video renditions, each defined by a resolution and a bitrate, that are encoded from one source file for adaptive bitrate (ABR) streaming. A player picks the highest rung that the viewer’s connection and device can sustain, and moves up or down the ladder as conditions change.
A bitrate ladder is a collection of video files encoded at varying bitrates, resolutions, and qualities. These files are carefully crafted to cater to different network conditions and device capabilities. The higher the bitrate, the more data is allocated to represent a video frame, resulting in higher quality but larger file sizes. By having multiple versions of a video at different bitrates, the streaming platform can dynamically adjust and deliver the most appropriate version based on the network conditions and device capabilities.
How Does a Bitrate Ladder Work?
- Encode. The source video is encoded into several renditions, for example 360p at 700 kbps up to 1080p at 5,000 kbps.
- Package. The renditions are split into short segments and listed in a manifest, an HLS .m3u8 playlist or a DASH .mpd file.
- Measure. The player tracks download throughput and buffer level while the video plays.
- Switch. At each segment boundary the player requests the best rung it can download in time, so playback continues without stalling.
What does a bitrate ladder look like?
The table below is an illustrative H.264 ladder at 30 fps. It is a starting point, not a standard. Tune every rung against your own content.
| Rung | Resolution | Video bitrate | Typical viewer |
|---|---|---|---|
| 1 | 426 x 240 | 300 kbps | Very weak mobile connections |
| 2 | 640 x 360 | 700 kbps | Slow mobile |
| 3 | 854 x 480 | 1,200 kbps | Typical mobile |
| 4 | 1280 x 720 | 2,500 kbps | Broadband and tablets |
| 5 | 1920 x 1080 | 5,000 kbps | Desktop and TV |
| 6 | 3840 x 2160 | 12,000 kbps | 4K TVs and fast connections |
Apple’s HLS authoring specification adds rules worth building in: the default video variant should be the 2,000 kbit/s average bitrate variant, all video variants should share the same aspect ratio, and when UHD video is offered some UHD variants should stay at or below 15 Mbit/s for maximum compatibility.
Where Is The Bitrate Ladder Used?
The bitrate ladder is a crucial component in adaptive bitrate streaming (ABR), a popular technique on streaming platforms like Netflix, YouTube, and Amazon Prime Video. ABR works by continuously monitoring the viewer’s network conditions and device capabilities and adapting the video stream in real-time to provide the best possible quality without interruptions or buffering.
When a viewer initiates video playback, the streaming platform analyzes the viewer’s network conditions and device capabilities. It then selects the most suitable video file from the bitrate ladder to begin playback. As the streaming session continues, ABR measures the viewer’s bandwidth. If the available bandwidth increases or decreases significantly, it seamlessly switches to a different version of the video from the bitrate ladder that matches the new network conditions. This dynamic adaptation ensures smooth playback and optimizes both quality and performance.
Fixed Ladder vs Per-Title vs Context-Aware Ladders
| Approach | How rungs are chosen | Strength | Weakness |
|---|---|---|---|
| Fixed ladder | The same resolution and bitrate pairs for every video | Simple to run and cache | Wastes bits on simple content and under-serves complex content |
| Per-title | Trial encodes of each video find the best resolution at each quality level | Smaller files for simple content, higher quality for complex content | More encoding compute per title |
| Context-aware | Per-title rungs plus ladders tailored to device limits and network conditions | Best fit for each viewer | Most complex to operate |
Per-Title Encoding applies a custom bitrate ladder for each video title based on its unique characteristics. It considers aspects like motion, complexity, detail, and noise, utilizing these attributes to sculpt an encoding ladder. This methodology excels for Video on Demand content, where the time to analyze and encode videos isn’t restricted to real-time constraints.
Context-Aware Encoding factors in variables beyond the individual video, considering the distribution conditions and the specific devices on which the content will be viewed. As the name suggests, it maintains an awareness of the context, adjusting the encoding strategy based on network conditions and device capabilities. Context-aware encoding ensures a more holistic optimization by considering bandwidth, screen resolution, and battery life.
Netflix described the problem with a fixed ladder in 2015. Its fixed ladder topped out at 5,800 kbps, which still showed blockiness on noisy content but was far more than needed for animation at 1080p. Its per-title method runs trial encodes, measures quality, and picks points close to the convex hull of the bitrate-quality curves, choosing bitrates from a finite set whose neighbors are about 5% apart. Netflix also designed extra ladders for devices limited to 480p or 720p.
How many rungs does a ladder need?
- Production ladders commonly use 4 to 8 rungs. Fewer rungs cut encoding and storage cost. More rungs give smoother switching.
- Space rungs so each step up is a visible quality gain. Netflix designs per-title ladders so adjacent rungs differ by about one just-noticeable difference.
- Check each rung with a quality metric such as VMAF instead of judging by bitrate alone.
- For on-demand HLS, keep peak bitrate within 200% of the average, as Apple’s specification recommends.
How does codec choice change the ladder?
More efficient codecs reach the same quality at lower bitrates, so each rung shifts down. Netflix reported in December 2025 that AV1 sessions use about one third less bandwidth than AVC and HEVC sessions, and that AV1 carries about 30% of Netflix viewing. Because not every device decodes AV1, a common approach is to keep an H.264 ladder as the fallback and add AV1 or HEVC ladders for devices that support them.
| Codec | Bitrate for the same quality | Device support | Use it for |
|---|---|---|---|
| H.264 / AVC | Baseline | Effectively universal | The fallback ladder every viewer can play |
| HEVC / H.265 | Roughly 30 to 50% lower than H.264 | Apple devices, most smart TVs, newer Android | A second ladder for devices that decode it |
| VP9 | Comparable to HEVC | Chrome, Android, YouTube | Browser delivery without HEVC licensing |
| AV1 | About one third lower than AVC and HEVC on Netflix sessions | Newer browsers, TVs and phones, growing | The efficiency ladder where decoding exists |
Which platforms build the ladder for you?
Most teams do not hand-build ladders. The question is usually which platform generates and delivers them.
| Platform | How the ladder is produced | Notable for |
|---|---|---|
| Cloudinary | sp_auto generates HLS or DASH renditions from one upload, or define custom representations | One API covering upload, transformation and adaptive delivery for both video and images |
| Mux | Automatic per-title encoding on ingest | Developer-first video infrastructure and playback analytics |
| Cloudflare Stream | Automatic renditions on upload, delivered over Cloudflare’s network | Bundled delivery and simple per-minute pricing |
| Bitmovin | Configurable per-title encoding | Fine-grained control over encoding profiles |
| api.video | Automatic transcoding into an adaptive ladder | Lightweight API for embedding video quickly |
Common mistakes when building a bitrate ladder
- Spacing rungs by bitrate instead of by visible quality. Two rungs 500 kbps apart can look identical. Check each step with a metric such as VMAF.
- Inconsistent keyframe intervals across rungs. If GOP sizes differ, the player cannot switch cleanly at a segment boundary and viewers see artefacts.
- No low rung. Without a 300 to 700 kbps option, viewers on weak connections buffer instead of dropping to a lower quality.
- Mixed aspect ratios between variants. Apple’s HLS specification expects all video variants to share one aspect ratio.
- One ladder for every device. A phone capped at 720p gains nothing from a 4K rung but still pays the storage and encoding cost.
How do you build a bitrate ladder in Cloudinary?
Cloudinary generates HLS or MPEG-DASH adaptive bitrate streams from a single uploaded video. Set the streaming profile to auto (sp_auto) and request a .m3u8 (HLS) or .mpd (DASH) extension, and Cloudinary chooses the representations on the fly. You can also pick a predefined streaming profile or create your own with custom representations.
HLS: https://res.cloudinary.com/<cloud_name>/video/upload/sp_auto/<public_id>.m3u8
DASH: https://res.cloudinary.com/<cloud_name>/video/upload/sp_auto/<public_id>.mpd
Check before you add transformations. Only a limited set of video transformations can be combined with sp_auto. 4K output requires setting a maximum resolution. See the Cloudinary adaptive bitrate streaming documentation for the current list.
Delivering the ladder is the other half of the job. Cloudinary serves the renditions over multi-CDN delivery, so the player reaches a nearby edge wherever the viewer is, and protected content can be restricted with signed URLs that carry an expiry and with token-based access at the edge. Assets are encrypted with AES-256 at rest and TLS in transit.
Frequently asked questions
What is a bitrate ladder in simple terms?
It is a menu of the same video at different sizes and quality levels. The player picks the best option for the viewer’s connection and switches as the connection changes.
What is the difference between a bitrate ladder and adaptive bitrate streaming?
Adaptive bitrate streaming is the delivery technique, and the bitrate ladder is the set of renditions it chooses from. The player’s ABR logic decides when to switch rungs.
How many rungs should a bitrate ladder have?
Commonly 4 to 8. The right number depends on your resolution range, codec and audience. Test whether each step up is a visible quality gain.
What is per-title encoding?
Per-title encoding analyses each video and builds a custom ladder from its complexity. Netflix introduced the approach in 2015 so that simple and complex videos would not receive the same bitrates.
Does AV1 or HEVC change the bitrate ladder?
Yes. More efficient codecs reach the same quality at lower bitrates, so rungs move down. Keep an H.264 ladder as a fallback for devices that cannot decode newer codecs.
Additional Resources You May Find Useful:
