A finished video or photograph may leave your workspace in several shapes and sizes. A vertical clip, a small web image and a full-resolution delivery can look similar in a folder while serving different purposes. Keeping a final master separate gives you a dependable reference and prevents a reduced social version becoming the accidental source for later work.
Define the master for this project
Agree what the master needs to preserve: the approved edit, intended picture quality, sound and any required captions or graphics. The appropriate format depends on the project and destination, so document the actual settings rather than relying on the word master alone.
Keep the editable project and original media as well when future revisions matter. A final render records the result but may not preserve separate tracks, layers or editable text. The master and the project are complementary parts of the finished work.
Create a protected reference location
Place approved masters in a clearly named folder separate from working exports. Include a version identifier and approval date or record those details in a delivery note. Avoid leaving several ambiguous final files in that location.
Back up the master along with the project material you intend to retain. If an error is found after approval, create a new identified revision instead of overwriting the old reference without explanation. This helps anyone who has already received the earlier file understand what changed.
Label versions by their destination
Name derived outputs with a clear purpose, such as portrait-social or web-small. Record relevant dimensions and whether the version includes burned-in captions, separate captions or no captions. These differences should not depend on opening every file.
When a crop changes the composition, review it as a separate output. A vertical frame may cut off a demonstration or place text over a face. Where appropriate, create the new version from the editable project so framing and graphics can be adjusted deliberately.
Check the relationship before delivery
Compare each derived file with the approved reference. Confirm that the intended content, ending and sound remain present. Check that the file corresponds to the right revision rather than an earlier review export with similar naming.
Open the actual exported versions and inspect them at their expected viewing size. Keep a short delivery list linking filenames to destinations. If a platform requires a new specification later, return to the master or project rather than repeatedly converting a smaller compressed copy.
A separate master preserves a stable reference while platform files do their specific jobs. Keep both the approved result and the editable material you need, name each derivative clearly and review every changed crop or caption treatment before sending it.
