Updated October 2026: new Netflix (AV1 at 30% of viewing), Zoom, Ookla and FCC bandwidth data, AV2 v1.0 test results, corrected 4:2:0 and studio bitrate math, and new sections on uncompressed file size, bits per pixel and SMPTE ST 2110.
Why this matters
Short answer. Bitrate compression is the job a video codec does: it cuts the number of bits a video needs per second while keeping the picture looking the same. To compress a video means to drop the detail the eye will not miss and to describe what repeats between frames once, instead of storing every pixel of every frame. The bitrate formula for raw video is width × height × bits per pixel × frames per second: 1080p at 30 fps in 8-bit RGB is about 1.49 Gbps uncompressed, while Netflix asks for only 5 Mbps to stream 1080p in 2026 — roughly a 300× reduction, and that reduction is what compression buys. 1
If you build, buy, sell, or operate anything that touches video — a streaming product, a video-conferencing app, a security-camera fleet, an e-learning platform, a live event — bitrate is the lever that controls your bandwidth bill, your video quality, your buffer rate, and the size of every storage invoice you will ever sign. Pick a bitrate that is too high and your costs blow up while half your audience cannot watch on a phone; pick one too low and the picture turns into a mosaic of compression artefacts and your support inbox fills with complaints. The decision touches product managers, founders, marketing leads, and operations people every quarter, often without their realising that the same simple equation drives every codec, every CDN, and every video paywall. By the end of this article you will be able to compute the uncompressed weight of any video format on the back of a napkin, see why a modern codec is a 200× to 500× discount, and tell when a vendor's bitrate claim is honest and when it is theatre.
What "bitrate" actually means
A bit is a binary digit: a single zero or one. A digital video file is, at its most basic level, a very long sequence of zeros and ones. Bitrate, often written as bps for "bits per second", is the speed at which that sequence flows — how many of those zeros and ones the file produces, or a network has to carry, every second the video plays.
A useful analogy: think of video data as water flowing through a pipe. The pipe is your internet connection or your hard drive's read speed. The bitrate is the litres-per-second the water is moving at. If the bitrate the video demands is higher than the pipe can carry, the water backs up — in video terms, the player buffers, freezes, or downgrades to a worse-looking version that fits. Get the bitrate right and the water flows smoothly and the picture stays clean.
The standard units climb in steps of one thousand. One kilobit per second (kbps) is a thousand bits. One megabit per second (Mbps) is a thousand kilobits, or one million bits. One gigabit per second (Gbps) is a thousand megabits, or one billion bits. A typical low-quality YouTube clip is one or two Mbps. Netflix asks for at least 15 Mbps to stream 4K (2026). An uncompressed 4K60 studio master in 12-bit 4:2:2 is about twelve Gbps — roughly 800 times the Netflix figure. The gap between those last two numbers is the entire reason video compression exists as an industry. 1
A word on bits versus bytes. A byte is eight bits, written with a capital B. Disk sizes are usually given in bytes (gigabytes, terabytes); network speeds are usually given in bits (gigabits, megabits). When somebody says "my home internet is a hundred meg", they almost always mean a hundred megabits per second, not megabytes. To convert a download speed in megabits per second into the file size in megabytes you can save per second, divide by eight. A 100 Mbps connection saves 12.5 megabytes per second, which is why a 1 GB file takes roughly 80 seconds, not 10. Mixing up bits and bytes by a factor of eight is the most common bandwidth mistake in the entire industry and you should expect to catch it in vendor decks at least once a month.
The math of uncompressed video — three multiplications
Every uncompressed video format in the world reduces to one simple equation. A frame is a grid of pixels. Each pixel is described by some number of bits. The video plays at some number of frames per second. Multiply those three numbers together and you have the raw bitrate.
bitrate (bits per second) = width × height × bits per pixel × frames per second
Three multiplications, that is the whole formula. Walk through it once out loud with a real example so the next time you see a vendor claim you can have an "uncompressed live feed" over a 1 Gbps link, you can do the math in your head and call the bluff.
Example one — 1080p at 30 fps, 8-bit RGB colour. A 1080p frame is 1920 pixels wide and 1080 pixels tall. Each pixel in 8-bit RGB is described by three channels — red, green, blue — at 8 bits each, so 24 bits total per pixel. The video plays at 30 frames per second.
bitrate = 1920 × 1080 × 24 × 30
= 2,073,600 pixels per frame
× 24 bits per pixel
× 30 frames per second
= 1,492,992,000 bits per second
≈ 1.49 Gbps
So an uncompressed 1080p30 stream weighs about one and a half gigabits per second — already more than most home internet connections in the world can carry. This is the cheapest of the three examples here — and the 8-bit 4:2:0 format used for most consumer video halves it again, to about 0.75 Gbps.
Example two — 4K at 60 fps, 10-bit YCbCr 4:2:0. A 4K frame is 3840 × 2160 = 8,294,400 pixels. The 10-bit YCbCr 4:2:0 format used in modern HDR delivery encodes brightness at full resolution and the two colour channels at quarter resolution, which works out to an average of 15 bits per pixel: in 8-bit that is 8 bits of luma plus 2 bits for each of the two quarter-resolution chroma channels, 12 bits per pixel in total, and 10-bit scales that by ten-over-eight to exactly 15.
bitrate = 3840 × 2160 × 15 × 60
= 8,294,400 pixels per frame
× 15 bits per pixel
× 60 frames per second
= 7,464,960,000 bits per second
≈ 7.46 Gbps
Studio formats carry more chroma and more bits. The 10-bit 4:2:2 format used for broadcast contribution and mezzanine masters is 20 bits per pixel, so 4K60 comes to about 10 Gbps; 12-bit 4:2:2 (24 bits per pixel) comes to about 11.9 Gbps — the “12 Gbps” studio figure used throughout this article — and full 12-bit RGB used in colour-grading suites reaches roughly 18 Gbps. Those numbers are why a professional edit suite needs a Thunderbolt 4 (40 Gbps) or Thunderbolt 5 (80 Gbps, up to 120 Gbps with Bandwidth Boost) connection and not a USB 3 cable (5 Gbps). 17 2
Example three — 8K at 120 fps, 12-bit RGB. An 8K frame is 7680 × 4320 = 33,177,600 pixels. Twelve-bit RGB is 36 bits per pixel.
bitrate = 7680 × 4320 × 36 × 120
= 143,327,232,000 bits per second
≈ 143 Gbps
That is three times what an HDMI 2.1 cable carries (48 Gbps) and still about 1.5 times the 96 Gbps of HDMI 2.2, the newest consumer video link, whose full specification was published in June 2025 16 — which is to say: raw 8K120 does not fit through any consumer cable you can buy in 2026. The pattern is short — every doubling of resolution multiplies bitrate by four, every doubling of frame rate doubles it, and every extra bit of colour depth adds 10 to 12.5 per cent. The numbers grow fast, and they grow without compression on the back of the envelope.
Figure 1. Uncompressed video bitrate climbs faster than anything else in your stack. The same axis that fits 1080p comfortably reaches the edge of the chart at 8K — a 96× jump in a single line.
How big is uncompressed video? Size per second, minute and hour
To turn the bitrate into file size, divide by eight to get bytes and multiply by the running time. An hour of uncompressed 4K60 in 10-bit 4:2:0 fills about 3.4 TB; an hour of 1080p30 in 8-bit RGB fills about 672 GB. Real camera originals are smaller because cameras record lightly compressed formats, but every edit, effect and AI model in the pipeline works on these raw frames in memory.
| Format | Bits per pixel | Bitrate | Per second | Per minute | Per hour |
|---|---|---|---|---|---|
| 1080p30, 8-bit 4:2:0 | 12 | 0.75 Gbps | 93 MB | 5.6 GB | 335.9 GB |
| 1080p30, 8-bit RGB | 24 | 1.49 Gbps | 187 MB | 11.2 GB | 671.8 GB |
| 4K30, 8-bit 4:2:0 | 12 | 2.99 Gbps | 373 MB | 22.4 GB | 1.34 TB |
| 4K60, 10-bit 4:2:0 (HDR delivery) | 15 | 7.46 Gbps | 933 MB | 56.0 GB | 3.36 TB |
| 4K60, 10-bit 4:2:2 (mezzanine) | 20 | 9.95 Gbps | 1.2 GB | 74.6 GB | 4.48 TB |
| 8K60, 10-bit 4:2:0 | 15 | 29.86 Gbps | 3.7 GB | 223.9 GB | 13.44 TB |
Bits per pixel: the number that compares any two streams
Run the formula backwards and you get bits per pixel (bpp) for a compressed stream: bpp = bitrate ÷ (width × height × frames per second). Raw 8-bit 4:2:0 video is 12 bpp. Netflix’s 15 Mbps recommendation for 4K at 24 fps works out to about 0.075 bpp, and YouTube’s recommended 12 Mbps upload for 1080p60 to about 0.096 bpp — a delivered stream keeps well under one per cent of the raw bits. Bits per pixel lets you compare a 4K offer with a 1080p offer, or one vendor’s ladder with another’s, on the same scale. Our bitrate and bits-per-pixel calculator does this arithmetic for any resolution, frame rate and codec.
SMPTE ST 2110: what uncompressed video over IP needs
Broadcast plants still move uncompressed video, now over IP instead of SDI. SMPTE ST 2110-20 carries only the active picture, with no blanking, so its bandwidth is the formula above plus a few per cent of RTP, UDP and IP packet overhead. 18 1080p59.94 in 10-bit 4:2:2 is 1920 × 1080 × 20 × 59.94 ≈ 2.49 Gbps of active video, so one 10 GbE port carries three such streams with headroom; 2160p59.94 in the same format is ≈ 9.94 Gbps, which leaves no headroom on 10 GbE and is planned on 25 GbE links.
What we have to flow through: real pipes, real bandwidth
Those uncompressed numbers only matter when you compare them to the pipes available to carry them. The pipes are smaller than people think.
In the United States, the Federal Communications Commission’s 2026 broadband progress report kept 100 Mbps down / 20 Mbps up as the benchmark for advanced broadband, found that 96.9 per cent of Americans had access to it by June 2025, and dropped the earlier long-term goal of 1 Gbps / 500 Mbps. 3 The 100 / 20 benchmark itself dates from March 2024, when the FCC raised it from 25 / 3. 4 That 20 Mbps upload is the hard ceiling for anybody trying to push live video out of a home network.
Mobile networks vary wildly by country. Ookla’s Speedtest Global Index, the most-cited public benchmark in the telecoms industry, put the global median at about 109 Mbps for mobile download and 130 Mbps for fixed broadband in August 2026 — but the median hides a huge spread between national markets. 5 The United Arab Emirates leads mobile at above 745 Mbps median thanks to aggressive 5G build-out, while many markets are still in the low double digits. For a real product the rule is: design for the bottom of your audience’s bandwidth distribution, not the top.
Inside a building the picture is different again. Wi-Fi 6 in a quiet apartment delivers 300 to 700 Mbps to a phone or laptop in the same room as the router, but drops below 50 Mbps when the user walks two rooms away or shares the link with three other devices on a video call. Wired ethernet inside a corporate office is usually 1 Gbps per port, but the up-link from the building to the internet is shared between every employee and rarely above 10 Gbps. The fact that nobody in a real product ever delivers uncompressed video — to anyone, on anything — is not a quirk; it is a hard physical consequence of these numbers.
| Pipe | Realistic 2026 speed | Can it carry uncompressed 1080p30 (1.5 Gbps)? | Can it carry uncompressed 4K60 10-bit (7.5 Gbps)? |
|---|---|---|---|
| FCC broadband benchmark (US), download / upload | 100 / 20 Mbps | No | No |
| Global median fixed broadband (Aug 2026) | 130 Mbps | No | No |
| Global median mobile download | 109 Mbps | No | No |
| 5G mid-band in a good market | 400 Mbps | No | No |
| Wi-Fi 6 in the same room | 600 Mbps | No | No |
| Office ethernet port | 1 Gbps | No | No |
| HDMI 2.1 cable inside a TV | 48 Gbps | Yes | Yes |
| HDMI 2.2 cable (spec 2025) | 96 Gbps | Yes | Yes |
| Thunderbolt 4 inside a studio | 40 Gbps | Yes | Yes |
| Thunderbolt 5 inside a studio | 80 Gbps | Yes | Yes |
| 12G-SDI in a broadcast truck | 12 Gbps | Yes | Yes |
The table makes the point with no commentary needed. Every consumer network connection is smaller than every uncompressed video format above 1080p, and most are smaller than even 1080p; only short cables inside a room (HDMI, Thunderbolt) and studio links carry raw video. The job of a video codec is to bridge that gap.
A simple mental formula for compressed bitrate
The compressed bitrate is what you actually ship. There is no closed-form equation for it the way there is for the uncompressed case — modern codecs are nonlinear and content-dependent — but a four-variable mental model gets you within a factor of two of reality, which is good enough for product conversations and budget arithmetic.
bitrate ≈ (target quality × scene complexity × resolution × frame rate)
÷ codec efficiency
Read each variable in turn. Target quality is how good you want the picture to look, usually expressed as a VMAF score (see the quality metrics article for the full definition) or a quality preset. Scene complexity is how much new information is in each frame: a static talking-head scene is low complexity, a crowd in a stadium under flashing lights is high complexity, and the bitrate gap between them at the same quality is typically 5 to 10×. Resolution and frame rate multiply in linearly the way they did in the uncompressed equation. Codec efficiency is the only variable that improves over time as the industry releases newer codecs — H.264, H.265, AV1, VVC — each generation needing about 30 to 50 per cent less bitrate than the last at the same quality, on average. 6
The mental model is not a literal formula you should plug into a spreadsheet. It is a way to predict which way the bitrate moves when one variable changes. Double the resolution at the same codec and quality: bitrate roughly quadruples (because the pixel count goes up 4×). Switch from H.264 to AV1 at the same quality: bitrate roughly halves in lab tests, and drops by about a third in Netflix’s production data, where part of the saving went into higher quality. Move from a talking-head to a sports scene at the same codec, resolution, and quality: bitrate triples or more. Lower the target VMAF from 95 to 80 at the same content: bitrate roughly halves. These are the relationships that make every codec roadmap and every bitrate ladder make sense.
The next section turns the mental model into real numbers from the streaming services that the rest of the industry copies.
Figure 2. The four input levers that drive compressed bitrate, and the codec generation that divides them. Move one lever, the output moves predictably.
What real services actually use
Numbers from real platforms anchor the math. The table below shows the bitrates that the three biggest names in video each ship today, alongside what their uncompressed equivalent would have weighed. Every figure is from an official source, dated 2024 or 2025 so it survives the next codec cycle. The full source list sits at the bottom of the article.
| Service & format | Codec | Shipped bitrate | Uncompressed equivalent | Compression ratio |
|---|---|---|---|---|
| Netflix 1080p stream | H.264 | ≈ 5 Mbps (recommended connection) 1 | 1,492 Mbps | ≈ 300× |
| Netflix 4K HDR stream | H.265 | 8–16 Mbps avg, peaks ≈ 17 Mbps 7 | 2,986 Mbps (4K24, 10-bit 4:2:0) | ≈ 200–370× |
| YouTube 1080p60 SDR upload | H.264 | 12 Mbps (recommended) 8 | 2,985 Mbps | ≈ 250× |
| YouTube 4K60 SDR upload | H.264 | 53–68 Mbps (recommended) 8 | 11,943 Mbps | ≈ 200× |
| Zoom 1080p HD video call | H.264 | 3.0–3.8 Mbps (peak) 9 | 1,492 Mbps | ≈ 400–500× |
| 4K Blu-ray disc | H.265 | up to 128 Mbps peak | 2,986 Mbps (4K24, 10-bit 4:2:0) | ≈ 25× at peak |
The first thing to notice is that compression ratios on real streaming services land in roughly the 200× to 500× range. Netflix’s per-shot encoding pipeline (the “Dynamic Optimizer”, or DO) needs only 58 per cent of the storage of its old fixed ladder for the same quality, so the same title now ships at well under the bitrate it used to. 7
The second thing to notice is that the same content compressed at the same quality looks very different on different services. Zoom budgets 3.0–3.8 Mbps for a 1080p call because real-time calls prioritise latency and reliability over per-frame sharpness — a single dropped video call destroys far more user trust than a slightly soft picture. Netflix spends about two-thirds more bits per pixel (≈ 0.10 bpp for 1080p at 24 fps against ≈ 0.06 bpp for a 1080p30 Zoom call) because its content is recorded, encoded for hours, and meant to look indistinguishable from a Blu-ray. YouTube sits in the middle. The mental formula above explains all three: the "target quality" variable is dialled way down on a video call and way up on a movie.
The third thing to notice is the Blu-ray row. Physical-media discs ship at ratios closer to 25–50× because storage is fixed — the disc holds what it holds — and quality is the only competitive lever. Streaming services live at ratios of several hundred to one because bandwidth is metered and quality is "good enough for the device the viewer is using". Two different optimisation problems, two different points on the same compression curve.
Common mistake — confusing average bitrate with peak bitrate
The single most common error in product discussions is treating the shipped bitrate as a single number. It almost never is. Modern codecs use variable bitrate (VBR) encoding: the bitrate goes up during action scenes and down during talking-head scenes, and what is reported is the average over the whole title. A Netflix 4K HDR stream that averages 8–16 Mbps over a title can peak around 17 Mbps in an action burst and drop to a few Mbps in quiet dialogue — which is why Netflix asks viewers for a 15 Mbps connection rather than the average. Networks have to size for the peak, not the average — if the user's pipe can only carry 12 Mbps and the codec asks for 17 Mbps mid-scene, the player buffers. The fix is a capped CRF or a constrained VBR encoding setting that lets the bitrate float but never exceeds a hard ceiling. The full topic gets its own article in the rate control section; for now, treat any single bitrate number with suspicion until you know whether it is the average, the peak, or the maximum that the network has to plan for.
Codec efficiency through the generations
The "codec efficiency" lever in the mental formula is the only one that gets cheaper over time. Every new codec generation buys roughly 30 to 50 per cent bitrate savings at the same visual quality, and the savings compound across generations. The compounding is why a 2026 streaming service running AV1 ships roughly half the bits a 2010 service running H.264 shipped for the same picture, and about a quarter of what MPEG-2 needed.
| Codec | Year shipped | Approx. bitrate vs H.264 baseline | Typical Netflix 4K HDR Mbps (modelled) |
|---|---|---|---|
| MPEG-2 | 1995 | 200% (i.e. 2× more than H.264) | ≈ 60 |
| H.264 / AVC | 2003 | 100% (baseline) | ≈ 30 |
| H.265 / HEVC | 2013 | 55–60% 10 | ≈ 16 |
| VP9 | 2013 | 65–75% | ≈ 20 |
| AV1 | 2018 | 40–50% 11 | ≈ 12 |
| H.266 / VVC | 2020 | 30–40% 12 | ≈ 9 |
| AV2 | 2026 (v1.0 spec) | ≈ 30% (≈ 30% below AV1) 15 | ≈ 8 (modelled) |
Two things to notice. First, the percentages are bitrate-at-equal-quality, not file-size-at-fixed-bitrate. A 50 per cent number means the new codec needs only half the bitrate to look the same as the old one — equivalent to saying the new codec is twice as efficient at the same quality. Second, every published number is the average across a wide test set, and the per-content spread is enormous. Slow, talky content gains far more from a new codec than noisy hand-held sports footage does; an honest vendor quotes the range, not the average alone.
The codec roadmap matters to a product manager mainly because each step down the column is a chance to reduce the bandwidth bill without changing the picture. A streaming service that re-encodes its catalogue from H.264 to AV1 cuts its egress cost by roughly a third to a half at the same VMAF — frequently the largest line-item cost saving in a streaming budget. The cost of doing the re-encode itself, however, is non-trivial: AV1 software encoding is several times slower than H.264 at comparable presets, and hardware AV1 encoders arrived only recently — NVIDIA from the Ada generation, Intel Arc, AMD RDNA 3 — while Apple silicon decodes AV1 (A17 Pro, M3 and later) but still has no AV1 hardware encoder. 19 Netflix’s own numbers show why the switch pays anyway: by December 2025 AV1 carried about 30 per cent of its on-demand viewing, and AV1 sessions used about one-third less bandwidth than AVC and HEVC sessions with 45 per cent fewer buffering interruptions. 14 The "is it worth it" calculation is the subject of the codec ROI article.
Figure 3. Every codec generation needs roughly 30–50 per cent less bitrate than the previous one at the same visual quality. The compounding across generations is why AV1 needs roughly half the bitrate of H.264 in lab tests, and about a quarter of MPEG-2, for the same picture.
The Shannon limit and where the industry is going
A theoretical question hangs over every codec roadmap: how far can compression go? The answer, surprisingly, has a real lower bound. Claude Shannon's source coding theorem, the 1948 result that founded information theory, says that any data source has an irreducible entropy — a floor below which no lossless codec can compress without losing information. For video, that floor depends on the actual information content of the scene; a single-colour blank frame has near-zero entropy and can be compressed to a handful of bytes, while a hand-held shaky shot of a leaf canopy has near-maximum entropy and resists compression almost completely. 13
Real codecs are still well above that floor for natural video, and each generation keeps finding more. AV2, whose v1.0 specification the Alliance for Open Media released in June 2026, measured about 30 per cent lower bitrate than AV1 in the alliance’s own common test conditions (29.8 per cent on PSNR and 33.8 per cent on VMAF in the random-access configuration). 15 Neural codecs (end-to-end learned compression) are the other path chasing the remaining gap. Our AV2 rollout article covers when it will reach real devices, and the theory is in the Shannon-limit article. For now, the takeaway is that we are not at the bottom yet — and the bitrate column above will keep shrinking.
The other near-term shift is per-title and per-shot encoding, where every piece of content gets its own bespoke bitrate ladder instead of a one-size-fits-all preset. Netflix introduced per-title encoding in 2015 and later moved to per-shot optimisation, which by 2023 covered its entire HDR catalogue with a ladder that takes 58 per cent of the old storage at the same quality — the largest single optimisation a streaming service can deploy without changing its codec stack. 7 Most of the industry still runs fixed or per-title ladders, which is where the next easy saving sits.
Frequently asked questions
What is bitrate compression?
Bitrate compression is what a video codec does: it lowers the number of bits a video needs per second while keeping the picture looking the same. Streaming services typically ship 200 to 500 times fewer bits than the raw video contains.
What does it mean to compress a video?
To compress a video means to re-encode it so it takes fewer bits: the codec drops detail the eye will not notice and stores what repeats between frames only once. The result is a smaller file and a lower bitrate at a similar visual quality.
What is the primary reason for compressing video files?
The primary reason is to decrease file size, and with it the bitrate. Raw 1080p30 is about 1.49 Gbps, far more than any home or mobile connection carries, so video has to be compressed before it can be stored cheaply or streamed at all.
What is the bitrate formula?
For uncompressed video, bitrate = width × height × bits per pixel × frames per second. 1920 × 1080 × 24 × 30 gives 1.49 Gbps for 1080p30 in 8-bit RGB; for compressed video, the same formula run backwards gives bits per pixel.
How much data does an hour of streaming use?
Divide the bitrate by eight and multiply by 3,600 seconds: a 5 Mbps 1080p stream is about 2.25 GB per viewer-hour and a 15 Mbps 4K stream is about 6.75 GB per viewer-hour. That delivered figure, not the raw size, is what a CDN bill is built on.
How big is uncompressed 4K video?
Uncompressed 4K60 in 10-bit 4:2:0 is about 7.46 Gbps, or roughly 56 GB per minute and 3.4 TB per hour. In 8-bit 4:2:0 at 30 fps it is about 3 Gbps, or roughly 22 GB per minute.
What is a video compression ratio?
The compression ratio is the uncompressed bitrate divided by the compressed bitrate. A 1080p stream at 5 Mbps against 1.49 Gbps raw is about 300:1; real streaming services land between roughly 200:1 and 500:1.
What bitrate does 4K at 60 fps need?
For upload, YouTube recommends 53–68 Mbps for 4K60 SDR and 66–85 Mbps for HDR. For viewing, Netflix asks for a connection of at least 15 Mbps for 4K, because delivery encodes are far more aggressive than upload masters.
How much bandwidth does SMPTE ST 2110 need?
ST 2110-20 carries only active video, so 1080p59.94 in 10-bit 4:2:2 needs about 2.49 Gbps plus a few per cent of packet overhead, and 2160p59.94 needs about 9.94 Gbps, which is planned on 25 GbE links.
Free download: Bitrate Math Cheat SheetA one-page A4 reference with the uncompressed bitrate formula, the four-lever mental model, the bitrates Netflix, YouTube and Zoom actually ship, and the codec efficiency ladder from MPEG-2 to AV2.Where Fora Soft fits in
Fora Soft has been building video products since 2005, and every one of them — video conferencing, video streaming, OTT and Internet TV, video surveillance, e-learning, telemedicine, AR/VR — runs into the same bitrate math the moment it goes live. On WebRTC video conferencing projects the question is how to keep a 1080p call under 2 Mbps so it survives a bad mobile connection; on OTT delivery the question is which codec ladder buys the right VMAF for the lowest CDN bill; on surveillance the question is how to fit thirty H.265 streams over a single uplink without losing the moments the camera was bought to catch. The math in this article is the same math we ran on the first day of every one of those 250+ shipped projects, and it is the math we run on day one of the next one. Our video encoding and processing development team turns it into codec and ladder choices, and our WebRTC development team applies it to keep real-time calls stable on weak mobile networks. For streaming launches, our OTT and IPTV platform development team sizes the bitrate ladder and the CDN budget against the bandwidth your viewers actually have.
The book
Video Encoding: A Complete Guide to Video Compression
This article is the first page of a 1,500-page argument: the three multiplications that give you 1.49 Gbps, and then every mechanism that turns 1.49 Gbps into the 4–6 Mbps a viewer actually receives. The book walks the four levers one at a time — what a VMAF target really buys, how scene complexity moves the number, where rate control decides between average and peak — and then the codec ladder from MPEG-2 to AV2 with the measurements behind each generation’s 30–50%. Written by Nikolay Sapunov, CEO at Fora Soft.
How many bits does your video actually need?
Tell us what you capture, what quality your viewers expect and what pipe they watch over, and we will do this math on your numbers: the bitrate ladder your content needs, what a codec switch is worth against what the re-encode costs, and where your peaks will break someone’s connection. 250+ video products shipped since 2005.
See our case studies
Case study
Worldcast Live
Concert feeds running at 1.5 Gb/s to 10,000 simultaneous viewers with 0.4–0.5 s latency — the case where the peak, not the average, is what the network has to be sized for.
Case study
Speed.Space
Remote production used on Netflix, EA and HBO shoots, recording 1080p at 8 Mbps — the four levers set per shoot, before a single frame is captured.
Case study
Mindbox
AI video management in 50+ deployments, pulling RTSP from cameras of every vintage through FFmpeg into HLS — where dozens of streams have to share one uplink and every Mbps is budgeted.
What to read next
Quality
Objective Quality Metrics: PSNR, SSIM, MS-SSIM, VMAF
The “target quality” lever with a number on it — and how to tell whether a bitrate cut actually looks worse.
Rate control
Rate Control: CBR, VBR, CRF, ABR, Capped CRF
Where average and peak bitrate part company, and the capped-CRF setting that keeps the peak from breaking a player.
Codecs
Comparison Table: MPEG-2, H.264, H.265, VP9, AV1, VVC
The efficiency ladder from the chart above, with the licensing, device support and encode cost that come with each rung.
Tooling
Per-Title and Per-Scene Encoding: Smart Bitrate Ladders
The 20–50% saving Netflix took without changing codec, and what it takes to run the same trick yourself.
-
Netflix Help Center, “Netflix-recommended internet speeds”. At least 3 Mbps for HD (720p), 5 Mbps for Full HD (1080p), 15 Mbps for Ultra HD (4K). https://help.netflix.com/en/node/306. Accessed 2026-10-24. ↩
-
SMPTE ST 2110 and BT.709 / BT.2020 colour standards, uncompressed 4:2:0 vs 4:4:4 pixel-bit counts. https://www.itu.int/rec/R-REC-BT.2020. Accessed 2026-05-16. ↩
-
Federal Communications Commission, 2026 Section 706 broadband progress report, as reported by Mobile World Live, August 2026. Keeps the 100 / 20 Mbps benchmark; 96.9 per cent of the US population had access at or above it by June 2025; the planned 1 Gbps / 500 Mbps long-term benchmark was removed. https://www.mobileworldlive.com/fcc/us-fcc-approves-broadband-progress-report/. Accessed 2026-10-24. ↩
-
Federal Communications Commission, "FCC Increases Broadband Speed Benchmark", March 2024. Raised the high-speed broadband definition to 100 Mbps download / 20 Mbps upload from the prior 25 / 3. https://docs.fcc.gov/public/attachments/DOC-401205A1.pdf. Accessed 2026-05-16. ↩
-
Ookla Speedtest Global Index, August 2026: global median 109.05 Mbps mobile download and 129.68 Mbps fixed broadband download; UAE first in mobile at above 745 Mbps median (2026 index). https://www.speedtest.net/global-index. Accessed 2026-10-24. ↩
-
Alliance for Open Media, AV1 specification overview and bitrate-savings test results vs H.264 / H.265 across the AOM common test conditions. https://aomedia.org/av1-features/. Accessed 2026-05-16. ↩
-
Netflix Technology Blog, "All of Netflix's HDR video streaming is now dynamically optimized", 2023. Per-shot encoding pipeline; HDR-DO ladder occupies 58 per cent of the storage of the prior fixed-bitrate ladder at the same quality. https://netflixtechblog.com/all-of-netflixs-hdr-video-streaming-is-now-dynamically-optimized-e9e0cb15f2ba. Accessed 2026-05-16. ↩↩↩
-
YouTube Help, "Recommended upload encoding settings". 1080p60 at 12 Mbps SDR / 18 Mbps HDR; 4K60 at 53–68 Mbps SDR / 66–85 Mbps HDR. https://support.google.com/youtube/answer/1722171. Accessed 2026-05-16. ↩↩
-
Zoom Library, “Calculating bandwidth usage for Zoom Meetings and Phone”. Estimated peak for 1080p HD: 3.8 Mbps up / 3.8 Mbps down one-on-one, 3.8 / 3.0 Mbps in group meetings; 720p HD 1.2 / 1.2 Mbps one-on-one. https://library.zoom.com/admin-corner/network-management/quality-of-service-and-network-best-practices-explainer/calculating-bandwidth-usage-for-zoom-meetings-and-phone. Accessed 2026-10-24. ↩
-
ITU-T Recommendation H.265 (HEVC); HEVC was designed for 50 per cent bitrate savings vs H.264 at equal subjective quality across the JCT-VC test set. https://www.itu.int/rec/T-REC-H.265. Accessed 2026-10-24. ↩
-
Alliance for Open Media, AV1 overview, and production data from Netflix (2025): AV1 sessions use about one-third less bandwidth than AVC and HEVC sessions. https://aomedia.org/av1-features/. Accessed 2026-10-24. ↩
-
Joint Video Experts Team (JVET) of ITU-T VCEG and ISO/IEC MPEG, VVC verification test results. H.266 / VVC designed for 30–50 per cent bitrate savings vs HEVC at equal subjective quality. https://www.itu.int/rec/T-REC-H.266. Accessed 2026-05-16. ↩
-
Claude E. Shannon, "A Mathematical Theory of Communication", Bell System Technical Journal, vol. 27, July and October 1948. Source coding theorem and the entropy floor for lossless compression. https://people.math.harvard.edu/~ctm/home/text/others/shannon/entropy/entropy.pdf. Accessed 2026-05-16. ↩
-
Netflix Technology Blog, “AV1 — Now Powering 30% of Netflix Streaming”, December 2025. About 30 per cent of on-demand viewing on AV1; AV1 sessions use about one-third less bandwidth than AVC/HEVC and have 45 per cent fewer buffering interruptions. https://netflixtechblog.com/av1-now-powering-30-of-netflix-streaming-02f592242d80. Accessed 2026-10-24. ↩
-
Alliance for Open Media, “Alliance for Open Media Releases AV2 Codec”, June 2026 (https://aomedia.org/press%20releases/Alliance-for-Open-Media-Releases-AV2-Codec/), and Lei et al. (Meta, Apple, Amazon, Trinity College Dublin), “Video Quality Evaluation Methodology and Result of AV2 Compression Performance”, arXiv:2605.15800, 2026: AV2 vs AV1 BD-rate −29.81% PSNR-YUV and −33.79% VMAF, random access. https://arxiv.org/abs/2605.15800. Accessed 2026-10-24. ↩↩
-
TVBEurope, “Full specifications released for HDMI 2.2”, June 2025. 96 Gbps bandwidth with HDMI Fixed Rate Link. https://www.tvbeurope.com/media-delivery/full-specifications-released-for-hdmi-2-2. Accessed 2026-10-24. ↩
-
Intel, “Intel Introduces Thunderbolt 5 Connectivity Standard”, September 2023. 80 Gbps bi-directional, up to 120 Gbps with Bandwidth Boost. https://www.intel.com/content/www/us/en/newsroom/news/intel-introduces-thunderbolt-5-standard.html. Accessed 2026-10-24. ↩
-
TV Technology, “SMPTE ST 2110-20: Pass the Pixels, Please”. ST 2110-20 transports only the active portion of each video frame, without blanking. https://www.tvtechnology.com/expertise/smpte-st-211020-pass-the-pixels-please. Accessed 2026-10-24. ↩
-
Bitmovin, “Apple AV1 support”. AV1 hardware decoding on A17 Pro, M3 and later Apple silicon; Apple silicon does not currently provide AV1 encoding. https://bitmovin.com/blog/apple-av1-support. Accessed 2026-10-24. ↩
