The file name is the only metadata that always travels

Assume everything you attach to a clip will be stripped, except the name. That is the design constraint, and once you accept it, naming stops being housekeeping and becomes the most durable metadata channel you own.

Watch what happens to a clip that leaves your suite. The transcode to a proxy or a delivery codec writes a brand-new file, and whatever lived inside the old container stays behind. The review portal your client uses hands them a download with the original filename and nothing else. The sidecar you carefully wrote survives exactly until someone drags the clip out of the folder without it, which is to say until the first client with a Dropbox. Bins, markers, and color labels live in project files that never leave the building. Through all of it, one field arrives intact on the far side, every time: the name.

The NLEs agree. Premiere shows the clip name in every bin, timeline, and relink dialog. Resolve matches metadata imports against clip names. EDLs and cut lists reference names. When a conform goes sideways at 11pm, the thing everyone is staring at is a list of names.

Design the name like a database record

Since the name is the one field guaranteed to travel, spend it deliberately. A good filename is a record: fields in a fixed order, one separator, a controlled vocabulary. Mine reads like this on a sports job: 72_TD_Johnson_A001C012.MOV. Jersey, play result, athlete, then the original camera name, in that order every single time. Anyone in the pipeline can decode it without asking, and so can a search box: type TD and every touchdown on the drive lines up, in Finder, in Premiere, in a client's file browser, with no software of mine anywhere in sight.

Two of those choices matter more than they look. The vocabulary must be fixed (TD, never Touchdown on Tuesdays), or the names stop being queryable. And the original camera name rides at the end, always, because that string is what relinks, cut lists, and "which card did this come from" conversations depend on.

Rules that survive Premiere, Resolve, and a client's Dropbox

The conventions below are tool-agnostic and learned the annoying way. Use letters, digits, underscores, and hyphens, nothing else: spaces break command lines and get rewritten as %20 by half the web, and slashes, colons, and asterisks are illegal somewhere you will eventually need to go. Never let two files differ only by capitalization, because macOS tolerates it and some servers do not. Write dates as YYMMDD so alphabetical order is chronological order. Keep names under about sixty characters, since delivery specs and burn-ins truncate. Never reuse a name for different content, ever: a name is an identity, and identities that lie cost conform time. Then write the convention on one page and hand it to everyone who touches a card.

Compose names from confirmed fields, not from memory

The failure mode of hand-naming is drift. By clip 300 of a long day the scheme is aspirational, and by next month it has dialects. The fix is to stop typing names and start generating them from metadata you already confirmed. In ClipLogger the project's palette carries a filename template, something like {f:team}_{action}_{players}_{original}, and the Rename bench builds every name from confirmed fields only: an unreviewed AI suggestion can never reach a filename. You get a live before-and-after preview per file, collision detection up front, and one-click undo for the whole batch, and rename-on-copy applies the same scheme during offload while leaving the card originals untouched. Sidecars move with the files in the same operation, and if a file gets renamed outside the app later, a content fingerprint reconnects it to its metadata anyway.

Generated names close the loop in the other direction too. The same template can be read backwards, parsing existing filenames into structured fields, which is the recovery path for the drives you named by convention years before you logged anything. The discipline you spent on old filenames comes back as metadata.

The name is the floor, not the ceiling

To be clear about the argument: the richer channels are worth writing. Sidecars, XMP, a CSV for Resolve, markers that ride into the NLE, all of it, and a pipeline you control should preserve them. The name is the only channel that survives the pipelines you do not control. Build the full record in the rich channels, then compose the name from the three or four confirmed fields the next stranger will need, and every hop your footage takes, however careless, carries at least that much of the truth along with it.

Everything else about a clip is an attachment that can be lost in transit, so put the metadata that matters most in the one field that cannot be.