YouTube export settings for Resolve, Premiere and Final Cut

Quick answer: Export MP4 with H.264, the frame rate you shot, AAC audio at 48 kHz, and a bitrate taken from YouTube’s own table (8 Mbps for 1080p at 24 to 30 fps, 35 to 45 Mbps for 4K). Then do one test upload to check the colour, because graded footage can go wrong there. Setup takes about 15 minutes once, and a saved preset makes every later export a single click.

What you need before you start

You need a finished timeline, a DaVinci Resolve, Premiere Pro or Final Cut Pro install, and one unlisted YouTube upload to test with. Basic familiarity with the Deliver page, Export dialog or Share menu is enough. Plan on 15 minutes for the first pass and 5 more for the colour check (that is an editorial estimate, not a measured time).

Menu labels below follow guides written for DaVinci Resolve 20 and for current Premiere Pro and Final Cut Pro releases, as of 4 November 2026. Adobe and Blackmagic move buttons between versions, so confirm names in your own build. The sources used here don’t flag any of the Deliver page options as Studio-only, but check your edition.

What YouTube actually asks for

YouTube Help lists an MP4 container with no edit lists and the moov atom at the front of the file (Fast Start), AAC-LC audio, and BT.709 as the standard colour space for SDR uploads. It also says no bitrate limit is required, and the bitrates it publishes are for reference.

The reference numbers, as reproduced in a Contenta bitrate table for SDR H.264 uploads, step up quickly with resolution. The chart plots the low end of each range.

YouTube reference SDR upload bitrate by resolution (low end of range). 24 to 30 fps: 720p 5, 1080p 8, 1440p 16, 2160p (4K) 35; 48 to 60 fps: 720p 7.5, 1080p 12, 1440p 24, 2160p (4K) 53 (Mbps) — YouTube reference SDR upload bitrate by resolution (low end of range)
Source: YouTube recommended upload encoding settings, as reproduced by Contenta (checked 4 November 2026); 4K plotted at the low end of 35 to 45 and 53 to 68 Mbps

For 24 to 30 fps that is 5 Mbps at 720p, 8 Mbps at 1080p, 16 Mbps at 1440p and 35 to 45 Mbps at 4K. For 48 to 60 fps the figures are 7.5, 12, 24 and 53 to 68 Mbps. Mark Studios adds YouTube’s container details: a closed GOP of half the frame rate, 2 consecutive B-frames, and 384 kbps for stereo audio.

Settings by situation

Use this table as a starting point. The YouTube column is the platform’s reference figure; the guide column shows where third-party guides land, which is opinion, not a YouTube requirement.

Situation	Codec	YouTube reference (Mbps)	Notes
1080p, 24 to 30 fps	H.264 High, MP4	8	Guides such as Video Editor London suggest 14 to 20 for headroom
1080p, 48 to 60 fps	H.264 High, MP4	12	Fast motion benefits from the upper end, per ANFX (16 Mbps)
1440p, 24 to 30 fps	H.264 High, MP4	16	48 to 60 fps: 24
4K, 24 to 30 fps	H.264 High, MP4	35 to 45	48 to 60 fps: 53 to 68
4K HDR, 24 to 30 fps	HEVC or AV1, 10-bit	44 to 56 (H.264 figure)	YouTube’s HDR page recommends VP9 profile 2, AV1 or HEVC
Vertical Shorts, 1080×1920	H.264 High, MP4	Not in the table used here	Guides disagree: SFX Engine says 10 to 15, Pixflow says 8 target with 12 maximum
Master or archive file	ProRes 422 HQ or DNxHR HQX	Not for upload	Miracamp recommends these for lossless-like masters

The 4K HDR figure comes from Unifab’s 4K guide. YouTube’s HDR upload page asks for 10 or 12-bit colour depth and PQ or HLG transfer, and says ProRes 422 and DNxHR HQX work but need very high bitrates.

Steps in DaVinci Resolve

Resolve’s Deliver page has a YouTube preset at the top of the Render Settings panel, according to Uncle’s Resolve guide. Treat it as a starting point and check each field against the table above.

Open the Deliver page (the rocket icon at the bottom of the window).
Set Format to MP4 and Codec to H.264, with resolution and frame rate matching the timeline.
Under Quality, choose Restrict to and type the bitrate in kb/s, for example 8,000 for 1080p30 or 35,000 to 45,000 for 4K30. A Japanese Resolve 20 guide notes that the Mac H.264 and HEVC setup doesn’t expose VBR or CBR directly, so Restrict to is the control you get.
In Advanced Settings, set Encoding Profile to High. The same Uncle guide says the Network Optimization checkbox handles the fast-start layout.
On the Audio tab, set Codec to AAC, Bitrate to 384 kbps if the field allows it, and sample rate to 48 kHz, as davinciresolve21.com describes.
Click the three dots at the top right of the render settings panel and choose Save as new preset, as Pixflow suggests, so you don’t rebuild this next time.

Steps in Premiere Pro and Final Cut Pro

In Premiere Pro, ANFX gives the path as File, Export, Media with Format H.264. Start from the Match Source, Adaptive High Bitrate preset and confirm that frame size and rate match the sequence.

Switch Bitrate Encoding to VBR, 2 pass, with the target from the table and a maximum of about 1.5 times the target (8 and 12 Mbps for 1080p30). Audio is AAC at 48 kHz. A gaming-video guide says Adobe describes 2 pass as often giving higher quality at the cost of a longer encode, and several guides tell you to tick Use Maximum Render Quality.

In Final Cut Pro, Apple Support says to select the project, click Share, choose Social Platforms, then click Settings for resolution, compression and caption options. Apple’s Social Platforms page says Multi-pass (Better) maximises quality and Single-pass (Faster) speeds things up. It also lists Allow export segmentation, which sends segments to available media engines to speed up H.264 and HEVC exports.

Apple’s documentation lists no numeric bitrate field for this destination. If you need to hit a specific figure, check the exported file’s bitrate in a media inspector before uploading.

Setting	DaVinci Resolve	Premiere Pro	Final Cut Pro
Where	Deliver page	File, Export, Media	Share, Social Platforms
Codec	MP4, H.264	H.264	H.264 (per Apple’s iPad notes)
Bitrate control	Quality, Restrict to (kb/s)	Target and Maximum (Mbps)	No numeric field listed
Quality pass	Multi-pass option in Advanced	VBR, 2 pass	Multi-pass (Better)
Colour tag	Advanced: Color Space Tag, Gamma Tag	Standard Rec.709 output	Handled by the destination

Getting graded colour through the export

A LUT or a manual grade is baked into the pixels at export. What the export settings control is the tag that tells players how to read those pixels. That’s why a grade can look right in Resolve and washed out on YouTube.

The usual culprit is the gamma tag. Knut Erik Evensen describes two fixes. One is to keep a Rec.709 Gamma 2.4 timeline, set the Deliver page Color Space Tag to Rec.709 and the Gamma Tag to Rec.709-A. The other is to set both timeline and output colour space to Rec.709-A. He reports no gamma shift in QuickTime Player or on YouTube with the first method.

Pixflow takes a different view for mixed audiences: Rec.709-A on Mac, Gamma 2.4 for viewers mostly on Windows and Android, with timeline, output and tag all matching. These two guides don’t fully agree, and a contributor on the Adobe Community forum warns that Rec.709-A adds a tag Premiere doesn’t write, which can confuse a Mac check of a file that passes through both apps.

The practical resolution is a test. Export a 10-second clip with your chosen tag, upload it unlisted, and compare it with the timeline on a phone and a desktop browser. Also check that Resolve’s output is set to Video levels rather than Data levels, a mismatch Hollyland’s guide names as a common cause of dull exports.

What the file size will be

Our calculation (video plus 384 kbps audio, container overhead ignored): at 1080p, 8 + 0.384 = 8.384 Mbps; 8.384 × 60 s ÷ 8 = 62.9 MB per minute, so about 629 MB for 10 minutes. At 4K using the 35 Mbps low end, 35 + 0.384 = 35.384 Mbps; 35.384 × 60 ÷ 8 = 265.4 MB per minute, so about 2,654 MB for 10 minutes. That is 2,654 ÷ 629, or about 4.2 times the 1080p file.

That ratio matters when a guide tells you to export 1080p footage at 4K. Video Editor London says it triggers YouTube’s higher-quality VP9 or AV1 encodes, and Swarmify suggests 1440p for the same reason. YouTube’s own page doesn’t say this, so the extra upload time is a trade you make on a guide’s word.

Common mistakes and fixes

Bitrate set far below the table. A 4 Mbps 1080p target gets crushed by YouTube’s re-encode, per Pixflow’s Premiere guide. Fix: use at least the reference figure for your resolution and frame rate.
Frame rate changed at export. Guides including Alan Spicer’s summary of YouTube’s advice say to keep the recorded rate. Fix: set the export to match the timeline, and use the 48 to 60 fps row only for footage that really is 48 to 60 fps.
Washed-out colour after upload. Usually a gamma tag mismatch. Fix: pick one of the tag pairings above, re-export a short clip and compare.
Uploading the master. ProRes and DNxHR files are accepted for HDR but need very high bitrates, per YouTube’s HDR page. Fix: keep them as masters and upload an H.264 or HEVC delivery file for everyday use.
Slow processing after a fast upload. A moov atom at the end of the file or edit lists can cause trouble, per YouTube Help. Fix: tick Network Optimization in Resolve and avoid edit lists.
Trusting the preset blindly. The davinciresolve21.com guide advises verifying every field against YouTube’s current settings. Fix: save your own preset once you have.

What this means for you

If you publish mostly 1080p at 24 to 30 fps, build one preset at 8 to 12 Mbps and save it, then raise the bitrate only if a test upload shows banding in skies or gradients. If you shoot 4K, start at 35 to 45 Mbps and expect files roughly four times larger than the 1080p equivalent.

Mac-based Final Cut Pro users can use Social Platforms with Multi-pass (Better) and spend their time on the colour test instead. Resolve users grading for a mixed audience should run the gamma tag test before the first client delivery.

Sources

Header image: illustration, AI-generated.