Updated: September 10, 2026
The last step, where finished work goes wrong
A video can be beautifully shot, tightly edited, well graded and properly mixed, and still arrive as a file that will not play on the client's laptop, looks blocky on the conference screen or gets rejected by the platform it was made for. Export is the point where all that work becomes a single file, and the settings on that export decide whether it survives the journey.
The subject has a reputation for being technical and dull. It is technical. It is also the difference between a delivery that lands cleanly and an afternoon of re-exports, so it repays a little attention.
The three things every export decides
Container
The file wrapper, indicated by the extension. It determines what a system recognises and what can be carried inside, including multiple audio tracks and captions. It says surprisingly little about quality on its own, which is why two files with the same extension can look completely different.
Codec
How the picture is compressed. This is what actually determines quality and file size. Delivery codecs are efficient and produce small files suitable for playback; editing and mastering codecs are less compressed, produce large files and survive further processing without degrading.
Bitrate
How much data per second is allocated. Higher means better quality and larger files. The right figure depends on resolution, frame rate and how much movement is in the picture, since fast motion and fine detail need more data than a static interview.
Master versus deliverable
The most useful habit in delivery is to separate the two.
A master is a high-quality, lightly compressed export that you keep. It is large, it is not meant for distribution, and it is what you return to when someone needs a different version six months later. Re-encoding from a master preserves quality; re-encoding from a compressed deliverable compounds the losses.
A deliverable is a compressed file made for a specific destination, sized and encoded to suit it. There are usually several, and each one comes from the master rather than from another deliverable.
Producing deliverables from deliverables is the most common cause of unexplained quality loss. A social version cut down from a web version that was itself exported from a compressed review file has been through three generations of compression, and it looks like it.
Matching the destination
| Destination | What matters most |
|---|---|
| Streaming platforms | generous bitrate; the platform re-encodes, so give it good source |
| Social feeds | correct aspect ratio and captions; heavily compressed on upload |
| Website embed | modest file size, fast start, wide browser compatibility |
| Presentation and events | reliable playback on the venue system, tested in advance |
| Broadcast | strict written specifications; ask for them and follow exactly |
| Client review | small, quick to download, watermarked if appropriate |
| Archive master | quality over size, widely supported codec |
The event row is worth expanding. A file that plays on your machine may not play on a venue laptop running different software, and the failure is discovered in front of an audience. Test the actual file on the actual system before the day, and carry a backup in a second format.
Frame rate and resolution
Frame rate should generally match what was shot. Converting between rates introduces either judder or artificial smoothing, and neither improves the material. Where a project mixes rates, decide the delivery rate early and handle the conversion once rather than repeatedly.
Resolution should usually match the project, and there is rarely a reason to upscale. Exporting a project finished at one resolution to a higher one adds file size without adding detail. Downscaling is legitimate and often sensible, particularly for social versions where the platform will compress heavily regardless.
Aspect ratio is a separate decision and one that should be made during the edit rather than at export, because reframing a wide composition into a vertical one requires attention rather than a crop. That process is covered in aspect ratios and reframing video for social and broadcast.
Colour on export
Colour is where exports most often surprise people. A file that looked correct in the edit can appear washed out or oversaturated in a browser or on a phone, and the cause is usually a mismatch in how colour information is tagged.
The practical guidance is to finish in a standard colour space unless there is a specific reason not to, make sure the export carries the correct tag, and then check the exported file in the environment where it will be watched rather than only in the editing application. A file that looks right in a player and wrong in a browser has a tagging problem, not a grading problem.
Where a project was shot in a log profile, the grade should be complete before export, since delivering ungraded log material to a client who was expecting finished video is a predictable misunderstanding.
Audio in the export
Audio settings get less attention than picture and cause just as many problems. Confirm the sample rate matches the project, use a sufficient bitrate for stereo audio rather than accepting a low default, and check whether the destination expects a single mixed track or separate ones.
Loudness needs to be right at export, since correcting it afterwards means another encode. And if a file is delivered with dialogue only on one channel because a mono source was never routed correctly, half the audience hears nothing. Play the exported file with headphones and listen to both sides.
Captions and subtitles
Decide early whether captions are burned into the picture or supplied as a separate file. Burned-in captions always appear, which suits social feeds where sound is off by default, but they cannot be turned off or translated. Separate caption files can be toggled and swapped for other languages, which suits platforms that support them.
Many projects need both, and producing them from the same source transcript keeps them consistent. Formats and accuracy considerations are covered in the post-production material on our blog.
Getting large files to the client
A finished master can be tens of gigabytes, and how it travels is a delivery decision in its own right. Email is out, and so is anything that silently re-compresses what you upload, which several messaging and collaboration tools do without warning.
For review copies, a streaming review platform is usually best. Clients watch in a browser, comments attach to timecode, and nobody downloads anything by accident. It also prevents the situation where an early cut circulates internally as a file and someone publishes it.
For finished deliverables, a straightforward file transfer service with a download link works well, provided you check the expiry period. Links that lapse after a week produce a request for re-delivery three months later, which is avoidable by noting the expiry in the delivery note or by using longer-lived storage for anything final.
For masters and archives, physical drives still make sense above a certain size. If a drive is being handed over, format it for the client's platform rather than yours, label it clearly, and include a plain text file listing the contents. And always keep your own copy until the client confirms they have theirs, because a drive in transit is a single point of failure.
Naming and handover
A delivery of six files named export_final_2 helps nobody. Use a consistent convention carrying the project name, the version, the aspect ratio, the duration variant and the destination. Dates written year first sort correctly by default.
Send a short delivery note alongside the files listing what each one is and where it is intended to go. Clients frequently forward these files internally, and the note travels with them. Handover of media and project files is discussed in media management, and the wider edit process in from raw footage to final cut.
A pre-delivery checklist
- Watch the exported file end to end, not the timeline.
- Check the first and last frames for black, flash frames or trailing silence.
- Listen on headphones and confirm both channels carry audio.
- Verify loudness against the destination target.
- Open the file in a browser and on a phone, not only in a media player.
- Confirm captions display correctly and are in sync.
- Check file size against any platform limit.
- Confirm naming matches the agreed convention.
- Keep the master, and note where it is stored.
How we handle delivery
We produce a master and generate every deliverable from it rather than from another compressed file, which keeps quality consistent across versions. We ask for the destination before exporting rather than after, because a broadcast specification and a social feed need different files and guessing wastes a day.
Every deliverable is watched through after export, checked on a phone and in a browser, and handed over with a note explaining what each file is for. More on our post-production process is on the blog, background on the about page, and you can reach us through the contact page.
The short version
Container, codec and bitrate are three separate decisions and only the last two determine quality. Keep a lightly compressed master and generate every deliverable from it, never from another deliverable. Match frame rate to the shoot, avoid upscaling, and settle aspect ratio during the edit rather than at export. Tag colour correctly and check the file in a browser and on a phone rather than only in the editing application. Confirm audio is on both channels and mastered to the destination loudness target. Decide burned-in versus separate captions early. Then watch the exported file end to end before sending it.