See the Real Bitrate and Resolution of YouTube Files

What does B-ROLL show about each downloaded file?#

B-ROLL shows the real bitrate and resolution of every downloaded file on its card, for example “Real bitrate 8.2 Mbps · 1080p”. Audio downloads show the bitrate only, for example “160 kbps”, because an audio file has no picture height.

The figure changes once. While a file downloads, B-ROLL shows the highest estimate it finds in YouTube’s format data. When the download finishes, B-ROLL replaces it with a measurement on the actual file: file size divided by the duration ffmpeg reads from that file. The resolution is written as the picture height plus “p”, so 3840 x 2160 reads 2160p.

The table shows the readings you will meet on a card, what each one tells you and what to do next.

The figure sits on every card next to the format badge, in the All, Active and Completed views. Every other check and export is listed on B-ROLL features for video editors.

Why does real bitrate matter more than the YouTube resolution label?#

Resolution counts the pixels; bitrate tells you how much data per second describes them. YouTube re-encodes every upload, so a 1080p download is YouTube’s version of the video, compressed again after the creator’s own export.

YouTube Help’s recommended upload encoding settings ask for 8 Mbps at 1080p and 24 to 30 fps, and 35 to 45 Mbps at 2160p and the same frame rates. The stream you download is YouTube’s encode of that upload, and what it carries varies per video. The measured ranges are on what bitrate YouTube streams at 1080p and 4K.

For editing, the bitrate is what decides how a shot behaves under pressure. A thin 1080p file bands in skies and turns blocky in the shadows as soon as you push contrast in a grade. A punch-in scales those compression artifacts up with the picture, so a 2160p label on a starved file buys you less reframing room than it promises.

The codec changes the math, too. As of September 2026, YouTube serves H.264, VP9 and AV1 depending on the video and the resolution, and the newer codecs spend fewer bits for a similar picture. That is why you compare bitrates between files of the same codec and resolution. The differences are laid out in YouTube codecs explained: H.264 vs VP9 vs AV1.

Where does B-ROLL show bitrate before you download?#

B-ROLL shows bitrate and resolution per video in search results and in the channel list, before any file exists. Type words instead of a link, press Search, and the 20 results fill in their bitrate and resolution one by one, next to views, duration and channel.

The “Download from channel” dialog works the same way. Paste a playlist link, or a channel link once channel downloads are switched on in Advanced options, pick “Choose videos from a list”, and each of the latest 60 videos shows its bitrate next to its thumbnail, views and duration. That lets you skip a channel’s soft uploads before you queue anything with the YouTube playlist and channel downloader.

Before the download these figures are estimates, since there is no file to measure yet. The Quality menu’s hints (“~45 Mbps”, “~8 Mbps” and so on) are rougher still: they describe the resolution caps in general, never the video in front of you. Only the card’s final figure is a measurement.

If a result shows 360p or 720p where you expected more, the causes and fixes are in YouTube download only 360p or 720p.

How does the source bitrate affect B-ROLL’s ProRes or DNxHR tier?#

B-ROLL uses the source bitrate to pick the ProRes or DNxHR tier: the lightest tier whose data rate, scaled to the video’s resolution and frame rate, is at least 10 times the source. If no tier reaches that, B-ROLL uses HQ, and a 10-bit source converted to DNxHR always gets HQX. A 1080p30 source at 8 Mbps gets DNxHR SQ, or ProRes 422 LT. Those tiers carry reference rates of 124 Mbps and 102 Mbps at 1080p 29.97, 10 times or more the source.

The source figure for the tier is not the card figure. ffmpeg measures it on the MKV master before the conversion, using the video stream’s own bitrate when ffmpeg reports one, so it leaves the audio out. The log prints it on the tier line, which reads “ProRes tier auto-picked” or “DNx tier auto-picked” and names the source and output bitrates. Read the YouTube source bitrate of a converted file there, because the card afterwards measures the .mov.

The whole conversion, including resolution, frame rate and the 16-bit PCM audio in the .mov, is covered in download YouTube videos in ProRes or DNxHR. The reasoning behind the 10x factor is in how B-ROLL picks a ProRes or DNxHR tier automatically.

How can you check a file’s bitrate yourself?#

You can check any file’s bitrate with ffprobe, the analysis tool that ships with ffmpeg. The ffprobe documentation describes the options used here: -select_streams picks the stream, -show_entries picks the fields and -of sets the output format.

This command prints the video stream’s own bitrate, in bits per second, plus its size and frame rate:

ffprobe -v error -select_streams v:0 -show_entries stream=codec_name,width,height,r_frame_rate,bit_rate -of default=noprint_wrappers=1 "Interview.mp4"

This one prints the whole file’s bitrate and duration, the closest match to B-ROLL’s card figure, which divides the file size by the duration:

ffprobe -v error -show_entries format=bit_rate,duration -of default=noprint_wrappers=1 "Interview.mp4"

An MKV or WEBM file can report bit_rate=N/A for the video stream. In that case read the format line instead, or trust the card: B-ROLL’s measurement works the same way for MP4, MKV, WEBM and .mov. The codec name and frame rate that the first command prints are also the two details the card leaves out.