The YouTube Bitrate to Set Before You Export

The recommended upload bitrates, by resolution

For a standard dynamic range (SDR) upload at 24, 25 or 30fps, the YouTube recommended bitrate is 8 Mbps at 1080p, 16 Mbps at 1440p and 35-45 Mbps at 4K. Export at 48, 50 or 60fps and each figure rises: 12 Mbps, 24 Mbps and 53-68 Mbps. Bitrate is the amount of video data per second of playback, counted in megabits per second, and the YouTube bitrate you want is the row that matches what you exported.

Those are the YouTube bitrate recommendations for SDR video, published by Google in Recommended upload encoding settings. High dynamic range (HDR) uploads have a separate, higher table: 10 Mbps at 1080p30, 15 Mbps at 1080p60, 66-85 Mbps at 4K60, and no HDR support at 480p or 360p. Audio is a fixed set of figures rather than a range: 128 kbps mono, 384 kbps stereo, 512 kbps for 5.1, all at 48 kHz.

The best bitrate for YouTube is the published figure for your resolution and frame rate, not the highest one your encoder will accept. Any value inside your row is a good bitrate for YouTube. The recommended bitrate for YouTube is a target for the file you hand over. What viewers receive is a different number.

What "recommended" means on YouTube's side

The recommended bitrate applies to the file you upload, not to the stream a viewer plays. YouTube re-encodes every upload into a ladder of renditions, which are separate copies of your video at different resolutions and codecs, and the player picks one for each viewer according to screen size and connection. So a YouTube video bitrate figure describes one of two things: what you sent, or what YouTube encoded from it and is now delivering.

The ladder exists so that one upload can play on a phone with a weak signal and on a television on a fast home connection. It is also why the same video can look sharp for you and soft for the next viewer.

The bitrate YouTube uses for delivery is lower than the one you exported. Your file is the source material for that re-encode, so a noisy or under-exported upload gives YouTube's encoder less to work with, and a clean one at the recommended figure gives it enough. What YouTube will not do is pass your 68 Mbps master through untouched.

The speed needed to watch is a third number. Google's system requirements page recommends a sustained 20 Mbps connection for 4K playback, 5 Mbps for HD 1080p and 2.5 Mbps for HD 720p. Those are viewing requirements, not export targets: a 4K video uploaded at 53-68 Mbps is watched over a 20 Mbps connection, because the rendition being delivered is not the file you sent.

Find your row: resolution and frame rate

Your row depends on two things: the resolution you exported at, and whether the frame rate is standard (24, 25 or 30) or high (48, 50 or 60). Two numbers answer almost every 1080p YouTube bitrate question, and two more cover 4K.

1080p at 60fps: 12 Mbps

The YouTube recommended bitrate for 1080p 60fps is 12 Mbps in SDR. Google publishes it as a recommended upload bitrate rather than a floor you have to clear, and it is a single figure rather than a range, so there is nothing to tune by content type. The best bitrate for YouTube 1080p 60fps is 12 Mbps for a talking-head interview and 12 Mbps for a gameplay capture. The one thing that moves it is HDR, where the same row reads 15 Mbps.

1080p at 30fps: 8 Mbps

The YouTube recommended bitrate for 1080p 30fps is 8 Mbps, and 24fps and 25fps sit on the same line. The distance between the two 1080p rows is worth reading carefully: twice the frames call for 50 percent more data, not twice as much. In HDR, 1080p at 30fps is 10 Mbps.

4K at 30 and 60fps: 35-45 and 53-68 Mbps

The YouTube 4K bitrate is 35-45 Mbps at 24, 25 or 30fps, and 53-68 Mbps at 48, 50 or 60fps. The 4K bitrate YouTube publishes is a range rather than a single value, and that is where content type finally matters. Grain, foliage, confetti and fast pans make the case for the top of the range. A static shot sits at the bottom. Strictly, YouTube 4K bitrate requirements do not exist. Google publishes recommendations and says plainly that no bitrate limit is required. The HDR 4K rows are 44-56 Mbps and 66-85 Mbps.

1440p at 30 and 60fps: 16 and 24 Mbps

The YouTube recommended bitrate for 1440p 60fps is 24 Mbps, against 16 Mbps at standard frame rates. If your timeline is 2560 by 1440, this is your row. 1440p is also one of the rungs YouTube can serve from a 4K upload, which is why it turns up in the quality menu of videos nobody shot at 1440p.

YouTube Shorts

There is no separate YouTube Shorts bitrate. Shorts read the same table by resolution and frame rate, so a vertical clip exported at 1080 by 1920 at 30fps takes the 1080p figure of 8 Mbps, and 12 Mbps at 60fps. Vertical framing does not change the number, and neither does the length of the clip. A vertical clip usually goes to more than one platform, and TikTok publishes no table like this one, so there the check is measuring what TikTok’s re-encode took rather than reading a number off a spec.

The export settings around the bitrate

Set the target bitrate for YouTube from the table above, then make the rest of the export match Google's spec. A correct YouTube upload bitrate is one line on that list, and the rest of the list is what gets the file processed the way YouTube expects. These are the YouTube bitrate settings and their neighbors as they appear in an export dialog.

• MP4 container, moov atom at the front, no edit lists. The moov atom is the index that tells a player where everything in the file is. Fast Start, sometimes labeled web optimized, is the option that moves it to the front so playback can begin before the whole file has arrived.
• H.264 video, High Profile, progressive. H.264 is the codec Google asks you to upload. VP9 and AV1 are codecs YouTube encodes to, so exporting in them gains you nothing.
• Closed GOP, two consecutive B-frames. A GOP is the group of frames between two keyframes. Closed means it does not reference frames outside itself, so each segment decodes on its own.
• CABAC entropy coding, 4:2:0 chroma subsampling. Both are defaults in most H.264 export presets, so this is a check rather than a change.
• BT.709 color space for SDR, 16:9 aspect ratio. A timeline that mixes color spaces produces a dull-looking upload that no bitrate will fix.
• AAC-LC audio at 48 kHz. Opus is accepted as well.
• Variable bitrate. Google recommends VBR and states that no bitrate limit is required, with the published figures given for reference.
• The frame rate the camera recorded. Content should be encoded and uploaded at its native frame rate. Deinterlace interlaced footage first: 1080i60 becomes 1080p30.

If the file is already exported and only the moov atom is in the wrong place, one command moves it without re-encoding anything:

ffmpeg -i input.mp4 -c copy -movflags +faststart output.mp4

Why a higher bitrate stops helping

Above your row, extra bitrate mostly buys export time and upload time. YouTube builds its own renditions from whatever you send, so bits beyond what its encoder decides to keep never reach a viewer. Exporting 1080p60 at 100 Mbps instead of 12 Mbps gives you a far longer upload and the same ladder at the other end. The highest bitrate for YouTube that changes what a viewer sees is the top of your own row.

There is no YouTube max bitrate in the published spec. Google's encoding page states outright that no bitrate limit is required and that its figures are there for reference, so the YouTube bitrate limit people go looking for does not exist as a published figure. The real ceiling is the point where extra bits stop reaching viewers, and that point is set by YouTube's encoder rather than by your export dialog.

When a 1080p upload still looks soft at 12 Mbps, the fix sits upstream of the bitrate field. Denoise grainy or low-light footage so the encoder is not spending its bits on noise, match the frame rate of the source instead of conforming 30fps material to a 60fps timeline, and export once from the timeline rather than re-encoding a file that has already been compressed.

Check what YouTube actually did to your upload

Once processing finishes you can measure what bitrate YouTube uses for your video instead of guessing at it.

1. Wait. Higher resolutions are encoded last. A video that looks soft twenty minutes after upload is often still being served from a lower rendition, and the quality menu in the player shows which resolutions exist so far.
2. Open Stats for Nerds. Right-click the player and choose Stats for Nerds. The codec line and the current/optimal resolution line tell you which rendition you are watching and what YouTube encoded it with. Stats for Nerds does not report a bitrate, so this check settles which rendition you are judging, not how many bits it carries.
3. Download the rendition and do the arithmetic. Paste the video URL into our YouTube video downloader, pick the resolution you care about from the list and save the file. The list gives a format name and a quality label rather than a bitrate, so the number comes from the file itself: Mbps = (file size in MB x 8) / duration in seconds.

That result is the average bitrate YouTube is delivering for that rendition. Averages flatten peaks, so a clip with one busy shot reads lower than the busy shot itself carries, but it is a measurement of your own video rather than a number from someone else's test.

A delivered figure well below your export is not a fault on its own. YouTube encodes its higher rungs with VP9 or AV1, and both reach a given picture quality at a lower bitrate than the H.264 you uploaded. The codec line in Stats for Nerds tells you which one you were given.

Read the measured figure against your row in the table, remembering that the delivered number is always the lower of the two. If you uploaded inside the recommendation and the rendition still breaks up where the picture is busy, the export settings have done what they can, and the source footage is what is left to change.

Audio: 128, 384 and 512 kbps

YouTube's audio recommendations are 128 kbps for mono, 384 kbps for stereo and 512 kbps for 5.1 surround, all at a 48 kHz sample rate in AAC-LC. Those three values describe channel layouts rather than quality tiers, so a voice recording mastered in mono has nothing to gain from a stereo export. A stereo mix pushed past 384 kbps does not survive either, because YouTube re-encodes the audio track as well as the video. If the audio track was the only part you wanted back from a video, our YouTube to MP3 converter extracts it from the same link, and what you get can only be as good as the audio stream YouTube is serving. Those figures are upload guidance and say nothing about what YouTube hands back, which is written down in only one place: the file you saved. Downloading audio from YouTube covers how to read it, and what to keep the file in.