Bitrate is how much data your video spends per second - and it is the export setting people overshoot most. Higher bitrate is not higher quality past a certain point; it is just bigger files and slower uploads. One formula approximates a target for any resolution and frame rate, one table (YouTube's own upload recommendations, checked November 2026) anchors real-world numbers, one shortcut predicts file size, and the review-export answer at the end is smaller than most editors expect.
What bitrate actually measures
Resolution and frame rate say how many pixels and frames exist; bitrate says how many bits describe them each second. Two files can be identical 1080p24 and differ 4x in size purely on bitrate and codec. The codec (H.264, HEVC - see the codec guide) determines how efficiently those bits are spent, which is why bitrate targets are always per-codec.
The rule-of-thumb formula
Streaming-engine documentation formalizes the heuristic (Wowza's bitrate-optimization doc): bits-per-pixel (BPP) = data rate ÷ (resolution × frame rate). Invert it to get a target: bitrate ≈ width × height × fps × BPP. For H.264 delivery, a BPP around 0.1 is the commonly cited sweet spot. Worked example, 1080p at 30 fps: 1920 × 1080 × 30 × 0.1 ≈ 6.2 Mbps. Reality check: YouTube's own recommended 8 Mbps for 1080p30 back-computes to about 0.13 BPP - so treat 0.1 as a floor-ish starting point, not a standard. The honest caveat: real encoding quality depends on content (a static interview needs far fewer bits than a handheld action scene), which is why platform tables beat pure math.
YouTube's recommended upload bitrates (checked Nov 2026)
| Resolution | Standard frame rates (24/25/30) | High frame rates (48/50/60) |
|---|---|---|
| 1080p SDR (H.264) | 8 Mbps | 12 Mbps |
| 2160p (4K) SDR (H.264) | 35-45 Mbps | 53-68 Mbps |
Audio: AAC-LC (or Opus) stereo at up to 384 kbps. These figures come from YouTube's recommended upload encoding settings page and are the safest public anchor for upload targets; other platforms publish similar tables.
The file-size shortcut
Frame.io's classic bitrate post (linked here as the source - it is a competitor's page, credited because it is where the shortcut lives) popularized the inverse trick: file size (MB) ≈ bitrate (Mbps) × minutes × 0.0075. Worked example: an 8 Mbps, 10-minute review cut lands around 600 MB. That is the quick sanity check before an upload - if your "small review export" computes to 4 GB, something went wrong in the export settings.
Myths worth retiring
- "Maximum bitrate = maximum quality." Past a content- and codec-dependent point, extra bits add size, not detail. The visual difference between 8 and 16 Mbps H.264 for a talking-head 1080p cut is usually nothing.
- "One more export pass won't hurt." Every lossy re-encode generation compounds. Export once from your timeline to the review/delivery codec; keep the master as the master.
- "The platform keeps my bits." YouTube, social platforms, and review players re-encode everything for their delivery ladders anyway. Your upload target exists to survive their re-encode, not to be the final word.
What review exports actually need
For client review, 1080p H.264 at 8-12 Mbps is ample. Review platforms transcode uploads into adaptive streaming versions - what the client watches is the platform's playback encode, not your file - so an oversized upload mostly costs you time. The review-export format guide has the full settings, why the reviewed image differs from your master explains what the transcode does to the image, and large-file sharing covers the upload side. Keep your high-bitrate master separate; the review copy is disposable by design.
FAQ
What bitrate should I use for 1080p 30fps?
8 Mbps is the platform-standard H.264 target (YouTube's own number), with 6-10 Mbps the common practice band depending on content motion. Delivery masters can go higher; review uploads do not need to.
Is higher bitrate always better quality?
No. Quality scales with bitrate only until the codec has enough bits to describe the content; beyond that, extra bitrate is dead weight. Content complexity moves the point of diminishing returns, which is why fixed targets are heuristics, not laws.
Does bitrate affect upload time?
Yes, roughly linearly - double the bitrate doubles the file and about doubles the upload. For review links, that is the strongest argument for the 8-12 Mbps band instead of 50+ Mbps masters.
CBR or VBR for exports?
VBR (variable bitrate) is the standard choice for exports - it spends bits where the content needs them. CBR survives mainly in live streaming contexts where a constant pipe matters more than efficiency.
What bitrate for client review links specifically?
1080p H.264 at 8-12 Mbps. The review platform re-encodes for streaming playback anyway, so your upload just needs to look clean before that transcode - higher buys nothing the client will see.