Skip to content

Video delivery and archiving: masters, formats, and naming for reuse

How to deliver and archive video so it can be reused instead of remade: masters, per-channel exports, subtitles, and naming that survive the first use.

Founder of PolimakeUpdated
Video delivery and archiving: masters, formats, and naming for reuse

The delivery format determines what you can do with a video later: broadcast it, re-edit it, keep it as a master, adapt it for social media, or send it to a client.

Most of the disputes that end up in back-and-forth emails, "this won't open," "it looks pixelated," "it's too heavy to upload," "we want to change the subtitle and we can't", are settled when you define masters, deliveries, and naming, not when you receive the file. This guide explains what to ask for and what to archive, in what order, and why.

Container and codec are not the same thing

MP4 and MOV are container formats: they wrap one or more data streams. Their extension alone does not identify the codec or guarantee playback at the destination.

The codec is what lives inside: the algorithm that compresses the video and audio. A single MP4 file can contain H.264, H.265, or AV1 video; AAC, MP3, or Opus audio. A MOV file can carry H.264 or ProRes. When someone says "I need an MP4," what matters is understanding: with which internal codec, at what bitrate, in what resolution.

The main containers and what they're for:

  • MP4 (officially MPEG-4 Part 14, ISO/IEC 14496-14, standardized in 2003): the most universal. It works in practically every player, browser, and platform. It's the default choice for digital deliveries, social media, and web publishing. Almost always with an H.264 or H.265 codec.

  • MOV (QuickTime, Apple's proprietary format since 1991): flexible, supports more codec types and professional metadata. It's the usual container in editing workflows, ProRes, intermediate codecs, files with several audio tracks. It plays without issue on macOS and Windows with the appropriate codecs, but some web platforms don't accept it directly.

  • MKV (Matroska, 2002): an open container, very capable, it supports multiple audio tracks, embedded subtitles, chapters. Popular in distribution and archiving, less so in commercial delivery because not every platform accepts it.

  • WebM (Google, 2010): an open, web-oriented container, usually carrying VP9 or AV1. Useful for serving video on your own sites when you control the player; it doesn't work as a generic delivery because some contexts don't support it.

  • AVI (Microsoft, 1992): legacy. It shows up in old files but isn't used for modern professional deliveries.

The operating rule: ask for MP4 when the destination is generic digital publishing; MOV when there's later editing, retouching, or a professional workflow; WebM only when publishing in your own player that supports it; MKV for high-capacity personal archiving. Everything else is usually legacy.

Masters, intermediates, and deliveries: three different things

One of the most expensive points of confusion is failing to distinguish between master, intermediate, and final delivery. All three are video files, but they have different functions and different formats.

The master is a high-quality reference version used to prepare other deliveries. It can be delivered or published when the destination supports it. A flattened master does not replace the originals, editing project, and dependencies when you need to change the edit or remove graphics already baked into the image.

Master options include ProRes 422 HQ, ProRes 4444 when you need alpha, and DNxHR, depending on the agreed workflow. Size depends on profile, resolution, and frame rate. Apple specifies about 220 Mbps for ProRes 422 HQ at 1920×1080 and 29.97 fps: roughly 1.65 GB per minute of video, before audio and container overhead.

An intermediate moves between stages and must retain the quality needed for the next task. A proxy makes editing or review easier, but does not replace the original by default for finishing or final delivery. Premiere exports from full-resolution media by default; exporting from proxies requires an explicit choice.

The final delivery is what reaches the destination, channel, platform, client. Here everything changes: the priority is no longer preserving quality for re-editing, but producing a reasonably sized file that plays well at the destination. MP4 with H.264 is still the safe choice for almost any commercial destination; H.265 offers a smaller size at equal quality but with slightly more limited compatibility. To decide case by case, it helps to know how to choose between H.264 and H.265 based on destination and compatibility.

Asking for "the final file" without specifying what it's for leads to misunderstandings. The right approach is:

  • "I need the archivable master in ProRes 422 HQ" (for my archive).
  • "I need the YouTube delivery in MP4 H.264" (to publish).
  • "I need a clean version without final graphics for future adaptations" (for re-edits).

These three are different deliveries. Asking for "the final file" without further detail forces the producer to guess.

What to ask for based on destination

These examples help frame the request, but the destination specification determines the delivery. Distinguish organic posts, ads, and local playback. References were checked on October 12, 2026; keep the applicable specification with the project.

YouTube. Its encoding guide recommends MP4 with H.264 and keeping the recording frame rate. Consult its table to match bitrate to resolution, fps, and SDR/HDR. Check the processed version; a larger upload alone does not guarantee a visible improvement.

Vimeo. Its compression recommendations include H.264, H.265, and ProRes 422 HQ. Choose based on quality, size, and account capacity; there is no general quality advantage over another platform for every video.

Meta (Facebook and Instagram). MP4 H.264, AAC audio. It recompresses aggressively, so it's best to upload versions already optimized to the correct size: 1080×1080 for square feed, 1080×1350 for vertical feed, 1080×1920 for Reels and Stories.

TikTok. Prepare the aspect ratio for the chosen placement and check the preview. For a vertical piece, 9:16 can be the working format. Do not assume desktop or API uploads preserve more quality than uploading through the app.

LinkedIn. For video ads, the official specification accepts MP4 files from 75 KB to 500 MB and from 3 seconds to 30 minutes, with placement-specific limits; in-stream ads can be up to 90 seconds. Do not apply these limits to organic posts.

X (Twitter). The official help page states up to 512 MB and 140 seconds for accounts without Premium. Extended limits depend on subscription and upload method; check them before preparing a long delivery.

Email marketing. Ideally, you don't include video as an attachment. You upload it to your own page or to YouTube/Vimeo and link to it. If you have to attach it, MP4 H.264 at the lowest possible weight (rarely above 5 MB).

Event screen or digital signage. Request the player and screen specification: container, codec, dimensions, fps, and audio. Physical resolution alone does not ensure compatibility; test the file on the equipment that will be used.

Your own website. MP4 H.264 as a universal fallback; ideally WebM with AV1 or VP9 as the primary source for its smaller size, with <source> tags offering both to the browser. For short looping background clips, H.264 is still the safest route.

TV broadcast. Request the broadcaster’s specification: container, codec, tracks, captions, and loudness. EBU R 128 recommends −23 LUFS programme loudness; this is not a universal value for every broadcast or platform.

Cinema/projection. DCP (Digital Cinema Package), MXF with JPEG 2000, a very specific format prepared with dedicated software. It's almost always outsourced to DCP mastering houses.

Subtitles: the most underestimated decision

How subtitles are delivered greatly changes the usefulness of the file later on.

Burned-in subtitles. They are part of the image and viewers cannot switch them off like a text track. Changing them without covering the image requires a clean version or the project. They can coexist with selectable captions and may overlap them. YouTube generates automatic captions through speech recognition; burned-in text does not block them by itself.

Subtitles as a separate file (sidecar). They come in standalone files:

  • SRT (SubRip): the most universal. Plain text, supported by almost everything. Limited styling.
  • VTT/WebVTT: the W3C standard for HTML5 video, supports more styling and positioning.
  • ASS/SSA: an advanced format with detailed styling, popular in distribution.
  • CEA-608/708: closed captions for broadcast, embedded in the stream.

For digital deliveries, SRT and VTT are common options. For broadcast, request the standard required by the broadcaster; CEA-608/708 are not universal requirements across every country and system.

Keep a separate subtitle file, such as SRT, alongside a burned-in version when needed. It lets you correct and translate the text. Check which tracks each destination supports and also keep a clean version for future adaptations.

Resolution, frame rate, and color: three constants worth locking down

Three more parameters that are neither container nor codec, but that shape the delivery.

Resolution. 1920×1080 (Full HD) and 3840×2160 (4K UHD) describe dimensions, not guaranteed quality. Deliver the agreed dimensions and preserve the original. Upscaling adds pixels but does not automatically recover detail that was never captured.

Frame rate. Keep the source frame rate when the destination accepts it. If it requires another rate or the edit mixes sources, plan the conversion and check motion, duration, and synchronization. Avoid converting out of habit; do not reject a conversion that is part of the delivery specification either.

Color space. Resolution and dynamic range are separate decisions: 4K video can be SDR. Rec.709 is a common reference for web SDR. For HDR, confirm primaries, transfer function, bit depth, and metadata; YouTube’s HDR guide requires Rec.2020 with PQ or HLG. Changing a color tag does not correctly convert the image.

Audio. Agree on codec, track count and order, sample rate, loudness, and true peak. AAC is common for digital deliveries and PCM for masters. Follow the destination specification; −14 LUFS for streaming and −16 LUFS for podcasts are not universal requirements.

Naming as part of the delivery

The last thing that seems to matter and the thing that ends up mattering most six months later: how the files are named. A delivery of fifteen versions named Final_v3_approved_REAL_FINAL2.mp4, final-final.mov, Untitled.mp4 is a delivery that in six months no one will know how to use.

A reasonable naming convention includes, in order: brand, campaign, piece, version, language, format, resolution, date. For example: polimake-launch-spot-30s-en-mp4-1080p-2026-05-05.mp4. It's ugly to read but filterable, sortable, and understandable months later.

The detail becomes critical when there are multiple versions per channel: 30s/15s/6s, horizontal/vertical/square, with subtitles/without subtitles. A single piece can generate fifteen legitimate files. Without naming conventions, they're impossible to manage.

Mistakes that invalidate deliveries

Asking for "the final file" without specifying. Without defining master, intermediate, or delivery, the producer guesses. The recipient may receive an export that is valid for a different use.

Recompressing already-compressed deliveries. Taking an MP4 H.264 that YouTube compressed and re-exporting it to MP4 H.264 accumulates artifacts. Each generation loses quality. If you have to re-edit, go to the master, not the file downloaded from the channel.

Confusing compression with quality. "It's small, so it must be bad" isn't always true: H.265 at 8 Mbps can look better than H.264 at 12 Mbps. "It's big, so it must be good" isn't either: a badly rendered master can weigh 10 GB and look worse than a well-made 100 MB MP4.

Delivering without checking the processed version. Do not assume 1080p will always outperform a 4K upload, or vice versa. Test the file through the intended publishing method and review image, text, crop, and audio after processing.

Not documenting master loudness. Record the target and final measurement. Prepare another mix if the specification requires it, rather than assuming a higher number will sound better on social media or every broadcaster requires the same level.

Forgetting the clean version. The "clean version" is the piece without final graphics, without burned-in subtitles, without overlaid text, just image and voice. It's the base on which future versions are built (other languages, other markets, other durations). Whoever doesn't request it in the original delivery has to renegotiate three months later.

How it fits into the workflow

Requesting formats correctly isn't just technical precision. It's what allows the piece to survive its first cycle of use. Delivery is the last phase of the video production process, but format decisions are anticipated from the shoot onward. A well-made delivery includes, at minimum:

  • An archivable master (ProRes/DNxHR).
  • A clean version without final graphics.
  • A final per-channel delivery with codec and bitrate tuned.
  • Subtitles in a separate SRT.
  • A burned-in version for silent-consumption channels.
  • A coherent naming convention.

This multiplies the files but divides the problems. The alternative, delivering only "the final", produces immediate savings and medium-term pain.

In Polimake, you can store and retrieve masters and their versions within your audiovisual library. Prepare and verify the export in your chosen editing tool; keeping the package and its context makes it easier to find the material for a later adaptation.

This relates to the decision about bitrate per channel, the choice between MP4 and MOV in professional workflows, and when it's worth subtitling a video instead of burning in text.

To wrap up

"What format will the video be delivered in?" is really five questions: which container, which internal codec, which resolution and frame rate, which type of file (master, clean, final), and which versions per channel. Resolving all five before exporting prevents the delivery from turning into a negotiation that drags on for weeks.

The difference between a team that delivers well and one that doesn't isn't technical talent, both know how to export. It's discipline in requesting and discipline in archiving. Whoever has that discipline can recover an old piece, translate it, trim it, refresh it. Whoever doesn't, produces from scratch again every time something changes.

Quick references

  • Master: ProRes 422 HQ or DNxHR HQ. Heavy but archivable.
  • Generic digital delivery: MP4 H.264, AAC audio.
  • Resolution: as agreed with the destination; also preserve the original.
  • Frame rate: preserve the source rate if accepted; verify any necessary conversion.
  • Color: specify SDR/HDR, primaries, transfer function, and metadata separately from resolution.
  • Subtitles: preserve the separate text and a clean version for future adaptations.
  • Loudness: target and measurement according to the destination specification.
  • Always a clean version: without final graphics, the base for future adaptations.
  • Naming: brand-campaign-piece-version-language-format-resolution-date.
  • Ask for multiple deliveries, not "the final."

Verify delivery before accepting it

Use a manifest with names, sizes, duration, resolution, audio, language, rights, and project relationship. Open masters and editable files, check dependencies, and confirm every derivative comes from the approved version. Preserve the specification that produced the file.

Frequently asked questions

What resolution is 4K?

In video, 4K UHD is 3840 × 2160 pixels at 16:9, the standard for TVs, YouTube, and most cameras. Cinema uses DCI 4K, at 4096 × 2160. Neither one tells you the container or the codec: a 4K video can arrive as an MP4 with H.265 or as a MOV with ProRes.

Is it worth asking for an 8K delivery?

Almost never as a final delivery. 8K UHD is 7680 × 4320 pixels, four times as many as 4K UHD, and it mostly makes sense at the shooting stage, to reframe or stabilize with room to spare. For publishing, 4K or 1080p is usually enough; what is worth doing is archiving the original at its native resolution.

What video format should I ask for to publish on social media?

For almost any network, an MP4 with H.264 video and AAC audio, prepared for each placement: 1080 × 1920 (9:16) for Reels, Stories, and TikTok, and 1080 × 1350 for Instagram's vertical feed. Ask separately for the master and the clean version, because the social MP4 can't be re-edited without losing quality.

How much space does one minute of ProRes video take up?

It depends on the profile, resolution, and frame rate. According to Apple, ProRes 422 HQ at 1920 × 1080 and 29.97 fps runs at about 220 Mb/s, roughly 1.65 GB per minute not counting audio. In 4K the size shoots up, so plan storage for the master before you request it.

In Polimake, the package can be shared and retrieved through the interface, API, or MCP, and scenes can be searched inside video. Format provides compatibility; context allows reuse without guessing.