What Bitrate Does YouTube Stream at 1080p and 4K?

What bitrate does YouTube stream at?#

YouTube does not publish the bitrate of the streams it serves, so a trustworthy figure is one measured on a named video on a named date. YouTube re-encodes every upload; a download is YouTube’s version, not the original file.

A stream’s bitrate depends on the video, not only on the resolution label. Motion, grain, the codec YouTube chose and the quality of the upload all change how many bits a 1080p or 2160p stream gets. As of September 2026, one video is often offered as several streams at the same resolution, each with its own codec and bitrate.

The table records measured streams: named public videos, the resolution and codec of the stream, its video bitrate and how and when it was read.

B-ROLL’s Quality menu shows hints next to each cap, such as “~8 Mbps” beside 1080p. Those hints are rough estimates for the cap in general, not a measurement of the video in front of you. The rest of the formats picture is in codecs and formats for editing YouTube footage.

Why is a YouTube stream’s bitrate lower than the upload?#

A YouTube stream is usually lighter than the upload because YouTube encodes its own delivery copies after the upload arrives. The upload is YouTube’s input; the stream is YouTube’s output, sized for playback over the internet.

YouTube Help’s recommended upload encoding settings ask for H.264 video in an MP4 container, with the bitrates in the table for SDR uploads. The measured column comes from the table of measured streams once the owner’s run is in.

The same help page lists higher figures for HDR uploads, for example 44 to 56 Mbps at 2160p and 24 to 30 fps. Those numbers describe what YouTube wants to receive, never what it streams back.

Codec is the other half of the gap. As of September 2026, YouTube serves many streams as VP9 or AV1, which reach a similar picture with fewer bits than the H.264 upload, so a lower number does not always mean a worse picture. YouTube codecs explained: H.264 vs VP9 vs AV1 compares the three.

A download that tops out at 360p or 720p is a different problem, with its own fixes in YouTube download only 360p or 720p.

Does 4K always look better than 1080p on YouTube?#

No. A 2160p stream carries more detail than a 1080p stream only when the upload had that detail; a 1080p video scaled up before upload gains pixels but no information.

When the upload is real 4K, YouTube’s own numbers favor it. Divide the recommended bitrate by pixels per second and you get the bits each pixel receives per frame:

• 1080p 30 fps at 8 Mbps: 8,000,000 / (1920 x 1080 x 30) = 0.13 bits per pixel.
• 2160p 30 fps at 35 Mbps: 35,000,000 / (3840 x 2160 x 30) = 0.14 bits per pixel.
• 2160p 30 fps at 45 Mbps: 45,000,000 / (3840 x 2160 x 30) = 0.18 bits per pixel.

The recommendation gives a 4K upload at least as many bits per pixel as a 1080p one. On a 1080p timeline, a 2160p source is scaled down by half in each direction, so four source pixels average into each output pixel and compression noise shrinks with them.

B-ROLL’s Quality menu offers Best, 4K, 1080p, 720p and 480p, each a height cap. A video whose highest stream is 1440p arrives at 1440p with Best or 4K, since both caps allow it.

How do you check a downloaded file’s bitrate?#

Check a YouTube file’s bitrate in two places: the stream list before the download, and the finished file after it. The first figure is YouTube’s metadata; the second is a measurement.

Before downloading, yt-dlp lists every stream with the -F (--list-formats) option, described in the yt-dlp README. In that list, the VBR column is the video bitrate, TBR the total of video and audio, and VCODEC the codec:

yt-dlp -F "https://www.youtube.com/watch?v=VIDEO_ID"

B-ROLL reads the same data for you. Search results and the channel list show “bitrate · resolution” for each video before you download. While a file downloads, its card shows the highest estimate from YouTube’s format data. When the download ends, B-ROLL replaces it with a measurement: file size divided by the duration ffmpeg reads from the file, for example “Real bitrate 8.2 Mbps · 1080p”. How each reading on the card helps you choose footage is shown in see the real bitrate and resolution of YouTube files.

Outside B-ROLL, ffprobe reports the codec, frame size and bitrate of any file with the -select_streams, -show_entries and -of options from the ffprobe documentation:

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

The first bit_rate line is the video stream and the second the whole file, both in bits per second. MKV and WEBM files usually report the stream value as N/A, so read the file line there. A B-ROLL card figure also covers the whole file, audio included, so it reads slightly above the video-only VBR value.

What does bitrate mean for grading and scaling?#

Bitrate decides how far a YouTube shot bends in a grade or a punch-in before it breaks. A thin 1080p stream holds up in a straight cut, but pushing contrast exposes banding in skies and blocks in shadows, and a punch-in enlarges those artifacts with the picture.

Reframing room is simple arithmetic. A 2160p source on a 1080p timeline allows a 200 percent punch-in (3840 / 1920) before you scale past the source pixels. A 1080p source allows none, and the compression shows first.

Converting to an intraframe codec changes how the file decodes, not what it contains. B-ROLL picks the lightest ProRes or DNxHR tier whose data rate is at least 10 times the source bitrate: a 1080p 30 fps source at 8 Mbps gets DNxHR SQ at 124 Mbps or ProRes LT at 102 Mbps. The tier ladder is explained in ProRes Proxy vs LT vs 422 vs HQ, and the disk cost in ProRes and DNxHR file size per minute.

Capturing the player instead of downloading adds a generation: the recording re-encodes YouTube’s already compressed stream. The trade-offs are compared in screen recording vs downloading YouTube for editing.