Best Export Settings for YouTube (2026): Resolution, Bitrate, Audio

1What are the best export settings for YouTube?

The settings YouTube itself recommends: an MP4 with H.264 video at the resolution and frame rate you recorded, variable bitrate, and AAC-LC stereo audio at 48 kHz. Everything in the table below is from YouTube Help: Recommended upload encoding settings, checked October 2026. The search results for this query are mostly forum threads, so we start from the first-party page and label our own views.

The bitrates are recommendations for uploads, not what viewers receive. One file rule carries a warning: YouTube asks for an MP4 with no edit lists, “or the video might not get processed correctly”. For every resolution, frame rate and SDR or HDR combination, our free YouTube export settings tool reads the same tables. This guide is about the decisions around them.

2Should I export in 4K or 1080p for YouTube?

Export at the resolution you shot and edited in. If the footage is genuinely 4K, export 4K; if it is 1080p, export 1080p unless you have tested an upscale and seen it help. YouTube's formatting guidelines for partners (checked October 2026) encourage uploads “as close to the original, high quality source format as possible”, and note that YouTube always re-encodes videos.

The question comes from a widely repeated rule: upload above 1080p so YouTube uses a better codec. The poster of the top-ranking thread for this query had heard it too:

Here is what YouTube's help pages actually say. The encoding page says that to view new 4K uploads in 4K, viewers need a browser or device that supports VP9, and the video quality page says some formats such as 1080p and 4K may not be available on devices without VP9 (both checked October 2026). We found no YouTube page that says the upload resolution decides which codec your video is processed with, so the 1440p rule is undocumented practitioner lore. We are not saying it is wrong.

What the upscale costs is documented. Using YouTube's SDR bitrates plus 384 kbps of audio, a 10 minute video at 24 to 30 fps comes to about 0.63 GB at 1080p, 1.23 GB at 1440p and 2.65 GB at 4K (our arithmetic: (8 + 0.384) Mbps x 600 s / 8 = 628.8 MB; the same with 16 and 35 Mbps, the low end of the 4K range). A 1440p frame has 1.78 times the pixels of a 1080p frame and a 4K frame has 4 times, and upscaled pixels add no detail. Our advice: if your 1080p uploads look soft, upload one test both ways and compare on your audience's devices. The video bitrate calculator does the size arithmetic for any length.

3Should I export at 44.1 or 48?

48 kHz. YouTube's recommended upload settings give the sample rate as 48kHz and do not mention 44.1 kHz. That is from the encoding settings page, checked October 2026, which lists AAC-LC, Opus or Eclipsa Audio, stereo or stereo plus 5.1, and 384 kbps for stereo.

The confusion has a source inside YouTube's own help. Its live encoder settings page (checked October 2026) recommends 44.1 KHz for stereo audio and 48 KHz for 5.1 surround. That page is for live streams, not uploads. If you are exporting a file, the upload page is the one that applies.

Export tools do not always convert for you. In our test (section 8), a default ffmpeg export from a 44.1 kHz mono source came out at 44.1 kHz mono; only an explicit -ar 48000 -ac 2 produced 48 kHz stereo. Our advice: convert 44.1 kHz material once, at export.

4Is .MP4 or .MOV better for YouTube?

MP4 is the container YouTube recommends, but .MOV is on its list of supported upload formats, so either will upload. What is inside the file matters more than the wrapper. The first line of the recommended settings is “Container: MP4”, and YouTube's supported file formats list includes .MOV, .MP4, WebM, ProRes, DNxHR, CineForm and HEVC (H.265), among others (both checked October 2026). The HDR article says MOV/QuickTime, MP4 and MKV have been tested to work for HDR.

Apple's Final Cut Pro guide (checked October 2026) says its Social Platforms share option transcodes the project to a MOV file with H.264 video and AAC audio, “suitable for posting on video-sharing websites such as YouTube”. No need to rewrap it.

Some editors upload a high-bitrate master instead. One reply in the same r/davinciresolve thread:

ProRes is on YouTube's supported list, so that works, at the cost of a much larger upload. Our view: MP4 with H.264 for the file YouTube describes, a ProRes MOV only when you also want an archive master.

5Should I export my video in 30 or 60 fps?

Export at the frame rate you recorded. YouTube says content should be encoded and uploaded at the same frame rate it was recorded, so 60 fps footage stays 60 and 30 fps footage stays 30. The encoding page lists 24, 25, 30, 48, 50 and 60 as common rates and says other rates are also acceptable. The partner guidelines are blunter: videos should be in their native frame rates without resampling, because resampling “can cause images to shudder” (both checked October 2026).

The frame rate changes the bitrate band. At 1080p, YouTube recommends 8 Mbps up to 30 fps and 12 Mbps from 48 to 60 fps, so a 10 minute 1080p60 export is about 0.93 GB against 0.63 GB at 30 fps (our arithmetic: (12 + 0.384) x 600 / 8 = 928.8 MB). Converting 30 fps footage to 60 spends that size without adding motion.

One case does change the rate: interlaced footage. YouTube asks for it to be deinterlaced before upload, with the example that 1080i60 should become 1080p30.

6What are the best export settings for HDR on YouTube?

HDR needs its own export: graded in Rec. 2020 with a PQ or HLG transfer function, 10 or 12 bit, tagged with HDR metadata, at 720p to 2160p. HEVC, VP9 Profile 2 or AV1 are the recommended codecs. All of that is from YouTube's Upload HDR videos article, checked October 2026. The SDR settings in section 1 do not carry over, apart from the audio.

• Frame rates: 23.976, 24, 25, 29.97, 30, 48, 50, 59.94 and 60.
• Codecs: VP9 Profile 2, AV1 and HEVC are recommended. ProRes 422, ProRes 4444, DNxHR HQX and 10-bit H.264 also work but need very high bitrates, which the article warns may mean longer upload and processing times.
• Metadata: the transfer function, Rec. 2020 primaries and the Rec. 2020 non-constant luminance matrix must be tagged. PQ videos should also carry SMPTE ST 2086 mastering data and MaxFALL and MaxCLL.
• Bitrate: for H.264 the article points back to the encoding page, which lists 10 Mbps for 1080p HDR (15 at high frame rate) and 44 to 56 Mbps for 4K at 24 to 30 fps.

The article flags one common mistake: mastering in DCI P3 and then tagging the file as Rec. 2020, which gives “an oversaturated look with shifted hues”. Viewers without HDR screens see an automatic SDR version. For iPhone HDR edited in Final Cut Pro, Apple's HDR support article (checked October 2026) says to export an HLG master file or share to Apple devices, then upload the file to YouTube with a web browser.

7Why does my video still look soft on YouTube?

Because YouTube re-encodes every upload, serves each viewer a quality chosen by their connection, screen and browser, and may not have finished the higher qualities yet. Your export settings cannot control any of those three. The poster of an r/youtubegaming thread had tried 30 to 60 Mbps at 1440p and still wrote:

What YouTube itself says, all checked October 2026:

• Every upload is re-encoded. The partner guidelines say “YouTube always re-encodes videos to optimize their playback quality.”
• HD and 4K arrive later. The upload help says higher qualities such as 4K or HD may take more time to process, and the browser support page notes that all qualities may not be available on newly uploaded videos. A video judged in its first minutes may still be playing a lower quality.
• Playback picks the quality. The video quality page lists internet speed, player size, the quality of the original upload and the browser as factors, and says 1080p and 4K may not be available on devices that do not support VP9.
• Noise costs bits. In the HDR article, YouTube says its processing “may remove some noise to achieve streaming bitrates”, and that denoising before rendering can help if a video looks too compressed when streamed. The advice sits in the HDR article, but by our reading the reason applies to any upload: grain and sensor noise use bitrate that detail would otherwise get.

Higher export bitrates are where opinions split. A reply in the same thread argued for 50 Mbps H.265 at 1440p; when another user linked YouTube's recommended settings, the replier answered: “I used to use recommended numbers but it turned out less appealing than what I have now.” YouTube says no bitrate limit is required, so going above its numbers is allowed. Our view: fast game footage and grainy footage are where extra bitrate is most likely to show, a talking head the least. Either way, wait for HD processing to finish before you judge.

8How do I check that my export matches YouTube's settings?

Run ffprobe on the exported file and compare the codec, profile, pixel format, sample rate, channels and atom order with section 1. It takes seconds and catches settings an export dialog hides. To see how far a default export drifts, we made a 10 second 1920x1080, 30 fps ProRes HQ test master with 44.1 kHz mono audio, then exported it twice with ffmpeg 9.0.2: once with only -c:v libx264 -c:a aac, and once with this command, which maps each line of YouTube's list to an ffmpeg option:

ffmpeg -i input.mov \
  -c:v libx264 -profile:v high -pix_fmt yuv420p \
  -bf 2 -g 15 -flags +cgop -coder cabac \
  -b:v 8M -maxrate 12M -bufsize 16M \
  -vf "setparams=color_primaries=bt709:color_trc=bt709:colorspace=bt709" \
  -c:a aac -ar 48000 -ac 2 -b:a 384k \
  -movflags +faststart -use_editlist 0 \
  youtube-1080p30.mp4

Then we probed both files (and used ffprobe -v trace to see the order of the moov and mdat atoms and any elst edit lists):

ffprobe -v error -show_entries \
  stream=codec_name,profile,pix_fmt,r_frame_rate,color_primaries,sample_rate,channels,bit_rate \
  -of compact youtube-1080p30.mp4

The default export carried the 10-bit 4:2:2 format of the source straight through, placed a keyframe only every 250 frames, put the moov atom at the end, wrote edit lists and kept 44.1 kHz mono. That breaks seven lines of YouTube's list: High Profile, 4:2:0 chroma, a GOP of half the frame rate, moov atom first, no edit lists, 48 kHz and stereo. It also left the color untagged, which YouTube's page says it treats as BT.709. The tuned file matched every line we checked. One honest gap: we asked for 384 kbps audio and ffmpeg's built-in AAC encoder delivered about 246 kbps on our test noise, so check that number too. These are our measurements on synthetic test media, not a statement about every encoder.

If you build commands like this often, the ffmpeg command generator writes them in the browser, and our field guide to ffmpeg commands AI gets wrong covers checking an AI-written one before you trust it.

9Where are these settings in Premiere Pro and Final Cut Pro?

Premiere Pro and Final Cut Pro both document a YouTube-ready export; use it, then check the result against section 1. We list only steps the vendor documents on its own help pages.

Premiere Pro. Adobe's export for social media page (last updated January 7, 2026, checked October 2026): select the sequence, choose File > Export > Media, turn on YouTube in the PUBLISH section, and for best results set Format to H.264 and Preset to “Match Source - Adaptive High Bitrate”. The Video section lets you change file format, frame size and bitrate.

Final Cut Pro. Apple's Share on the web guide (checked October 2026): choose File > Share > Social Platforms, click Settings to confirm them, then Next, and save. If the project plays from proxy media, switch the viewer to Optimized/Original first so the export uses full-quality media. The Social Platforms destination offers a Resolution setting and a Compression choice, where “Multi-pass (Better)” maximizes quality.

We left out DaVinci Resolve, whose PDF manual we did not verify for this guide, and CapCut, whose pages we found were marketing articles rather than help documentation.

Frequently asked questions