Export at the Size of the Job

A problem we recently had to set a hard rule for: exports that were far larger than they needed to be. A long-form master came out of the edit at a size that dwarfed the original camera files. It uploaded slowly, filled drives, and was no better to watch than a file a fraction of its size.

Oversized exports usually come from good intentions. Maximum quality settings feel safe. But past a certain point, extra bitrate adds nothing the eye can see, and everything downstream pays for it.

A master should never be bigger than its source

That is now our first rule. The camera already made decisions about how much information to capture. An export cannot add detail that was never recorded; a much larger file just stores the same picture less efficiently. If a master comes out larger than the footage it was cut from, a setting is wrong.

As a working benchmark, a ninety-minute 4K master should land in the region of twenty gigabytes. If an export is several times that, stop and check the preset before it goes anywhere.

Export for where the file is going

There is rarely one correct file. There is the archive master, the client review file, the web version, and the social cuts, and each has a different job. A review link needs to stream quickly. A website file needs to be small enough not to stall a phone. An archive master needs quality and a sensible size. Exporting one enormous file and using it everywhere serves none of them well.

Why it is worth a rule

Storage is cheap per gigabyte and expensive in aggregate. More importantly, oversized files slow down every handoff: uploads to review, transfers to clients, backups overnight. A team that exports sensibly moves faster, and nobody watching the finished piece can tell the difference.