Best Video Formats and Aspect Ratios (2026 Guide)

Want the exact pixel sizes for every platform while you read? I keep a free cheat sheet updated: moonb.io/tools/social-media-sizes. No login, and it runs entirely in your browser.

I have exported the same sixty-second video a dozen different ways for a dozen different feeds, and I have also watched a good film die on arrival because someone sent the wrong file to the wrong place. Two decisions cause almost all of that damage, and people mix them up constantly. The file format is the codec and container you export in, and it decides whether your video plays at all and how heavy it is. The aspect ratio is the shape of the frame, and it decides how much of the screen you own once the clip lands in a feed. Get both right and the video looks sharp, loads fast, and fills the phone. Get them wrong and it buffers, letterboxes, or crops straight through your subject’s face.

If you only want the settings:

• Deliver in MP4 (H.264). It plays on every phone, browser and TV made in the last decade, with no setup. I only reach for AV1 or HEVC when there is a specific reason, which I get into below.
• Match the ratio to where it lives. 16:9 for YouTube and the web, 9:16 for Reels, TikTok, Shorts and Stories, 4:5 for the Instagram and Facebook feed, and 1:1 when a single clip has to work everywhere at once.
• Frame for the vertical crop from the first take. Cropping a wide shot down to vertical afterwards throws away more than half the picture, and it is usually the half with your subject in it.

The frame: which shape wins where

Aspect ratio is just the shape of the picture. These are the ones I actually deliver, drawn to scale, with where each one earns its place.

The rule that has held up for me is simple: 4:5 in the standard feed, 9:16 for anything full-screen. A 4:5 frame (1080x1350) is the tallest shape Meta will show before it starts cropping you in the feed, so it takes up about 25 percent more vertical space than a square, and that extra height is the mechanical reason it stops more thumbs. Meta recommends 4:5 as the default feed ratio itself. For Reels, TikTok, Shorts and Stories, 9:16 is the only shape that fills the screen edge to edge, and the algorithms there favour clips that do; a square video, which is not treated as native, gives up discovery for no reason.

On the old “does vertical really beat square” argument, there is one clean study I trust enough to quote. In Buffer’s paid-social test, vertical video beat square on the Instagram feed by 6 percent more three-second views and 187 percent more deep views (past half the runtime), and on the Facebook feed it cost 26 percent less per click. A parallel Animoto test pointed the same way. The caveat I always add out loud: that is 2018 paid-ad data comparing vertical to square, not fresh organic Reels numbers, and clean modern studies putting vertical against horizontal are scarce. So I treat “vertical beats square in the feed” as well-supported, and “vertical beats horizontal” as a screen-geometry argument rather than a proven lab result.

If you want the three-minute version of why the frame shape matters at all, this is the clearest short explainer I have sent to clients:

Keep your message inside the safe zones

Every platform stacks its own buttons, captions and progress bars on top of your video, and they land in the same places every time. Two old broadcast rules still save me here: action-safe is the centre 90 percent (keep faces, products, anything that matters inside it) and title-safe is the centre 80 percent (keep all text, subtitles and calls-to-action in there). In a vertical 9:16 frame the danger is the top and bottom rather than the sides, because that is where the platform interface sits. TikTok alone eats roughly the top 130 pixels, a bottom band of about 440 pixels for the caption and buttons, and around 120 pixels on the right for the like-and-share rail. Instagram moved its grid preview to 3:4 in 2025, so a Reel cover can get cropped top and bottom in the profile thumbnail; I keep the cover text and the face dead centre for that reason.

One habit that costs nothing and I never skip: burn in captions. Feed video has been watched mostly on mute for years now, and open captions lift completion everywhere sound is off by default.

The platform cheat sheet

Recommended specs as of 2026. When I am not sure, I upload MP4 (H.264) at 1080p or higher and let the platform transcode it.

The file: which codec to actually deliver in

The container (almost always MP4) is the box. The codec inside it does the compression, and for the same 1080p picture, a newer codec needs far less bitrate, which is why the file comes out smaller.

Smaller is only worth it if the thing still plays, though, and compatibility is where the codec choice actually bites:

• MP4 / H.264 is my safe default. It plays on everything, hardware-accelerated on basically every chip made in the last decade. It is the least efficient of the four, but for a website hero, a landing-page embed, an email, a sales deck, or anything you hand to a prospect whose device you cannot see, “it will just play” beats a smaller file every time. Pick this unless you have a reason not to.
• HEVC (H.265) is about twice as efficient as H.264 and excellent for 4K and HDR, but its web support is patchy and the patent licensing is expensive and fragmented. I use it for 4K and HDR uploads to platforms that transcode anyway, and inside Apple-only pipelines. I never self-host it as the only web file.
• VP9 is royalty-free, roughly as efficient as HEVC, and what YouTube has served for years. In practice it is the WebM fallback you pair next to an MP4 source, not usually a first choice you make on purpose in 2026.
• AV1 is the most efficient mainstream codec, royalty-free, and it now powers around 75 percent of YouTube and most of Meta’s playback. The problem is Apple: it ships no software AV1 decoder, so anything before the iPhone 15 Pro and every Intel Mac cannot play it at all. Upload AV1 when you have hardware encoding and the platform transcodes, but the second you self-host it, ship an H.264 MP4 alongside or older Apple and Intel viewers get nothing.

There is a second split that trips up a lot of teams: delivery formats versus master formats. Your editor should be working in a lightly compressed master (ProRes on Mac, DNxHR on Windows and Avid) that survives round after round of edits and colour grades without visible loss, then export a compressed delivery file, H.264 by default, only at the very end. Keep the master so you can re-cut future versions cleanly. I never hand a client a ProRes file as “the final video,” and I never try to re-edit a delivery MP4, because both are how you quietly end up redoing work you already paid for.

On bitrate, one rule saves a lot of mushy uploads: go well above the platform’s baseline. Every upload gets re-encoded, and each pass adds loss on high-motion or low-light footage. For 1080p H.264, YouTube’s baseline sits around 8 Mbps at 30fps, but I give it 16 to 24 for busy footage; for 4K I aim for 35 to 45. Our free video bitrate calculator does the maths for any resolution and frame rate.

Shoot once, cut for every crop

The mistake I watch create all of this rework is shooting for one ratio and trying to rescue the rest afterwards. Crop a 16:9 master down to 9:16 and you bin more than half the frame, and whatever sat near the edges, a face or a logo, is gone. The habit that fixes it:

1. Shoot at the highest resolution with a portrait-first eye. Keep the subject centred with head and side room to spare so it survives every crop.
2. Master in ProRes or DNxHR, grade once, then version out.
3. Export each ratio into its own safe zones, sliding graphics and text so nothing collides with the platform interface.
4. Deliver H.264 MP4 unless you have a specific reason, and the hardware, to use AV1 or HEVC.

Two of our free tools take the fiddly parts off your plate: the aspect ratio calculator for planning the crops, and the social media sizes cheat sheet for every platform’s exact dimensions.

Getting it right at scale

None of this is hard to do once. Doing it for every video, on every platform, every week, is where teams slip: the wrong crop ships, or the captions slide out of the safe zone, or a file lands too heavy to open on a phone. That is the part my team owns for clients, mastering once and cutting every format and ratio a channel actually needs, so the technical layer never gets in the way of the idea. If that is the part eating your week, see how Moonb works.