Blurry video on YouTube: why it happens and what to check first

YouTube processes a low-quality version of every upload first and adds the higher resolutions later: according to YouTube Help, a 60-minute 4K video at 30 fps can take up to four hours to fully process, and longer at 60 fps. If you opened it five minutes after uploading, that alone can explain the blur. If it still looks bad hours later, the cause is either your file or YouTube’s re-encode, and one quick test tells you which.

The video looks great on your PC. You upload it, the grass turns into smudges, the water loses its detail and blocks show up every time the camera turns. Before you change OBS, Premiere, DaVinci and half your PC, open the file you uploaded. If that file already looks bad, the problem happened before YouTube. If the file looks good and YouTube looks worse, keep reading.

You just uploaded it: wait

YouTube doesn’t prepare every quality at once. It serves a lighter version first, then 1080p, 1440p or 4K arrive, and the higher the resolution, the longer it takes, per YouTube Help. That’s why you can upload a 4K video, open it right away and think it’s ruined.

Click the gear icon on the player and go to Settings > Quality. If the resolution you uploaded isn’t listed yet, YouTube is still working on it. Let it finish before you touch a single setting.

Check your file before blaming YouTube

Open the exported video straight from your drive and find the same scene that looks bad on YouTube. If your local file looks bad too, YouTube received a video that had already lost detail. Check, in this order, your recording, resolution, frame rate, bitrate and export settings.

If your local file looks good, the detail got lost afterward. YouTube creates its own versions of every video so it can play on phones, TVs and computers over very different connections, and that re-encode can cost detail. What you control is handing it the best possible source.

Why gameplay suffers so much

Look at a face in front of a plain wall: very little changes from one frame to the next. Now look at gameplay with moving grass, trees, shadows, water, traffic, particles and a spinning camera. Every frame changes a lot, and that kind of image is much harder to compress.

That’s why grass, foliage, water, smoke, dark scenes, driving and fast camera turns are the first things to fall apart. You can see it in your own video: find a still wall, then a forest in the rain while you’re running. The difference usually shows up on its own.

Use the bitrate YouTube asks for

Bitrate is the amount of data your video carries every second. Think of a box: a still wall fits easily. Add grass, rain, water, smoke, a car flying past and a spinning camera, and you need a bigger box. With too little bitrate you get blocks and smudges.

For SDR video, YouTube’s recommended upload encoding settings are:

Resolution	24–30 fps	48–60 fps
1080p	8 Mbps	12 Mbps
1440p	16 Mbps	24 Mbps
4K (2160p)	35–45 Mbps	53–68 Mbps

The same page asks for an MP4 container, H.264 High Profile video with progressive scan and 4:2:0 chroma subsampling, and AAC-LC audio at 48 kHz, stereo at 384 kbps. Treat it as your starting point.

Keep your original frame rate

Recorded at 60, export at 60. Recorded at 30, export at 30. YouTube asks you to upload at the same frame rate you recorded, per its recommended settings page. Converting 30 to 60 on export repeats or invents frames: the real moments are still the 30 per second you captured.

Your source footage sets the ceiling

Record a blurry image, export it at 4K, and you get a bigger blurry image. Detail that never made it into the recording stays out, and a higher export resolution just spreads it across more pixels. If you want real 4K detail, the source has to have it: record and export from footage that already carries it.

More bitrate helps, up to a point

You export at 5 Mbps and it looks bad. You go to 12 and it gets better. At 50 it might improve a bit more. At 200 the file is huge and YouTube re-encodes it anyway. A giant file gives YouTube a better source, and what reaches viewers comes out of YouTube’s re-encode at the bitrate YouTube picks. So I’d start close to the official numbers and test from there.

Starting settings for 1080p, 1440p and 4K

For regular gameplay at 1080p60: 1920×1080, 60 fps, about 12 Mbps, progressive video and 48 kHz audio. At 1440p60 the resolution goes up to 2560×1440 and the bitrate to 24 Mbps, because there are more pixels to feed. At 4K60, 3840×2160 and 53 to 68 Mbps, with files that are much bigger and take longer to export, upload and process.

Uploading 1080p as 1440p or 4K

There’s a trick that’s been around for years: record at 1080p, upscale to 1440p or 4K on export and upload that. The theory is that YouTube treats higher-resolution uploads better. It’s a community trick, and YouTube doesn’t mention it in its recommended upload settings. So I wouldn’t sell it as a universal fix. We’re going to test it with the same clip uploaded at 1080p, 1440p and 4K, comparing the same scene, and publish what we find.

What VP9 means in Stats for nerds

Right-click the player and open Stats for nerds to see which codec YouTube is serving you: avc1 (H.264), vp09 (VP9) or av01 (AV1). A codec is a way of compressing the image to send it over the internet. Seeing VP9 tells you which version you’re getting, and that version is still a re-encode of your file.

Before you chase the codec, look at the picture. Open the video, find a hard scene and watch it. If it looks good, get back to work. If it looks bad, go through resolution, processing, your original file, bitrate and frame rate, and leave the codec for last. A label in Stats for nerds won’t fix the grass.

What to check in OBS, DaVinci Resolve, Premiere and CapCut

In OBS, check the original recording first. If it already has blocks, the problem is in the recording: for local recording, as a starting point I’d use a constant quality mode (CQP or CQ, depending on the encoder) and make sure OBS isn’t dropping frames while you play. Full settings are in our best OBS settings for gaming guide, and if your PC is struggling, in OBS settings for a low-end PC.

In DaVinci Resolve, start at 12 Mbps for 1080p60, 24 Mbps for 1440p60 and 53 to 68 Mbps for 4K60. The step-by-step is in our DaVinci Resolve export settings for YouTube.

In Premiere, check resolution, frame rate, the H.264 codec and bitrate before you export. It’s all in our Premiere Pro export settings for YouTube.

In CapCut, check resolution, frame rate and bitrate, and remember that with Proxy on, the preview can look worse while you edit without affecting the final file. More in our CapCut export settings for YouTube. If you’re still choosing an editor, compare options in best video editing software for YouTube.

Run this test before changing twenty settings

Export one minute before you export an hour. Build a clip with four scenes: small text or a HUD, grass or foliage, water, smoke or particles, and a fast camera move. Export it, check the local file, upload it as unlisted, wait for YouTube to finish processing and compare the exact same seconds. That’s where you start to see where the quality drops.

The order I’d follow

1. Wait for processing to finish and check which qualities are available.
2. Check the local file.
3. Check resolution and frame rate.
4. Check bitrate.
5. Look at a scene with lots of motion.
6. Then change settings.

If you change everything at once, you can end up with a better video and still not know what was wrong. A short test usually tells you more.

---

Primary sources: YouTube Help, recommended upload encoding settings and video processing after upload.

Last checked: October 1, 2026.