How bitrate, resolution and frame rate relate
What bitrate controls, why higher resolutions and frame rates need more of it, and how to read the SDR upload guidelines sensibly.
What bitrate actually controls
Bitrate is how many bits of data the encoder spends on each second of video, measured here in megabits per second. More bits mean more room to preserve fine texture, gradients and motion before compression artifacts such as blocking or banding appear. Resolution sets how many pixels there are, but bitrate decides how faithfully those pixels are stored. Two 4K clips can look very different if one is starved of bitrate and the other is given plenty.
Why resolution raises the target
Jumping from 1080p to 4K roughly quadruples the pixel count, so the encoder has far more detail to describe in every frame. That is why the recommended rate climbs steeply, from 8 Mbps at 1080p30 to 45 Mbps at 4K30 in these guidelines. The relationship is not perfectly linear, because compression exploits similarity between neighbouring pixels, but higher resolution always pushes the sensible bitrate up.
Why high frame rate needs more bits
Frame rate multiplies the amount of motion information per second. Doubling from 30 to 60 fps means twice as many frames, each needing enough data to stay crisp when the scene moves quickly. The guidelines handle this with a separate high-frame-rate column that starts above 30 fps, lifting 1080p from 8 to 12 Mbps and 4K from 45 to 68. Sports, gaming and action footage benefit most from that headroom.
Guidelines versus your own encode
These numbers are upload recommendations for standard dynamic range, tuned so a platform can re-encode your file without visible loss. They are not the only correct answer. A slower, more efficient codec or a two-pass encode can match the quality at a lower bitrate, while noisy or highly detailed footage may want more. Use the recommendation as your default export target, then adjust if you can see artifacts or if your storage and upload budget is tight.