YouTube Shorts Aspect Ratio and Size: The Specs That Actually Matter
YouTube Shorts Aspect Ratio and Size
The headline answer is short: 9:16 vertical, 1080×1920, up to 3 minutes.
That is genuinely all most people need. But it is also the part everyone already gets right, and it is not why Shorts come out looking soft, or why text ends up hidden behind a Subscribe button. This guide covers the full spec, then the three things that actually change how your Short looks: safe zones, export bitrate, and what YouTube's transcoder does after you hit upload.
The Full Spec Sheet
| Property | Recommendation | Notes |
|---|---|---|
| Aspect ratio | 9:16 | Square (1:1) also qualifies as a Short |
| Resolution | 1080×1920 | Up to 2160×3840 (4K) supported |
| Length | Up to 3 minutes | Extended from 60s in October 2024 |
| Container | MP4 | MOV and WebM accepted |
| Video codec | H.264 | HEVC and AV1 accepted |
| Audio codec | AAC-LC | 128–384 kbps, 48 kHz stereo |
| Frame rate | 30 or 60 fps | Match your source; do not convert |
| Max file size | 256 GB | Shared with regular YouTube uploads |
A few of these deserve elaboration.
The 3-minute rule has a cutoff date
Videos uploaded on or after 15 October 2024 that are square or vertical and 3 minutes or shorter get categorized as Shorts. Videos uploaded before that date are still governed by the old 60-second limit and are not retroactively reclassified. If you are looking at an older upload wondering why a 90-second vertical video is not a Short, that is why.
Aspect ratio is a classifier, not just a display choice
This is the part people miss. On YouTube, aspect ratio is how the platform decides what a Short is. Upload something 16:9 and it is a regular video no matter how brief. Upload something 9:16 and under 3 minutes and it enters the Shorts feed. There is no manual toggle that overrides the geometry.
4K vertical: worth it or not?
Uploading at 2160×3840 does tend to earn a better transcode — YouTube allocates more generous bitrates to higher-resolution sources, and the 1080p rendition derived from a 4K master often looks slightly cleaner than a natively-uploaded 1080p one.
Whether that is worth roughly four times the file size and upload time is a judgment call. For most creators shooting on a phone and viewed on a phone, 1080×1920 is the right default. If you are shooting on a proper camera and the footage is detailed, 4K is a defensible upgrade.
Safe Zones: Where Your Content Gets Covered
The Shorts player draws its interface on top of your video, not beside it. Nothing is letterboxed away, but a meaningful portion of the frame sits underneath UI elements.
On a 1080×1920 canvas, plan for roughly:
- Top ~140 px — occasionally overlapped by system UI and the Shorts header
- Bottom ~420 px — video title, channel name, description, and the progress bar
- Right ~150 px — like, dislike, comment, share, remix, and the spinning sound disc
That leaves a comfortable working area of roughly the central 780×1360 region. Treat these as approximate: YouTube adjusts the layout across devices and app versions, and a long title wraps to two lines and eats further into the bottom.
Practical consequences:
- Burned-in captions belong in the middle third, not the lower third. The lower-third habit carried over from broadcast is actively wrong here.
- Logos go top-left, never bottom-right.
- Never put a call to action in the bottom 25%. "Follow for more" tucked at the bottom of the frame is a line nobody will read.
If you are repurposing a horizontal video, the same discipline applies as when resizing video for Instagram — reframe deliberately rather than letting an automatic crop decide what survives.
Bitrate: The Setting That Decides Sharpness
Resolution tells YouTube how many pixels there are. Bitrate decides how much information describes them. A 1080×1920 export at 2 Mbps and one at 12 Mbps have identical dimensions and dramatically different quality.
Sensible export bitrates for Shorts:
| Resolution / frame rate | Target bitrate |
|---|---|
| 1080×1920 @ 30 fps | 8–12 Mbps |
| 1080×1920 @ 60 fps | 12–16 Mbps |
| 2160×3840 @ 30 fps | 35–45 Mbps |
| 2160×3840 @ 60 fps | 50–68 Mbps |
These are deliberately generous, and the reason matters.
YouTube re-encodes everything you upload. Your file is never served to viewers as-is; it is transcoded into VP9 or AV1 at YouTube's own bitrates, which are considerably lower than the numbers above. Every compression artifact present in your upload gets baked in and then compressed again by that second pass.
So the goal when exporting is not to produce a small file. It is to hand YouTube the cleanest possible source, because the platform will do the shrinking regardless. Uploading a heavily-compressed 3 Mbps Short to "save time" means YouTube compresses your artifacts rather than your footage — and generation loss on already-degraded video is very visible on a phone held at arm's length.
Our guide to video bitrate covers the quality/size relationship in more detail.
The one time to compress before uploading
If your export is genuinely unwieldy — a 3-minute 4K60 ProRes master running to several gigabytes over a slow connection — re-encoding to high-bitrate H.264 first is sensible. You lose very little at 50+ Mbps and the upload finishes in a fraction of the time.
That is compression in service of upload practicality, not quality. Compressing below the table above to make the file small is working against yourself.
Frame Rate: Match, Don't Convert
Shoot at 30 fps, export at 30 fps. Shoot at 60, export at 60.
Converting between them requires the encoder to either duplicate or discard frames, and neither is free. 60 → 30 throws away half your temporal information; 30 → 60 duplicates frames without adding any, producing a larger file that looks identical at best and judders at worst.
The exception is genuine slow motion: footage shot at 120 or 240 fps and conformed to 30 fps in your editor. That is a deliberate creative retime, not a format conversion, and it works correctly. See what frame rate is in video if you want the underlying detail.
Codec: H.264 Unless You Have a Reason
YouTube accepts H.264, HEVC, VP9 and AV1. It re-encodes all of them.
H.264 is the right default. It encodes fast, every editor exports it reliably, and since YouTube is going to transcode anyway, the efficiency advantage of HEVC or AV1 buys you nothing on the delivery side — it only makes your upload smaller.
That last point is not nothing. If bandwidth is your constraint, HEVC at the same visual quality is roughly 40% smaller than H.264, which meaningfully shortens uploads. Just be aware that some editing and export pipelines handle HEVC less predictably.
A Sane Export Preset
For a typical phone-shot Short:
- Resolution: 1080×1920
- Frame rate: match source (usually 30 fps)
- Codec: H.264, High Profile
- Bitrate: 10 Mbps, VBR 2-pass, or CRF 18–20
- Audio: AAC-LC, 192 kbps, 48 kHz stereo
- Container: MP4
Then check your safe zones before uploading — open the export on a phone and confirm nothing important sits in the bottom 25% or the right edge.
Where Compression Fits
For Shorts specifically, the honest advice is upload the highest-quality file you reasonably can. YouTube's transcoder is the compressor that matters, and pre-compressing works against you.
Compression becomes useful at the edges of that workflow:
- Shrinking a huge master for upload over a slow or metered connection, without dropping to a quality level that shows.
- Repurposing the same cut for platforms with real limits — TikTok, Instagram, WhatsApp — where hard file-size ceilings do apply.
- Archiving your masters once a Short is published, so a year of vertical content does not consume a drive.
Compresto handles all three natively on macOS. Hardware-accelerated H.264 and HEVC encoding, batch processing for a whole folder of exports, target-size mode when a platform imposes a hard ceiling, and everything stays on your machine.