
Most teams obsess over hooks, lighting, and editing pace, then treat frame shape as an afterthought. That order is backwards. Aspect ratio is the first thing a viewer perceives, before a single word of narration lands. A 16:9 clip dropped into a vertical feed gets letterboxed into a thin strip that occupies roughly a third of the screen; the same clip reframed at 9:16 fills the display and competes on equal footing with everything else in that feed. Nothing about the storytelling changed — only the geometry.
Frame shape also signals intent. Vertical framing reads as native to a phone. Square reads as considered and editorial. Widescreen reads as cinema, broadcast, or a desk-bound viewing session. Recommendation systems have learned to read those signals because their business depends on keeping people inside the app, and a video that fills the canvas keeps attention longer than one that looks pasted in.
This guide covers the ratios that matter, how to plan a shoot so one session can produce every format, how automated recommendation layers actually choose a crop, and where those systems still need a human eye. It is written for creators, social teams, and editors who ship a lot of video and cannot afford to re-cut each piece five times.
An aspect ratio describes the proportional relationship between width and height. It is not a resolution. 9:16 at 1080x1920 and 9:16 at 720x1280 are the same shape at different pixel densities. Confusing the two is one of the most common sources of export problems, because a platform may accept the ratio but recompress the pixels and soften fine text.
A clean workflow separates three decisions: shape, resolution, and bitrate. Choose the shape from the destination, the resolution from the smallest reliable delivery tier for that destination, and the bitrate from how much motion and detail the footage contains. Talking-head footage at 1080p can look better than confetti-heavy motion graphics at 4K if the bitrate is starved.
Keep a naming convention that encodes all three, for example campaign_9x16_1080p_v3.mp4. When a client asks for "the vertical one," you will know exactly which file to send, and you will stop shipping a 720p cut to a placement that expects 1080p.
A common shortcut is to export one wide master and let each platform crop it. The result is predictable: faces clipped at the chin, captions hidden behind interface elements, and product shots half out of frame. Platforms crop from the center by default, and center is rarely where your subject is. Treat the wide master as a source, not a deliverable, and derive every other shape from it deliberately.
Ratios drift over time, but the underlying logic is stable: full-screen vertical for phone-first feeds, tall portrait for feed placements, widescreen for seated viewing. Use the reference below as a starting point, then verify in the platform's own ad or creator documentation before a major campaign.
| Placement | Preferred shape | Notes |
|---|---|---|
| TikTok, Reels, Shorts | 9:16 | Keep text clear of the bottom interface band and top caption area |
| Instagram feed | 4:5 or 1:1 | 4:5 occupies more screen; 1:1 crops more gracefully |
| Stories and status rows | 9:16 | Leave the outer margins empty for UI overlays |
| YouTube long-form | 16:9 | Thumbnails are 16:9 with the lower-right corner reserved for a duration badge |
| 1:1 or 4:5 | Muted autoplay favors bold captions and early visual payoff | |
| Facebook feed | 4:5 or 1:1 | Vertical video performs well when it is not buried in UI |
| X / microblog feeds | 16:9 or 1:1 | Vertical works but is often partially hidden behind controls |
| 2:3 or 9:16 | Tall pins win; 16:9 wastes most of the canvas | |
| Twitch and live streams | 16:9 | Vertical live is a separate production, not a crop |
| Presentations and screens | 16:9 or 16:10 | Assume unknown projectors and add generous margins |
On TikTok, Reels, and Shorts, the canvas is the whole screen. That means the bottom band belongs to the platform, not to you. Captions, calls to action, and lower-third graphics that sit inside the final 15 to 20 percent of the frame will be covered. Design the composition so the subject's eyes sit in the upper third and the key visual information sits in the central band.
Feeds are layout-driven. A 4:5 post takes a larger share of the scroll than a square one, which is why portrait rectangles perform strongly in feed contexts. But feeds also crop aggressively on smaller devices, so avoid putting essential detail within roughly five percent of any edge.
Widescreen remains the default for intentional viewing. If you produce a 16:9 piece and also want a vertical cut, plan it at the script level: wide establishing shots rarely survive a vertical crop, while medium shots and clean single takes translate well. Shoot coverage with both in mind rather than hoping the editor can salvage it.
Two forces push creators toward native ratios. The first is mechanical. Platforms size their players to the viewport, so a mismatched video is either letterboxed, pillarboxed, or cropped by the app. All three outcomes reduce the usable pixels devoted to your content. The second is behavioral. Full-screen video removes competing interface elements and other posts from view, which keeps viewers watching longer, and watch time is the currency most ranking systems care about.
There is a third, quieter factor: text legibility. Vertical video is usually watched at arm's length on a small screen. Type that looked tasteful in a 1080p widescreen edit can become unreadable when scaled to fit a phone. The practical rule is to size captions and lower thirds for the smallest expected viewing context first, then scale up for larger canvases.
None of this means a widescreen video cannot succeed in a vertical feed. It means you are paying a tax in screen real estate and viewer patience. When you can avoid the tax with a deliberate crop, take the deal.
Here is a workflow that produces a full ratio set from one shoot without turning the edit into a puzzle.
Decide which placement matters most and treat that as the hero. If the campaign lives on short-form feeds, the hero is 9:16 and everything else is derived from it. If it lives on a landing page or a long-form channel, the hero is 16:9. Naming a hero prevents the classic stalemate where every version gets equal, mediocre attention.
Compose with more headroom and side room than the hero frame requires. On a 16:9 shoot, keep the subject inside a central 9:16 column so a vertical crop exists without digital surgery. On a vertical shoot, keep a wider safe area so a square or landscape version remains possible. This single habit eliminates most reframing pain.
Create an overlay graphic for each platform showing the zones the interface will cover. Drop it on the timeline, position captions and logos inside the clear area, then disable the overlay before export. Standardizing this template across a team is worth more than any single editing trick, because it turns framing into a checklist instead of a judgment call.
Export the full set in one pass: 9:16, 4:5, 1:1, and 16:9 where relevant. Encode at a consistent quality target rather than picking random bitrates, and keep a manifest file listing which version goes where. Batch export is where automation earns its keep, because repeating the same four renders by hand introduces small inconsistencies that show up as visual jitter across a campaign.
Watch each export on the device it will be consumed on. A desktop review will not reveal that a caption block disappears behind a phone's interface. Check the first two seconds, the midpoint, and the final frame, since end cards and calls to action are the most commonly clipped elements.
Automated ratio recommendation sounds like magic and is mostly layered heuristics. Understanding the layers helps you trust the output where it deserves trust and override it where it does not.
At the bottom is a simple lookup: destination, placement, and format map to a recommended shape and resolution. This layer handles the easy 80 percent and never hallucinates. If your tool knows the asset is headed to a vertical feed, telling it to export 9:16 is a lookup, not intelligence.
Next comes inspection. The system reads metadata, duration, and possibly frame content to classify the asset — talking head, screen recording, product demo, animation. Screen recordings and slide decks rarely survive an aggressive crop; they need letterboxing or a re-layout. A detection layer that flags these cases saves an editor from discovering the problem after publication.
This is where computer vision does real work. Face detection, motion saliency, and object tracking produce a focal path across the timeline. The crop window then follows that path instead of staying locked to center. Good implementations offer smoothing so the window glides rather than snapping between subjects, plus the ability to pin a subject and let the rest of the frame move.
Automated crops fail in predictable places: scenes with two speakers on opposite sides of the frame, graphics with edge-anchored text, and rapid cuts where the focal point changes every second. Review flagged moments rather than every frame. A five-minute pass over the ten percent of shots that matter is a better use of time than manual cropping everything.
Not every editor needs the same feature set. Score candidates against your actual constraints.
A useful test: hand the tool a messy real project — mixed frame rates, embedded graphics, a talking head with captions — and see how much cleanup it demands before export. Demos use clean footage; your work does not.
Cropping instead of reframing. Center-cropping a wide shot removes context and often the subject. Fix: build a crop path with keyframes, or shoot with the vertical column protected from the start.
Ignoring the interface band. Captions placed near the bottom edge vanish behind platform controls. Fix: use safe-zone templates and keep the bottom fifth clear on vertical formats.
Mixing resolutions in one sequence. Dropping a vertical clip into a widescreen timeline forces scaling and softening. Fix: work in a hero timeline and generate variants as separate sequences with matched settings.
Over-cropping to fill the frame. Sometimes letterboxing is the honest answer, especially for screen recordings. Fix: accept pillar boxing with a branded background rather than destroying legibility.
Rendering once per platform with different quality settings. Resulting inconsistencies read as sloppy across a campaign. Fix: standardize encode settings and batch the exports.
Trusting thumbnails. Thumbnails are their own composition problem, often with their own ratio and a badge in the corner. Fix: design thumbnails separately rather than grabbing a frame.
Is a 9:16 export always better than a 1:1 for social?
Not always. Full-screen vertical wins where the placement is phone-first and full-screen. Square and 4:5 remain strong in feed contexts where the post sits among other content and a square crop preserves more of the composition.
Can I just crop a widescreen video to vertical?
You can, but plan it. Protect a central vertical column during the shoot, or expect to lose the edges of the frame. Scenes with two subjects far apart will not survive a center crop.
What resolution should I export?
Match the placement rather than chasing maximum pixels. Deliver the smallest tier that looks clean on the target device and encode at a bitrate appropriate to the motion in the shot.
How much margin should I leave for interface overlays?
A practical starting point is roughly the outer five percent on all sides, with a larger reserve of the bottom fifth for vertical formats. Verify against current platform guides before a major launch.
Do automated crop tools replace editors?
They remove the mechanical work. Judgment about which moment matters, how long a beat should breathe, and where a caption lands is still editorial, and it still decides whether the video works.
How do I keep a campaign consistent across six formats?
Set a hero frame, build one safe-zone template per placement, lock encode settings, and review all variants on the devices they will be watched on. Consistency comes from process, not from a single clever export.

Alexander
Vidu Q4 alternatives compared: Kling 4.0, Seedance 2.5, Wan 3.0, and Runway Gen-4 — 4K support, input modes, durations, audio, and what each costs in credits on Domer.
The top 4K AI image generators on Domer compared: Flux 3 Klein, Nano Banana 2.1, GPT Image 2.5, GPT Image 2, and Nano Banana Pro — 4K credit costs, reference limits, and speed.
Nano Banana 2.1 vs GPT Image 2.5 Flare compared: credit costs per resolution, aspect ratios, reference images, text rendering, and which tasks fit each model.