How to Send Video to an Ad Agency: Optimize Files for AI

Why AI Video Handoffs Break at the Agency Door

AI video generators have made it easy to produce beautiful footage. They have not made it easy to hand that footage to somebody else. Most delivery failures have nothing to do with the creative quality of the render. They happen because the file itself is incompatible with the pipeline waiting on the other side: a media manager that refuses a non-standard container, an editor whose software cannot read an unusual pixel format, or a broadcast compliance tool that flags an audio track with the wrong channel layout.

The friction is structural. Generative tools optimize for fast preview and small downloads. Advertising pipelines optimize for predictable decoding, consistent color, and traceable versions. Those two goals pull in opposite directions, which is why a clip that looks flawless on your laptop can arrive at an agency looking washed out, stuttering, or completely unreadable.

The fix is not exotic. It is a repeatable handoff process: agree on a spec, encode deliberately, verify before you send, and transfer through a channel that preserves the file bit for bit. This guide walks through that process step by step, with the settings and decision criteria that matter most in real production work.

Before You Encode: Have the Delivery Spec Conversation

The single most expensive mistake in a video handoff is encoding before you know what the receiver needs. A re-encode from a delivery master always costs quality, and sometimes it costs a day of rework.

Ask five questions before touching your export settings:

1. What is the final destination? A connected-TV placement, a paid social cutdown, a DOOH screen, and an internal pitch reel all have different technical expectations.
2. What is the delivery container and codec? Most agencies will name a specific pair, for example an MP4 container with an H.264 or H.265 video stream, or a QuickTime container with ProRes for editorial.
3. What resolution and frame rate? Confirm both the raster size and the exact frame rate, including whether it is integer or fractional.
4. What audio standard applies? Stereo or multichannel, what sample rate, and whether loudness normalization is required.
5. How should files be named and delivered? Naming conventions, folder structure, and the transfer method are part of the spec, not an afterthought.

Ask for a written spec, not a verbal one

Verbal instructions decay quickly. Request the spec in writing, ideally as a one-page document or a link to the agency's delivery portal. If they have no formal spec, send your own proposed spec and ask for confirmation. A written spec turns a subjective argument about quality into a binary check.

Clarify whether the agency will re-encode

Some agencies ingest your master and transcode internally. Others expect you to deliver platform-ready files. If they transcode, give them the highest-quality master you can reasonably transfer, because their encoder will do the final compression. If they expect finished deliverables, you need to match platform targets precisely, including maximum file size and bitrate ceilings.

Containers, Codecs, and Frame Rates That Survive Real Pipelines

Once you know the target, choose the combination that decodes reliably everywhere.

Containers

• MP4 / MOV are the safe defaults. MP4 is universally accepted for distribution; MOV with ProRes or an editing codec is the standard for editorial handoff.
• MXF appears in broadcast and some CTV workflows. Use it only when explicitly requested, because not every small studio can open it.
• WebM, MKV, and raw image sequences are rarely accepted as delivery formats. They are useful internally, but they create friction at the agency boundary.

Video codecs

• H.264 (AVC) is the most compatible distribution codec. It plays everywhere and is the safest choice when you do not know the recipient's toolchain.
• H.265 (HEVC) offers better quality per bit but carries licensing and decoding quirks on older systems. Confirm support before choosing it.
• ProRes 422 HQ or 4444 is the standard for editorial and finishing handoffs. Files are large but decode cheaply and preserve gradients well.
• AV1 and VP9 are excellent for streaming but are still inconsistent as an agency delivery format.

Frame rates

Match the source. If your AI tool generated at 24 fps, delivering at 30 fps introduces duplicated frames that look like judder in motion-heavy scenes. If the destination requires 29.97 or 25, convert with a proper frame-rate conversion method rather than a simple retime, and check any speed changes to the audio.

Also verify whether the destination needs interlaced or progressive footage. Modern digital placements almost always want progressive, but legacy broadcast slots still occasionally request interlaced delivery, and interlacing a progressive render badly is a common and visible error.

Color Space, Bit Depth, and Gamma: Keeping Renders Faithful

AI-generated footage often contains subtle gradients, volumetric light, and synthetic skin tones that punish sloppy color handling. Two settings cause most of the damage.

Color primaries and matrix

Deliver Rec.709 for standard dynamic range advertising. If your tool outputs Rec.2020 or a wide-gamut intermediate, convert deliberately rather than letting the player guess. Untagged files are the worst case: the receiving system applies whatever default it prefers, and your carefully graded look shifts.

Bit depth and chroma subsampling

8-bit delivery is acceptable for most distribution, but 10-bit is strongly preferred for anything that will be graded or keyed downstream. Synthetic imagery with fine gradients bands visibly in 8-bit. For chroma subsampling, 4:2:0 is standard for distribution codecs, while 4:2:2 is a better choice for editorial handoffs because it survives keying and color work far better.

Gamma and full-range versus limited-range

This is the quietest, most destructive mismatch in the entire handoff. Full-range (0-255) and limited-range (16-235) interpretations of the same data produce either crushed blacks or washed-out contrast. Decide once, tag the file correctly, and verify on a reference monitor or with a scope. If the agency says the footage looks flat or milky, range mismatch is the first thing to check.

Bitrate Strategy, GOP Length, and Entropy Coding

Bitrate decisions are where quality, file size, and transfer time collide. There is no universal best number, but there is a reliable method.

Constant versus variable bitrate

• CBR holds a steady data rate. It is predictable for streaming and for any pipeline with strict bandwidth ceilings, but it wastes data on simple scenes.
• VBR, ideally two-pass, allocates data where it is needed. It produces better quality at the same average size, which matters for AI footage with detailed textures and fast motion.
• Capped VBR gives you the quality benefit of VBR with a hard ceiling that satisfies platform maximums.

For agency delivery, capped VBR is usually the best compromise. Use CBR only when a spec explicitly requires it.

GOP length and keyframe placement

A short GOP (more frequent keyframes) improves seeking and makes editing easier at the cost of a larger file. A long GOP compresses better but is harder to scrub. For editorial handoffs, keyframes at one-second intervals are a friendly default. For pure distribution, two to four seconds is fine. Never let a keyframe land in the middle of your logo reveal or a hard cut, because some players display that frame during scrubbing.

Entropy coding

If your encoder offers CABAC and CAVLC, CABAC delivers better compression efficiency and is the default for high-quality H.264 output. CAVLC is occasionally required by older or constrained decoders. Unless a spec demands otherwise, leave entropy coding on the higher-efficiency setting and let the bitrate savings go toward visual quality.

Audio Tracks: Sample Rate, Channels, and Loudness

Audio problems are more likely to trigger a rejection than video problems, because they are easier to measure automatically.

• Sample rate: 48 kHz is the standard for video. If your source is 44.1 kHz, resample it rather than delivering a mismatched track.
• Channel layout: stereo for most digital placements, 5.1 only when requested. Never deliver a mono track labeled as stereo or a stereo track with an empty channel.
• Bitrate: 192 to 320 kbps for AAC is typical and transparent for advertising content.
• Loudness: target the platform's loudness standard, and confirm whether the agency wants a normalized master or a raw mix. Normalizing when they intended to mix downstream removes headroom they needed.

Separate stems are not optional for agencies

If there is any chance the agency will adapt the spot for another market, deliver dialogue, music, and effects as separate stems alongside the mixed track. Retrofitting stems after delivery is far more work than exporting them during the handoff.

Metadata, Naming, and Version Discipline

Metadata is the difference between a file the agency can find in six months and a file nobody can identify. Populate the basics: title, campaign, client, spot length, aspect ratio, language, and the person who approved the cut.

Establish a naming convention

A predictable pattern prevents version collisions. A workable convention:

Client_Campaign_SpotName_Duration_Version_AspectRatio_Language

Keep versions numeric and sequential. Avoid final, final2, and approved-final-really, because those labels carry no information and cause the wrong cut to be trafficked.

Include a delivery manifest

A short manifest listing every file, its duration, its codec, and its intended destination saves the agency's traffic team an hour of guesswork. Pair it with a checksum for each file so the receiver can verify nothing was corrupted in transit.

Choosing a Transfer Method Without Corrupting Anything

How you send files matters as much as how you encode them. Large video files are sensitive to interrupted connections, aggressive antivirus scanning, and cloud services that silently transcode uploads.

• Managed file transfer (MFT) platforms provide encryption in transit, audit trails, resumable transfers, and access controls. They are the right choice for high-value or confidential creative assets.
• Enterprise cloud storage with shared folders works well for ongoing relationships. Verify that the service does not compress or transcode video on upload, and always transfer the original file rather than a preview link.
• Consumer file-sharing links are fine for internal review but risky for final delivery because of expiry, compression, and unclear access logs.
• Physical drives remain practical for very large editorial packages, especially when bandwidth is limited. Label the drive, include a checksum file, and use a tracked courier.

Always send a checksum

Generate a checksum for each deliverable and include it with the manifest. It takes seconds and eliminates an entire category of blame when a file arrives corrupted.

Pre-Flight QA: A Delivery Checklist and Common Rejections

Run this check on every file before it leaves your machine:

1. Play the file start to finish in a player different from the editor you used.
2. Confirm duration to the frame, especially for strict spot lengths.
3. Verify the first and last frames are clean, with no flash frames or half-second black tails.
4. Check that the logo, legal text, and end card are legible at the delivered resolution.
5. Confirm audio peaks are within limits and loudness targets are met.
6. Inspect a scope for crushed blacks or clipped highlights introduced during export.
7. Validate the container and codec by opening the file in a third-party tool, not just your own encoder.

The most common rejection reasons

• Wrong or unlabeled color space, producing a visible look shift.
• Mismatched audio channel layout or an out-of-spec loudness measurement.
• A file that exceeds the platform's maximum size or bitrate ceiling.
• Aspect ratio errors from exporting a cropped composition inside a mismatched frame size.
• Duplicated frames from an incorrect frame-rate conversion.
• Missing stems or captions that the spec listed as deliverables.

FAQ

What is the safest single format to send an ad agency?

If you have no spec, an MP4 container with H.264 video, AAC audio at 48 kHz, Rec.709 color, and a capped variable bitrate is the most broadly compatible choice. If the agency is doing editorial work, send ProRes 422 HQ instead and let them handle final compression.

Should I send a master file or a compressed deliverable?

Send the highest-quality master when the agency will transcode internally. Send a platform-matched deliverable when the spec calls for finished assets. When in doubt, ask, and send both if the transfer size allows.

Why does my video look washed out after the agency receives it?

Almost always a color range or color space mismatch. Check whether the file is tagged as full range or limited range and whether the primaries are Rec.709. A quick scope comparison between your export and their import confirms it within minutes.

Can I just send a cloud share link?

For review, yes. For final delivery, prefer a managed transfer or a tracked shared folder, and confirm the service does not transcode uploads. Link-based sharing can also expire before the agency's traffic team gets to the file.

How do I handle multiple aspect ratios and cutdowns?

Deliver each aspect ratio as its own file with a clear suffix in the filename, and keep frame rate and audio settings identical across versions. Group them in a folder that mirrors the manifest so the receiving editor can map deliverables to placements without asking.

What should I do if the agency keeps asking for re-encodes?

The pattern usually points to a missing spec rather than a bad encode. Ask for their written delivery requirements, compare them against your export settings line by line, and create a reusable preset once the settings are agreed. After that, every handoff becomes a checklist rather than a negotiation.

Building a Repeatable Handoff Process

The difference between a smooth handoff and a frustrating one is rarely technical skill. It is process discipline. Agree on a spec in writing, choose conservative container and codec pairs, manage color and bit depth deliberately, keep audio within measurable standards, name and document everything, and verify before you transfer.

Once that process exists, it becomes a preset. You export consistently, you check the same list, and you stop losing hours to re-encodes and explanations. AI tools will keep changing how footage is generated, but the delivery layer changes slowly, and that stability is an advantage for anyone willing to build a proper handoff workflow.