Vidlora guide
Understanding video bitrate
Bitrate is the amount of data used for each second of video, usually written in kbps or Mbps. It is the main link between file size and quality, yet it is easy to misread because it interacts with resolution, frame rate, codec and content. This guide explains what bitrate means, shows typical values, covers constant versus variable bitrate, and shows how to read the real figure from a file so you can decide whether to compress, convert or leave it alone.
7 minute read
What bitrate measures
Bitrate is data per second of playback. One megabit per second (1 Mbps) equals 1,000 kbps and about 0.125 MB per second, or 7.5 MB per minute. So a video at 8 Mbps uses 60 MB per minute, and at 2 Mbps about 15 MB per minute. File size is simply total bitrate (video plus audio) multiplied by duration, which makes bitrate the easiest way to predict how big a file will be before you make it. Bits are not bytes: file sizes are in bytes, bitrates in bits, so divide by eight. When someone mentions bandwidth needs for streaming, they are talking about the same number: a 5 Mbps video needs a connection that can sustain at least 5 Mbps.
Bitrate versus resolution
Resolution is how many pixels are in each frame; bitrate is how many bits you can spend describing them. A 1080p video with a very low bitrate looks blocky and smeared, while a 720p video at a healthy bitrate can look cleaner. A rough efficiency measure is bits per pixel per frame: for H.264, values around 0.07 to 0.12 give good quality for typical content. At 1920x1080 and 30 fps that is about 4.4 to 7.5 Mbps. Content changes the picture: fast sport, grain and confetti need more, slideshows and talking heads less. The lesson is that high resolution only helps when bitrate keeps up; choosing 4K at a starved bitrate wastes resolution.
Typical bitrates in the real world
Streaming and upload recommendations give useful anchors. For H.264 at 30 fps, platforms commonly suggest around 1 Mbps for 360p, 2.5 to 4 Mbps for 720p, 5 to 8 Mbps for 1080p, 12 to 16 Mbps for 1440p and 35 to 45 Mbps for 4K; 60 fps content needs roughly 1.5 times more. Phones record much higher: 4K at 30 fps is often 40 to 60 Mbps, and 1080p around 15 to 20 Mbps, because they use fast, light encoding. Blu-ray movies run 20 to 40 Mbps. Audio is much smaller: 128 to 256 kbps for AAC stereo, 96 kbps often enough for speech. Streaming services re-encode uploads, so supplying a clean, high-bitrate source gives their encoder more to work with.
Constant, average and variable bitrate
Constant bitrate (CBR) keeps the data rate fixed, which helps live streaming over a known connection but wastes bits on easy scenes and starves complex ones. Variable bitrate (VBR) lets the rate vary, spending more on action and less on calm moments, giving better quality for the same average size. Average bitrate (ABR) targets a total size, and two-pass encoding improves distribution. Constant rate factor (CRF) fixes quality rather than bitrate, so the resulting bitrate depends on content; it is the usual default for local files. That is why a quality-targeted setting, like the one in Vidlora's compressor, may produce a 1.5 Mbps result for a static clip and 8 Mbps for a busy one. The metadata shows the average, not the peaks.
How codecs change the picture
Codec efficiency changes how far a bitrate goes. At the same visual quality, H.265 and VP9 typically need 30 to 50 percent less bitrate than H.264, and AV1 slightly less again. So 3 Mbps of H.265 might look like 5 Mbps of H.264. Older codecs such as MPEG-2, used in DVDs, need far more: DVD video at about 5 Mbps looks worse than 1.5 Mbps in H.264 at the same size. When comparing two files, check the codec as well as the number. A higher bitrate in an older codec does not guarantee better quality. The reverse also applies when transcoding: moving to a more efficient codec lets you lower bitrate without a visible loss, at the cost of compatibility.
Reading bitrate from a file
A video metadata viewer reads the container and streams and reports the overall bitrate, codec, resolution, frame rate and duration, plus audio details such as codec, channels and sample rate. Vidlora's metadata viewer uses ffprobe for this, without changing the file. Overall bitrate includes everything in the file, including audio and overhead. If it is missing, divide file size by duration: a 300 MB file lasting 10 minutes is 300 x 8 / 600 = 4 Mbps. Compare it with the typical values for the resolution. A 1080p file at 20 Mbps has plenty of room to shrink; a 1080p file at 1.5 Mbps is already tight, and re-encoding it will probably hurt more than help.
Choosing a bitrate for your goal
For uploading to a platform, use the platform's recommended bitrate or a bit higher, since it will re-encode. For archiving a recording you care about, keep the original or use a low CRF so bitrate stays generous. For email and chat with strict limits, calculate backwards: target size in megabytes times eight, divided by seconds, minus audio. 25 MB over 60 seconds is about 3.3 Mbps in total. For mobile viewing, 1.5 to 3 Mbps at 720p looks good on a small screen. For live streaming, choose a bitrate at most about 70 percent of your upload speed so spikes do not cause buffering. Finally, test with a short sample and view it on the destination device.
Common misunderstandings
Many people believe that raising bitrate always improves quality. That is only true up to the source's quality: re-encoding a 720p video at 20 Mbps gives a huge file with no extra detail. Others think a larger file always means better video, ignoring codec and content. Some assume resolution alone defines quality, though a starved 4K video looks worse than a well-fed 1080p one. The bitrate shown in a player may be the current rate, not the file's average. Converting an MP3 or AAC to a higher bitrate does not restore detail either. And remember that bitrate in a metadata display is averaged, so a file labelled 6 Mbps may peak at twice that. When in doubt, inspect, test and compare.
Try the free video downloader