Export Settings, Codecs and Delivery Specifications
Which codec belongs in which situation, why one master cannot serve every destination, and the delivery list that should exist before the edit starts.
Export is treated as the last five minutes of a project and is responsible for a surprising share of its problems: a file that will not play at the venue, a social upload that looks soft, a broadcast rejection, a version that is too quiet. Most of these come from using one export setting for every destination, which no single setting can serve.
The distinction that clarifies everything is between mastering codecs and delivery codecs. A mastering codec stores the finished film at high quality with every frame complete and independent, which makes it large, fast to decode and suitable as the source for everything else. A delivery codec compresses aggressively for distribution, with frames that depend on their neighbours, which makes it small, efficient to stream and poor as a source for further work.
The practical consequence is that a project should always produce a master first, then derive every delivery version from it. Exporting a compressed file and then re-encoding it for another destination compounds the compression, and the result is visibly worse than encoding each version from the master. This is the single most common technical mistake in delivery and it is entirely avoidable.
For web and social, the destination re-encodes whatever it receives, which changes the strategy. Uploading a very large file does not preserve quality, because the platform will compress it regardless; uploading a well prepared file at the platform's recommended specification gives its encoder the best possible input. Sharpness, contrast and fine detail all survive compression differently, and material with heavy grain or fast movement suffers most, which is worth knowing when grading for social.
For event playback the requirements are almost the opposite. Media servers prefer intra frame codecs where every frame is complete, because they scrub, loop and decode predictably under show conditions. A file encoded for web efficiency may stutter on a playback system that has to decode it in real time at large dimensions. Asking the AV vendor what the server expects, and delivering exactly that, removes the risk entirely.
Resolution should match the destination rather than defaulting to the largest available. Delivering a file that does not match an LED canvas means the server scales it, which costs sharpness. Wang et al. (2022), reviewing image quality measurement for large screen displays including LED, emphasise assessing quality from realistic viewing conditions, and scaling artefacts are precisely the degradation that is invisible on a monitor and obvious in a room.
Frame rate should match the destination's expectation and should not be converted casually. A film edited at one rate and exported at another is interpolated or duplicated, and the resulting judder is far more visible on a large screen than on a phone. Confirming the show rate or the platform expectation before finishing, rather than at export, avoids a conversion that cannot be undone cleanly.
Audio loudness is the specification that catches out more projects than any video setting. Platforms normalise loudness, so a mix mastered as loud as possible is turned down and left sounding squashed, while a film mixed for a quiet room is inaudible in a ballroom. Mastering to the target the destination expects, and producing a separate mix for event playback, is the reliable approach. Zhang et al. (2025) found that audiovisual features contribute measurably to engagement, and a version that is too quiet to follow is a version that is not being engaged with.
Colour space and metadata are where files subtly shift appearance between applications. A film graded in one colour space and exported without the correct tags will be interpreted differently by different players, producing the familiar situation where a film looks correct in the editing application and washed out in a browser. Tagging exports correctly is a small step that prevents an entire class of confusing feedback.
The delivery list should exist before the edit begins rather than being assembled at the end. A typical corporate project needs a master, platform versions at several aspect ratios and durations, a silent version, subtitled versions per language, an event specification version if relevant, thumbnails and a set of stills. Agreeing that list at quotation stage sets the price honestly, determines the framing and layering decisions while they are still cheap, and prevents the familiar situation where a film is approved on Friday and six unbudgeted exports are requested on Monday.
References
Wang, J., Mou, X., & Wen, C. (2022). Measurement of image quality for large-screen displays based on audience viewing: Overview of standardization and preliminary study on laser projection displays and LED displays. Journal of the Society for Information Display, 30(6), 523–530. https://doi.org/10.1002/jsid.1095
Zhang, Z., Qiu, K., & Ye, Y. (2025). Influence of audiovisual features of short video advertising on consumer engagement behaviors: Evidence from TikTok. Journal of Business Research, 201, Article 115662. https://doi.org/10.1016/j.jbusres.2025.115662