What Bitrate Do You Need for 1080p Video?

Every few weeks I see the same question in editing forums. Someone exports a 1080p video, it looks like mush, and the replies are a mix of “just raise the bitrate” and “use 20 Mbps”. Nobody says why 20, or what happens at 5, or whether the answer changes if you film a quiet interview instead of a football match.

So I ran a test. It is not perfect, but it uses real numbers instead of folklore, and it changed a couple of my own habits.

The test I ran

I took a 10 second, 1080p, 60 fps clip. It is a piece of the open-source short film Big Buck Bunny, which is useful because it has everything that breaks encoders: fur, fast camera moves, leaves, grass, and big flat color areas next to detailed ones. The original file was already compressed at about 4.2 Mbps, so keep in mind that I was measuring how much each new encode drifted away from an already compressed master. That makes absolute numbers a little flattering, but the shape of the curve is real.

I encoded it with x264 using the medium preset at six target bitrates, with a maximum rate of twice the target. Then I measured PSNR against the source. PSNR is a blunt tool, and I will say more about its limits below, but it is good at showing trends.

Here is what came out:

Target bitrate	File size (10 s)	PSNR vs source
0.5 Mbps	635 kB	28.5 dB
1 Mbps	1.25 MB	31.3 dB
2 Mbps	2.47 MB	34.7 dB
4 Mbps	4.89 MB	38.7 dB
8 Mbps	9.63 MB	42.7 dB
16 Mbps	19.35 MB	45.7 dB

Two things jump out. First, quality climbs steadily as you double the bitrate, roughly 3 to 4 dB each time up to 8 Mbps. Second, the last doubling from 8 to 16 Mbps bought only about 3 dB, and I could not see the difference when I flipped between the two at full screen. Below 2 Mbps the picture falls apart in a very specific way: grass and foliage turn into flat tiles, and fur loses its strands.

What those numbers feel like

PSNR is a number. What you actually care about is whether it looks bad. Here is how each step looked to me on a 27 inch monitor, playing the clip at 100 percent.

0.5 Mbps. Awful. In the frame I pulled out, the grass turned into a flat green paint smear and the fine strands of the roots were gone. In motion it also shimmers and breaks into squares. Flat areas like sky are fine, which is why bad encodes look fine in dull scenes and terrible in busy ones. If your video looks like this, you are not looking at a “quality setting” problem, you are looking at a data starvation problem.

1 Mbps. Still clearly damaged. The block edges are softer, but the grass is a green smear and there is visible banding in gradients.

2 Mbps. This is where most chat apps and cheap screen recorders sit, and it is the number that gives phone video its “WhatsApp look”. Good enough on a phone screen, noticeably soft on a monitor.

4 Mbps. Watchable. Most people would not complain. If you freeze a frame in a fast pan you can still find blocks, but in motion your eye forgives it.

8 Mbps. Clean. This is the level I would call “fine” for nearly everything at 1080p and normal frame rates. YouTube’s recommended upload bitrate for 1080p at standard frame rates is in this neighborhood (8 Mbps for 24 to 30 fps, and more for higher frame rates).

16 Mbps. Indistinguishable from the 8 Mbps version at normal viewing distance. You pay with a file twice the size.

Why the same bitrate gives different results on different video

This is the part most guides skip. Bitrate is not quality. Bitrate is a budget, and what matters is how hard the picture is to compress.

Think of the encoder as someone drawing a copy of your video using a limited amount of ink per second. A static shot of a person against a white wall needs almost no ink, because most of the picture repeats from frame to frame. A shot of confetti, rain, or leaves in the wind changes everywhere, all the time, and eats ink instantly.

So 4 Mbps can be perfect for a lecture and hopeless for a skateboard video. If your footage has any of these, move your target up:

• Fast camera movement, handheld footage or pans
• Foliage, water, snow, crowds, confetti, smoke
• Film grain or sensor noise (the encoder wastes bits trying to preserve it)
• Gradients like sunsets or a studio backdrop (these band at low bitrates)
• 60 fps, which doubles the frames per second to describe

A related thread I read on r/premiere had someone complaining about pixelated parts of a 4K export. The top answer pointed out that the bad sections were the busy handheld ones, the clean sections were the still ones, and 10 Mbps for 4K at 30 fps was “pathetically low”. That matches what I saw: the problem shows up where the picture is hardest, not everywhere.

The numbers I would actually use

After this test, here is what I use, for H.264 1080p at 30 fps:

• Talking head, screen recording, slides: 5 to 8 Mbps
• Typical vlog or travel footage: 8 to 12 Mbps
• Gameplay, sports, handheld, foliage: 12 to 20 Mbps
• Master you plan to edit again: 30 Mbps or more, or use an intermediate codec like ProRes or DNxHR

For 60 fps, multiply by about 1.5. For 4K at 30 fps, roughly multiply the 1080p number by 3 or 4. Adobe’s own export guidance for Premiere suggests 20 to 30 Mbps for HD and 60 to 80 Mbps for 4K when you are using hardware encoding, which is on the generous side but fine if storage is no issue. Hardware encoders (NVENC, Quick Sync, VideoToolbox) tend to need more bitrate than x264 to reach the same quality, so if you use them, lean toward the higher end.

If you are choosing between a quality mode and a fixed bitrate, I would pick the quality mode (CRF in x264) for a file you control and a target bitrate for anything that has a size limit. I wrote about that in CRF explained.

Constant, variable, and two-pass

Most editors give you three choices.

CBR (constant bitrate) gives every second the same budget. It is predictable, which streaming needs, but wasteful: quiet moments get more than they need and busy moments get less than they deserve. For uploads to a platform, I avoid it.

VBR 1-pass lets the encoder borrow from easy scenes and spend on hard ones, within a target average. This is a good default, as long as the maximum bitrate is high enough. If your max is close to your target, VBR behaves like CBR and your busy scenes fall apart.

VBR 2-pass analyses the whole video first, then spends the budget where it is needed. It is slower, and it produces the best quality at a given file size. If you have a size limit, use it.

My rule: set VBR, set a max at least 1.5 times the target, and use two passes if the export tool offers them and you are not in a hurry.

A word about PSNR and its limits

I used PSNR because it is easy to compute and consistently directional, but it does not know what humans notice. A video with slightly higher PSNR can look worse if the errors land on a face. Newer metrics like VMAF are closer to human judgment, and Netflix uses them to decide how much bitrate each title needs. If you are making decisions that matter, look at the video with your eyes, at 100 percent, on the screen your audience will use.

Also, my source was already compressed. The 16 Mbps encode “matching” the source at 45.7 dB mostly means I was copying the existing compression faithfully, not recovering extra detail. That is a lesson on its own: if the source is blocky, a high bitrate will preserve the blocks perfectly. More bitrate does not repair damage that already happened. For that you need a different tool, such as the pixelated video fixer on this site.

Common mistakes I see

Exporting a social media preset for your master. Presets for Instagram or TikTok are designed for small files. Keep a high-quality master and let the platform compress it once.

Matching the bitrate of the source. If the source is a phone clip at 17 Mbps and you export at 17 Mbps with a different codec setup, you will usually lose detail. Re-encoding costs quality, so give yourself a margin.

Raising the bitrate to fix a low-resolution source. An upscaled 480p clip at 20 Mbps looks like a perfectly preserved 480p clip. The encode is not the weak link. If that is your case, read how to make low quality video HD.

Ignoring audio. Audio at 128 to 192 kbps AAC is plenty for most content. It costs next to nothing and prevents the “it sounds underwater” problem at 64 kbps.

How to check the bitrate of a file you already have

Before you decide anything, look at what you actually have. There are three easy ways.

On Windows, right-click the file, choose Properties, then the Details tab, and look for “Data rate” under Video. On a Mac, select the file and press Command-I, or open it in QuickTime Player and press Command-I for the inspector. If you have FFmpeg installed, ffprobe -hide_banner yourfile.mp4 prints the bit rate near the top, and the stream line shows the resolution and frame rate.

What I look for is the ratio. Divide the bitrate by the number of pixels per second (width times height times frames per second). Encoders call this “bits per pixel”. For H.264, anything under about 0.05 bits per pixel is starved, 0.05 to 0.12 is workable, and above 0.12 is comfortable. For a 1080p, 30 fps video, that works out to roughly 3 Mbps, 7.5 Mbps, and 7.5 Mbps and up. This is the same measure the pipeline on this site uses to decide how aggressively to clean a file, which is why a heavily compressed phone video gets a stronger treatment than a clean screen recording.

Should you lower the resolution to save bitrate?

Sometimes, yes. This is a trade people forget about. If you have a budget of 2 Mbps, a 1080p encode has to spread that thin across two million pixels per frame. A 720p encode spends the same bits on less than half as many pixels, so each region gets more detail. In my experience, a clean 720p at 2 Mbps often looks better than a blocky 1080p at 2 Mbps, especially on a phone.

That is why streaming services use a “ladder”: they offer 480p, 720p and 1080p versions of the same title and switch between them as your connection changes. They are not being stingy. They are choosing the resolution that makes the best use of the bits available.

For your own exports, the rule is: if you are forced to use a low bitrate because of a file size limit, reduce the resolution before you reduce the bitrate into the danger zone. A sharp 720p is nicer than a mushy 1080p.

Platform notes

Platforms re-encode what you send, so it helps to know what they do.

YouTube re-encodes everything and gives better treatment to higher resolutions, which is why some creators upload 1080p footage as 4K. If you upload 1080p, aim for the 8 to 12 Mbps range or higher. Higher is not wasted, because YouTube’s encoder starts from your file.

Instagram and TikTok compress aggressively and cap the bitrate they will keep, so uploading a 50 Mbps file does not give you a 50 Mbps result. Export at 1080 by 1920, 30 fps, and about 10 to 15 Mbps, and turn on any “upload in highest quality” setting in the app. More on this in my guide to Instagram and TikTok pixelation.

Messaging apps are the harshest. WhatsApp and iMessage target small files and will crush video to a couple of megabits. If quality matters, send the file as a document or use a cloud link.

Your own website is up to you. If you host video yourself, a two-step approach works: store a high-quality master, and serve a 5 to 8 Mbps 1080p copy to visitors, with a lower-resolution version for mobile.

A worked example: picking a bitrate for a real project

Say you have a 6 minute travel video, shot on a phone, with lots of walking shots, a few street scenes and some drone-style pans. You want to upload it to YouTube and also keep a copy on your hard drive.

Start from the footage, not from a number. Handheld walking is busy, street scenes are busy, and the pans are the worst case for an encoder. That puts you in the “12 to 20 Mbps” bucket. I would pick 16 Mbps VBR with a 24 Mbps maximum, two passes if the editor offers it. At 16 Mbps, six minutes is about 720 MB, which is a fair price for a clean upload.

For the copy on your hard drive, you probably do not need to keep a second export at all. If you saved the project and the original clips, you can re-export at any time. If you did not, keep that 16 Mbps file as your master and never re-encode it again unless you have to.

Now suppose the file size limit is 200 MB because you are emailing it. Six minutes in 200 MB is about 4.4 Mbps total, minus audio. Rather than exporting 1080p at 4 Mbps and getting blocks, I would drop to 720p at 4 Mbps. Same file size, much cleaner picture, and on a laptop or phone most people will not notice the lower resolution.

The point is that bitrate is a budget you spend on purpose. Look at the footage, set a number that fits it, and check the result at 100 percent before you send it to anyone.

What to do if the video is already pixelated

If you already exported at a low bitrate and lost the project, you cannot get the original data back. You can reduce the visible damage with a deblocking filter and a gentle denoise, enlarge the picture with a good scaler, and sharpen lightly. That is what the tool on this site does, and on the clips I tested it makes a visible difference to the blockiness even though it cannot restore lost detail.

If you still have the project, re-export it with a higher bitrate. It takes five minutes and gives a better result than any repair.

Quick reference

If you only remember one thing from this article, remember this: start at 10 Mbps for 1080p, go up for busy footage, and never trust a preset that does not tell you its bitrate. Check the number in the export dialog, because the preset name will not.

And if your file is already damaged, upload it here for a free preview to see how much of the blockiness can be cleaned up before you decide anything.