MP4 or MOV: what to deliver at each project stage
How to choose MP4 or MOV for sources, masters, review, and publishing without letting the container name obscure the actual codec.
The team behind Polimake. We explore the intersection of technology, creativity, and automation.
MP4 and MOV are containers
A container organizes video, audio, captions, and metadata. It does not define quality by itself: an .mp4 and .mov may contain very different codecs, bitrates, and resolutions.
“Deliver a MOV for quality” is therefore an incomplete brief. The agency should specify the file's purpose and relevant parameters.
A practical answer
- Client review: a lightweight, compatible MP4 is often appropriate, with visible version identification when needed.
- Web or social publishing: MP4 is commonly suitable, but confirm the channel's current specifications.
- High-quality master: MOV can contain appropriate post-production codecs, though it is not the only option.
- Exchange between edit, color, and sound: follow the technical workflow specification; never decide from the extension alone.
The review file does not replace the master. The master does not need to be sent to every reviewer.
Example delivery matrix
| Stage | Use | Container and codec | Owner |
|---|---|---|---|
| V03 review | Client comments | MP4 + H.264 | Post-production |
| Approved master | Delivery source | MOV + agreed codec | Post-production |
| Instagram portrait | Publishing | MP4 to channel spec | Social |
| Archive | Retention | Master + project and sources | Operations |
Also define resolution, FPS, audio, color, captions, aspect ratio, and naming.
Prevent ambiguous versions
- Retain an asset ID and version.
- Connect every export to its source master.
- Mark the client-approved version.
- Record channel and delivery date.
- Never overwrite the master with a compressed social file.
In Polimake, the master, derivatives, and delivery states can remain connected. That is more useful than a folder containing final.mp4, final.mov, and final_good.mp4 without context.
Questions when someone asks for “a MOV”
- Is it for editing, projection, broadcast, archive, or publishing?
- Which codec does the destination accept?
- Which resolution, FPS, audio, and color space are required?
- Does it need alpha or separate tracks?
- Is there a file-size limit?
For compression inside the container, continue with H.264 or H.265 by compatibility and use.