Export Settings for Vertical Video That Survive Upload

Every platform re-encodes what you upload. That single fact explains most of the "why does my video look worse after posting" complaints. You are not choosing a final file; you are choosing how much quality is left for their encoder to work with.

Get the basics right and a phone-shot clip looks crisp after upload. Get them wrong and even good footage goes soft, stutters, or arrives silent.

Resolution: 1080 by 1920 is the floor, not the target

Vertical video is 9:16. The safe export is 1080 by 1920. It is what every platform accepts, it plays everywhere, and it is small enough to upload quickly.

Exporting larger has one real benefit: if the platform decides to re-encode at a higher resolution, it has detail to work with. Exporting at 1440 by 2560 or 2160 by 3840 from a source that genuinely has that detail can look slightly cleaner after upload. It also multiplies file size and upload time, and it does nothing at all if the original footage was 1080 by 1920 to begin with.

The rule that matters: never upscale. Exporting a 720p source at 4K produces a large file full of interpolated mush, and the platform's encoder will spend bitrate preserving the mush.

If your footage is horizontal and you are cropping to vertical, check the crop before you check the settings. A crop that cuts off the top of someone's head is not fixable in the export dialog.

Frame rate: match the source, do not convert

Export at the frame rate you shot. 30 frames per second for most talking-head and tutorial content, 60 for gameplay, sports and anything with fast motion.

Converting frame rates is where stutter comes from. 24 to 30 requires inventing frames or repeating them, and 30 to 24 means dropping them. Both produce judder that is subtle on a desktop monitor and obvious on a phone.

The other trap is variable frame rate. Many phone cameras and nearly all screen recorders write files whose frame timing varies instead of staying constant. Editors dislike this, and the mismatch can produce audio drift that grows over the length of the clip. If you record screen content, check whether the recorder can output constant frame rate, and set the export to the same rate.

Bitrate: the setting that actually decides sharpness

Bitrate is how many bits per second are spent describing the picture. Too low and motion turns into blocks; too high and you have a big file with no visible gain, because the platform will compress it anyway.

As a starting point for 1080 by 1920:

• 30 fps: roughly 10 to 16 Mbps is a sensible window for most content.
• 60 fps: roughly 16 to 24 Mbps, because there are twice as many frames to describe.
• Talking head with a static background: the low end is fine. Compression loves stillness.
• Fast motion, confetti, water, camera movement: go to the high end. These are the patterns that break first.

If a platform offers a quality slider instead of a number, choose the high setting for anything with movement and the middle setting for static content. Do not choose the maximum out of superstition; it costs upload time and returns little.

Codec: H.264 unless you have a reason

H.264 is understood by every platform, every browser and every phone. It is the safe default and the one to use when you do not want to think about this section.

H.265, also called HEVC, produces a smaller file at the same quality, which matters if your upload connection is slow. The cost is compatibility: some platforms re-encode it poorly, some browsers will not preview it, and older devices may refuse it. If you use HEVC, keep the H.264 version as the one you actually upload and treat the smaller file as a backup.

ProRes, DNxHD and similar editing codecs are for intermediate work, not for publishing. They are enormous and platforms will compress them heavily. Export them only as a master copy you keep for later re-edits.

Audio: the settings nobody checks until it is silent

Audio problems are the most common reason a finished export gets pulled minutes after posting. Set these deliberately:

• Sample rate: 48 kHz. Music and platform pipelines assume it, and resampling a 44.1 kHz export adds a step you do not need.
• Channels: stereo, even for a single voice. Mono tracks sometimes play on one side only depending on how the platform handles them.
• Bitrate: 320 kbps AAC, or 256 if the option is not offered. Audio bitrate is cheap; do not economise here.
• Loudness: many platforms normalise toward roughly minus 14 LUFS. Mixing far below that gets turned up, which raises the noise floor; mixing far above gets turned down, which flattens impact. Aim near it and check the meter rather than trusting your ears on one device.

Then listen to the exported file on a phone speaker at low volume. If the voice is still intelligible, the mix works.

The five export mistakes that show up most

1. Double compression. Exporting from an already-published download, then uploading again. Each pass costs quality. Always export from the original source.
2. Wrong aspect ratio. A 16:9 export with black bars top and bottom is technically vertical and looks like a mistake. Crop or reframe instead.
3. Cropping after styling. Captions and graphics placed for a full frame get cut when the frame is cropped at export. Style for the final canvas.
4. Exporting before checking the last frame. Exporters occasionally drop the final frame or freeze it. Watch the end, not just the beginning.
5. Trusting the preview. Editor previews are frequently scaled down, so softness and caption placement errors are invisible there. Judge the exported file.

A checklist to run once per batch

• Canvas 1080 by 1920, no letterboxing.
• Frame rate matches the source and is constant.
• Bitrate at the high end for motion, the low end for static.
• H.264 unless there is a specific reason otherwise.
• 48 kHz stereo audio, around minus 14 LUFS.
• File plays start to finish outside the editor.
• Audio audible on a phone speaker at a third of the volume.
• Captions clear of the platform interface.

Save that as a preset and the export pass in a batch becomes near-mechanical, which is exactly what you want it to be. The batching method itself is in how to batch produce a week of shorts.