Ozmov field note based on production practice. It is not attributed to a search platform or presented as a universal technical rule.
Separate the master from the delivery file
A high-quality master preserves more of the finished work. Platform deliveries may then be created from that master for different codecs, resolutions, aspect ratios, caption requirements or file-size limits.
Keep versions understandable
Final-v2-really-final is not an archive system. Clear naming, dates, language/version identifiers and approval status reduce mistakes when a campaign has many stakeholders or markets.
Preserve source material with context
Original footage, photographs, graphics, audio, project files, licences, releases and usage notes can retain value long after the first campaign. Without context, a technically intact file can still become unusable.
Plan alternate formats while the project is active
Vertical, square, subtitled, silent-autoplay, short-form and presentation versions are easier to produce when they are anticipated before the edit and design are locked.
Archive according to future value
Not every temporary render deserves permanent storage. The useful archive is selective: approved masters, important sources, project files required for revision and the documentation needed to understand rights and provenance.
Use the principle, not a formula
Production choices depend on the brief, location, people, platform and risk. This note explains Ozmov’s working approach rather than claiming one setup is correct for every project.