Dogu at the mixing console during an audio session
Video post-production

Delivery and export

An agreed delivery specification, consistent file names and an organised archive.

Built for
exports that vary by editor, files named without a system, bitrates set by default and renders that soften the grade.
Video post-production
The short version

What you get. Files prepared for the agreed destinations and organised for your team, with the retention window stated.

Is this for you? For work that needs reliable exports, clear versions and a delivery location everyone involved can use. Long-term storage sits with you; we keep our copies for a year.

What leaves your plate. Export specifications, version checks, file names and delivery to the agreed storage location.

Start with the Free Audit.

Why the export settings are written down per partner

Each partner has a written delivery specification

The specification records resolution, frame rate, codecs, bitrate settings, audio and metadata handling. It has a date and is checked against the intended platform and the brand’s needs when either changes. Shared presets support the same standard across editors.

The bitrates differ, and that is the argument

One partner's ceiling is sixty megabits per second. Another's is sixty-five. A third exports the same resolution somewhere between thirty-five and forty-five. Those are decisions about what each platform does to a file and what each brand's footage needs, taken against the platform's live guidance and revisited when it changes rather than set once and forgotten. Using the highest number everywhere is the easy answer, and it would cost the third partner render hours for nothing.

Maximum depth and maximum render quality stay on, for different reasons

Maximum depth concerns processing bit depth; maximum render quality concerns scaling. We test the settings for the footage, output and available hardware, checking gradients and resized detail in the exported file. The appropriate choice depends on the render path.

File names are built for whoever goes looking

Two partners sort by subject and format, so their files read as the name of the piece followed by the version. Another sorts by date and product code, so its files open with the date. Identical craft, opposite convention, and both are correct, because those two teams go hunting for a file in completely different ways.

The same craft, three different sets of numbers

Resolution, all three4K, 3840 × 2160
Frame rate25 fps
Video codecH.264, VBR, two pass
Lesson channeltarget about 45 Mbps, ceiling about 60
Recipe channel, onetarget 45 Mbps, ceiling 65
Recipe channel, twotarget 35 to 45 Mbps
AudioAAC, 48 kHz, stereo, 384 kbps
Master meterno clipping; limiter ceiling about 1 dB below the top, as insurance
Render settingsmaximum depth and maximum render quality on, metadata off
Vertical formats1080 × 1920 at 9:16; feed posts 1080 × 1350
Typical renderabout 1.5 hours per long-form export

What happens after the render

One shared platform, agreed at the start

Whichever one the partner already uses. Everything delivered goes to the same place every time, and that place is reachable by every one of us working on the brand and by nobody outside it. The point of agreeing it in week one is that your team never has to ask where something went.

A tracked list, with the states written on it

Every deliverable sits on a shared sheet carrying its state: in progress, waiting on raw footage, delivered, invoiced. It exists so the answer to where is that video is a filter rather than a message, and so a month of work can be looked at as a month and not as a folder.

Corrections are versioned clearly

When a passage changes, we render the corrected material and deliver an unambiguous current version. Superseded files are clearly marked. Each video’s footage, masters and working project are retained for one year after delivery; editable project-file handover is agreed separately.

At the bench

The work, demonstrated

Try a decision from the craft: drag, tap or toggle, then read the trade-off.

These are illustrative models; no partner’s results are shown.

More demonstrations at the bench →

Whose turn. One video, from footage to delivery, in six stages, each with a named owner. The schedule includes our work and your review windows.

  1. Footage lands. Our turn. The pipeline starts without anybody asking.
  2. First cut built. Our turn. Two internal rounds happen before you see anything.
  3. Waiting on your notes. Your turn. Your notes are due here. We agree the review window before the work begins.
  4. Notes actioned. Our turn. On the exact frame, and each one ticked off in the open.
  5. Waiting on your approval. Your turn. Your release decision is due here. A late decision can move the delivery date.
  6. Delivered. Our turn. To the written specification, named so your team can sort it.

Open project. Eight things a handover can hold. Finished exports, text-free masters, footage we shot and rendered graphics are included.

  • The finished file.
  • Editable timeline, if separately agreed. Confirm the application, version and dependencies before agreeing an editable handover.
  • Footage we shot, named and organised. Relinked footage is the difference between an afternoon and a fortnight.
  • Layered graphics files, if separately agreed. Rendered graphics can be repositioned; changing their wording needs new artwork or the separately agreed source files.
  • Music licence records and usage terms, in your folder. This is the one that matters at nine on a Sunday.
  • Colour notes and editable grade, where agreed. A finished master can be adjusted, but it does not preserve every source grading decision.
  • The subtitle file alongside whatever is burned in. A burned-in caption cannot be corrected or translated. The separate file can be both.
  • A written note on where everything is. Written for somebody who has never met us, because in a year that is who opens it.

A finished export can be enough for publishing.

Check your delivery against the written scope. The files needed to publish and the files needed to rebuild an edit are different.

Editable timelines, layered artwork and their dependencies must be scoped separately. Agree them at the start or request a later quote. Licence restrictions still apply.

Per destination. The same track mastered three ways, loud, matched and quiet, against example loudness targets of -14 and -16 LUFS. Check each destination's requirements, and the master's true peaks and dynamics as well as its loudness.

There is no correct bitrate. There is a correct bitrate for this brand, on this platform, written down where the next person will find it.

What changes for you

Clearly named files, checked against the agreed specification and delivered to the shared location, with a defined retention window.

Related: Multi-camera editing · Vertical video editing · Colour grading · Mastering for platform

Send recent videos. We will review the edits and reply with the changes we would prioritise.

A quick fit check

Request your Free Audit.

Three fields, and a written reading back.

A bare domain, a full URL, a channel link or an ad library link.
Received. We reply in writing, usually within three working days.
That did not send. Try once more, or write to us instead.

Your audit usually arrives within three working days. We use your details only to reply to your enquiry.

What you will get

✓

What is working, what could improve and whether we can help.

✓

Two or three priorities, with the reason for each.

✓

A recommended next step, even if that step is not us.

There is no obligation to continue. We only arrange a call if you ask for one.

The work, written up

The case studies keep their dates, sources and limits visible.

See the casework →