Video Exports

A Pre-Upload Checklist for YouTube Exports

Inspect the actual export for stream settings and play through a brief checklist before uploading to YouTube.

Open the exported file from the folder you plan to upload. Your editing timeline can sound correct while the export uses an alternate track or still has an old ending. Test the delivered file before you copy its name into your release checklist.

Write down your intended duration, resolution, frame rate, audio language and output name. Open the file in a player and compare those expectations with what actually arrived. Include one detail that distinguishes this edit from the last one, such as a corrected end card or a different opening line.

Read the streams

FFmpeg's ffprobe documentation describes how to report container and stream data. With FFmpeg installed, this read-only command lists both for a local test export.

ffprobe -v error -show_format -show_streams -of json upload.mp4

Find the video stream and check its dimensions, frame rate, codec and field order. Find each audio stream and check its codec, sample rate and channel layout. Note any stream you did not expect, and listen to each intended narration or language set. Use the stream list to confirm the track exists. Listen to the first line and a later edit to identify the mic take.

YouTube's recommended upload encoding settings for its Content Manager partners list MP4 with H.264 progressive video and 48 kHz audio options including AAC-LC. Check your own delivery target and use that reference when preparing an ordinary SDR test export. Ask the receiving channel for any specific needs. For baked padding, YouTube's aspect ratio help describes how its player adapts to the source dimensions. It advises against adding your own bars to fill the player.

Play the edges of the file

Moment Verify with playback
First visible frame Intended image, no reference slate left in
First spoken line Correct voice, language and timing
A loud or visually busy passage Dialogue is clear and the output contains no accidental freeze
A cut near the middle and the last spoken line Picture and sound still agree
Final frame The expected end card finishes cleanly

Export a short sample with a spoken line, a cut and the final slate whenever you change a preset. Open it with the same tools you use for the finished file. This gives you time to catch an unintended scale, an omitted audio bus or a shifted cut before encoding the whole video. Follow with the same playback checks on the full export since the sample cannot reveal a later missing segment.

After the local pass and upload, open the channel's playback preview. Compare it against your outgoing file after the video finishes processing. Watch the slate and the same spoken segments so you can spot a change introduced at that stage.

Compare the visible file with the approved cut

Pick one thing that distinguishes this export from another review copy. The project might have changed the opening title, the audio language or the final text. Write that detail in a checked record with a rough time. Open the exported file from the real output folder and seek to that point. Check the expected duration and look for long silent gaps or duplicate clips around the parts just edited. A file with the correct resolution and codec can still contain an older cut.

Inspect the reported video rate together with the rate you intended. Check the visible frame dimensions and whether the picture fills them in the intended way. Baked bars can appear in a file with ordinary widescreen dimensions while the actual picture occupies a much smaller space. Watch in a neutral player and open a representative frame from the file. If the borders are meant to be part of the design, record that choice for the person who will upload it. Otherwise, compare the sequence and export framing.

For a platform whose player accepts different aspect ratios, compare the actual source with the place the viewer will watch it. The vertical clip can be vertical in its own export. If a widescreen player preview already supplies padding, adding another border to the file shrinks the image further. Use a short test file before reworking the full edit. For screen tutorials, the phone readability check can show whether that framing made the important label too small.

Listen for the track you actually exported

A common test case is a draft with the temporary commentary and intended narration both in the editing project. Note which one should appear in the publish file. Check the streams with the command, then play the first line in an ordinary player. Listen again where narration switches between speakers or other tracks. If the expected language is missing, inspect which buses and channels the export included before recutting anything.

A peak or click heard in the player may have been absent from the source scene. Check the start of the loudest music passage and the end of the program. Include a quiet word in the check if the mix has consistent background sound. If you accept more than one audio stream, make sure each one corresponds to the intended label and order. Open the actual file in an app that lets you select those streams. Give the receiving channel the language and track list with the delivered file.

Compare the processed upload with a known reference

When the platform has finished preparing versions for playback, open the right upload in its preview. Check both the start and end. Play the portion that reveals the new title, language or crop. If an early low-resolution playback version looks poor, inspect it again after the expected version is available. Document any difference you need to investigate and compare it against the approved local file.

Make the handoff record explicit. Put the correct file name, stream and language configuration, caption file and publish route in it. If an upload uses a different destination than the preview, verify the exact file and setting that go to that destination. If the channel returns a corrected requirement, start by making a short tested export with that change and record how it differs from the accepted version. This helps prevent a revised local file and an earlier upload from trading places.

Sources