DaVinci Resolve Club
Home   Export   DaVinci Resolve YouTube Export Settings
Export

DaVinci Resolve YouTube Export Settings

By Jason Miller Updated Nov 13, 2026 12 min read

Quick answer

Export MP4 with H.264 High at the timeline's resolution and frame rate, AAC at 48 kHz and BT.709 tags. YouTube's SDR reference is 8 Mbps for 1080p (12 at 48 to 60 fps), 16 Mbps for 1440p and 35–45 Mbps for 4K (53–68 at high frame rates). These are references, not minimums.

DaVinci Resolve 21 YouTube export settings on the Deliver page with MP4 H.264 High and 48 kHz audio

For a standard SDR upload, export MP4 with H.264 High Profile at the timeline's resolution and frame rate, AAC audio at 48 kHz and matching BT.709 tags. YouTube's reference bitrate is 8 Mbps for 1080p at 24 to 30 fps (12 Mbps at 48 to 60 fps) and 35–45 Mbps for 4K (53–68 Mbps at high frame rates), and none of those figures is a minimum. Use the YouTube preset for a quick setup or Custom Export when you need more control.

The built-in preset gets you there quicker, and it now covers 720p, 1080p, 1440p and 2160p. Custom Export earns its extra clicks when you need to inspect Quality, keyframes, audio routing or color tags. Whichever you pick, YouTube will re-encode the upload. What you're aiming for is a clean source file with correct timing, color and audio, because no magic setting lets you dodge YouTube's compression.

If the Deliver page itself is new to you, start with the full Resolve export walkthrough. This guide sticks to the YouTube-specific decisions. For every other delivery target, the compact DaVinci Resolve Export Settings hub routes you by task without repeating this YouTube recipe.

DaVinci Resolve YouTube Export Settings: Quick Answer

ControlRecommended starting pointDecision impact
PresetYouTube 720p/1080p/1440p/2160p or Custom ExportBoth are valid; Custom exposes more controls
ResolutionMatch the intended timeline/outputDo not upscale only to chase a codec rumor
Frame rateKeep the intended timeline frame rateYouTube asks for the source frame rate
Format / codecMP4 / H.264Matches YouTube's published upload baseline
Encoding profileHighThe profile named in YouTube's baseline
QualityAutomatic quality, where offered, or a deliberate bitrateResolve's Restrict to field is a maximum data rate
Key framesAutomaticAvoid forcing the wrong GOP for a platform-specific encoder
AudioAAC, normally stereo, 48 kHzMatches YouTube's upload audio guidance
SDR colorBT.709 primaries, transfer and matrixAvoids an avoidable metadata conversion
DaVinci Resolve YouTube preset defaults beside five checks for resolution, render range, 48 kHz audio, burn-in and Rec.709 tags
The YouTube preset is a reasonable start. Match its size and frame rate to the timeline, treat any bitrate cap as a ceiling, and confirm AAC at 48 kHz before you queue the job.

On the YouTube preset, pick the resolution version that matches the timeline and confirm the timeline frame rate. According to the Resolve 21 Reference Manual, the preset renders one clip at the timeline frame rate with MP4, H.264 High and AAC. It can also upload directly once you connect a YouTube account, with chapter markers taken from timeline markers and a thumbnail you select. The preset inherits Data Burn-In from the project as well, so make sure no unwanted burn-in preset is active before you render. All of these preset details still match the 21.1 manual.

On Custom Export, choose MP4 and H.264, then look at the controls your own system offers. Encoder and rate-control choices vary with operating system, GPU, driver and edition. Use a quality-based Automatic setting if the encoder has one, or set a deliberate bitrate and check a short export. Every encoder has its own Quality menu, so expect the layout to change from one machine to the next. Resolve describes Restrict to as a maximum data rate. It caps the bitrate without promising a guaranteed average, and the field takes Kb/s, so convert from Mbps first.

For a finished edit, choose Single clip and confirm Entire Timeline in the render-range menu; save In/Out ranges for deliberate excerpts. Check the filename and destination, add the job to the Render Queue, then look over the queued job before you render. If Entire Timeline is unavailable, clear clip filtering first. The right codec won't rescue a job that only exports half the timeline.

Keep the timeline's intended frame rate, including fractional rates such as 23.976 or 29.97. With mixed-rate footage or slow motion, sort out the retiming in the edit and keep the export at the timeline rate, whatever one camera happened to shoot. Check pans and lip sync in the rendered sample, because a higher export frame rate can't recreate source frames that were never there.

YouTube Bitrate Recommendations for 1080p, 1440p and 4K

The current YouTube recommended upload encoding settings page gives the SDR references below. Standard frame rate means 24, 25 or 30 fps; high frame rate means 48, 50 or 60 fps. When Resolve asks for Kb/s, multiply the Mbps figure by 1,000.

Resolution24/25/30 fps48/50/60 fps
2160p (4K)35–45 Mbps53–68 Mbps
1440p16 Mbps24 Mbps
1080p8 Mbps12 Mbps
720p5 Mbps7.5 Mbps
YouTube recommended SDR upload bitrates for 720p, 1080p, 1440p and 4K video
YouTube's recommended SDR upload references vary by resolution and standard or high frame rate.

These numbers don't set a quality floor, and YouTube says outright that no bitrate limit is required. Use them as a size-and-quality reference for an H.264 upload. A quality-based export may come out larger; a manually restricted one may be smaller and more predictable. Fast motion, grain, particles and gradients are much harder to compress than a locked-off talking head, so inspect a representative rendered section before you commit to a long queue.

YouTube's H.264 baseline also names progressive scan, two consecutive B-frames, CABAC, 4:2:0 chroma, variable bitrate and a closed GOP of half the frame rate. Resolve exposes different subsets of these controls depending on container and encoder. I'd leave Key Frames on Automatic unless the selected encoder exposes a reliable manual option and you understand how its value maps to the recommended GOP.

H.264 vs H.265 for a YouTube Upload

Choose H.264 when you want the closest match to YouTube's published baseline and the broadest handoff compatibility. H.265/HEVC can produce a smaller upload at the same visual quality, but how much smaller depends on the encoder and the source. YouTube accepts an HEVC file, and that alone doesn't mean it prefers HEVC for ordinary SDR uploads. No universal H.264-to-H.265 bitrate conversion can replace a test.

For HDR the choice changes, because YouTube requires 10- or 12-bit video and valid HDR metadata. Its HDR upload guidance recommends HEVC, VP9 Profile 2 or AV1. Your Resolve installation may not export every listed codec or profile. And changing an SDR file’s codec or tag alone won't turn it into an HDR master.

Free vs Studio: Check the Controls You Actually Have

Resolve Free’s overall delivery ceiling is Ultra HD 3840×2160 at up to 60 fps. Codec availability is a separate question. Studio extends the resolution and frame-rate ceiling and adds accelerated encoding options on supported systems, yet GPU, operating system and codec combinations still aren't interchangeable.

Before you buy Studio to fix a slow render, compare the Encoder and Audio menus on your own system with the Free edition limits and system requirements. Use software H.264 only where your installation offers it. In particular, don't assume a Linux setup has the same H.264/AAC choices as a Mac or Windows machine. Check the platform-specific codec guide before you select an intermediate file or a separate encoding step.

Audio Export Settings for YouTube

In Render Settings > Audio, export the same Main bus you monitored. Use AAC for a normal MP4 upload, a 48 kHz sample rate, and the correct channel layout. YouTube recommends 384 kbps for stereo and 512 kbps for 5.1. A clean mix matters more than a bigger codec number, especially while the wrong bus, a muted track or clipping is still in there.

For an ordinary stereo upload, export the stereo mix and leave individual timeline tracks out of it. If the AAC encoder doesn't offer exactly 384 kbps, use an available high-quality setting and check the file; YouTube doesn't reject an upload for missing that recommendation. For surround, check the stereo presentation too. YouTube's listed channel layout is stereo plus 5.1, and that's no reason to send a multichannel mix nobody monitored.

Loudness is a different control. The Resolve 21 manual gives -14 LUFS as the YouTube loudness target, and the YouTube preset exposes Normalize Audio. That normalization uses Resolve's delivery target. YouTube's upload form doesn't accept or reject a file by its loudness. The Resolve LUFS and audio-level guide covers integrated loudness, true peak and bus measurement without mixing them up with AAC bitrate.

To mix toward that target instead of leaving it to the render, open File > Project Settings > Fairlight and set Target Loudness Level in the Audio Metering section to -14 LUFS. The "0" mark on the loudness meter then moves to -14 LUFS instead of Resolve's default -23 LUFS target. I'd mix to that meter rather than tick Normalize Audio, because then the level approved during playback is the level that renders.

Color Space: SDR BT.709 and the HDR Boundary

For SDR, YouTube recommends BT.709 for color primaries, transfer characteristics and matrix coefficients. If the project uses DaVinci Wide Gamut, ACES or CST nodes, verify that the output transform lands in SDR BT.709 and that the exported file carries matching tags. Color Space Tag and Gamma Tag describe the file, and changing those tags alone won't apply a missing output transform. Raising the bitrate won't fix a color-management problem either.

HDR needs its own master: compatible 10- or 12-bit encoding, Rec.2020 primaries with a non-constant-luminance matrix, and a PQ or HLG transfer function with matching metadata. YouTube publishes separate HDR bitrate references, 44–56 Mbps for 4K at 24/25/30 fps and 66–85 Mbps at 48/50/60 fps. The Resolve color-management guide explains RCM, CST order and double-transform failures before you reach Deliver.

YouTube Preset vs Custom Export

Use the YouTube preset when you want a fast, documented MP4/H.264 High export and optional direct upload. Use Custom Export when you need to control a delivery ceiling, inspect the audio bus, choose a different codec, verify color tags or save a reusable preset. Custom isn't automatically higher quality. It just puts more decisions in front of you.

If the selected MP4 encoder exposes Network Optimization, turn it on for a web-delivery file. YouTube asks for the MP4 moov atom at the front, commonly called Fast Start. Resolve's available controls vary by encoder, so when this packaging detail matters, verify the finished file itself. One checkbox won't behave the same way on every platform.

Before a final upload, check Use Proxy Media, Use optimized media and Use render cached images if the selected preset shows them. Each of those can pull proxy, optimized or cached files into the output. Leave them off when those files are lower quality than the intended master, and make sure the originals are online. Playback proxies and delivery choices are two separate decisions.

Upload Directly to YouTube from DaVinci Resolve

Resolve can render and upload in one job, because the YouTube preset carries its own upload fields. Sign in first: open Preferences, go to the System tab and use the Internet Accounts panel. A floating window takes the account login and any two-factor step, and Resolve signs back in by itself each time it opens.

I'd switch on Review Before Upload in the Render Queue option menu before the first direct upload, because playing the local file is quicker than deleting a bad upload and waiting through YouTube's processing again. With it on, the job stops at "Waiting for Upload" after the render. Right-click the job, reveal the rendered file and play it, then choose Upload to YouTube or Cancel Upload from the same menu. Once an upload finishes, Reveal in Browser on that job opens the video on YouTube.

  1. On the Deliver page, select the YouTube preset and pick the resolution that matches the timeline from its dropdown.
  2. Tick Upload directly to YouTube, choose the channel if the account has more than one, then enter the Title and Description.
  3. Set Visibility and Category, then tick Chapters from Markers and select the marker color you used for chapter points.
  4. Tick Upload Thumbnail and choose a still image if the video needs a custom thumbnail.
  5. Click Add to Render Queue and render. The upload starts when the render finishes, a percentage in the job shows its progress, and Workspace > Background Activity tracks it from any page.

YouTube's chapter list has to start at 00:00, hold at least three timestamps and keep every chapter at least 10 seconds long. Put the first marker of your chapter color on the first frame of the timeline, place at least three of them and keep them 10 seconds or more apart. Keep the last marker at least 10 seconds before the end as well. If chapters aren't available, request access to YouTube's Advanced features.

Signing in also puts the YouTube upload fields into Custom Export, so a custom codec or bitrate can still go up with the same title and description entry. To reuse that setup, choose Save as New Preset from the Render Settings three-dot menu, name it and tick Add to quick export. It then appears in File > Quick Export on every page, and Quick Export can upload to YouTube as well. Only Single clip settings can be saved this way.

Exporting Vertical Video for YouTube Shorts

For a vertical Short, prepare and reframe a portrait timeline (1080×1920 is a practical starting size), then verify the exported dimensions. It's easy to slip into assuming a landscape preset will rotate them, and it won't. YouTube’s player adapts to the file’s aspect ratio, so don't bake black side bars into a widescreen frame. The aspect-ratio guide covers reframing subjects and captions.

For new uploads, YouTube classifies square or vertical videos up to three minutes long as Shorts. Its three-minute Shorts guidance also explains an important exception: a Short over one minute with an active Content ID claim is blocked globally. Check the upload’s classification and restrictions in Studio, because changing the bitrate won't remove a claim.

Why a YouTube Upload Looks Soft, Dark or Incomplete

First, wait for high-resolution processing. YouTube puts up a low-resolution version before 1080p and 4K processing finishes, and high-resolution processing can take hours. Judge the upload only once the quality option you exported for appears.

If it still looks wrong, isolate the failure. Soft blocks in motion point toward the source encode or an overly restrictive data rate. A global gamma or saturation shift points toward color primaries, transfer or matrix tags. Missing sound points toward the selected output bus or the Audio checkbox. If the local file looks different, reimport a short sample into the same managed project, compare it with the timeline, then check another player. That helps separate an export or transform error from player interpretation. If the local file checks out and the processed upload doesn't, investigate metadata, YouTube processing and playback before you touch the grade.

A washed-out look, with lifted blacks and weak saturation, needs the most care: a player mismatch, a data-levels mismatch and a missing output transform all produce it, and no single control fixes all three. My advice is one change per short test render, because two changes at once hide which one was wrong. The washed-out export guide maps each branch, including a file that only looks faded in QuickTime or Safari on a Mac.

Pre-upload checklist for a DaVinci Resolve YouTube export
Verify frame rate, progressive scan, audio, BT.709 tags, a short test file and the final destination before uploading.

Render a short section that contains motion, gradients, dialogue and the darkest shot. Play that file outside Resolve, check the audio, then upload it as unlisted and wait for the intended resolution. It's quicker, and far more reliable, than changing five unrelated settings after a full-length export has gone wrong.

YouTube Export FAQ

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

YouTube recommends 35–45 Mbps for 4K at 24/25/30 fps and 53–68 Mbps at 48/50/60 fps for SDR H.264 uploads. These are reference values; they aren't minimums. A quality-based Automatic mode is another option where your encoder offers one. Either way, check a representative export before you trust the label alone.

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

Both work. The YouTube preset gives you a documented MP4, H.264 High, timeline-frame-rate export and optional direct upload. Use Custom Export when you need explicit control over bitrate, audio routing, codec or color tags.

Should I export H.264 or H.265 for YouTube?

Use H.264 for the closest match to YouTube's published SDR upload baseline and broad compatibility. HEVC can reduce upload size, and it's useful for supported HDR workflows, but no universal bitrate conversion makes it automatically better.

What audio settings should I use for YouTube?

Use AAC in a normal MP4 file, a 48 kHz sample rate, and the bus and channel layout you actually mixed. YouTube recommends 384 kbps for stereo and 512 kbps for 5.1 uploads.

What color space should I export for SDR YouTube video?

Use BT.709 primaries, transfer characteristics and matrix coefficients for SDR. If the project is managed in DaVinci Wide Gamut, ACES or CST, verify the final output transform and the tags. Changing only the codec won't fix either of them.

Does upscaling 1080p to 4K guarantee better YouTube quality?

No. Upscaling can't recreate detail that was never captured, and these upload settings can't guarantee which playback codec or quality a viewer receives. If you want to compare a higher-resolution upload, make a short A/B test and wait for both versions to finish processing. Keep whichever version actually looks better with your footage.

Why is my YouTube upload blurry even though the local export is sharp?

Wait until 1080p or 4K processing finishes; YouTube publishes the low-resolution version first. If the final high-resolution stream is still soft, compare short tests for source quality, frame rate, bitrate restriction and color metadata, one variable at a time.

Updated November 13, 2026 Check version and edition requirements before following a workflow.
Jason Miller
Jason Miller I run DaVinci Resolve Club, an independent publication. My guides explain editing, color, Fairlight, Fusion and delivery, with clear Free vs Studio limits.
Explore the Export hub: Deliver settings, platforms and fixes