Definition

What Is Bitrate? Bitrate for Calls and Video Streams

Bitrate decides how sharp a call looks and whether it survives a weak connection. Here is how to read it, what calls typically need and how to set it.

Bitrate vs bandwidth

Bitrate

Bandwidth

What it measures

Data a stream uses per second

Data a connection can carry per second

Who controls it

The encoder, through its target

The network path and plan

Units

kbps or Mbps

Mbps or Gbps

Changes during a call

Yes, the encoder adjusts it

Yes, as the network gets busier or weaker

If it's too high

Packets queue and drop, causing freezes

Not a problem; spare capacity

Rule of thumb

Keep it below available bandwidth

Leave headroom for other traffic

What is bitrate?

Bitrate is a rate: bits per second. A 64 kbps audio stream sends 64,000 bits every second. A 2 Mbps video stream sends 2 million. Divide by eight for bytes, so 2 Mbps is 250 KB per second, or about 15 MB per minute.

In calling and streaming, bitrate is usually the target you give the encoder. The codec then decides how to spend that budget: how sharp each frame is, how much motion it can describe and how much audio detail it keeps. The same bitrate can look very different with different codecs, which is why AV1 at 1 Mbps can match H.264 at a noticeably higher rate.

How bitrate shapes quality

For video, three things share the same budget: resolution, frame rate and detail per frame. Raise one and the others get less.

  • A 720p stream at 30 fps needs more bits than 360p at 30 fps to look equally clean.

  • Cutting frame rate from 30 to 15 fps frees bits for sharper frames, which suits screen sharing of slides or code.

  • Fast motion and noisy, low-light scenes eat bits. Static talking heads need fewer.

When the budget is too small, you see it: blocky artifacts, smeared motion and soft edges. Real-time encoders handle this by dropping resolution or frame rate before quality falls apart.

For audio, the Opus spec lists 16 to 20 kbps as the sweet spot for wideband speech, 28 to 40 kbps for full-band speech and 64 to 128 kbps for stereo music. G.711, the phone codec, always uses 64 kbps.

Rule of thumb: when bandwidth drops, lower frame rate or resolution before you let the picture turn to blocks. A steady 360p call beats a frozen 720p one.

CBR vs VBR

  • Constant bitrate (CBR): the encoder sends close to the same number of bits every second. Network load is predictable, which helps on tight links and with some live ingest services. Quality varies: complex scenes look worse.

  • Variable bitrate (VBR): the encoder spends more bits on complex moments and fewer on simple ones, for the same average. Quality is steadier, but bursts can exceed the link's capacity.

  • Capped or constrained VBR: VBR with a maximum. This is what most live and real-time encoders use in practice.

Real-time calls add a twist: the target itself moves. WebRTC estimates the available bandwidth continuously and raises or lowers the encoder's target, a form of adaptive bitrate.

Example: cap a WebRTC video bitrate

You can set a ceiling on what a WebRTC sender uses. The browser still adapts below it.

// Cap the video sender at 800 kbps and 24 fps
const sender = pc.getSenders().find(s => s.track && s.track.kind === 'video');
const params = sender.getParameters();
if (!params.encodings || !params.encodings.length) params.encodings = [{}];
params.encodings[0].maxBitrate = 800000;   // bits per second
params.encodings[0].maxFramerate = 24;
await sender.setParameters(params);

Typical bitrates for calls and streams

  • Voice calls: tens of kbps for the codec itself; CometChat recommends 100 to 300 kbps of bandwidth for a voice call to cover packet overhead and headroom.

  • SD video calls: around 500 kbps to 1 Mbps.

  • HD video calls: around 1.5 to 3 Mbps.

  • Screen sharing: around 1 to 2 Mbps; text needs sharp frames more than smooth motion.

  • Group calls: each participant sends one stream and receives several, so download needs grow with the number of visible tiles.

  • Live streams to viewers: encoded at several bitrates so each viewer gets one that fits their connection.

Limits and pitfalls

  • More isn't always better: a bitrate above the available bandwidth causes queuing and packet loss, which looks worse than a lower, steady bitrate.

  • Upload is the bottleneck: home and mobile connections often have far less upload than download. Size the sender for upload.

  • Headroom matters: packet headers, retransmissions and other apps all take a share. Don't target 100% of measured bandwidth.

  • VBR can leak information: with encrypted VBR voice, packet sizes can hint at what was said. RFC 6562 advises care, and CBR for sensitive calls.

  • Bitrate alone doesn't predict quality: the codec, resolution and content matter as much. Compare quality, not just numbers.

Bitrate in CometChat calls

If you're adding calling to your app, you mostly need to know what bandwidth your users need and that quality adapts on its own.

Adaptive bitrate with published bandwidth guidance

The CometChat Calls SDK uses adaptive bitrate encoding for voice and video that adjusts to network conditions. Its docs recommend 100 to 300 kbps for a voice call, 500 kbps to 1 Mbps for SD video, 1.5 to 3 Mbps for HD video and 1 to 2 Mbps for screen sharing. Video runs from 180p to 720p depending on layout and bandwidth, at a default 30 fps. The call UI includes a network quality indicator, which you can hide with the hideNetworkIndicator session setting.

Check network requirements · Start building free

Frequently asked questions

What is a good bitrate for video calls?

Roughly 500 kbps to 1 Mbps for SD and 1.5 to 3 Mbps for HD, per stream. Voice needs far less. Real-time apps adjust within these ranges as the network changes.

Is higher bitrate always better quality?

Only up to a point and only if the network can carry it. Past what the connection supports, a higher bitrate causes loss and freezes. Better codecs also get more quality from the same bitrate.

What is the difference between kbps and Mbps?

1 Mbps is 1,000 kbps. Audio is usually quoted in kbps and video in Mbps. Both are bits, not bytes; divide by eight to get bytes.

Should I use CBR or VBR?

Use capped VBR for most streaming and calls, since it keeps quality steadier. Use CBR when a service requires it or when you need predictable load, such as encrypted voice where packet sizes could leak information.

How does bitrate relate to resolution?

Higher resolution needs more bits to look clean. At a fixed bitrate, raising resolution or frame rate leaves fewer bits per pixel, so the picture gets softer or blockier.

Related terms