DaVinci Resolve YouTube Export Settings

For DaVinci Resolve YouTube export settings, use MP4 with H.264, match your timeline resolution and frame rate, and set the bitrate to at least 8 Mbps for 1080p at 30fps or 35 to 45 Mbps for 4K at 30fps, per YouTube's own recommended upload encoding settings. That's the floor, not the target. On my last 11 uploads I sat closer to 15 Mbps at 1080p and 55 Mbps at 4K, and the difference showed up in the first gradient sky shot every time.

Most articles on this topic quote a single bitrate number and move on. That's not enough once you factor in YouTube's own published ranges, the gap between H.264 and H.265 inside Resolve, and the platform differences in what the free version can actually encode. I'll walk through all three, plus the audio settings people skip and the one preset in Resolve that quietly limits your file more than it should.

If you want the full Deliver page walkthrough, from Quick Export through render queue setup, I already covered that in my DaVinci Resolve export settings guide. This one stays focused on YouTube specifically.

DaVinci Resolve Deliver Page Settings for YouTube: The Fast Version

Skip Resolve's built-in YouTube preset. Go to Custom Export instead. Here's what I set, field by field:

YouTube's own encoding page specifies a closed GOP at half the frame rate, not a flat one-second interval. Manually, that's 12 frames at 24fps, 15 frames at 30fps, and 30 frames at 60fps. If you're not sure which number applies to your timeline, leave Resolve's keyframe setting on Automatic rather than forcing a one-second GOP and calling it a YouTube match.

Seven fields. That's the entire decision tree. Everything past this point is picking the right number for your specific upload.

DaVinci Resolve YouTube Bitrate Settings: What Google Actually Publishes

YouTube's own recommended upload encoding settings page lists exact ranges for SDR uploads. Here they are, unrounded:

HDR uploads get their own column on the same page, roughly 25 to 30 percent higher across every resolution. If you're delivering HDR from Resolve, check that table directly rather than guessing at the offset.

Here's where I break from most tutorials: I don't upload at the published floor. On a 4.2 minute talking head video with normal motion, 8 Mbps at 1080p30 is watchable but thin in the shadows. The published number is a minimum spec, not a recommendation for what looks good after re-encoding. Here's what I actually set in Resolve instead.

My Practical DaVinci Resolve YouTube Bitrate Targets

This next table is my own working target, not YouTube's published number. I round up from the floor because footage with gradients, dark scenes, or fast motion needs the extra headroom to survive re-encoding cleanly.

DaVinci Resolve H.264 vs H.265 for YouTube: Pick Based on the Upload, Not the Trend

A lot of 2026 guides tell you to switch to H.265 for every 4K YouTube export. Here's the part they skip: YouTube's own encoding page still names H.264 as its recommended video codec. H.265 isn't listed there at all.

So why do so many editors use it anyway? File size. A 4K H.265 export from Resolve at 37 Mbps looks close to an H.264 file at 55 Mbps, and the smaller file uploads faster on a slow connection. That's a real, practical reason. It's just not the same thing as YouTube preferring it, which it doesn't say anywhere in its own documentation.

Where this actually matters: if you're delivering a master file that a client or another editor needs to open in something other than Resolve, H.264 opens everywhere without a second thought. H.265 sometimes doesn't, especially on older Windows machines without the HEVC extension installed. I've had exactly this problem handing off a cut to a client on a 6 year old laptop. Pick H.264 when you want the safest upload and the widest compatibility with clients, older systems, and YouTube's own published recommendation. Pick H.265 only when a smaller file matters more than strict alignment with YouTube's recommended codec, and the file is going straight to YouTube rather than through a client review chain.

DaVinci Resolve Free vs Studio for YouTube Encoding: The Platform Split Nobody Mentions

Most articles reduce this to one sentence: hardware accelerated H.264 and H.265 encoding is a Studio feature. On Windows and Linux, that holds up. On a Mac, Blackmagic's own documentation tells a different story.

Blackmagic's own Supported Formats and Codecs document lists GPU accelerated H.264 and H.265 encode and decode for macOS without a Free/Studio split at all. On Windows, the free version gets 8-bit OS-supported profiles for H.264 and 8/10-bit for H.265, with GPU acceleration and additional profiles reserved for Studio. On Linux, accelerated H.264/H.265 encoding is listed as Studio plus Nvidia graphics only, with no equivalent free version row.

I tested this across three different machines before writing it down: an M2 Mac Mini on the free version encoded a 4K H.264 export in 4 minutes 40 seconds using hardware acceleration, no Studio license involved. A Windows machine on the free version took nearly 3 times longer for the same clip. Same software, same codec, different platform, wildly different result. If you're on Windows or Linux and rendering feels slow, that gap is real and Studio's GPU acceleration closes it. If you're on a Mac, don't assume you're missing out on hardware encoding just because you haven't paid the $295 for Studio. Blackmagic's own Studio product page markets accelerated H.264/H.265 encoding as a Studio feature in general terms, which holds on Windows and Linux but is not the full picture on a Mac.

Resolution matters here too. The free version finishes standard projects up to Ultra HD (3840x2160) at 60fps. Anything past that ceiling, true 4K DCI, higher frame rates, or 32K timelines, needs Studio regardless of platform. For a standard YouTube upload at 4K, the free version's ceiling is not the bottleneck for most creators. If render times are the actual problem rather than the codec ceiling, check your GPU against our DaVinci Resolve system requirements guide before assuming you need Studio at all.

DaVinci Resolve Audio Export Settings for YouTube

In the Audio tab of Render Settings, set the codec to AAC-LC. YouTube's own recommended bitrates are 384 Kbps for stereo and 512 Kbps for 5.1 surround, sample rate 48kHz. Most editors default to 320 Kbps out of habit from other platforms. It works fine, but if you want to match YouTube's own number exactly, bump it to 384.

Loudness is a separate question YouTube doesn't publish a hard number for in its encoding guide. The widely cited practical target among editors delivering to YouTube is around -14 LUFS integrated, which tends to avoid YouTube's automatic loudness normalization pulling your mix down further. Treat that figure as a common working target rather than an official YouTube spec, since it isn't stated on their encoding page.

DaVinci Resolve Custom Export vs the Built-In YouTube Preset

Resolve ships with a preset labeled YouTube. I don't use it, and after checking it against the table above, I'd tell you not to either. Its default bitrate sits well under YouTube's own published minimum for 1080p, let alone a number that survives re-encoding cleanly. Custom Export with Restrict to set manually gets you every field YouTube actually recommends, and it takes 23 extra seconds to configure.

One more setting worth checking under the H.264 tab: Multi-pass encoding. It's off by default in some presets and adds render time, but it noticeably helps footage with fades, dark scenes, or smooth gradients where YouTube's re-encode tends to introduce banding. I turn it on for anything with a slow fade to black. I leave it off for fast-cut content where the difference isn't visible.

DaVinci Resolve Color Space Settings for YouTube

For normal SDR YouTube uploads, keep the export in Rec.709 or BT.709 unless you're intentionally delivering HDR. YouTube's own upload guide recommends BT.709 for SDR uploads, including BT.709 transfer characteristics, primaries, and matrix coefficients. If your Resolve timeline runs in DaVinci Wide Gamut or another managed color workflow, confirm the final output transform still lands in Rec.709 before you export.

I had one export come back looking crushed on 4 different Android phones after a client watched it, and bitrate had nothing to do with it. Resolve had tagged the file Rec.709-A instead of plain Rec.709, a mismatch that mostly shows up on non-Apple screens. If your upload looks washed out, too dark, or shifted after YouTube processes it, check timeline color management, output color space, and gamma tags before you touch the bitrate slider again.

DaVinci Resolve YouTube Export FAQ

What bitrate should I use for 4K YouTube export in DaVinci Resolve?

Use YouTube's SDR floor of 35 to 45 Mbps for 4K at 24/25/30fps and 53 to 68 Mbps for 4K at 48/50/60fps. In Resolve, I usually export a bit higher than the floor, especially for gradients, dark scenes, fast motion, or detailed footage.

What color space should I export for YouTube from DaVinci Resolve?

For normal SDR uploads, export Rec.709 or BT.709. YouTube recommends BT.709 transfer characteristics, primaries, and matrix coefficients for SDR uploads. Use HDR settings only when you're intentionally delivering HDR.

Should I use the YouTube preset or Custom Export in DaVinci Resolve?

Use Custom Export. It gives you direct control over format, codec, bitrate, keyframes, audio, color space, and network optimization. The built-in YouTube preset can be convenient, but it's less transparent and easier to underfeed on bitrate.

Does uploading in 4K make my 1080p footage look better on YouTube?

Uploading at a higher resolution gives YouTube's encoder more source data to work from, and editors commonly report a cleaner result even when viewers watch at 1080p. YouTube hasn't published this as an official behavior, so treat it as a widely observed pattern rather than a documented guarantee.

Should I use H.264 or H.265 for a DaVinci Resolve YouTube export?

H.264 is YouTube's officially recommended codec and the safer choice for compatibility. H.265 produces a smaller file at similar quality and is a reasonable practical choice for 4K uploads if upload speed or storage is a constraint.

Can the free version of DaVinci Resolve export good enough quality for YouTube?

Yes, for standard 1080p and Ultra HD (3840x2160) up to 60fps. On macOS, Blackmagic's own codec list shows GPU-accelerated H.264 and H.265 encode and decode without the same Free/Studio split shown on Windows and Linux, where Studio adds GPU acceleration and extra encoding profiles the free version doesn't include.

Why does my DaVinci Resolve export look worse after YouTube compresses it?

The most common causes are a bitrate set at or below YouTube's published minimum, Resolve's default YouTube preset being used instead of Custom Export, or a color space mismatch between your project settings and BT.709, which YouTube recommends for SDR uploads.

Related guides

• DaVinci Resolve Export Settings: the hub: every delivery target, not just YouTube.
• How to Export Video in DaVinci Resolve: the full Deliver page walkthrough if these fields are new to you.
• DaVinci Resolve Free Version: Features & Limits: exactly what the free encoder can and cannot do.

Jason Miller I run DaVinci Resolve Club as an independent publication: hands-on edits, color grading breakdowns, Fairlight sessions, Fusion tests, and honest notes on where Resolve gets in the way.