Render presets worth saving, and why the defaults are wrong for most jobs

Delivery happens at the end, usually late, usually in a hurry. Choosing a codec, a bitrate, an audio configuration and a colour tag from a panel of dozens of options at that moment is how mistakes happen.

Presets move that decision to a calm afternoon, where you can look up what a platform actually wants and test that the result is correct.

Six cover nearly every job. Build them once and delivery becomes a choice from a short list rather than a form to fill in.

• Master. A high-quality intermediate you keep. Everything else is derived from it, so it should be visually lossless.
• Client review. H.264, modest bitrate, small enough to send. Quality is secondary to it opening everywhere.
• Web landscape. H.264, sRGB, sized for the platform.
• Web vertical. The same, in a tall frame, sized for phones.
• Broadcast. Whatever the specification says, built from the delivery document rather than from memory.
• Stills. Frame exports for thumbnails and reference.

Name them by where they are going. A preset called 'H.264 20Mbps' requires you to remember what that was for; one called 'Client review' does not.

Video destined for the web needs to be tagged appropriately for how browsers will interpret it. Untagged or mis-tagged files render with shifted colour and contrast — usually washed out or overly contrasty — and the difference does not appear in a professional player, which reads the actual data.

The result is a client reporting that the colour is wrong on a grade you know is correct. It is a tagging problem, not a grading one.

Set it deliberately in the preset and verify once by viewing an export in a browser next to the timeline. Confirming it takes two minutes and removes a recurring confusion permanently.

Audio configuration is where deliveries fail: mono where stereo was expected, a track laid out wrongly, levels above the specified maximum.

Build the channel configuration into each preset and note the required loudness where a specification defines one. Broadcast in particular has firm numbers and a delivery outside them comes back.

Listen to the first ten seconds of every export before sending. It catches silent tracks, wrong channels and the occasional file that rendered with a muted layer — none of which are visible in a picture check.

A finished render is not a verified one. The routine that catches almost everything takes two minutes:

1. Open the file in a normal player, not the editing application.
2. Check the first and last seconds — both are where errors cluster.
3. Confirm resolution and duration match what was intended.
4. Listen to the audio briefly.
5. Scrub the middle for missing media or black frames.

Errors found here are free. The same errors found by the client are not.

Platform requirements shift, specifications get updated, and a preset built three years ago may target something that no longer applies.

Check them once a year against current requirements, and update immediately whenever a delivery is rejected — the rejection tells you exactly which setting was wrong.

Keep them exported to a file alongside your other reusable assets. Presets living only in one installation are lost with the next machine.