A bitrate in video is the amount of data used to represent one second of playback, quoted in kilobits per second (kbps) or megabits per second (Mbps). That is the whole definition. The interesting part is what the number does not tell you.
Read on its own, a bitrate is not a quality grade. 8 Mbps is not “good” and 2 Mbps is not “bad”. The same 4 Mbps buys a clean talking-head stream and a smeared sports feed, because the bits are being spread across a different amount of moving detail in each case. A bitrate figure only becomes meaningful once you name four things alongside it: the codec, the resolution, the frame rate, and how complex the source content is.
Why the number is meaningless on its own
The useful way to read a bitrate is as a ratio, not an absolute. Divide the bitrate by pixels per second — resolution multiplied by frame rate — and you get bits per pixel per second, which is roughly comparable across formats. That ratio is what actually tracks perceived quality, and it is the only form in which two bitrates from different rungs of a ladder can be compared honestly.
Codec efficiency shifts the ratio again. A newer codec generation reaches the same perceptual score with fewer bits per pixel than an older one at the same encoder effort, which is why a bitrate table written for one codec transfers badly to another. Content complexity moves it a third time: static scenes compress well, fast motion and film grain do not.
A bitrate is a budget, not a setting.**
Quick answer
| Question | Short answer |
|---|---|
| What is it? | Data per second of playback, in kbps or Mbps |
| What does it not tell you? | Quality — until codec, resolution, frame rate and content complexity are named |
| Comparable unit | Bits per pixel per second (bitrate ÷ resolution ÷ frame rate) |
| Video vs audio | Quoted separately; audio is typically a small, near-fixed share of the total |
| Encoder figure vs delivered figure | Not the same — players select rungs, so delivered bitrate is a distribution |
| How to judge it | Average delivered bitrate per device class against a perceptual score such as VMAF |
Two numbers to check before you export
Look at your encoder’s target bitrate and the actual file size per minute—if they don’t align with your platform’s recommended range, viewers will see either pixelation or unnecessarily long upload times. Teams that re-read the same ladder as bits per pixel per second against their real device mix hit the same quality target with materially fewer bits per stream. The measurement pair worth holding is average delivered bitrate per device class against VMAF or an equivalent perceptual score — before and after, at a held quality-of-experience level.
Transcoding workflows break down immediately when teams conflate bitrate with resolution or frame rate. A bitrate figure understood in context can be adjusted; one copied from a forum table cannot, because nobody knows what it was assuming. Our broader work on cost per stream in media and broadcast delivery starts from exactly this reading, and the parent discussion of how bitrate, codec and device mix set delivery economics is developed in the bitrate and delivery cost hub.
The open question in most catalogues is not what bitrate to pick — it is whether anyone has measured what viewers actually receive, rung by rung, against what the encoder was told to produce.
