Compact camera on a tripod with its rear screen visible.

Capture metadata can make footage easier to understand and reuse. It may identify technical settings that explain why two clips look different or help an editor interpret an unfamiliar file. But a camera-generated field is not a complete account of the event pictured, and it should not be asked to prove more than it records.

The buying decision is which useful technical information should travel with the acquisition files, and how the recipient will access it. This is a practical handoff requirement, distinct from certifying a project's progress or resolving conflicting accounts of when work occurred.

Request information with a purpose

The EBU Acquisition Technical Metadata Set describes information collected from cameras and associated devices to support material exchange. It provides a framework for technical description, not a promise that every camera writes every field or that every editing application reads it.

Start with the recipient's needs. A colour workflow may require a clear identification of the recording colour space. A later matching exercise may benefit from lens and exposure information. A specialist application may need other acquisition fields. Ask which are actually available in the proposed setup and how they will be preserved.

Request a small sample package early. The receiving team should demonstrate that it can locate the relevant information rather than merely confirm that a metadata file exists. A field nobody can interpret is less useful than a short, clearly labelled camera report linked to the correct clips.

Separate description from verification

Ordinary technical metadata and signed provenance are not interchangeable. C2PA's explainer also makes a broader distinction: information about origin and history does not alone establish that the depicted content is factually true. Do not treat either kind of record as a substitute for the evidence needed to support a business claim.

For example, a recorded lens setting can help explain an image's appearance. It does not establish the dimensions of the building, whether an installation complies with a requirement or what occurred outside the frame. Those questions need their own appropriate evidence.

The useful approach is to retain descriptive context while being precise about its limits. That makes the footage more valuable without overstating its authority.

A hypothetical multi-camera handoff

A contractor receives material from two camera teams for a single communications programme. The files look different, and the editor needs to know which recording colour settings were used. One team supplies a concise clip-linked report and preserves the available camera metadata; the other supplies only renamed exports.

A pre-production sample exchange could have revealed this difference. The buyer therefore specifies the technical fields the editor needs and checks their availability before the main recording. It does not demand an elaborate metadata system that the project has no use for.

Define a readable handoff

List the required fields, where they will be supplied and who checks them. Preserve original filenames or provide an explicit mapping when names change. Distinguish recorded values from manually entered notes so the recipient understands their origin.

Keep a copy of the sample package that passed the handoff test. If software or camera settings change, confirm that the important information still arrives. Metadata earns its place in the brief when it answers a real technical question, not when its presence is mistaken for proof of everything the image appears to show.

Sources and scope

Discuss the capture brief

Contact Live Images to discuss this image requirement, the proposed scope and suitability for your production.

Prepared with AI assistance for Live Images. Planning guidance is general; suitability and production scope must be agreed for your project.