What Is Bitrate, and How It Governs Quality, Bandwidth and Storage

Definition in one line

Bitrate (also data rate) is the amount of data a video stream uses per unit of time. It is the most important control over picture quality in audio and video encoding: at the same resolution, a higher bitrate means a lower compression ratio and a better picture.

Units: how big is a Kbps or Mbps

Bitrate expresses how many bits per second are needed to represent the encoded (compressed) audio and video. A bit is the smallest unit in binary — either 0 or 1.

• bps = bits per second.
• 1 KB/s = 1024 × 8 bps (one byte is eight bits). So 500 Kbps is roughly 61 KB of data per second.
• Common scales: Kbps (kilobits per second) and Mbps (megabits per second). 1 Mbps = 1000 Kbps.

Bitrate	Per second (approx.)	Per minute	Per hour
2 Mbps	0.24 MB	14 MB	0.86 GB
4 Mbps	0.48 MB	29 MB	1.7 GB
8 Mbps	0.95 MB	57 MB	3.4 GB
16 Mbps	1.9 MB	114 MB	6.9 GB

The practical value of that table: storage cost follows directly from bitrate. For surveillance and lecture capture, which accumulate over years, bitrate is quite literally disk money.

Bitrate and quality: the other side of compression

The relationship is simple: higher bitrate means better quality and a larger file; lower bitrate means the reverse.

One frequent confusion: a video file's total bitrate includes audio. Audio has its own bitrate, and the file's bitrate is the sum. So when a figure like "4 Mbps" is quoted, establish whether it is video-only or combined — for bandwidth budgeting the difference matters.

How audio bitrate is calculated

For audio: bitrate = sample rate × bit depth × channels.

For CD-quality audio: 44,100 × 16 × 2 = 1.41 Mbit/sec, about 1411 Kbps.

In practice audio bitrates are far lower: with AAC, 64–128 Kbps is fine for mono and 128–256 Kbps typical for stereo. Audio is a small share next to video, but still worth trimming when total bandwidth is tight.

Choosing between CBR and VBR

	CBR (constant)	VBR (variable)
Behaviour	Bitrate stays roughly fixed even on complex scenes	Rises on complex scenes, falls on simple ones
Bandwidth	Predictable — easy to budget bandwidth and storage	Has peaks; budget against the peak
Quality consistency	Complex scenes may starve and soften	More even quality overall
Best for	Fixed bandwidth, many parallel streams, strict quotas	Archive recording, spare headroom, quality first

Why multiple bitrates exist

In live streaming, viewers sit on wildly different networks. With a single fixed bitrate:

• Viewers on fast connections still get less sharpness than they could handle;
• Viewers on slow connections spend too long decoding, so playback stutters.

The simplest effective fix is multi-bitrate delivery: output the same picture at high, medium and low bitrates so each viewer takes what their network supports — sharpness and smoothness balanced.

That is also the origin of the encoder's main and sub stream design: main for high-quality recording or local display, sub for mobile or remote viewing. It is multi-bitrate at the device level.

Practical rules: measure upstream first

1. Measure real upstream: test at the hour you actually stream — evening peaks differ sharply from 3 a.m. Take the low reading.
2. Set bitrate at 60–70% of that, leaving room for protocol overhead and fluctuation. Never saturate the uplink.
3. Validate with real content: tables only give a starting point. Run 20–30 minutes of actual material and watch motion, text edges and shadow noise.
4. Drop frame rate before bitrate: when bandwidth is short, reducing 60 fps to 30 fps usually preserves per-frame quality better than cutting bitrate.
5. Work backwards from storage: for recording, derive disk needs from the table above, then choose the bitrate tier.