Bit-exact exports in Video by Zaweba

Export the same project twice in most editors and you get two files that look identical but differ in their bytes. Video by Zaweba has an option that closes that gap. With bit-exact exports turned on, the same project gives the same file twice, down to the last byte.

That sounds like a curiosity until you need it. For archiving, checking and some kinds of automated work it is a genuinely useful guarantee.

Why two exports usually differ

Two things normally make exports drift apart. The first is information stamped into the file: the date and time it was made and the versions of the tools that made it. Change the clock and the file changes. The second is the encoder. Hardware encoders on graphics cards are fast, but their exact output can depend on the card, its driver and its mood that day, so two runs need not match.

What the option changes

Bit-exact export deals with both. It writes no dates or tool versions into the file, and for MP4 it uses the software encoder rather than the graphics card. With those two sources of variation gone, the same timeline, the same media and the same settings produce the same bytes.

The price is speed on MP4 exports, because the software encoder generally takes longer than a graphics card. For a one-off upload that is not worth paying. For the jobs below, it often is.

Jobs it suits

Checking a change is the clearest one. If you re-export a project after touching something you believe has no visible effect, such as tidying the bin or renaming tracks, a bit-exact export lets you confirm that by comparing file checksums. Same checksum, same file, nothing changed.

Archives benefit too. If you keep a master and its checksum, you can rebuild the master later and prove it matches. That is reassuring for anyone storing work for the long term or handing material to an organisation that records checksums.

Automated exports are the third. Video by Zaweba can be driven from the command line, and a script that rebuilds files on a schedule should not produce a fresh, different copy every night when nothing changed. Identical output lets other tools notice that nothing needs uploading or backing up again.

Things to keep in mind

Bit-exact only promises the same file from the same inputs. If a media file is replaced, a font changes, or a setting moves, the output will change, and that is the point: the difference tells you something moved.

Keep the option for projects where reproducibility matters, and leave it off for everyday work where the graphics card can save you time. A preset of your own with the option turned on makes it easy to switch between the two.

Because no date is written into the file, do not rely on the file's internal metadata to tell you when it was made. Use the folder's own dates or your file names for that.

A simple test

If you want to see it for yourself, export a short project twice with the option on, then compare the two files with any checksum tool. They will match. Turn the option off, export again, and compare once more. The difference shows what the option is doing.

Most people will never need this. Those who do, archivists, people building automated pipelines and anyone who has to prove a file has not changed, will find it a quiet and dependable part of Video by Zaweba's export tools.