Video Delivery Specs

Deliver motion content correctly across platforms: produce per-platform spec sheets, repurpose one master into every aspect ratio safely, handle captions and accessibility, and run a pre-delivery QC and collect-files pass before handover.

When to use

Use when exporting or delivering finished motion, when targeting multiple platforms from one master, when checking safe areas for UI-overlay platforms, when deciding caption strategy, or when packaging a project for handover/archive.

Decision tree — master strategy and spec path

Two judgments: what to build as the master so it survives every crop, and which delivery path each platform needs. Decide the master before animating — re-cropping after the fact is where deliveries break.

How many ratios does the brief's distribution need?
├─ One ratio only → animate native to that ratio; no spine needed.
└─ Multiple ratios → build a 16:9 master with a centre 1:1 "title-safe
    spine"; expect to RE-LAYOUT (not just crop) for 9:16.

Per target, which path?
├─ Social (Reels/TikTok/Shorts/Story) → 9:16 1080×1920, H.264 8-12 Mbps,
│   burn in captions, keep action out of top/bottom/right UI zones.
├─ Feed → 4:5 (1080×1350) for most screen real estate.
├─ YouTube long-form → 16:9, upload high-bitrate / ProRes, .srt sidecar.
├─ Broadcast → follow the broadcaster's spec PDF EXACTLY: ProRes 422 HQ,
│   region frame rate, R128/A85 loudness, title-safe 90%, textless + slate.
├─ OOH/signage → pixel-exact to the screen, silent, oversize type.
└─ Web hero → MP4+WebM, muted autoplay loop, compress hard, poster frame.

Rule of thumb: if a platform overlays UI (all vertical social), the safe-area map governs layout before the spec governs export. Get the layout wrong and no bitrate fixes it.

Workflow

1. List target platforms from the brief's distribution line (Reels, Feed, Story, TikTok, YouTube, Shorts, broadcast, OOH, web).
2. Pull each platform's spec (table below; full detail in references/platform-specs.md).
3. Plan the master + cutdowns using the repurposing matrix so the 16:9 master survives the crop to 9:16 and 1:1.
4. Decide captions/accessibility — burned-in vs uploaded, styling, safe placement.
5. Run QC against the checklist, then collect files for handover/archive.

Per-platform spec sheet (essentials)

Bitrate guidance (H.264): 1080p social 8-12 Mbps; 1080p high-quality 16-20 Mbps; 4K 35-45 Mbps. Audio AAC 320 kbps stereo, 48 kHz. For broadcast/archive use ProRes 422 HQ, not H.264. Full codec/bitrate detail in references/platform-specs.md.

Safe areas and UI danger zones

Social platforms overlay UI on top of the video. Keep titles and key action out of these zones:

• 9:16 (Reels/TikTok/Shorts/Story): reserve top ~250px (handle/close) and bottom ~250-400px (caption, CTA, controls). On TikTok also reserve the right ~120px column (icons). Keep essential text within the centre ~1080×1080 region.
• 16:9 broadcast: title-safe = inner 90%, action-safe = inner 93%. Nothing critical outside title-safe.
• OOH: follow the vendor's exact pixel map and bleed; assume viewing distance — oversize type.

A visual map of each zone is in references/safe-areas.md.

Cutdown / repurposing matrix (one master → all ratios)

Design the 16:9 master so the centre survives cropping. Plan it before animating, not after.

Best practice: build a "title-safe 1:1 spine" down the centre of the 16:9 master so every crop keeps the message. For 9:16, expect to re-layout rather than crop — budget time for it. Full matrix and a reflow recipe in references/repurposing-matrix.md.

Captions and accessibility

• Open (burned-in) captions: baked into the video. Default for social — most users watch muted, and platform auto-captions are unreliable. Always burn captions for Reels/TikTok/Shorts.
• Closed captions (.srt/.vtt sidecar): uploaded separately; user-toggleable. Required for YouTube long-form and broadcast accessibility compliance; good practice everywhere.
• Styling for burned-in: high contrast (white text, subtle shadow or box), legible weight, 1-2 lines max, placed inside the caption-safe zone (above the bottom UI band, not under it). Sync to speech; ~1-2s per line minimum.
• Beyond captions: avoid conveying meaning by colour alone; keep flashing under 3 flashes/sec (photosensitivity); provide a descriptive title/transcript for screen readers where the platform allows.

Pre-delivery QC checklist (top items)

• Correct dimensions, ratio, and duration for each target.
• First and last frames clean (no black flash, no held render frame).
• Audio present, levels sane, no clipping; broadcast: correct loudness target.
• All text spell-checked; legal/super present and held long enough.
• Logo lockup correct; brand colours match; no placeholder assets.
• Safe areas respected; nothing critical under platform UI.
• Captions accurate and inside the caption-safe zone.
• Export matches codec/bitrate spec; file plays on a fresh machine.
• File names follow convention; versions not mixed up.

Full QC + collect-files checklist in references/qc-checklist.md.

Worked examples

GOOD — one master planned for every crop:

Brief needs 16:9 (web), 1:1 (feed), and 9:16 (Reels + TikTok). You animate a 16:9 master keeping all titles and the logo inside a centre 1:1 spine, then crop to 1:1 cleanly and re-layout (not crop) to 9:16 — restacking the headline above the product, captions burned in above the bottom UI band, action clear of TikTok's right column. Each export matches its platform's bitrate; captions sit inside the caption-safe zone.

ANTI-PATTERN — "we'll just crop it later":

A wide 16:9 hero with the logo bottom-left and a tagline spanning the full width gets center-cropped to 9:16 for Reels. The logo is gone, half the tagline is cut, and the burned-in captions land under the platform's CTA bar where no one can read them.

Why it fails: the master wasn't designed for the crop, and the safe-area map was ignored. The fix is the master strategy above — centre spine, re-layout for vertical, captions above the UI band — decided before animation, not after delivery is due.

Common mistakes

Deliverable spec — what a good handover contains

The output is a packaged, dated delivery folder plus the QC pass behind it (full structure in references/qc-checklist.md). A good handover:

• Has every deliverable at the correct ratio, pixels, duration, codec, and bitrate for its target.
• Separates final exports, captioned versions (+ .srt/.vtt), textless masters, and stills.
• Includes a README listing deliverables, specs, and every font/music/stock licence with its usage scope.
• Uses the file-naming convention consistently, with the final version clearly flagged.
• Has passed the full pre-delivery QC checklist before it leaves.

Before you finish — checklist

• Each target's dimensions, ratio, duration, codec, and bitrate verified.
• First/last frames clean; no dropped frames or artifacts.
• Audio correct (or correctly absent); broadcast loudness met.
• Text spell-checked; legal/super held long enough; logo lockup correct.
• Safe areas respected; nothing critical under platform UI.
• Captions accurate, synced, inside the caption-safe zone.
• Plays on a fresh machine; colour correct outside the editor.
• File names follow the convention; final version flagged; old versions removed.
• Handover folder structured; README + licence/rights notes included.

Quick reference

Reference files

• references/platform-specs.md — full per-platform spec sheet: exact pixels, durations, codecs, bitrates, audio, and file-size limits.
• references/safe-areas.md — ASCII safe-area maps per ratio with pixel measurements for UI danger zones.
• references/repurposing-matrix.md — full cutdown matrix and a step-by-step 16:9→9:16 reflow recipe.
• references/qc-checklist.md — complete pre-delivery QC checklist plus the Collect-Files / handover packaging list and naming convention.