· Everpop
Upload MP4 with H.264 video and AAC-LC audio — that is what YouTube's recommended upload encoding settings list. MOV also uploads, and so do ProRes, DNxHR and HEVC. But the container is the small decision. The big one is handing over the cleanest source file you own, before anything has re-compressed it.
What video format does YouTube recommend for uploads?
Google publishes an actual spec sheet, which saves a lot of arguing. The short version of YouTube's recommended upload encoding settings:
| Setting | What the page says |
|---|---|
| Container | MP4, with "No Edit Lists (or the video might not get processed correctly)" and "moov atom at the front of the file (Fast Start)" |
| Video codec | H.264 — "Progressive scan (no interlacing)", "High Profile", "Closed GOP. GOP of half the frame rate", "Chroma subsampling: 4:2:0" |
| Audio codec | "AAC-LC or Opus or Eclipsa Audio", sample rate 48 kHz |
| Audio bitrate | 128 kbps mono, 384 kbps stereo, 512 kbps for 5.1 |
| Frame rate | "Content should be encoded and uploaded in the same frame rate it was recorded" |
| Bitrate mode | "Variable bitrate. No bitrate limit is required, though we offer recommended bit rates below for reference" |
| Color space | BT.709 for SDR uploads |
Two of those lines are worth reading twice. Edit lists are container atoms that describe a timeline of their own — FFmpeg's mov demuxer "modifies the stream index to reflect the timeline described by the edit list" — and YouTube's warning is blunt: a file carrying them "might not get processed correctly". Fast Start puts the index at the front instead of the end. In FFmpeg that is -movflags +faststart — a "second pass moving the index (moov atom) to the beginning of the file", per the FFmpeg formats docs.
Is MP4 or MOV better for YouTube Shorts?
Both upload. YouTube's supported file formats page lists ".MOV, .MPEG-1, .MPEG-2, .MPEG4, .MP4, .MPG, .AVI, .WMV, .MPEGPS, .FLV, 3GPP, WebM, DNxHR, ProRes, CineForm, HEVC (H.265)". Same page, one flat refusal: "Audio files, like MP3, WAV, or PCM files, can't be uploaded to create a YouTube video."
So MP4 versus MOV is close to the wrong question. A container is a box: a .mov holding H.264 and AAC and an .mp4 holding H.264 and AAC are near-twins. What changes the outcome is the codec inside.
A .mov holding ProRes is a different animal. Apple's ProRes white paper puts the target data rate of ProRes 422 HQ at "approximately 220 Mbps at 1920 x 1080 and 29.97 fps" — roughly 27 times the 8 Mbps YouTube recommends for 1080p SDR. That is not waste. The same paper calls ProRes "one of the most popular codecs in professional post-production" and says ProRes 422 HQ stays "visually lossless through many generations of decoding and re-encoding". It is a mastering codec. H.264 is a delivery codec. Use each for the job it was built for:
| What you have | What to hand over | Why |
|---|---|---|
| A camera or editor master in ProRes or DNxHR | The master, if the destination accepts it | No extra generation of lossy encoding |
| A finished edit with no master kept | One H.264 / AAC MP4 at the recommended bitrate | Matches the published spec and moves quickly |
| A file already exported for another platform | Go back for the export it came from | Each extra generation of lossy encoding costs picture |
| An HEVC screen or phone recording | The original, untouched | Re-wrapping costs nothing; re-encoding costs picture |
What bitrate should a vertical Short use?
The SDR recommendations from the same encoding page:
| Resolution | Standard frame rate | High frame rate |
|---|---|---|
| 1080p | 8 Mbps | 12 Mbps |
| 1440p | 16 Mbps | 24 Mbps |
| 2160p (4K) | 35–45 Mbps | 53–68 Mbps |
For HDR, the 1080p figures rise to 10 Mbps and 15 Mbps.
Note the ceiling before exporting a 4K vertical master: YouTube's Shorts creation page states "You can upload Short videos with a maximum resolution of 1080p." Aim at the 1080p row.
Source resolution is a separate question from delivery resolution, and this is where people get it backwards. Reframing a horizontal master into 9:16 is a crop, and a crop spends pixels. Cut the tallest 9:16 window out of a 3840 x 2160 frame and you get 2160 × 9 ÷ 16 = 1215 pixels of width — more than the 1080 columns a 1080 x 1920 Short needs, so the crop still fills the frame with real detail. Run the same crop on a 1920 x 1080 source and the window is 607.5 pixels wide, which must then be stretched to 1080. Identical delivery format; very different picture underneath. Does 4K matter for YouTube Shorts? works through when that gap is visible and when it honestly is not.
What is the pre-upload checklist?
- Vertical or square, three minutes or under. Under the heading "Videos uploaded after October 15, 2024", YouTube's three-minute Shorts page states: "Any videos uploaded on or after this date with a square or vertical aspect ratio up to three minutes in length will be categorized as Shorts on YouTube."
- MP4 container, H.264 High Profile, 4:2:0 chroma, progressive scan.
- AAC-LC audio at 48 kHz — 384 kbps for stereo.
- Frame rate identical to the recorded frame rate. No conforming 24 to 30 to make a timeline tidy.
- Fast Start on, edit lists off.
- 8 Mbps for 1080p standard frame rate, 12 Mbps for high frame rate.
- Inside the hard limits: "The maximum file size you can upload is 256 GB or 12 hours, whichever is less" (YouTube Help).
- Not an audio file with a still image. YouTube refuses those.
One line that matches the container and audio recommendations above:
ffmpeg -i master.mov -c:v libx264 -profile:v high -pix_fmt yuv420p \
-b:v 8M -c:a aac -ar 48000 -b:a 384k -movflags +faststart short.mp4
Reach for that when you must deliver a compressed file. Skip it when the master is still on disk; re-encoding a master to satisfy a spec sheet is rarely a trade worth making. And if the master is ProRes, prefer your editor's own export: Apple warns that "using any unauthorized implementation (like the FFmpeg and derivative implementations) may lead to decoding errors, performance degradation, incompatibility, and instability".
Why does the file's route matter as much as its format?
Every re-encode is a small tax, and the sneakiest happen in transit rather than in your editor. A file pulled back down off a platform has already passed through that platform's encoder, so anything cut from it is a copy of a copy.
That is why Everpop is upload-first. Drag the file into the upload hub, or share one Google Drive "Finals" folder and new exports get picked up through Google's official Drive API — unshare it whenever you like. Pasted YouTube links are refused. It is a channel-safety position as much as a picture-quality one, and sending finished videos for clipping via Google Drive covers the folder setup. Clips come back for review before anything posts, and the editor handoff exports FCPXML, EDL and SRT if you would rather finish in Premiere or Resolve.
The honest summary: MP4 with H.264 and AAC is the safe delivery answer, and it is not what decides how a Short does. One clean generation, the recorded frame rate, and enough pixels to survive a 9:16 crop matter far more than any container argument.
Frequently asked questions
- Do I need to convert MOV to MP4 before uploading a Short?
- No — .MOV appears on YouTube's supported file formats list, so it uploads as-is. YouTube's recommended upload encoding settings list MP4 with H.264 video and AAC-LC audio, but a .mov carrying H.264 and AAC behaves much like an .mp4 carrying the same pair. A .mov carrying ProRes is a mastering file rather than a delivery file.
- What bitrate should I use for a 1080p vertical Short?
- YouTube's recommended settings list 8 Mbps for 1080p SDR at a standard frame rate and 12 Mbps at a high frame rate; for HDR the figures are 10 Mbps and 15 Mbps. The same page notes "No bitrate limit is required, though we offer recommended bit rates below for reference", so treat those numbers as targets rather than ceilings.
- Can I upload a 4K Short?
- YouTube's Shorts creation page states "You can upload Short videos with a maximum resolution of 1080p." Shooting or editing in 4K still helps upstream: cropping a 9:16 window out of a 3840 x 2160 frame leaves 1215 pixels of width, which is more than the 1080 columns a 1080 x 1920 Short needs.
- Does YouTube accept ProRes files?
- Yes. ProRes appears on YouTube's supported file formats list alongside DNxHR, CineForm and HEVC (H.265). Expect a large file: Apple's ProRes white paper puts ProRes 422 HQ at "approximately 220 Mbps at 1920 x 1080 and 29.97 fps", and YouTube's limit is "256 GB or 12 hours, whichever is less".
- Why did my Short upload look soft or process badly?
- Three usual suspects trace straight back to the spec sheet. Edit lists in the container, which YouTube warns can mean "the video might not get processed correctly". A frame rate changed on export, when the guidance is that content "should be encoded and uploaded in the same frame rate it was recorded". And re-encoding a file that was already an export, which stacks one generation of H.264 compression on top of another.
- Can I upload an MP3 with a still image as a Short?
- Not as an audio file. YouTube's supported file formats page says "Audio files, like MP3, WAV, or PCM files, can't be uploaded to create a YouTube video." Render the audio and the image into a video file first — MP4 with H.264 and AAC is the safe choice.