The best export settings for YouTube are an MP4 container with H.264 video and AAC-LC audio, encoded at YouTube’s recommended bitrates: 8 Mbps for 1080p30, 12 Mbps for 1080p60, 16–24 Mbps for 1440p, and 35–68 Mbps for 4K, with audio at 384 kbps stereo. Everything else is refinement — and the tables below cover all of it.
One piece of context makes every number make sense: YouTube re-encodes every upload. Viewers never see your file; they see YouTube’s compressed versions of it. Your export settings therefore set a quality ceiling, not the delivery quality — export too low and YouTube compresses an already-compressed file, stacking artifacts. The goal is a clean, high-quality master that survives the platform’s transcode, without rendering a 40 GB file for a vlog.
The Bitrate Tables
These are YouTube’s official recommendations for SDR (standard dynamic range) uploads, per Google’s recommended upload encoding settings, retrieved July 2026:
| Resolution | 24/25/30 fps | 48/50/60 fps |
|---|---|---|
| 720p | 5 Mbps | 7.5 Mbps |
| 1080p | 8 Mbps | 12 Mbps |
| 1440p (2K) | 16 Mbps | 24 Mbps |
| 2160p (4K) | 35–45 Mbps | 53–68 Mbps |
HDR uploads run about 25% higher:
| Resolution | 24/25/30 fps (HDR) | 48/50/60 fps (HDR) |
|---|---|---|
| 1080p | 10 Mbps | 15 Mbps |
| 1440p (2K) | 20 Mbps | 30 Mbps |
| 2160p (4K) | 44–56 Mbps | 66–85 Mbps |
Treat these as minimum-comfortable targets for a VBR encode, not hard caps. Going moderately above them (say, 16 Mbps for 1080p30) costs upload time and can rescue difficult footage — confetti, rain, film grain, fast gameplay — but returns diminish quickly, because YouTube’s transcode is the bottleneck either way. Going below them is where quality visibly dies.
The Settings That Aren’t Bitrate
The rest of YouTube’s recommended recipe, straight from the same Google support page:
| Setting | Recommended value |
|---|---|
| Container | MP4, moov atom at the front (“fast start”), no edit lists |
| Video codec | H.264, High Profile, progressive scan |
| GOP / keyframes | Closed GOP, keyframe interval of half the frame rate |
| Chroma subsampling | 4:2:0 |
| Audio codec | AAC-LC (Opus also accepted) |
| Audio bitrate | 384 kbps stereo, 512 kbps for 5.1 |
| Sample rate | 96 kHz or 48 kHz |
| Frame rate | Same as recorded — don’t resample 24 to 30 |
Most editors set the container details correctly by default; the two people actually get wrong are frame rate (export at whatever you shot — resampling creates stutter) and audio bitrate (128 kbps AAC is a podcast setting, not a music-bed setting; use 320–384 kbps).
Should You Export H.264, HEVC, or AV1?
H.264 remains the default answer: it’s what YouTube’s recommendations specify, every editor exports it fast, and at these bitrates it’s visually clean. YouTube will re-encode your upload into VP9 and AV1 for delivery regardless of what you feed it — the viewer-side codec is not your decision to make.
Higher-efficiency upload codecs (HEVC, AV1) are accepted and produce smaller files at equal quality, which matters on slow connections. And for maximum-fidelity masters, YouTube happily ingests ProRes — enormous files, but the cleanest possible source for the platform’s transcode. When each codec earns its place is covered in H.264 vs ProRes: When to Use Each, and if your source footage is a WebM or MOV your editor dislikes, the format trade-offs are in the MP4 vs WebM vs MOV guide.
Does Uploading in 1440p or 4K Actually Look Better?
Often, yes — even for 1080p viewers. YouTube has historically allocated its more efficient codecs and higher-bitrate transcodes to higher-resolution uploads first, which is why creators upscale 1080p projects to 1440p or 4K before uploading: the 1080p stream derived from a 4K upload frequently looks cleaner than the stream from a native 1080p upload. It’s a workaround, not a documented guarantee, and it costs render time and upload size.
Whether shooting and editing in 4K is worth it in the first place is a separate question — 4K vs 1080p for motion graphics breaks down where the extra pixels pay off and where they don’t.
Per-Editor Quick Recipes
Premiere Pro
- File → Export → Media, format H.264.
- Preset “Match Source – Adaptive High Bitrate” as a base; confirm resolution and frame rate match your sequence.
- Bitrate Settings: VBR, 2 pass; target from the table above (8 Mbps for 1080p30, 12 for 1080p60), maximum ~1.5× target.
- Audio: AAC, 320 kbps, 48 kHz. Export.
DaVinci Resolve
- Deliver page → YouTube preset for a one-click 1080p master, or Custom for control.
- Custom: Format MP4, Codec H.264, “Restrict to” the table bitrate in kbps (12,000 for 1080p60).
- Check Network Optimization — that’s Resolve’s “moov atom at front” switch.
- Audio: AAC, 320 kbps. Add to render queue and render.
CapCut
- Export button → Resolution to match your project (1080p minimum; 4K if your footage is 4K).
- Frame rate to match your footage — don’t let CapCut resample 60 fps gameplay to 30.
- Bitrate: the highest option offered. CapCut’s “Recommended” sits below YouTube’s table values, and effects-heavy footage shows it.
- Format MP4, codec H.264. Export.
A note on hardware encoders
NVENC, Quick Sync, and Apple’s hardware encoder render dramatically faster than software x264, at slightly lower efficiency — a hardware encode needs roughly 10–20% more bitrate to match software quality. For YouTube uploads the fix is trivial: use the hardware encoder and set the bitrate a notch above the table (say 10 Mbps instead of 8 for 1080p30). The render-time savings are worth far more than the marginally larger upload.
Shorts and vertical video
Shorts follow the same logic rotated 90 degrees: 1080×1920, H.264 MP4, same per-resolution bitrate guidance as 1080p. Export vertical projects at their native frame size — uploading a horizontal video with black pillarboxes baked in wastes bitrate on black pixels and disqualifies the video from the Shorts shelf.
If the exported file comes out enormous and you need a smaller local copy after uploading the full-quality master, that’s a different problem with different settings — see How to Reduce Video File Size.
FAQ
What bitrate should I use for 1080p 60fps YouTube uploads?
12 Mbps, per YouTube’s official recommendation (as of July 2026). Fast-motion content — gameplay, sports, confetti — benefits from pushing toward 16 Mbps with VBR 2-pass encoding.
Is a higher bitrate than YouTube recommends worth it?
Moderately higher, sometimes: complex motion survives the platform transcode better from a 1.5–2× master. Beyond that, no — YouTube’s re-encode is the quality bottleneck, and a 100 Mbps H.264 upload delivers the same streams as a 20 Mbps one, minus hours of upload time.
Should I use VBR or CBR for YouTube?
VBR (variable bitrate), 2-pass where your editor offers it. VBR spends bits where the footage needs them; CBR wastes bitrate on static shots and starves complex ones. CBR is for live streaming, not uploads.
What audio settings does YouTube want?
AAC-LC, stereo, 384 kbps, at 48 or 96 kHz. In practice editors capping AAC at 320 kbps are fine — just don’t ship 128 kbps under a music-heavy edit.
Why does my video look blurry right after uploading?
YouTube publishes the low-resolution transcode first and processes HD, 1440p, and 4K versions afterward — anywhere from minutes to hours depending on length and resolution. Check back before re-exporting anything; the blur usually fixes itself.
