Camera clip naming conventions

Why the file name is not yours to invent

Every camera writes clip files the same structural way: a fixed prefix, an incrementing counter, and sometimes a fixed suffix. The prefix and suffix almost never change. The counter is the only part that moves, and it is the part that has to line up with what you write on the slate and in the shot log, or the editor spends day one of the cut just figuring out which file is which.

Some of that suffix is not even predictable in advance. RED and ARRI both append a wildcard, a date-and-camera-ID stamp the camera generates at record time, which you cannot know until the card comes off the camera. Blackmagic does the same. When you are naming a shot in a log ahead of time, you match on the part you control, the running number, and let the unpredictable stamp travel through untouched.

Do not rename the native files

It is tempting to batch-rename a card straight to Scene24_TakeB3.MP4 the moment it lands on a drive, so the folder reads like the script. Resist it, especially on RAW formats. RED, ARRI, and Blackmagic RAW files travel with sidecar metadata, lens data, color decisions, look files, that is keyed to the original file name. Rename the picture file without renaming its sidecar in lockstep and you can silently detach the metadata from the clip it belongs to.

Even on formats with no sidecar to break, renaming still fights the tools you will use next. Premiere Pro's own batch rename in the Project panel applies one name to every selected clip at once, which is exactly backwards for a card full of individually different takes; you end up undoing the batch rename by hand, clip by clip, which is slower than not renaming at all.

The fix is not to touch the file name. It is to keep a shot log, a spreadsheet or an app, that maps the camera's own file name to the scene, shot, and take it belongs to. The camera's numbering stays exactly what the camera wrote; your log is where the human-readable version lives.

The reel letter: bump it when the card changes

On cameras that bake a reel number into the prefix, Canon Cinema's A001C001, RED's A001_C001, ARRI's A001C001, that leading A001 is the reel or magazine, not the clip. It does not increment on its own. When you swap to a fresh card, you bump it by hand: A001 becomes A002, and the clip counter usually resets to C001 underneath it. Forget to bump it and two different cards both claim to be reel A001, which is a much harder mixup to untangle in post than it looks like on set, because both cards' clip numbers can genuinely overlap too.

The collision nobody warns you about

Here is the one that actually costs a day in the edit and almost never makes it into a naming-convention guide: most cameras restart their clip counter every shoot day, not just every card. Day 1 starts at C0001. Day 5, on a fresh card with the same camera and the same settings, also starts at C0001. Two completely different physical files, on two different days, with the byte-identical name.

On its own that is harmless, the files sit in different day folders. It stops being harmless the moment an NLE's automatic relink feature is loose about what counts as a match. Point “relink others automatically” at a filename match with nothing else pinned down, and it will happily bind day 5's C0001.MP4 to day 1's take, silently, with no error, because as far as the match rule is concerned they are the same file.

Production sound has its own numbering

A separate sound recorder, a Zoom, a Sound Devices unit, is its own device with its own counter and its own file-naming pattern, typically a prefix like SND_ followed by a zero-padded number: SND_0001.WAV. It does not share a namespace with picture, and it should not be renamed to mirror the scene or take either, for the identical metadata reason as RAW picture files. Keep the recorder's native name, and let the shot log carry the mapping from SND_0041 to “scene 24B, take 3” instead of baking it into the file itself.