Tutorials Video

Export Settings for Every Platform

By Infinite Creation · Beginner · ~25 min

Some links on this page are Amazon affiliate links. If you buy through them, we earn a small commission at no extra cost to you.

A 1960s mid-century comic book style editorial illustration showing a video editor and a director reviewing the cut together, with a colour grading panel with trackballs visible in the frame.

Overview

Export settings are where good edits go to get needlessly compressed. This guide gives you one reliable mastering and export workflow that adapts cleanly to YouTube, Instagram, TikTok, and podcast video, so you're not guessing at settings for every new upload.

What You Need

Your finished edit in Premiere, DaVinci Resolve, or Final Cut
The site's Platform Video Specs Reference and Export Settings for Every Platform tables

Steps

Master at the highest quality you'll ever need

Export one high-bitrate master file (H.264 or ProRes, resolution matching your source footage) before making any platform-specific compressed exports. Always compress down from a high-quality master, never re-export from an already-compressed file.

Pick the right codec and container

H.264 in an MP4 container is the safest universal choice. Every platform accepts it and re-encodes predictably. H.265/HEVC gives better quality per bit but has less universal platform support. Use it only where you've confirmed compatibility.

Match colour space to delivery

Export Rec. 709 for standard web delivery unless you're specifically delivering HDR content, which needs its own colour space (HDR10 or Dolby Vision) and platform support check first, exporting HDR footage as if it were SDR causes washed-out, flat-looking video.

Set bitrate per platform and resolution

Higher isn't always better: platforms re-encode on upload anyway, so massively over-shooting bitrate mostly wastes upload time and storage. Use the Video Export Bitrate Calculator to match bitrate to your actual resolution and frame rate.

Export a version per destination

Export separately for each platform's aspect ratio and spec rather than uploading one file everywhere. A 16:9 master force-fit into a 9:16 slot looks worse than a properly reframed export, even if it saves a step.

Tested: what a frame rate mismatch does to motion

We tested the page's Frame Rate Consistency section on 2026-09-25 with FFmpeg 8.1.2. We drew a white bar 32 pixels wide moving 8 pixels a frame across a black strip, at the source frame rate, with no motion blur. Then we converted it to the export rate two ways. FFmpeg's fps filter drops or repeats whole frames. Its framerate filter blends the two nearest frames into a new one. In every output frame we read where the bar was and whether the frame held one clean bar or two faint ones.

Conversion	Dropping or repeating frames	Blending: frames that became blends
24 to 30 fps	1 frame repeated in every 5, 6 a second	95 of 120 (79%)
30 to 24 fps	1 frame dropped in every 4, 6 a second	72 of 96 (75%)
24 to 25 fps	1 frame repeated in every 25, 1 a second	88 of 100 (88%)
25 to 24 fps	1 frame dropped in every 24, 1 a second	84 of 96 (88%)
23.976 to 24 fps	1 frame repeated every 41.7 s	2,104 of 2,400 (88%)
29.97 to 30 fps	1 frame repeated every 33.4 s	2,652 of 3,000 (88%)

Dropping and repeating gives judder, and it is regular. At 24 to 30 fps the bar stood still for one frame in every five, six times a second. At 30 to 24 it jumped twice its normal distance at the same rate. At 24 to 25 or 25 to 24 the stumble came once a second.

Blending gives the smoothed look. Every step was even: at 24 to 30 fps the bar moved 6.4 pixels a frame, exactly the source speed spread over the new rate. But 79 percent of the frames held two ghosted bars instead of one sharp one. FFmpeg only copies a source frame unchanged when an output frame falls within 6 percent of a frame interval of it. That is the filter's default interp_start of 15 and interp_end of 240, on a scale of 0 to 255. So most frames are a mix.

The mismatch that is easiest to miss is 23.976 against 24 fps, because both are often called 24. Dropping and repeating handled it with one repeated frame every 41.7 seconds. Blending changed 88 percent of the frames to fix the same 0.1 percent difference. Check the exact rate of your footage before you set the export, because exporting at the other one converts every frame.

We also tried step 2's warning about H.265 on the same Mac, with the player test from our guide to video that will not play. An 8-bit and a 10-bit HEVC file, both tagged hvc1, played in AVFoundation, Safari, Chrome and Firefox, and the hardware decoder took both. So did 10-bit H.264, which is what FFmpeg wrote when it re-encoded the 10-bit HEVC with no pixel format set. It is the High 10 profile, not the High profile a device specification usually lists. A recent Mac playing your file therefore tells you little about the platforms and devices step 2 means. We did not test those. Set -pix_fmt yuv420p for H.264 and check the platform's own upload specification for HEVC.

To read a file's exact frame rate, which shows 24000/1001 for 23.976 and 24/1 for true 24: ffprobe -v error -select_streams v:0 -show_entries stream=r_frame_rate -of csv=p=0 input.mov

Validated. Measured 2026-09-25 with FFmpeg and ffprobe 8.1.2 and numpy on an Apple M1 Max Mac running macOS 26.6.2, with Safari 26.6.2, and with Google Chrome 153.0.8010.54 and Firefox 156.0.1 run headless. The moving bar is synthetic. The cadence depends only on the two frame rates, but how visible it is depends on the footage. We did not test an editor's own frame rate conversion or optical flow, and did not upload to any platform. "Played" means the player decoded video frames from the file. A Safari file that failed to start was tried up to three times, as in that guide. 1 Safari file needed a second try in this run.

Pro Tips

Save your export presets once you've dialled them in. Most NLEs let you save a custom preset per platform so you're not re-entering settings every upload.
Always watch back your actual exported file before publishing, not just the timeline preview, compression artifacts and audio sync issues sometimes only appear in the rendered file.
Keep your high-quality master files archived, platform compression is one-way. You'll want the master again for future re-edits or re-platforming.

Knowledge Base

Why "Just Export and Upload" Isn't Enough

Every platform applies its own compression pass on top of whatever you upload. If your source file is already poorly compressed, aggressively low-bitrate, or the wrong colour space, that second compression pass compounds the problem. The difference between a clean master and a rough one is much more visible after two rounds of compression than after one.

Bitrate: More Isn't Automatically Better

Beyond a certain point (roughly double the platform's own recommended bitrate for your resolution), extra bitrate in your uploaded file provides no visible benefit because the platform re-encodes it down anyway. You're just spending longer uploading a bigger file for the same result.

Frame Rate Consistency Matters More Than People Expect

Exporting at a frame rate that doesn't match your source footage forces a frame rate conversion that can introduce judder or an unnatural smoothed look. Match your export frame rate to your project's native frame rate whenever the destination platform allows it.

Where This Fits

Export settings are the last stage of Video Production Fundamentals, which explains how the earlier stages limit what an export achieves.

FAQ

Q: Should I always export in the highest resolution my footage supports?
A: Export at your source resolution up to the platform's supported maximum, uploading upscaled footage adds file size without adding real detail.

Q: Is ProRes worth using for final delivery?
A: ProRes is excellent for a mastering/archive file or for passing footage to a collaborator, but H.264/MP4 is what you should actually upload to platforms. ProRes files are far larger with no streaming-quality benefit on most platforms.

Vocabulary

Export preset. A saved group of settings applied in one step. Removes the most common source of delivery error, which is a setting changed for one job and forgotten on the next.

Two-pass encoding. Analysing the whole file before encoding so data can be allocated where the picture needs it. Takes roughly twice as long and produces better results at a given file size.

Constant and variable bitrate. Constant spends the same data every second regardless of content, and variable spends more on complex passages. Variable is generally better for delivery, and constant is simpler for streaming.

Upload specification. The settings a platform publishes as its preferred input. Following it gives the platform's own re-encoding the best material to work from, which matters more than exceeding it.