Video Bitrate Planning: CBR, VBR, Resolution, and Real File-Size Trade-offs

Reviewed 30 October 2026. The short answer is: choose bitrate from the destination, codec, resolution, frame rate, motion complexity, and upload constraints. CBR is useful when a live connection needs predictable throughput; VBR is usually more efficient for an uploaded file because the encoder can spend more bits on difficult scenes.

Start with the destination, not a universal number

A bitrate is a rate of data, normally expressed in kilobits or megabits per second. It is not a quality score. The same 8 Mbps target can look different when the codec, encoder preset, source noise, frame rate, or motion changes.

YouTube's official upload guidance recommends variable bitrate and publishes reference ranges by resolution and frame rate. For SDR uploads at standard frame rates, its current examples include 5 Mbps for 720p, 8 Mbps for 1080p, and 35–45 Mbps for 2160p. Those figures are destination guidance, not guarantees for every encoder or platform.

CBR and VBR answer different constraints

• Constant bitrate (CBR): targets predictable network use. YouTube's live-encoder guidance specifies CBR because a live contribution must fit the available upload path continuously.
• Variable bitrate (VBR): shifts more data toward complex motion and less toward simple scenes. This is usually a better fit for an uploaded file when final size and quality matter more than moment-to-moment network predictability.
• Quality-targeted encoding: some encoders expose a quality or quantizer target instead of a fixed average bitrate. File size then becomes an output to measure rather than a number known in advance.

Worked example: a ten-minute 1080p upload

Suppose a creator plans a ten-minute 1080p30 export at 8 Mbps video plus 384 kbps stereo audio. The combined nominal rate is 8.384 Mbps.

8.384 megabits/second × 600 seconds ÷ 8 = 628.8 megabytes

This is a planning estimate. Container overhead, metadata, encoder behaviour, and a VBR encode's actual average can move the final number. Run the finished file through a probe and compare its measured duration and size with the estimate.

A repeatable planning workflow

1. Confirm the destination's current codec, container, resolution, frame-rate, audio, and bitrate guidance.
2. Keep the source frame rate unless a deliberate conversion is required.
3. Choose CBR for a constrained live contribution; start with VBR for an uploaded file.
4. Add video and audio rates before estimating storage.
5. Encode a representative sample containing motion, detail, gradients, text, and quiet scenes.
6. Inspect the result on the devices that matter and revise from evidence.

Limitations

No table can account for every codec, encoder, scene, or platform transcode. A low-motion talking-head clip and fast game footage can need different rates at the same resolution. HDR, 10-bit video, multiple audio tracks, subtitles, and long-GOP settings also change the decision.

Use the NexxiqAI video bitrate calculator to compare plans, then verify the actual encode rather than treating the estimate as a promise.

Primary sources

• YouTube recommended upload encoding settings — upload codec, frame-rate, VBR, audio, and reference bitrate guidance.
• YouTube live encoder settings — live CBR and resolution-specific ingestion guidance.
• FFmpeg and ffprobe documentation — bitrate and rate-control options in bits per second.