The last watch before a YouTube upload
Check a finished export for cadence, readable detail, working audio and the version a viewer will actually receive.
The timeline played cleanly all afternoon. The exported file opens on a black frame, a second of a discarded music intro and the title from yesterday. All three can happen without an error message. An export is another version of the film, with its own in point, media choices, codec and file name. Give that version one uninterrupted watch before the person publishing the video receives it.
Write the delivery line first
Make a single line describing the requested file. For a sample brief it might read “Three-minute pottery demonstration, landscape 1920 by 1080, 25 fps progressive, SDR BT.709, stereo, English captions supplied separately.” Compare each part with the approved sequence. The line gives you a way to notice the wrong shape, a duplicated subtitle treatment or a change of frame rate before you leave a render running.
Find the approved cut by its revision and duration. Look for marks left over from a short test export and check whether the export range uses them. Inspect the first visible frame and the last audible tail. If the video ends on a card meant to link to a second lesson, give the publisher the name of that lesson along with the file. The card's design and the link the publisher adds are separate pieces of work.
Use an encoding setting that fits the recording
For an ordinary SDR YouTube upload, its encoding guide gives MP4 with H.264 video as a starting point, recommends progressive video and describes BT.709 for SDR. For a straightforward shoot, preserve the recorded frame rate. When a project deliberately mixes rates or uses slow motion, review the approved sequence cadence and make those conversions deliberately. Merely exporting a twenty-five-frame sequence at fifty frames per second cannot invent fifty distinct original moments.
YouTube's table lists 8 Mbps for a standard-frame-rate 1080p SDR upload and 12 Mbps for the higher frame rate range in that row. Those are useful starting points for this example. Watch the difficult material and check the destination guide when making a new preset. Fine leaves blowing across the whole picture, fabric patterns during a pan and tiny moving type can demand more of an encoder than a still interview background.
For a quick size estimate, 8 megabits per second times 180 seconds gives 1,440 megabits, or about 180 megabytes before the audio and container overhead. A variable-bitrate export will vary with the material and the encoder. This calculation is a rough planning tool for a slow upload connection. An unexpectedly tiny output is a reason to inspect the range and preset before sending it.
Render the troublesome seconds first
Choose a short extract containing the most demanding shot, a title and a cut from bright to dark. Use the actual delivery settings and open the result in a separate video player. Check for broken gradients, crawling outlines, an unexpected matte or a shadow that has lost its texture. If a problem exists in both the original timeline and the export, examine the source, effects and design before raising the bitrate.
Look closely at any screen recording. Small grey menu lettering that seems legible on a large editing monitor can disappear on a phone. Try cropping into the relevant controls or holding the active panel longer. Run the same short export again after the adjustment. This comparison tells you whether the change improved the lesson, and costs far less time than repeating a long final render.
Watch the complete file like a first-time viewer
Play the finished file from its actual delivery folder. Leave the editor closed for this pass. On headphones, notice the first word, changes between speakers and the last music tail. On a phone, play the busiest instruction and look for text hidden by a player control. If captions are supplied separately, load the matching file into a compatible player. Check an early cue, a cue following a long pause and a cue near the end.
Write issues with the playback time, the symptom and where you checked it. “At 01m12s the title shows the wrong ingredient in the MP4” gives the next editor a small investigation. “Export looks off” does not tell them whether to examine a source graphic or the encoder. After a fix, watch both sides of the changed section and compare the total duration with the approved version.
Look at the platform copy when the publisher has access
Have the authorised publisher upload the reviewed file using the intended visibility setting. YouTube makes lower-quality playback available before higher-resolution processing has finished. Check which resolution the player is serving before treating softness as a rendering problem. Once the expected option appears, inspect the same detailed shot used for the local test, then check the caption language and playback on a second screen.
If only the uploaded copy looks different, keep the local export intact while investigating. Check the selected playback quality, whether the difference also appears on another device and whether the uploaded file matches the revision you reviewed. These checks can save a pointless re-export of a clean master.
Give the publisher the verified filename, duration, caption filename and one sentence recording the intended frame rate and colour space. Keep a copy of the approved sequence and the settings that produced that file. The next time the client asks for a vertical cut, you will know exactly which version they saw and which details survived the trip to their screen.