What is video bitrate?

Data spent on every second

Every second of video is stored as a stream of bits, and the bitrate is the size of that stream. At 8 Mbps a second of video takes 8 megabits, or 1 megabyte, so a minute takes about 60 megabytes before audio. Resolution sets how many pixels there are to describe, the frame rate sets how many times per second they are described, and the bitrate sets how much data the encoder may spend doing it. Squeeze a large frame into too little data and the encoder has to discard detail. That shows up as blocky shadows, banding in skies and smooth gradients, smeared edges whenever something moves quickly, and fine text that turns fuzzy even though the resolution is technically high.

Constant, variable and constant quality

Encoders spend data in three broad ways. Constant bitrate spends the same amount every second, which suits live streaming because the network knows what is coming, but it wastes data on still scenes and starves busy ones. Variable bitrate spends more on busy scenes and less on quiet ones around a target, which is how Vimeo's upload guidance is expressed. Constant quality, such as the CRF mode of the widely used x264 encoder for H.264, sets a quality level and lets the bitrate follow the content. The FFmpeg documentation describes that scale as running from 0 to 51, where lower numbers mean higher quality and 23 is the default. A still title card then costs very little and a fast camera move costs a lot, while the look holds steady across both.

When bitrate matters most

It matters most for the file you upload, because platforms re-encode everything they receive and detail lost before upload cannot be restored in their encode. That is why YouTube recommends 8 Mbps for a 1080p upload at standard frame rates and 35 to 45 Mbps for 4K. It matters for content that is hard to compress: confetti, water, foliage, film grain, fast pans and full screen gradients all need far more data than a presenter against a plain wall. It matters for tutorials, where small interface text blurs at a low bitrate. And for video you host on your own website, the balance shifts the other way, toward smaller files that start playing quickly on a mobile connection.

Common mistakes

Judging quality by resolution alone is the first; a 4K file at a starved bitrate looks worse than 1080p at a healthy one. The second is exporting at a low bitrate to make uploading faster, then blaming the platform's compression for damage that was already in the file. The third is the opposite, pushing a file for a website to a very high bitrate, where it buffers on mobile data for no visible gain. The fourth is re-exporting an export. Each lossy encode throws more detail away, so every new version should be made from the original project or source files, never from a previous export that has already been compressed once. The fifth is copying one platform's recommended figure for every destination. YouTube and Vimeo publish different numbers for the same resolution, so check the guidance for the place the file is actually going.

Where it shows up in the product

The video builder here has no bitrate setting. Exports are H.264 MP4 files at 30 frames per second, encoded at a constant quality level rather than a fixed data rate, so a scene of mostly still text stays small while a scene full of movement gets the data it needs. The choice you do make is resolution: the canvas size of 1920 by 1080 or 1080 by 1920, or a 4K export on the Starter plan and above. Exporting the same unchanged video again reuses the MP4 already rendered, so there is no second encode to degrade it. If a platform's re-encode leaves one scene blocky, a calmer animated background on that scene, such as one from the Minimal or Gradient categories, usually survives better than a bigger export.

Questions people ask