There’s a special kind of disappointment in exporting a video you’re proud of, uploading it everywhere, and watching each platform chew it up differently. The YouTube version looks fine. The TikTok version is soft and washed out. On Reels, the like and comment buttons sit directly on top of your captions. The Shorts version cuts your subject’s face in half. In half!
None of this is random. Every platform is its own delivery environment — its own resolution, aspect ratio, bitrate, codec, and interface layer. Hand them one generic file and each resolves the mismatch its own way: recompressing your video again, scaling it to the wrong frame, or letting its buttons cover your text. They don’t care about your feelings. They just process.
The professional answer is a discipline: master once, export many. Finish one high-quality master, then render a purpose-built copy per destination, each matched to that platform’s specs, safe zones, and captions. The extra renders take minutes; the difference in how your work looks is the difference between amateur and professional delivery. Minutes. That’s all it costs.
The Master File: Your Single Source of Truth
Everything downstream depends on the master. A master file is not the file you upload to TikTok — it is the highest-quality render your project can produce, archived and used as the source for every platform-specific export. Get it right and every export after it is a clean, controlled step down. Get it wrong — master at 720p, or as a heavily compressed MP4 — and every delivery copy inherits those limits permanently. Permanently.
Build the master at the highest resolution your timeline supports — 4K project, 4K master; 1080p sources, 1080p master (upscaling adds nothing). Keep your delivery frame rate, the graded color, and the full 48 kHz audio mix. Nothing about the master gets compromised for a platform. Nothing.
For the codec, use a high-bitrate mezzanine format: ProRes 422 (or 422 HQ) on Mac workflows, DNxHR HQ/HQX cross-platform. These are visually near-lossless, so platform exports compress from a clean source. If storage is tight — ProRes 4K runs several gigabytes per minute — a high-bitrate H.265 master (50–100+ Mbps for 4K) is a reasonable compromise: far smaller, still clean enough to export from. Never master as low-bitrate H.264 and compress again per platform. Never.
This is the most common delivery mistake: never re-compress a compressed delivery file for another platform. Each lossy pass throws away detail permanently — re-rendering your TikTok MP4 as a YouTube upload stacks two generations of damage. Always go back to the master. Always.
Two habits make this work: archive the master with a clear name and date — re-edits, spec changes, and repurposing all start from it — and if you work with AI-generated footage, generate source clips at the highest resolution your tool offers first (most top out at 1080p, with higher tiers on some — see our roundup of the best AI video generators in 2026). A 1080p master from clean 1080p sources beats a 4K timeline upscaled from the same material. Every time.
Vertical Video Specs: TikTok, Reels, and YouTube Shorts
TikTok, Instagram Reels, and YouTube Shorts are close enough in requirements that one well-built vertical export usually serves all three. The numbers below are practical working values, not official specs — platforms change limits and encoding behavior regularly, so check each platform’s current specs page before a major campaign.
- Resolution: 1080 × 1920 (9:16) — accepted everywhere, displayed natively on phones.
- Codec: H.264. Universal compatibility, fast encodes, accepted everywhere. H.265 uploads are handled inconsistently across platforms and apps, so H.264 is the safe vertical delivery choice in 2026.
- Bitrate: 10–20 Mbps for 1080p vertical. Pushing much higher mostly buys longer uploads, not better results — each platform recompresses your upload anyway, and that recompression is the real bottleneck.
- Frame rate: 30 fps is the social standard. Use 60 fps for high-motion content (dance, sports, fast action). Keep the timeline at the same rate — don’t mix 24 and 30 fps clips in one edit.
- Audio: AAC, 48 kHz, 128–320 kbps. Keep peaks controlled — phone speakers punish harsh highs.
- Format: MP4 container. Universally accepted.
Duration limits shift often — all three platforms have moved their maximums multiple times — so check the current specs page before building around a duration, and design with margin. And watch file sizes: at 10–20 Mbps, a 60-second vertical video lands around 75–150 MB, which uploads reliably even on mobile data.
A Note on Platform Recompression
After you hit upload, every major platform re-encodes your video into its own adaptive-bitrate ladder. Your upload isn’t what viewers see — it’s the source material for the platform’s encoder. A clean upload gives it the best starting point; a mangled file gives it damage to preserve. Feed it well. That’s the whole philosophy in three words: feed it well.
YouTube Long-Form Specs: The 16:9 Standard
YouTube long-form has no buttons covering your frame, but viewers watch on large screens where compression artifacts show. Every blocky gradient is visible. YouTube publishes recommended upload encoding settings — follow them as targets and verify against the current help page.
- Resolution: 1920 × 1080 baseline, 3840 × 2160 when the master supports it. A 4K upload often looks cleaner at 1080p playback than a native 1080p upload, because YouTube assigns higher-bitrate encodes to 4K uploads. Tradeoff: upload time and file size.
- Codec: H.264 in an MP4 container — the broadly compatible choice.
- Bitrate: YouTube’s published guidance has long centered on targets like 8 Mbps for 1080p SDR and 45 Mbps for 4K SDR (higher for high frame rates and HDR) — verify current numbers on YouTube’s help page. The takeaway: YouTube expects far more bitrate than a TikTok upload.
- Frame rate: 24 fps for a cinematic feel, 30 fps as the clean default for tutorials, talking-head, and screen content. 60 fps suits gaming and high-motion work. Keep it consistent across the project.
- Audio: AAC at 48 kHz, 128–384 kbps. Mix quality matters more than bitrate — a clean 128 kbps track beats a sloppy 320 kbps one.
Leave a few seconds of handle at the head and tail of your master before trimming platform versions — it lets you adjust the YouTube cut’s start and end points without reopening the timeline. Little insurance policy. Costs nothing.
Safe Zones: Where Platform UI Covers Your Video
Every short-form platform lays its interface over your video — profile names, captions, buttons, progress bars, titles — for the entire watch. Text under them is unreadable; faces half-covered by buttons look like mistakes. Safe zones aren’t polish; they’re basic legibility. Basic.
The rule: keep critical text, faces, and key action inside the center ~80% of the frame. For 1080 × 1920, that means practical margins like these (working guidelines — verify on a real phone, since interfaces shift):
- Top: ~150–250 px clear — profile info, search, titles. Shorts overlays title and channel text up here.
- Bottom: ~300–400 px clear of critical text. Captions, descriptions, progress bar, and navigation stack here — the most violated zone, exactly where the platform puts its own text.
- Right side: ~120–200 px clear — TikTok’s like, comment, share, and sound buttons run down this edge; Reels uses a similar band.
- Left side: ~60–100 px, guarding against edge cropping on unusual screen ratios.
Your truly safe canvas on 1080 × 1920 is roughly the central band between the danger zones, inset from the sides — about 860 × 1150 px. Design titles, lower-thirds, and captions for that region. All of them.
Three habits: cut with a safe-zone guide template visible in your editor; check the final export on a real phone in the real app (desktop previews don’t show actual button layouts); and when reframing to vertical, position the subject with these margins in mind — a centered face can still land under the caption area in a bottom-heavy composition.
Captions: Burned-In vs. Sidecar Files
Captions are a primary viewing mode on short-form. A large share of TikTok and Reels viewing happens muted — in public, autoplay with sound off, or viewers who prefer reading. If meaning lives only in the audio, muted viewers scroll past. Gone. One swipe.
Two methods: burned-in (open) captions rendered into the picture — every viewer sees them, everywhere; and sidecar captions (typically SRT) uploaded alongside, rendered as toggleable subtitles.
For TikTok, Reels, and Shorts, burned-in wins. Viewers don’t turn captions on — they watch what’s in front of them. Burned-in guarantees text on mute, survives re-uploads and shares, and lets you control styling. Costs: text can’t be disabled or auto-translated, and a typo means re-rendering. For short-form, the tradeoff favors burning in.
For YouTube long-form it flips: an SRT gives toggleable captions, automatic translation, and indexed caption text that helps search. Many creators do both — clean video plus SRT for YouTube, burned-in vertical for short-form.
Styling basics for the burned-in versions carrying your short-form performance:
- Position above the bottom UI — lower third of the safe zone, above that 300–400 px danger area, centered horizontally.
- Readable at arm’s length — bold sans-serif, large on a normally held phone. If you squint at 100% in your editor, viewers won’t read it.
- Contrast always — white or yellow text with a dark stroke, shadow, or semi-transparent box. Thin decorative fonts over bright footage are decoration, not captions.
- One to two lines, short phrases — break at natural phrase boundaries; chunk so no caption lingers or flashes by.
- Check timing on mute — watch the export once with sound fully off. If you can follow it, the captions work.
Codecs, Plainly Explained
The practical codec question is simple: which format gives each platform clean source material without wasting time or disk space? In 2026, the delivery answer is refreshingly boring. Good boring. The kind of boring that works.
H.264 is the universal delivery codec. Every platform accepts it, every editor exports it fast with mature hardware acceleration, every device plays it. Its compression is older and less efficient — larger files for the same quality — but compatibility beats efficiency for delivery. When in doubt, deliver H.264.
H.265 (HEVC) compresses roughly twice as efficiently — similar quality at about half the bitrate — but encodes slower and is handled inconsistently as an upload format across social platforms and apps. It shines as a mezzanine/archive codec when storage is tight; as a social delivery codec in 2026, it’s the riskier choice.
AV1 is the emerging efficiency leader — better than H.265, royalty-free, increasingly used in platforms’ internal streaming ladders. As a creator upload format, though, encodes are heavy, editor support is maturing, and upload handling varies. Watch AV1; don’t standardize on it yet.
The practical 2026 map: master in ProRes 422 or DNxHR (high-bitrate H.265 if disk space forces it), deliver H.264 to TikTok, Reels, Shorts, and YouTube, and keep an eye on AV1 without rebuilding around it. Revisit yearly — codec support moves fast.
Frame Rates: Pick One and Commit
Frame rate is a creative choice with one hard rule: every shot in one project shares the same frame rate. Mixed rates force the editor to invent or discard frames — judder on moves, stuttering motion, pacing that feels “off.”
- 24 fps — the cinematic standard. The motion blur and cadence read as “film.” Suits narrative and mood-driven work. Tradeoff: fast pans can strobe, so camera movement must be deliberate.
- 30 fps — the social standard. Slightly smoother and more immediate than 24, matches phones and monitors cleanly, and is the default expectation on TikTok, Reels, and Shorts. The safe default for tutorials, talking-head, and product content.
- 60 fps — smooth motion for sports, dance, action, gaming. Also gives clean slow motion: 60 fps conformed to a 30 fps timeline plays at half speed with every frame real. Costs are larger files and a “video” look that can feel less cinematic.
Converting between rates needs care. Interpreting footage (treating 60 fps as 30 fps) changes playback speed — right for slow motion, wrong when accidental. Retiming 24 fps onto a 30 fps timeline forces frame blending or interpolation, which warps on complex motion. Cleanest policy: decide the delivery rate first, then shoot or generate everything at that rate — or an even multiple like 60 for 30 fps delivery.
For AI-generated footage, generate at your delivery frame rate when the tool allows it, and normalize unusual output rates before editing, not after.
Reframing: Moving Between Aspect Ratios
Every project eventually needs two shapes: the 16:9 horizontal cut and the 9:16 vertical cut. How you move between them decides whether the vertical version looks intentional or like a panicked crop. Three approaches, in order of quality.
From 16:9 to 9:16
1. Punch-in (center crop). Scale the 16:9 frame until it fills 9:16, discarding roughly the left and right thirds. Fine for centered talking-head and single-subject shots; destructive for edge action. A 4K horizontal master gives the crop more pixels to work with.
2. Reposition (pan-and-scan). Keyframe the crop window to follow the subject, shot by shot. The most intentional-looking results, because a human decides what matters — and the slowest method, best suited to hero content over daily output.
3. AI-assisted reframing. Auto-reframe tools detect the subject and reposition the crop automatically. Genuinely useful on clean single-subject footage; confidently wrong on busy scenes. Related: generative outpainting — extending frame edges with generated content instead of cropping. Check outpainted edges frame by frame for warping, and favor simple backgrounds (skies, walls, blurred interiors). Review every AI-reframed shot before export; automation proposes, you dispose.
The deeper fix is upstream: compose for both frames from the start — subjects near center, sensible headroom, nothing critical at the edges. One more reason storyboarding first pays off: that’s where you decide what survives the crop.
From 9:16 to 16:9
The reverse — vertical footage in a horizontal video — uses the blurred-background pillarbox: the vertical clip sits centered while a duplicated, heavily blurred, slightly darkened copy fills 16:9 behind it. Done well it reads as a designed treatment; too sharp or bright and it fights the main image.
Either direction: faces and key action stay in the safe center, text gets repositioned (never just scaled with the crop), and every reframed shot gets a fresh look before shipping.
The Export Preset Checklist
Run this sequence on every project. Save each platform’s settings as a named preset once, and it becomes a few clicks instead of fresh decisions. Set it up once, use it forever:
- Lock the edit, then export the master. Highest timeline resolution, ProRes 422 or DNxHR (high-bitrate H.265 if storage demands it), 48 kHz audio, full handles. Archive it: projectname_master_YYYY-MM-DD.mov.
- Export the YouTube 16:9 delivery. H.264, 1920 × 1080 or 3840 × 2160 to match the master, YouTube’s published bitrate targets as guide (verify current numbers), project frame rate, AAC 48 kHz. SRT alongside.
- Export the vertical delivery. 1080 × 1920, H.264, 10–20 Mbps, 30 fps (60 for high motion), reframed per the section above, burned-in captions above the bottom UI zone. One file serves TikTok, Reels, and Shorts — spot-check safe zones in each app.
- Render caption variants. Burned-in vertical plus a clean version without burned text (for clients and sidecar workflows), and the SRT for YouTube.
- QC on a real phone. Watch the vertical export in each app: no text under buttons, captions readable on mute, image clean after platform processing. Watch the YouTube export on the largest screen available.
- Upload, then verify. After each platform finishes processing — not just uploading — watch the opening seconds of the live version. Silent processing failures and surprise crops happen; catching them now costs minutes.
File naming keeps the system from collapsing into “final_v7.mp4” chaos. One convention everywhere:
projectname_platform_YYYY-MM-DD_v1.ext
For example: neon-noir_master_2026-10-08.mov, neon-noir_youtube4k_2026-10-08.mp4, neon-noir_tiktok_2026-10-08.mp4, neon-noir_youtube_2026-10-08.srt. Platform says what the file is for; date says which render is newest; version says how many re-exports. Future you will be grateful. Trust me on this one.
Delivery specs aren’t glamorous, but they decide whether your work arrives intact. A clean master, platform-matched exports, respected safe zones, readable captions, a checklist you run — that’s the system. Build it once as presets and habits, and every video looks made for its screen. Because it was.