# Vertical Video Dimensions: A Cross-Platform Export and Preview Guide

> Choose vertical video dimensions by destination, preserve a clean source master, and check each platform's interface without inventing a shared safe zone.

- Canonical: https://fluxgravity.io/guides/vertical-video-dimensions
- Published: 2026-10-11
- Content type: guide

A 9:16 master is a useful starting point for many full-height placements, but platform specs, upload paths, crops, and overlays are not identical.

![Original comparison showing a shared vertical source branching into destination-specific crops and previews](https://fluxgravity.io/images/editorial/vertical-video-dimensions-platform-map.svg)

*Original workflow diagram only. It uses no measured platform UI or universal safe-zone margin; review each destination separately.*

## What dimensions count as vertical video?

**Answer:** Vertical describes orientation, while a ratio such as 9:16 gives the frame shape and pixel dimensions give its resolution.

A 1080 by 1920 frame has a 9:16 ratio. A 720 by 1280 frame has the same ratio at smaller pixel dimensions. A 1080 by 1350 frame is 4:5, also vertical, but not the same canvas. The phrase 'vertical video size' therefore needs a destination and an intended display before it can be answered precisely.

Ratio is calculated as width divided by height. Reducing both dimensions by the same factor keeps the ratio: 1080/1920 equals 9/16. Increasing pixel dimensions does not restore detail that was lost in a low-resolution source, and changing the ratio by stretching distorts the image. Preserve a source master and make intentional crops for delivery.

A full-height phone canvas is a common creative target, but that phrase does not specify codecs, upload limits, account eligibility, or how the interface will display text and controls. Those are separate checks. No one dimension guarantees successful playback or publishing across every platform.
- 9:16 example: 1080 x 1920
- 4:5 example: 1080 x 1350
- State ratio, pixels, and destination separately

## Why a single export may not fit every destination

**Answer:** Platforms can accept or recommend different ratios for different placements, and each interface can cover different portions of the frame.

TikTok for Business lists 9:16 as recommended for some in-feed ad creatives, while its other placements and file pathways have their own guidance. Meta's Instagram Reels Publishing API sample recommends 9:16 for that API publishing route. LinkedIn's organic video-sharing help lists a broad aspect-ratio range, while LinkedIn's video-ad page specifies particular ad ratios. These sources describe distinct contexts, not one cross-platform contract.

YouTube classifies eligible Shorts by a square or vertical shape and a duration condition in its current help, rather than requiring one fixed pixel pair in the source checked here. Pinterest's help recommends 2:3 for certain image or video Pin contexts and 9:16 for full-bleed video. The platform and placement determine what the ratio means in practice.

An export may technically upload yet still crop the subject, shrink text, or obscure a disclosure. Plan a master and destination versions. Capture important detail in the central composition where reasonable, then use each destination preview to check actual UI coverage instead of borrowing a safe-zone template from a different network.
- Specs are placement-specific
- Upload acceptance differs from visual suitability
- Preview every destination and account path

## Choose a master canvas and preserve the original

**Answer:** Start with the source footage and the destinations that matter, then make reversible versions rather than destructively resizing the only copy.

If the project needs several full-screen placements, recording or editing a 9:16 version can be a practical starting point. Frame the subject with enough room for later adjustments, but do not assume every future crop can be obtained from the same shot. If the key action happens near an edge, capture an alternate take or a wider source when feasible.

Keep the untouched camera original and an editable timeline. Export each destination as a separate version with explicit dimensions and a name that identifies platform, placement, ratio, and revision. Example: `launch-reel-vertical-9x16-v02.mp4`. Record the source file and export date so that a reviewer can reproduce the version that was approved.

A master is a production convenience. It is not a promise that each network will accept it. If a platform's documented maximum or minimum differs from the source, render an intended version and check the exact route. Never quietly rescale or crop a file after approval without reviewing the changed framing.
- Preserve source footage and project
- Create destination-specific exports
- Name version and dimensions
- Re-review any crop change

## Compare documented platform contexts carefully

**Answer:** Use a small reference table to remember which source supports which statement, not to claim identical rules across organic and paid placements.

TikTok ad help gives specific pixel minima and recommended ratios for named ad types; the Content Posting API has separate file constraints. Instagram's Reels API sample recommends 9:16, but that is not every consumer upload surface. LinkedIn Help for organic uploaded videos and LinkedIn's ad specifications are different pages with different requirements. YouTube Help describes square or vertical classification for Shorts eligibility. Pinterest distinguishes 2:3 recommendations and full-screen 9:16 video contexts.

A table is only as reliable as its scope labels. Before a release, follow the primary source and check its update date. If account type, device, campaign type, or placement is unclear, the number should not be treated as universal. This guide records representative official sources available on October 6, 2026, but final factual review must revisit them.

The comparison does not imply that all destinations use a common safe zone. A user interface may change by device, caption, feature, or ad placement. No pixel insets are shown in the original graphic because a cross-network fixed safe-zone number would be unsupported.
- TikTok: ad, Studio, API, and organic sources differ
- Instagram: API recommendation is not universal app policy
- LinkedIn: organic and ad docs differ
- Pinterest and YouTube define separate vertical contexts

## Review overlays without drawing fake boundaries

**Answer:** Keep important content legible and test the real preview; use official safe-zone templates only for the specific placement they document.

Every destination may place account labels, captions, buttons, progress indicators, or actions over a video. The amount of overlay can vary. TikTok's advertising guidance expressly links its safe-zone sizing to the format, caption length, and interactive add-ons. Pinterest provides safe-zone guidance for Pin contexts, but that does not create a universal template for TikTok, Reels, Shorts, or LinkedIn.

For a general first pass, avoid putting essential text at the extreme edges and keep the subject visible throughout movement. Treat this as a production heuristic, not a platform measurement. Then inspect the actual preview and the video on a phone. Check a long caption, stickers, ads controls, or other elements that apply to the chosen placement.

If you cannot obtain a preview, state that the safe-area check is unverified. Do not publish a colored inner rectangle labeled 'official safe zone' unless it comes from a current official source and matches the exact format, dimensions, and options. The SVG on this page is intentionally abstract and has no interface screenshot.
- Keep essential copy away from edges as a heuristic
- Use format-matched official templates where supplied
- Check actual UI preview
- Never turn the heuristic into a measured margin

## Worked example: fictional museum exhibit clip

**Answer:** A fictional museum plans a vertical source but prepares different reviews for three destinations.

An invented museum records a 1080 by 1920 clip showing a conservator demonstrating how a display case is cleaned. The clip is fictional and no real museum or conservation procedure is represented. Before publication, a qualified staff member would verify the process and approve the visible artifacts and filming permissions.

The team creates a TikTok organic candidate, a YouTube Short candidate, and a LinkedIn company Page video version. It checks the current creator upload guidance for TikTok, Shorts eligibility and upload display for YouTube, and LinkedIn's organic video specifications. If it later buys ads, it returns to each ad specification rather than reusing the organic checklist. It checks captions, names, and the crop in each platform preview.

This exercise does not claim that a common 9:16 source is accepted identically or that one crop suits all three. If the LinkedIn preview or another target cuts off context, the editor prepares a distinct crop or shot. No view count or performance result is implied.
- Shared source: 9:16 working example
- Three destination reviews, not one approval
- Fictional scenario with no platform upload

## Inspect the exported file and destination render

**Answer:** Check media metadata and visual behavior as separate layers before you approve a destination version.

Confirm width, height, frame rate, file type, codec, duration, and file size against the current rules for the exact workflow. The rules can be different for an app upload, developer API, and ad manager. Keep the source file and export metadata with the approval record. A correct dimension pair does not prove the encoding or account path is eligible.

Watch the full export on a phone. Check the opening and final frames, action continuity, audio, captions, readable text, and interface overlap. Look at the playback and any cover or thumbnail separately because the still image can be cropped differently. If the destination provides a processed preview, compare it with your local file and note any change.

If an upload fails, save the error and identify the exact path. Do not change dimensions at random. Check documented codecs, account permissions, publishing requirements, and policy warnings before making a new version. Record the version that passed review; never describe a local render as a live published post.
- Inspect metadata against the named path
- Review entire export on phone
- Check cover and video separately
- Save the exact upload error and version

## Copy-ready cross-platform production brief

**Answer:** Ask for a comparison that names destinations, links, dates, asset inputs, and unknowns rather than inventing matching rules.

Prompt: 'Create a versioning plan for this source video. Source width and height: [verified values]. Available source footage: [list]. Destinations and exact placements: [list]. For each destination, use only these official documentation links and access dates: [sources]. Return any documented ratio or pixel limits with their specific organic, API, or advertising scope; show ratio arithmetic; identify unknown or conflicting specs; and list a preview check for each output. Do not invent cross-platform safe-zone numbers, acceptance outcomes, or UI screenshots. Label any hypothetical example fictional. Recommend which destination needs a separate crop and why. A human will verify the current source and inspect the actual exports.'

An assistant cannot infer that the account has permission to publish, that every destination accepts the same file, or that a particular overlay is present. Supply the real asset metadata and verify the outputs with the destination's current interface.

No FluxGravity video transformation or publishing feature is claimed. The signup destination below is a generic account entry and does not promise video processing.
- Name exact placements
- Attach current official docs
- Request gaps and scope boundaries
- Human inspection of every render

## Representative official guidance and its limits

Reference snapshot checked October 6, 2026. Each row belongs to the linked format or platform pathway.

| Destination/source | What the source says | Scope limit |
| --- | --- | --- |
| TikTok auction in-feed ad help | Vertical 9:16 recommended for specified non-Spark ads | Not a blanket organic upload rule |
| Instagram Reels Publishing API sample | Recommends 9:16 | API reference, not all app behavior |
| LinkedIn organic video help | Lists a supported ratio range | Check current uploader and device |
| LinkedIn video ads | Lists placement-specific ad ratios | Ad requirements only |
| YouTube Shorts Help | Square or vertical video within duration conditions can qualify | Classification does not set one pixel pair |
| Pinterest Pin specifications | 2:3 recommendation for some Pin assets; 9:16 for full-bleed video | Image, video, organic, and ad contexts differ |

## Frequently asked questions

### What is the best size for vertical video?

There is no single universal size. Choose a ratio and dimensions for the destination and placement, and verify them in the current official documentation.

### Is 1080 by 1920 the same as 9:16?

Yes. Both dimensions reduce by a factor of 120 to 9 by 16. That arithmetic describes the shape, not a universal platform requirement.

### Can I use one 9:16 video on every social platform?

A shared source can be adapted, but create and inspect each destination version. Upload specs, crops, overlays, and previews vary by platform and placement.

### Is there a universal safe zone for vertical videos?

No universal pixel safe zone is established here. Use current, platform-issued guidance for the exact format and inspect the actual preview.

### Do vertical video dimensions guarantee acceptance?

No. File format, codec, duration, account permissions, rights, and publishing route are separate from pixel dimensions.

### Should I crop a landscape video to 9:16?

Only if the key subject and context remain clear. Reframe from source footage, create an alternate take when needed, and review the complete result on a phone.

## Sources
- [TikTok Ads Manager: TikTok Auction In-Feed Ads](https://ads.tiktok.com/resources/help/article/tiktok-auction-in-feed-ads?lang=en-GB)
- [Meta: Reels Publishing API sample](https://github.com/fbsamples/reels_publishing_apis/blob/main/insta_reels_publishing_api_sample/README.md)
- [LinkedIn Help: Video sharing troubleshooting](https://www.linkedin.com/help/linkedin/answer/a551346)
- [LinkedIn Help: Video ads advertising specifications](https://www.linkedin.com/help/linkedin/answer/a424737)
- [YouTube Help: Understand three-minute YouTube Shorts](https://support.google.com/youtube/answer/15424877?hl=en)
- [Pinterest Help: Review Pin specs](https://help.pinterest.com/en/article/review-pin-specs)
- [Google Search Central: Creating helpful, reliable, people-first content](https://developers.google.com/search/docs/fundamentals/creating-helpful-content)

## Related pages
- https://fluxgravity.io/guides/youtube-shorts-ideas
- https://fluxgravity.io/guides/how-to-schedule-tiktok-posts

## Try FluxGravity

Give FluxGravity one goal and receive finished work.

https://app.fluxgravity.io/