Video Aspect Ratios Explained: A Platform-by-Platform Export Guide

You finish editing a video, upload it, and immediately notice something is wrong. The subject is awkwardly cropped, captions are hiding behind interface buttons, or the platform has turned crisp footage into a blocky mess. The frustrating part is that the edit may be excellent. Often, the real problem is simply that the file was designed or exported for the wrong destination. A 16:9 YouTube video, a 9:16 Reel, and a 1:1 feed post can contain the same story, but they are not interchangeable files.

That is why understanding social media video aspect ratios matters. Aspect ratio controls the shape of the frame, while resolution defines how many pixels fill that shape. Frame rate affects motion, bitrate influences compression, and the codec determines how those pixels are packaged. Then every platform adds its own player, recommendation surfaces, interface overlays, and compression system. If those layers sound confusing, do not worry. Once you understand how they fit together, choosing the best video export settings becomes a repeatable workflow rather than a guessing game.

This guide gives you that workflow. We will cover landscape, square, portrait, and vertical formats; practical master-file settings; safe zones; and platform-specific recommendations for YouTube, Instagram, TikTok, Facebook, LinkedIn, X, Pinterest, and Snapchat. You will also see examples of how creators and marketers can turn one source project into several native-looking exports without rebuilding the edit from scratch. Platform specifications change over time, so always verify account-level limits before a high-stakes campaign, but the principles here will remain useful even when an upload limit or interface detail moves.

An aspect ratio describes the proportional relationship between a video's width and height. In 16:9, the frame is 16 units wide for every 9 units high; 1920 × 1080 and 3840 × 2160 are therefore both 16:9. In 9:16, that relationship is rotated, which is why 1080 × 1920 fills an upright phone screen. A square uses 1:1, such as 1080 × 1080, while 4:5 commonly appears as 1080 × 1350. Aspect ratio describes shape, not quality: a 360 × 640 file and a 1080 × 1920 file are both 9:16, but they do not carry the same detail.

Resolution is the actual pixel count. More pixels can preserve fine text, product details, and texture, but only if the source footage and export pipeline support them. Upscaling a soft 540 × 960 clip to 1080 × 1920 does not magically restore missing information; it merely creates more pixels from the same limited image. Likewise, exporting a tiny source at 4K may produce a huge file without a visible improvement. For most social delivery, 1080 pixels across the relevant short edge is a dependable baseline, while 4K is useful for YouTube, premium footage, archival masters, and edits that may need reframing later.

Orientation describes how viewers encounter the frame. Landscape 16:9 remains the natural fit for televisions, desktop players, presentations, gaming, interviews, and traditional YouTube videos. Full-screen vertical 9:16 is native to Shorts, Reels, TikTok, Snapchat, and mobile story experiences. Square 1:1 and portrait 4:5 are efficient feed formats because they occupy more vertical screen space than landscape without requiring a full-screen viewer. The best choice is therefore not simply the shape your camera captured. It is the shape that best matches the viewing surface and the story.

Here is a useful mental shortcut: choose the viewing experience first, the aspect ratio second, and the pixel dimensions third. If you want immersive mobile viewing, start with 9:16 and usually deliver 1080 × 1920. If you want a conventional YouTube watch-page experience, start with 16:9 and choose 1920 × 1080 or 3840 × 2160. If you want maximum feed presence on Instagram or LinkedIn, consider 4:5 at 1080 × 1350. Thinking in that order prevents a common mistake—editing around a random timeline preset and hoping the destination will accommodate it.

Before we discuss individual platforms, it helps to separate a master from a delivery file. Your master is the clean, high-quality version you keep; the delivery file is the compressed version you upload. If storage allows, export a mezzanine master in Apple ProRes 422, ProRes 422 HQ, DNxHR HQ, or a comparable high-quality intraframe codec. Keep the native timeline resolution, native frame rate, full-quality audio, and a standard color space such as Rec.709 for ordinary SDR social content. That master gives you a strong source for future crops, revisions, translations, and re-exports.

For direct uploads, MP4 with H.264 video and AAC audio remains the safest broadly compatible combination. H.265 or HEVC can create smaller files at similar visual quality, but compatibility, processing behavior, alpha support, and editing performance vary. Unless a platform or workflow specifically favors HEVC, H.264 is the low-drama choice. Use progressive scanning rather than interlacing, square pixels, high-profile encoding where available, and a keyframe interval of roughly two seconds. For audio, stereo AAC at 48 kHz and 192–320 kbps is more than adequate for most social videos.

Bitrate needs enough room for the complexity of the image. A talking head against a simple background compresses easily; confetti, foliage, gameplay, camera noise, water, and fast motion do not. As practical starting points, use about 8–12 Mbps for 1080p at 24–30 fps, 12–20 Mbps for 1080p at 50–60 fps, 35–45 Mbps for 4K at 24–30 fps, and 53–68 Mbps for 4K at 50–60 fps. These are sensible delivery ranges, not rigid laws. Variable bitrate is generally more efficient than constant bitrate, and two-pass encoding can improve allocation when rendering time is less important than file size.

What most people do not realize is that social compression is unavoidable. Uploading an extremely low-bitrate file means the platform compresses an image that is already damaged, while uploading a wildly oversized file rarely prevents another transcode. The goal is a clean, robust input—not an infinite bitrate. Review the exported file locally before uploading, then inspect the processed version on both Wi-Fi and mobile data. If text edges break up or gradients band, try a higher-quality source, less aggressive sharpening, a little more bitrate, or reduced visual noise rather than simply exporting the same weak timeline again.

Frame rate should usually match the source and the creative intent. Filmic footage is often recorded at 23.976 or 24 fps, general online video at 25 or 30 fps, and sports, gameplay, demonstrations, or fluid motion at 50 or 60 fps. Converting 24 fps footage to 60 fps at export does not create genuine motion detail; it duplicates or invents frames and can introduce judder or interpolation artifacts. Likewise, forcing 60 fps source footage into 24 fps without planning can make motion uneven. When possible, record, edit, and export at the same frame rate.

Shutter speed influences how those frames feel. A common starting point is a shutter speed around twice the frame rate: roughly 1/50 for 24 or 25 fps, 1/60 for 30 fps, and 1/120 for 60 fps. This is not an export setting, but it determines whether motion looks natural before compression ever begins. Very fast shutters create sharp, staccato motion that can be harder for encoders to compress, while excessive motion blur makes details muddy. If you are creating screen recordings, animations, or AI-generated scenes, preview motion at the target frame rate instead of assuming a higher number is always better.

Color deserves similar attention. Standard dynamic range video should normally be exported as Rec.709 with correctly interpreted levels. HDR can look spectacular, especially on modern phones and televisions, but it complicates monitoring, metadata, cross-platform consistency, and SDR fallback. Ever seen a social upload become washed out, too dark, or strangely saturated? That is often a color-management or tagging mismatch rather than an exposure problem. Unless you understand the destination's HDR pipeline and can check the result on multiple displays, a carefully graded SDR deliverable is usually safer for broad campaigns.

Audio is easy to overlook because platforms normalize playback differently, yet poor audio will make a polished picture feel amateur. Avoid clipping, remove intrusive noise, keep dialogue intelligible on phone speakers, and leave a little true-peak headroom; a ceiling around -1 dBTP is a practical target for encoded delivery. Many teams aim for integrated loudness somewhere around -14 to -16 LUFS for online content, but intelligibility and consistent dynamics matter more than chasing one universal number. Test with headphones, a laptop, and a phone speaker. A mix that works only on studio monitors is not ready for a mobile feed.

For standard YouTube videos, 16:9 is the default canvas. Export 1920 × 1080 for Full HD or 3840 × 2160 for 4K, using the source frame rate and a progressive H.264 MP4 for straightforward delivery. YouTube accepts many other resolutions and aspect ratios, and its player can adapt without forcing every upload into a permanent 16:9 bake. Still, 16:9 is the most predictable choice for tutorials, commentary, podcasts, reviews, gaming, documentaries, and videos intended for televisions as well as phones. Avoid adding your own black bars; let the player handle unused display space.

YouTube recompresses uploads and may take time to generate higher-resolution versions. If a new 4K upload initially looks soft, the HD and 4K transcodes may simply not be ready. Uploading a strong 1440p or 4K source can sometimes yield more favorable processing than a marginal 1080p file, but it cannot rescue poor focus, noise, tiny text, or an underexposed original. A good baseline is H.264 High Profile, AAC at 48 kHz, roughly 8–12 Mbps for 1080p30, 12–20 Mbps for 1080p60, 35–45 Mbps for 4K30, and 53–68 Mbps for 4K60.

YouTube Shorts call for a different composition. A 9:16 frame at 1080 × 1920 is the practical standard, although YouTube can classify supported square or vertical uploads as Shorts depending on current duration and publishing rules. Build for full-screen vertical viewing, keep important faces and text away from the lower and right-side interface regions, and check how the Short appears in both the Shorts player and channel surfaces. Duration eligibility, music rights, and categorization rules can change, so confirm current requirements in YouTube's help documentation rather than designing a permanent workflow around an old time limit.

I've seen repurposing work particularly well when creators treat the long video and the Short as related edits, not as one file with two crops. Imagine a 20-minute interview recorded in 4K landscape. The main upload might be 3840 × 2160 at 24 fps, while three 1080 × 1920 Shorts use punch-ins, reframed two-person layouts, larger captions, and a faster opening. The spoken content is shared, but the visual grammar is native to each surface. That distinction often matters more than a minor bitrate adjustment because retention begins with composition.

Instagram is where a single video can encounter several different frames. For Reels and Stories, use 9:16 at 1080 × 1920. For portrait feed video, 4:5 at 1080 × 1350 is a strong choice because it occupies substantial screen space while fitting naturally in the feed. Square 1:1 at 1080 × 1080 remains useful for modular brand content, and 16:9 can work for landscape material, though it appears smaller on a phone. Instagram's publishing options and profile previews evolve, so think of the upload frame, feed display, and grid thumbnail as separate compositions.

For a dependable Instagram export, choose an H.264 MP4, AAC audio, progressive scan, and the native timeline frame rate—usually 24, 25, 30, 50, or 60 fps. A video bitrate around 8–15 Mbps is a reasonable range for 1080p social delivery, with more headroom for 60 fps or visually complex footage. Extremely large files do not bypass Instagram's processing. Cleaner source footage, controlled noise, readable typography, and sensible contrast usually survive recompression better than brute-force bitrate.

Here is the thing: dimensions alone do not make a Reel safe. Captions placed at the extreme bottom can collide with the caption area and account information, while graphics near the right edge may sit beneath engagement controls. Keep the central subject and essential text comfortably inside the frame, leaving generous breathing room near all edges. Also preview the cover image in the full vertical player, feed, and profile grid. If a person's face or headline depends on the top and bottom of the 9:16 canvas, the narrower profile preview may cut it off.

Consider a marketer turning a landscape product demonstration into an Instagram campaign. The Reel should not merely crop the center, because the product may move from one side of the table to the other. A better approach is to keyframe the crop, reposition overlays, and occasionally use a split-screen or designed background when two important elements cannot fit vertically. Then create a 4:5 feed variant with a slightly calmer pace and repositioned call to action. The message stays consistent, but each export uses the available screen space instead of fighting it.

TikTok is built around 9:16 vertical video, and 1080 × 1920 is the safest working target. Square and landscape files may upload, but they sacrifice screen space or depend on alternative viewing behavior, which can weaken the immediate full-screen impact. Use H.264 in an MP4 container, AAC audio, progressive scan, and a frame rate that matches the source. For 1080p delivery, roughly 8–15 Mbps is a practical starting point, increasing for high-motion 60 fps footage when file limits allow.

Composition on TikTok is inseparable from interface awareness. The right side contains engagement controls, while the lower area can contain the account name, caption, sound information, prompts, and other overlays. There is no permanent pixel-perfect safe-zone template because interface placement varies by device, app version, ad format, caption length, and publishing context. A good habit is to reserve the outer edges for nonessential texture, keep the primary face or product near the central region, and place subtitles high enough to avoid the densest lower overlay area. Always test a private or limited-visibility post when a campaign depends on precise placement.

Snapchat Spotlight and story-style creative follow the same basic 9:16, 1080 × 1920 logic, but Snapchat's interface and advertising templates require their own checks. Full-screen vertical framing, fast visual clarity, and large mobile-readable text are more important than squeezing desktop-style detail into the image. Keep logos, disclaimers, and calls to action away from the top and bottom edges, and consult the current Snapchat Ads Manager specifications for paid placements. Organic and paid assets may have different duration, file-size, audio, or interactive-element constraints.

What does this mean for you in practice? If you produce one vertical master for both TikTok and Snapchat, keep it clean—without baked-in platform watermarks—and maintain editable caption and graphic layers. Export separate delivery files after moving calls to action and text for each interface. A cooking creator, for example, might keep the bowl centered, move ingredient labels to the upper-left safe area, and shift the final recipe prompt depending on where platform controls appear. The edit can be 90 percent shared while the last 10 percent makes each version feel intentional.

Facebook supports a broad mix of placements, so there is no single universal canvas. For feed video, 4:5 at 1080 × 1350 or square 1:1 at 1080 × 1080 generally makes efficient use of mobile space. Landscape 16:9 at 1920 × 1080 remains appropriate for long-form, cross-posted YouTube-style material, presentations, and viewing contexts where horizontal framing is part of the content. Reels and Stories should normally be 9:16 at 1080 × 1920. Use an H.264 MP4 with AAC audio, source-matched frame rate, and a healthy 1080p bitrate around 8–15 Mbps.

Paid Facebook and broader Meta campaigns deserve extra care because placement automation may distribute one creative across feeds, Stories, Reels, and other surfaces. One file can technically reach multiple placements, but technically accepted is not the same as visually optimized. Build at least a 4:5 feed version and a 9:16 full-screen version, then adapt headlines, subtitles, logos, and calls to action. Check Meta Ads Manager's current placement previews and file requirements before launch, especially for regulated disclaimers, interactive elements, and maximum durations.

LinkedIn is more restrained visually, but the same mobile-feed logic applies. Square 1080 × 1080 and portrait 1080 × 1350 are strong choices for thought leadership, case studies, hiring messages, product explanations, and event clips. Landscape 1920 × 1080 works well for webinars, executive interviews, screen recordings, and content that may be watched on desktop. LinkedIn accepts a range of specifications that can vary by organic post and ad product, so use H.264 MP4, AAC audio, progressive video, and verify current campaign-level restrictions when purchasing media.

I've noticed that business audiences reward clarity more than cinematic density. A software company once has one complicated demo but three viewing contexts: a 16:9 webinar recording, a 4:5 LinkedIn cut, and a 9:16 Meta Reel. The strongest workflow is to preserve the full demonstration in landscape, then create a portrait version that enlarges the cursor area, replaces tiny interface labels with callouts, and burns in concise captions. Simply cropping the screen recording would make the product unreadable. Re-authoring the information hierarchy turns the same footage into a credible native asset.

Video on X can appear in a fast-moving feed, an expanded player, replies, embeds, and paid placements. Landscape 16:9 at 1920 × 1080 is a safe option for news clips, commentary, sports, trailers, and screen-based content. Square 1080 × 1080 and portrait 1080 × 1350 can command more feed space, while vertical video may be appropriate for mobile-first content and current full-screen surfaces. Because upload duration, resolution, and file-size privileges can differ by account type and product, verify X's latest specifications before delivering long or high-resolution files.

For compatibility, use an H.264 MP4 with AAC audio, progressive scanning, and the source frame rate. A moderate 1080p bitrate—often around 8–12 Mbps for 24–30 fps—provides a clean input without creating an unnecessarily cumbersome upload. Pay attention to small text, gradients, and dark footage because feed compression can expose weaknesses quickly. If a clip contains a critical statistic or quote, make it large enough to remain readable in an inline preview rather than assuming everyone will expand the video.

Pinterest is more explicitly visual-search and discovery oriented. Vertical creative generally fits the product well, with 2:3 at 1000 × 1500 serving as a classic Pin proportion and 9:16 at 1080 × 1920 fitting full-screen video experiences. A 4:5 export can also be useful when adapting assets from Instagram or a commerce catalog. Keep the product, transformation, or promised result visible early; Pinterest users often encounter the video while researching an idea rather than following a creator's chronological feed.

The difference in intent changes editing decisions. On X, a topical clip may need the key claim in the opening sentence and a frame that still works beside surrounding conversation. On Pinterest, a home-renovation video might lead with the finished room, then show the steps and keep searchable visual labels on screen. Both can use H.264 and similar bitrate settings, yet they should not necessarily share the same hook, crop, cover, or duration. Export specifications protect quality, while platform intent determines whether the video earns attention.

Safe zones are the areas where essential information is least likely to be obscured or cropped. Traditional broadcast title-safe percentages are a useful starting concept, but social interfaces are less predictable. Usernames, captions, progress bars, reaction controls, shop buttons, and calls to action occupy different areas across devices and placements. Instead of relying on one universal overlay, create platform-specific guides in your editor. Keep faces, products, subtitles, and logos inside a conservative central area, then preview actual placement simulations before export.

Captions need more than grammatical accuracy. Use strong contrast, a readable size, sensible line breaks, and enough screen time to follow the speech. Avoid placing one long line across the entire width of a vertical frame; two compact lines are usually easier to scan. Burned-in captions guarantee the intended style, while uploaded caption files improve accessibility, searchability, translation, and user control. When the platform supports it, using both can be valuable, but check that duplicate captions do not appear. Also keep a caption-free master so you can correct errors or create localized versions later.

A reliable multi-platform workflow starts with capture. If you know the footage must become both 16:9 and 9:16, record at the highest practical resolution and frame subjects with enough room for alternate crops. A centered medium shot in 4K gives you more reframing freedom than a tight 1080p profile at the edge of the frame. For interviews, consider an isolated camera for each speaker rather than relying on a single wide two-shot. For screen content, record the screen at high resolution and plan enlarged callouts because a desktop interface becomes tiny inside a vertical canvas.

Then build aspect-ratio-specific timelines from a clean master sequence: perhaps 3840 × 2160 for landscape, 1080 × 1920 for vertical, 1080 × 1350 for portrait feed, and 1080 × 1080 for square. Duplicate the edit, use automatic reframing as a first pass, and manually correct every shot where the subject moves or graphics break. Tools such as Faceless can help generate scenes, captions, and multiple format variants, but human review still matters. Watch each export on the device and in the orientation where viewers will encounter it. The final quality-control question is simple: does this feel designed for the platform, or merely tolerated by it?

If a video looks blurry after upload, begin with the source rather than the platform. Check whether the original is in focus, whether digital zoom has exceeded the available resolution, and whether the timeline is scaling a low-resolution asset. Next, inspect the local export at 100 percent size. If that file is clean, wait for platform processing to finish and compare playback at the highest available quality. Persistent softness may call for a higher-resolution upload, a little more bitrate, larger text, less noise, or gentler grading—not aggressive sharpening, which can create halos and increase compression stress.

Unexpected cropping usually comes from confusing the upload frame with the display preview. Verify sequence dimensions, pixel aspect ratio, scale mode, rotation metadata, and any nested sequences. Then check whether the platform is showing a grid thumbnail, feed preview, ad placement, or full-screen player. These surfaces may crop the same upload differently. Build custom covers when available, and never place a logo or headline at the absolute edge. If black bars appear, remove bars baked into the source and export the intended aspect ratio directly.

Audio sync drift and stutter often trace back to variable-frame-rate phone footage or screen recordings. Transcode problematic clips to a constant frame rate before editing, then keep the timeline and export frame rates aligned. If colors shift, confirm Rec.709 tagging, data levels, HDR interpretation, and display color management. If the upload fails entirely, simplify the delivery: H.264 MP4, AAC audio, progressive scan, standard frame dimensions, a supported duration, and a smaller file. Also remove unusual edit lists or metadata by transcoding to a fresh file.

Before publishing, run a repeatable preflight rather than trusting memory. Confirm the destination, aspect ratio, pixel dimensions, frame rate, duration, codec, audio, file size, captions, spelling, safe zones, thumbnail, and rights-cleared music. Watch the first and last seconds for accidental black frames, check the complete file for glitches, and test on a phone. For paid or time-sensitive work, upload an unlisted, private, or draft version first. Five minutes of preflight can save a campaign from days of weak performance and awkward re-uploads.

The most important lesson in this video dimensions guide is that there is no single perfect social file. Landscape 16:9, vertical 9:16, portrait 4:5, square 1:1, and discovery-friendly 2:3 each solve a different viewing problem. In practical terms, that usually means 1920 × 1080 or 3840 × 2160 for standard YouTube and landscape playback; 1080 × 1920 for Shorts, Reels, TikTok, Snapchat, and Stories; 1080 × 1350 for mobile feeds; 1080 × 1080 for square placements; and 1000 × 1500 for a classic Pinterest Pin. Use source-matched frame rates, H.264 MP4 and AAC for broad delivery compatibility, and enough bitrate to provide a clean input for platform compression.

Just as importantly, treat composition, captions, covers, and safe zones as part of exporting rather than decorative details added at the end. Preserve a high-quality master, create separate delivery timelines, preview every placement, and verify current platform rules before major launches. Whether you edit manually or use Faceless to accelerate production and resize content, the winning habit is the same: make each version feel native. Once that becomes routine, export settings stop being a last-minute technical chore and become a reliable part of how your videos earn attention.