AVIF container metadata from one still

AVIF container metadata from one still?

A 64 by 64 gray AVIF written on this machine with ffmpeg and libaom-av1 is 309 bytes, and the site video inspector reports major brand avif with compatible brands avif, mif1, miaf, and MA1B, plus top-level boxes ftyp, meta, and mdat.

Last updated 2026-10-21

Last checked 2026-10-22

What was written

The command used ffmpeg’s lavfi color source, 64 by 64 gray, one frame, codec libaom-av1, still-picture 1. The file was 309 bytes. Top-level boxes were ftyp, meta, and mdat. The inspector fields were Major brand avif and Compatible brands avif, mif1, miaf, MA1B.

A raw walk of every four bytes inside ftyp also sees the minor-version field. That field is not a brand, and it is not listed above. The compatible-brand line is the inspector’s list.

What this does not establish

It does not say where an Exif item lives inside every AVIF, and it does not say a social app will keep or drop these boxes. The sample has no camera maker and no GPS tag because none was written.

Read a real still in the video metadata viewer only if you accept that the walker is the MP4 box reader. Compare two copies on the verify page with the same limit.

Sources

The byte counts, brands, and boxes are from the ffmpeg file written on this machine on 2026-10-21. They are not a quote from the AVIF specification.

Last checked 2026-10-22.

Questions

Is this a camera AVIF?

No. ffmpeg wrote a one-frame gray still with libaom-av1 and still-picture mode. It is a container sample, not a phone original.

Does the verify tool have a separate AVIF reader?

No. The file starts with ftyp, so the video inspector classifies the format as mp4 and then prints the major brand avif. A clean verdict on that path is only about the boxes and fields that walker reads.

AVIF container metadata from one still