YouTube export settings for Resolve, Premiere Pro and Final Cut

Quick answer: export an H.264 MP4 at the bitrate YouTube lists for your resolution and frame rate (8 Mbps for 1080p up to 30 fps, 35 to 45 Mbps for 4K at the same rates), keep the timeline’s frame rate, and make sure the file is tagged Rec.709. Do it once, save it as a preset, and every later export is a single click.

What you need and how long it takes

You need a finished timeline in DaVinci Resolve, Premiere Pro or Final Cut Pro, and a YouTube channel to upload to. Allow 15 to 20 minutes to build and save a preset (that’s an estimate for a first pass, not a measured figure). After that the work is choosing the preset and pressing a button.

The settings here follow YouTube’s recommended upload encoding settings, which Google flags as aimed at partners using YouTube Studio Content Manager but which creators use as the working reference. The page asks for an MP4 container with no edit lists and the moov atom at the front of the file (Fast Start), and AAC-LC, Opus or Eclipsa Audio. The audio sample rate is 48 kHz.

Software versions matter for menu names. As of 17 November 2026, Wikipedia lists DaVinci Resolve 21 as the current major version, and the Resolve steps below follow a Resolve 21 export guide. The Premiere Pro steps follow a September 2026 write-up on Premiere 26.5.1, and Adobe has released a newer Premiere version since, so labels in its Export panel may have moved. None of the sources flag these particular settings as limited to a paid tier, but check your own edition.

The YouTube numbers to export against

YouTube’s bitrate figures are recommendations for reference. As reproduced by YouTuber and consultant Alan Spicer, for standard SDR uploads YouTube recommends around 8 Mbps for 1080p at 24 to 30 fps, 12 Mbps for 1080p at 48 to 60 fps, 35 to 45 Mbps for 4K at 24 to 30 fps, and 53 to 68 Mbps for 4K at 48 to 60 fps. A June 2026 update on Joseph Nilo’s site repeats the same four figures. I couldn’t read the numeric table on YouTube’s own page in my research, so confirm them there before you lock a preset.

YouTube recommended SDR upload bitrate bands. Low end of recommended range: 1080p, 24-30 fps 8, 1080p, 48-60 fps 12, 4K, 24-30 fps 35, 4K, 48-60 fps 53; High end of recommended range: 1080p, 24-30 fps 8, 1080p, 48-60 fps 12, 4K, 24-30 fps 45, 4K, 48-60 fps 68 (Mbps)
YouTube recommended SDR upload bitrate bands
Source: YouTube recommended upload encoding settings, as reproduced by Alan Spicer and Joseph Nilo (2026); 1080p figures are single values

The jump from 1080p to 4K is steep. Our calculation: a 10-minute 4K clip at the top of the 30 fps band is 45 Mbps × 600 s = 27,000 Mb, which divided by 8 is 3,375 MB, or about 3.4 GB of video. The same 10 minutes of 1080p at 8 Mbps is 8 × 600 ÷ 8 = 600 MB, so the 4K file is roughly 5.6 times larger (video only, audio excluded).

Higher is not automatically better. Total Media’s upload guide says to treat the figures as reference values, since complex motion or a different encoder may need testing, and a higher bitrate cannot repair a poor source. Export at the resolution you actually shot or edited in, because upscaling 1080p to 4K only makes a bigger file.

Settings by situation

Situation Format and codec Video bitrate (Mbps) Frame rate Note
1080p, talking head or tutorial MP4, H.264 High 8 Match timeline (24 to 30 fps) YouTube’s reference figure for SDR
1080p, gameplay or sport MP4, H.264 High 12 Match timeline (48 to 60 fps) Fast motion is where low bitrates show first
4K, cinematic or travel MP4, H.264 High 35 to 45 Match timeline (24 to 30 fps) Aim for the upper half if the footage is detailed
4K, high frame rate MP4, H.264 High 53 to 68 Match timeline (48 to 60 fps) Check file size and upload time first
Master or archive copy QuickTime, ProRes Set by the ProRes flavour Match timeline Keep this, upload the H.264 copy

Audio is the same in every row. Soundstripe summarises YouTube’s audio guidance as 128 kbps for mono, 384 kbps for stereo and 512 kbps for 5.1, at 48 kHz.

Apple’s documentation supports the master-file row: Final Cut Pro’s Export File command produces a high-quality file that can serve as source media for the final stages of post-production or distribution. Apple lists Apple ProRes (all versions), H.264 and HEVC among the Export File formats.

DaVinci Resolve: Deliver page steps

  1. Open the Deliver page. It’s the rocket icon at the bottom of Resolve.
  2. Pick the YouTube preset. It sits at the top of the Render Settings panel. Choose the resolution version that matches the timeline. According to the Resolve 21 Reference Manual, as described by Resolve Club, the preset renders one clip at the timeline frame rate with MP4, H.264 High and AAC.
  3. Check Resolution and Frame rate against the timeline. A preset can override the timeline resolution, so reset it to the native value if it has.
  4. Set quality deliberately. Resolve’s “Restrict to” field is a maximum data rate, so type a figure from the table rather than leaving a huge value in place.
  5. Open Advanced Settings. Type half your frame rate into Key Frame Every (15 at 30 fps, 12 at 24 fps, 30 at 60 fps). Tick Network Optimization for the fast-start file layout.
  6. Set audio. On the Audio tab choose AAC, 384 kbps if the field allows manual entry, at 48 kHz.
  7. Save it. Choose Save as New Preset from the three-dot menu in Render Settings, name it, and tick Add to quick export.

If you sign in to YouTube under Preferences > System > Internet Accounts, you can tick Upload directly to YouTube.

Premiere Pro: Export panel steps

  1. Open the export dialog. Use File > Export > Media (Ctrl + M).
  2. Set Format to H.264. The write-up on Premiere 26.5.1 says Adobe recommends H.264 for most online videos.
  3. Start from a Match Source preset. Match Source – Adaptive High Bitrate, then VBR 2 Pass with a target at or above YouTube’s 12 Mbps for 1080p60 SDR is the example given there. Adobe’s own community FAQ also names the older route: “YouTube 1080p Full HD” for HD and “YouTube 2160p 4K Ultra HD” for 4K.
  4. Set the profile. Change Profile to High.
  5. Choose the bitrate mode. Guides disagree: Adobe Basics suggests CBR, while others use VBR 2 pass. Either works if the target follows the table; VBR 2 pass spends bits where the picture is busy and takes longer to render.
  6. Save the preset. Click the three dots next to Preset and choose Save preset.

For speed, Adobe’s community FAQ points to Video tab > Encoding Settings > Performance > Hardware Encoding, if your CPU is Quick Sync capable or your GPU is supported. The same post says changes to those settings require a reboot. Choosing Queue instead of Export sends the job to Media Encoder, which can export multiple files.

Final Cut Pro: Share destination steps

Final Cut Pro manages exports as destinations. Destinations are saved export settings you can use to output clips and projects. I found no Apple page that lists a bitrate field for H.264, so the bitrate-by-number approach below uses Compressor.

  1. Start the export. Choose File > Share > Export File (or press Command-E).
  2. Click Settings at the top of the Share window. The available settings vary based on the format you choose from the Format pop-up menu.
  3. Pick H.264 or HEVC for the upload copy. Pick ProRes for the master. Apple notes that changes you make to a destination’s settings are saved as its defaults.
  4. Need a specific bitrate? Compressor lets you create highly customised export settings and works directly with Final Cut Pro. Create a destination from the Compressor Presets destination and it appears in the Share menu.
  5. Keep your destination. Add one through File > Share > Add Destination. The Destinations pane in Settings lets you modify, delete and bundle destinations, so you can export several outputs at once.

Colour tags and where the LUT sits

Colour problems on export usually start before the Deliver page. PlayPause’s Resolve troubleshooting guide says that on a Rec.709 timeline, HLG footage looks washed out before you render anything, and the fix is a Color Space Transform node from Rec.2100 HLG to Rec.709 Gamma 2.4, or proper project colour management, because no export tag rescues it later. The same logic applies to log footage: convert to Rec.709 with the LUT or transform, grade, then export.

The tag then decides how players read the result. YouTube’s page lists upload colour space problems such as an unspecified transfer characteristic, or a mix of BT.601 and BT.709 primaries and matrix, so export with explicit Rec.709 values.

On a Mac, Resolve has one extra wrinkle. If a QuickTime export looks different from the Resolve viewer, the manual’s named fix is Automatically Tag Rec.709 Scene Clips as Rec.709-A in Preferences > System > General. Per Hey Eddie’s Resolve 21 guide, Blackmagic describes that tag as for exporting “for the web rather than broadcast”. Colourist Knut Erik Evensen’s Resolve 17.2 tests found that using the Rec.709-A gamma tag on export, while keeping the timeline at Rec.709 Gamma 2.4, avoided a visible shift in QuickTime Player, Vimeo and YouTube (his write-up).

Resolve Club cautions that Rec.709-A is a specific Mac, QuickTime and web branch, not a universal delivery standard, and two of the related preferences change the viewer while one changes the file tag, so switch them on one at a time and retest (source).

Common mistakes and fixes

Mistake What you see Fix
Exporting at a bitrate far below the table Blocky or smeared detail in motion Use the table figure for your resolution and frame rate
Preset overrides resolution Wrong frame size on upload Reset Resolution on the Deliver page to the timeline value
Changing frame rate on export Dropped or blended frames Keep the timeline frame rate
Mismatched gamma tag Export looks darker or lighter than the viewer Check Color Space Tag and Gamma Tag, then retest one change at a time
Log footage without a transform Flat, washed-out grade Apply the LUT or colour space transform before export
Missing Fast Start layout YouTube processing trouble Tick Network Optimization in Resolve; use MP4

Two of these deserve a note. On frame rate, Hey Eddie’s Resolve guide is blunt: don’t change the frame rate on export. And for vertical Shorts in Resolve, a Pixflow guide says to set the timeline to 1080×1920 in Project Settings, then set the export resolution to 1080×1920 and toggle on “Use vertical resolution” on the Deliver page.

What this means for you

If you upload mostly 1080p at 24 or 30 fps, build one preset at 8 Mbps and use it everywhere. If you shoot 4K, start near 45 Mbps and check the file size against your upload speed; the 5.6 times jump over 1080p is real.

On a Mac with Resolve, test colour with a short clip before committing a long project: export once with the default tag, once with Rec.709-A, and compare in the browser you’ll watch YouTube in. On Premiere Pro, save a preset from H.264 with Match Source, and on Final Cut Pro, keep ProRes as your master and use Compressor if you need a specific number. Check YouTube’s page for any change in the recommended figures as of today, 17 November 2026.

Sources

Header image: illustration, AI-generated.