Naming conventions that survive every pipeline

The filename is the only metadata field every application on earth can read. Premiere reads it, Resolve reads it, the Finder reads it, a render farm reads it, an FTP window at 2 a.m. reads it. Databases are richer and sidecars carry more, but the name is the lowest common denominator, which is exactly why it deserves a scheme instead of a shrug.

A good scheme has one job: a stranger, in a different tool, on a different operating system, five years from now, can sort the folder and know what each file is without opening it. Everything below serves that stranger.

What breaks a name

Four things break filenames in the wild, and all four are avoidable.

Spaces. Fine in the Finder, hostile everywhere else: shell scripts, URLs, watch folders, and half the command-line tools your pipeline secretly depends on. Use underscores.

Length. Filesystems commonly cap a filename around 255 bytes, and Windows paths on network shares hit limits far earlier than you expect once folders nest. A name that needs a whole sentence is metadata that belongs in a field, not a filename. Stay under about sixty characters.

Emoji and accents. Different systems store accented characters as different byte sequences for the same visible name, and tools disagree about which sequence they wrote. The name looks right and matches nothing. Stick to a-z, 0-9, underscore, hyphen.

Case. The Mac's default filesystem treats CLIP_A.mov and clip_a.mov as the same file; most Linux-based NAS boxes treat them as two. A convention that leans on capitalization will eventually collide on one machine or silently duplicate on another. Pick lowercase and never think about it again.

That list is tool-agnostic. It applies whether you rename by hand, by script, or not at all.

Date first, then who, then what

Start every name with the date, digits only, biggest unit first: 250914, or 20250914 if you prefer. This single habit makes every folder self-sorting in every file browser ever written, no sort menu required, and it stops shoots from interleaving alphabetically by client name, which is how a delivery folder becomes a scavenger hunt.

After the date comes the who-and-what, in the order someone would search: subject or team, action, people, then the camera's original name as the final segment. Something like 250914_72_td_johnson_A001C012.MOV tells a stranger the date, the jersey, the play, the player, and exactly which card the frame came from. Keep the original camera name always. It is the thread back to the source card and its manifests, and throwing it away buys you nothing.

Names should come from decisions, not typing

Typing names by hand invents variants. Around clip 300 you will type "touchdwn," and that clip will hide from every search you run for the rest of the project. The durable version is a template over metadata you already confirmed: log the fields once, then compose the name from them, mechanically, the same way every time.

ClipLogger does this with token templates: a date token, a token per palette field, sequence counters, the original name at the end. Only confirmed values ever reach a filename; a pending AI suggestion cannot name a file, which is the correct level of paranoia. It also runs in reverse: Parse Names to Metadata reads an existing convention off old filenames and writes the recovered values back as real fields, which is the rescue path for the 2019 drive that was named by scheme but never logged.

Rename copies, or rename in place with an exit

There are two honest ways to apply a scheme, and the difference is what happens to originals.

Rename-on-copy applies the template while the card offloads: the copies get the scheme, the card originals stay untouched, and verification hashes content, so renaming never weakens the copy check. This is the right default for new footage, because nothing is at risk and the scheme is in place from the first minute the files exist.

In-place renaming is for footage already on disk, and it needs three safety features before you trust it with a thousand files: a live preview of every before and after, collision detection up front rather than halfway through the batch, and an undo that restores the entire batch in one click. ClipLogger's Rename bench does all three, and it moves every sidecar with its file so the metadata follows the new name. Even a rename done outside the app reconnects afterward, because clips are identified by a content hash rather than by name. That last property is the quiet requirement: a convention only survives if renaming is safe enough that people actually do it.

A name that sorts by date, says who and what in a stranger's vocabulary, and is composed from confirmed metadata will outlive every tool in your pipeline.