YouTube Export Settings That Keep Your Video Sharp
Your edit looked crisp on the timeline, but after upload the dark corners turned to blocky mush and the text went soft.

Your edit looked crisp on the timeline, but after upload the dark corners turned to blocky mush and the text went soft. Most of that damage comes from YouTube export settings that fight the platform's own re-encode instead of feeding it something clean to work with.
YouTube re-compresses every file it receives. You cannot stop that. What you can control is how much detail and headroom your master gives the encoder, and that is where a few deliberate choices make a visible difference.
Why your upload looks worse than your timeline
When you upload, YouTube transcodes your file into several resolutions and codecs, then serves whichever one fits the viewer's connection. A 1080p upload is often streamed at a bitrate around 4 to 8 Mbps. If your master was already squeezed to 8 Mbps, the second compression pass has very little to work with, and gradients like skies or shadowed walls break into bands.
Two other things make it worse. Fast motion and grain eat bitrate, so a handheld shot of leaves will degrade faster than a locked-off interview. And very dark footage is where compression hides its errors least well, because the eye is sensitive to steps in near-black tones.
The YouTube export settings I actually use
These are the values I set for a typical 1080p or 4K delivery from Premiere Pro, DaVinci Resolve or Final Cut Pro. Names differ slightly between programs, but every editor exposes the same controls.
| Setting | 1080p | 4K (2160p) |
|---|---|---|
| Container | MP4 | MP4 |
| Codec | H.264, High profile | H.264 or H.265 |
| Frame rate | Same as timeline | Same as timeline |
| Bitrate (24 to 30 fps) | 16 to 20 Mbps | 50 to 80 Mbps |
| Bitrate (50 to 60 fps) | 24 to 30 Mbps | 80 to 100 Mbps |
| Rate control | VBR, 2 pass if available | VBR, 2 pass if available |
| Audio | AAC, 48 kHz, 320 kbps | AAC, 48 kHz, 320 kbps |
| Color | Rec. 709, progressive | Rec. 709, progressive |
Those bitrates sit above YouTube's own published recommendations on purpose. The extra data costs you upload time and disk space, not quality, and it gives the platform's encoder a cleaner starting point.
Keep the frame rate identical to your timeline. Converting 25 fps footage to 30 fps on export creates duplicated frames and a faint stutter on pans. If you are unsure what your timeline should be set to in the first place, the guide on choosing a timeline frame rate for your delivery platform covers the decision.
Upload 1440p even if you shot 1080p
This is the counter-take, and it goes against the common advice to always export at your native resolution. For footage that will mostly be watched at 1080p, I often upscale the export to 2560 by 1440.
The reason is how the platform allocates quality. Uploads at 1440p and above are usually processed with the VP9 or AV1 codec, which tends to hold more detail at a given bitrate than the H.264 version a plain 1080p upload often gets. Viewers watching at 1080p then receive a 1080p stream derived from the higher-quality pipeline, and it typically looks sharper in motion and in dark scenes.
The trade-offs are real. A 10 minute export at 1440p and 40 Mbps is roughly 3 GB instead of 1.5 GB, uploads take twice as long, and processing for the higher tier can lag behind the lower versions by an hour or more. For a quick talking head clip, it is not worth it. For a graded short film or a gameplay piece with lots of texture, it usually is.
Color and gamma shifts after upload
A common complaint is that the upload looks brighter or more washed out than the editor viewer. Usually the file is fine and the difference is in how players and editors interpret gamma. QuickTime on a Mac, for example, may display Rec. 709 material with a different gamma curve than a browser does.
To keep things predictable:
- Grade on a monitor set to Rec. 709 with a gamma of 2.4 if you work in a dim room, or 2.2 in a brighter office.
- Export with Rec. 709 color tags, and make sure your editor writes them into the file.
- Judge the result in a web browser, not in a desktop media player, because that is what your viewers use.
- If footage was shot under awkward light, fix it in the grade rather than hoping export will help. The walkthrough on color grading footage shot under mixed lighting is a good place to start.
Audio is part of the export too
Viewers forgive soft video faster than harsh audio. Export at 48 kHz to match most camera and recorder sources, and avoid 44.1 kHz unless your whole project was built at that rate, because resampling on export can introduce small artifacts.
For loudness, YouTube normalizes playback to roughly minus 14 LUFS integrated. If your mix is much louder, it gets turned down and may sound flat next to other channels. If it is much quieter, it can sit below everything else. Aim for minus 14 to minus 16 LUFS integrated with true peaks under minus 1 dBTP, and you will land close to where the platform wants you.
A quick checklist before you hit export
- Timeline resolution and frame rate match the final delivery.
- No accidental scaling, such as a 4K clip shrunk to fit a 1080p frame and then sharpened.
- Render at maximum bit depth if your editor offers it, which reduces banding in gradients.
- Captions exported as a separate file rather than burned in, so they stay sharp and editable.
- Watch the first and last 10 seconds of the exported file before uploading, because black frames and audio pops hide there.
Once a project is delivered, keep the master and the project files together. A clean export is only useful if you can rebuild it later, which is why archiving a finished edit properly belongs at the end of every job.
Frequently asked questions
What is the best bitrate for a 1080p YouTube upload?
For 24 to 30 fps, a VBR target of 16 to 20 Mbps works well, and 24 to 30 Mbps for 60 fps. Going higher is fine but brings diminishing returns. Going lower than about 10 Mbps gives YouTube's encoder less detail to preserve.
Should I export in H.264 or H.265 for YouTube?
H.264 is the safe default because every editor and every upload path handles it well. H.265 makes smaller files at the same quality, which helps with large 4K uploads. YouTube accepts both and re-encodes either one, so pick based on file size and export speed.
Why is my YouTube video stuck at low quality after upload?
YouTube processes the lower resolutions first so the video can go live quickly. The HD and 4K versions finish later, sometimes an hour or more for long uploads. Wait for processing to complete before you judge the final quality, and check the gear menu to see which resolutions are ready.
More in Video Editing
Video Editing
B-Roll for Talking Head Videos That Keeps Viewers Watching
A talking head video can lose half its viewers in the first minute, and the face on screen is rarely the reason.
Video Editing
Jump Cuts in Talking Head Videos Without Looking Choppy
You trimmed every pause out of your talking head video, and now it looks like your face is glitching every four seconds.
Video Editing
How to Sync External Audio to Video in Any Editor
You recorded an interview with a lav mic into a separate recorder, the camera captured its own scratch track, and now you have...