Conform is the most frustrating step in modern post-production for a reason that is almost never the conform itself. It is metadata. Specifically: the asset identifiers that should have moved cleanly from camera to NLE to grade to master, and did not, because somewhere in the chain a tool stripped them, a human renamed a file, or a sidecar XMP did not get copied alongside its parent.
We have stopped pretending this is the colorist's problem to solve at conform time. It is an asset-management discipline that starts on day one of a project, lives in a single source-of-truth schema, and saves a meaningful share of finishing time when it is honored. Most projects do not honor it. Most studios do not even have the schema written down.
What the standards actually say
XMP is the Adobe-introduced metadata framework standardized as ISO 16684-1. It can embed inside a media file or live alongside it as a sidecar — a small .xmp file with the same base name. IPTC Core and IPTC Extension are the structured field schemas the photo and video industries have agreed to. Camera RAW formats almost always need the sidecar because their containers do not support embedded metadata. Anyone who has lost a key after a re-ingest knows what happens when the sidecar gets left behind.
EDLs and ALEs are the older, narrower formats — the ones that move cuts and clip lists between Avid, Resolve, and Premiere. They carry a different slice of metadata. They were not designed for the modern multi-tool, multi-cloud world. They still do most of the work.
Why a unique ID matters more than a clean filename
The IPTC specification includes a unique identifier field whose purpose is to let downstream tools recognize a file as the same file even if its filename changes. This is the field nobody trains junior assistants to respect. It is also the field that decides whether the colorist's grade snaps back onto a re-conformed timeline in two minutes or two days.
Filenames lie. They get changed by every tool that touches them. They get prefixed with version numbers, suffixed with delivery codes, lowercased by macOS, capitalized by Windows. A unique ID survives all of that. It is the only honest pointer.
“The conform is not where you fix metadata. It is where you find out whether you fixed it on day one.”
What changed in 2025
The IPTC Photo Metadata Working Group released version 2025.1 of the standard, and it added formal fields for AI-generated content. Three of them are now part of the schema: AI Prompt Information, AI System Used, and AI Prompt Writer Name. This is not optional infrastructure for a studio that uses generative B-roll. It is what platforms, broadcasters, and increasingly clients are going to ask for, and the studios that have not built provenance tracking into their pipelines are going to be inventing it under deadline pressure.
The same fields apply whether the AI work was produced in Sora, Runway, Veo, Pika, or anything that follows them. They give a downstream auditor a way to ask: which frames in this final master were generated, by what tool, with what prompt, by which person. There is a real chance that within twenty-four months these answers become a delivery requirement on every major OTT.
What a working pipeline looks like
- Asset ingest writes a unique ID per clip into both the embedded metadata and a sidecar XMP — never one without the other
- Every tool in the chain reads and writes the unique ID rather than relying on filename
- AI-generated material gets the IPTC 2025.1 AI provenance fields populated at the moment of generation, not retroactively
- Sidecars travel with their parent file in every backup, every transfer, every re-ingest — verified by a checksum manifest
- Conform reads from the unique-ID column, not the filename column. Always.
None of this is glamorous. None of it shows up in a reel. It is the difference between a finishing pass that lands on Friday and one that slips to Tuesday. It is the difference between a colorist who does creative work and a colorist who does forensic work. It is the difference, ultimately, between a studio that can hold its delivery dates and one that cannot.
The edit suite you actually need is not in the rack. It is in the schema.
