To tell whether a delivery video is missing container-level metadata or metadata on an individual stream, compare each required field with the FORMAT section and every relevant STREAM section in an ffprobe report. A blank spot in one section does not establish that the whole file has no metadata: first identify the field’s required level and the stream it belongs to.
Inspect the required fields in order
- Start with the delivery specification, not the probe output. Write down each required tag, its expected level (
FORMATorSTREAM), and, for stream fields, the intended stream type or track. Requirements are project-specific; ffprobe does not define which tags your recipient requires. - Open the actual delivery file with ffprobe and request both sections and their tags:
ffprobe -v error -show_format -show_streams -of json delivery.mp4. The official ffprobe documentation describesFORMATas container information and prints recognized container and stream tags in their corresponding sections. - For each required field, inspect its expected location. Check
format.tagsfor aFORMATrequirement; check each applicablestreams[].tagsentry for aSTREAMrequirement. Record the stream index and type so a value on one track is not mistaken for a value on another. - Classify the result as present with a value, present but empty, not shown in the expected section, found only at another level, or target stream absent. These are different findings. A tag found under
FORMATdoes not prove that a required stream tag exists, and vice versa.
If you only need tag output, ffprobe also supports selecting tag entries with -show_entries stream_tags:format_tags. Use the full report for the first pass so you can identify which streams exist; the entry-selection documentation explains that section entries can be limited to tags.
Acceptance worksheet: a hypothetical delivery
The observations below are invented examples, not a report from a tested file. The required levels come from a hypothetical project specification; they are not universal metadata rules.
| Required field | Expected level | Hypothetical observation | Affected stream | Decision to record |
|---|---|---|---|---|
title | FORMAT | format.tags.title is Spring Cut | None | Present at required level |
language | STREAM | Audio stream 1 has eng; audio stream 2 has no language tag | Audio stream 2 | Missing on one required track; query the owner of that track |
comment | FORMAT | Key appears with an empty value | None | Empty, not a confirmed usable value; clarify the contract |
language | STREAM | No audio stream is listed | Intended audio track | Stream absent; this is not merely a missing tag |
Use separate rows when a field applies to multiple tracks. That makes the worksheet an audit of required fields and affected streams, rather than a blanket claim that the file “has no metadata.”
Limits and what to do next
A field not shown under its expected section means ffprobe did not report it there; it does not by itself prove that every recipient needs it, or that the value is unavailable by every other method. Decide whether to fix it by checking the delivery contract or asking the recipient, then report the precise level, field, and stream. Do not add a value at another level and mark the requirement satisfied unless the specification allows that.
If the report is unclear, rerun the probe with the full FORMAT and STREAM sections and compare the output against the written field list. If the intended stream itself is absent, raise that as a separate stream-presence issue. ffprobe reports recognized metadata; the documentation does not promise that every format exposes every tag identically or establish a universal rule for empty values. A probe result is evidence for the report, not a substitute for the project’s acceptance criteria.
Common questions
If a tag exists in FORMAT, does that satisfy a STREAM requirement? Not unless the delivery specification explicitly treats those levels as interchangeable. Record where the observed value appears.
Is an empty tag the same as a missing tag? No. Record an empty value separately from a tag that is not shown, then ask whether the contract accepts it.
What if the expected stream is not listed? Record the stream as absent and identify the intended track. Do not classify the issue as only missing stream metadata.
Sources and next step
This guide interprets public documentation and uses explicitly hypothetical acceptance examples, not application tests. Controls and availability can change; verify the cited manual against your installed version.
For work created in Imagild, carry the input requirements and acceptance checklist into the film workspace. The external software controls discussed above belong to their respective products.