Skip to content
AI Music Video Deliverables: Masters, Aspect Ratios, 4K and Clean Plates

AI Music Video Deliverables: Masters, Aspect Ratios, 4K and Clean Plates

MIDIVOXX — Pearl In The Shell cinematic-ai-music- video-production

AI Music Video Deliverables: Masters, Aspect Ratios, 4K and Clean Plates

A professional delivery package should include a high-quality master (preferably 4K), platform-specific encodes (horizontal, vertical and square cutdowns), audio stems and TAC/metadata, and clean plates or source frames for future fixes. Name files clearly, include checksums and a delivery manifest so labels and distributors can ingest, re-edit and archive without re-asking for assets.

Delivery checklist

What a professional delivery package includes

Below is a practical checklist you can use when specifying deliverables with your production partner.

  • Master video (highest-quality): resolution, codec and color space (details below)
  • Platform encodes: 16:9, 9:16 (vertical), 1:1 (square) and any platform-specific versions
  • Web-optimized files: H.264/H.265 MP4s for web and social
  • Clean plates / source frames: background-only frames or masked passes for VFX fixes
  • Audio: full mix, vocal/instrument stems, 48 kHz WAV, and timecode alignment
  • Metadata & assets: edit decision list (EDL/AAF/XML), color LUTs, fonts, and project notes
  • Delivery manifest: file list, checksums (MD5/SHA1), delivery method and contact

Masters, codecs and color

Choose a master you can go back to for future edits or broadcast.

  • Preferred master: 4K (3840×2160) or higher where the project supports native output. Use a mezzanine codec such as ProRes 422 HQ, ProRes 4444 (if alpha/transparency is required) or DNxHR. These preserve quality for re-grading and repurposing.
  • Archive alternative: lossless ProRes or high-bitrate DNxHR if storage is a concern.
  • Web masters: supply H.264/MP4 or H.265/HEVC encodes for streaming and distribution; include bitrate targets and frame rates.
  • Color: deliver in a clear color space (Rec.709 for SDR, Rec.2020/P3 for HDR). Include any 3D LUTs or grading notes used on the final master.

Note: whether we can produce specific codec files (e.g., ProRes 4444 with alpha) depends on the project pipeline and tooling. Confirm before committing to a codec.

Aspect ratios and social cutdowns

Music videos must live on multiple platforms. Specify which aspect ratios you need and whether reframing is required.

  • Primary: 16:9 (landscape) — typical for YouTube and broadcast.
  • Vertical: 9:16 (stories/reels/TikTok) — requires reframing or separate comps to keep key action and titles visible.
  • Square: 1:1 — good for feed posts and previews.
  • Social cutdowns: 30s, 15s or 6s edits for ads and promos. Provide edited versions with platform-safe title placement.

When requesting vertical masters from horizontal footage, agree on safe-action areas and who handles re-framing. Automated crops can work, but for performance and titles, manual recompose is recommended.

Clean plates, VFX passes and source frames

Clean plates are background or empty-scene frames with no foreground subject — essential for future touch-ups, retiming or removal of AI artifacts.

  • Provide at least a few clean plates per scene and full-resolution source frames for any AI-generated composites.
  • If the project includes layered passes (alpha channels, depth, matte, or motion vectors), list them explicitly in the manifest.
  • If native project files from AI tools are available and shareable, they are useful for later re-render or debugging — but not all AI toolchains export stable project files.

Audio, stems and metadata

Include a delivery-ready audio package:

  • Full mix (broadcast/master) in 48 kHz WAV, plus stereo and any required loudness spec notes (LUFS) for platforms.
  • Stems: vocals, drums, bass, instrumental, FX — clearly labeled and timecode-aligned to video.
  • Metadata: timecode start, frame rate, sample rate, composer credits, ISRC tags if applicable.

Naming, checksums and delivery mechanics

A good naming convention saves time during intake. Use: Artist_Song_Video_Version_Res_Codec_Date (e.g., Artist_Title_Master_4K_ProRes422_20260912.mov).

Always include a delivery manifest that notes file sizes, MD5/SHA1 checksums and transfer method (Aspera, S3, signed URL). State contact and any playback requirements.

Practical decision guide — what to choose and why

  • Need future-proofing and broadcast options? Ask for a 4K ProRes master, color LUTs and full stems.
  • Only digital streaming or social? A 1080p or 4K master + optimized H.264/H.265 encodes and vertical cutdowns will cover most needs.
  • Expect creative revisions? Request clean plates, source frames and any available project files or AI pass exports.

Be explicit about limits: if a project used a generator or third-party API that doesn’t export editable project files, the studio may only be able to supply rendered masters and asset passes.

Example delivery packages

  • Basic: 4K H.264 master, 1080p web MP4, 9:16 vertical MP4, 48 kHz stereo WAV, manifest.
  • Standard (recommended for labels): 4K ProRes master, 1080p/720p social encodes, 3 vertical/square re-composes, full stems, LUT, clean plates, manifest.
  • Archive/Broadcast: 4K ProRes (or higher), ProRes 4444 (alpha if needed), EDL/AAF/XML, full VFX passes, stems, checksums and transfer link.

For help choosing the right package for your release schedule and platforms, see our AI Music Video Production guide (/what-to-prepare-before-starting-an-ai-music-video-project/) and Cost considerations page (/ai-commercial-production-cost-what-brands-should-budget-for/).

FAQs

What file formats should I request for long-term archiving?

Request a high-quality mezzanine master such as ProRes 422 HQ or DNxHR at the project’s native resolution (4K if available), plus a delivery MP4 for web. Include color LUTs and an EDL for future regrades.

Can you create vertical versions from a horizontal master?

Yes — but vertical versions work best when recomposed manually to preserve framing and titles. Automated crops are faster but may lose important subject detail; agree on safe-action areas during production.

What are clean plates and why do I need them?

Clean plates are background-only frames or sequences with no foreground subjects. They let editors remove artifacts, replace backgrounds or re-time elements without re-rendering the whole scene.

Will I get the AI project files used to generate the video?

Not always. Some AI toolchains do not export stable, shareable project files. Ask during scoping if access to native project files or generator passes is essential — we’ll confirm availability per project.

How should files be named and delivered?

Use a consistent naming convention (Artist_Title_Version_Resolution_Codec_Date) and include a delivery manifest with checksums. Deliver via agreed transfer method (Aspera, S3, signed links) and confirm receipt.

Frequently asked questions

What file formats should I request for long-term archiving?

Request a high-quality mezzanine master such as ProRes 422 HQ or DNxHR at the project's native resolution (4K if available), plus a delivery MP4 for web. Include color LUTs and an EDL for future regrades.

Can you create vertical versions from a horizontal master?

Yes — but vertical versions work best when recomposed manually to preserve framing and titles. Automated crops are faster but may lose important subject detail; agree on safe-action areas during production.

What are clean plates and why do I need them?

Clean plates are background-only frames or sequences with no foreground subjects. They let editors remove artifacts, replace backgrounds or re-time elements without re-rendering the whole scene.

Will I get the AI project files used to generate the video?

Not always. Some AI toolchains do not export stable, shareable project files. Ask during scoping if access to native project files or generator passes is essential — the studio will confirm availability per project.

How should files be named and delivered?

Use a consistent naming convention (Artist_Title_Version_Resolution_Codec_Date) and include a delivery manifest with checksums. Deliver via agreed transfer method (Aspera, S3, signed links) and confirm receipt.