Production management · 30 October 2026

Shot codes, versions and file names: a system that holds

A naming system holds when it keeps three counters apart: a shot code that never changes, a version number per shot that only goes up, and a review round that you agree with the client. File names are then built from those counters in a fixed order, without words like “final”. Most naming trouble in CGI, VFX and post comes from mixing the three, for example renumbering shots after an edit change or treating “v3” as both the third render and the third client round.

Why do naming systems break?

Because they are invented on day one by one person and then stretched by the edit, the team and the client.

The familiar failures all have the same root. A shot is inserted between 030 and 040, and someone renumbers everything after it, so last week’s notes now point at the wrong shot. A file is called final, then final_v2, then final_final. Two artists save the same version number from different machines. A client says “v3 looked better” and nobody knows whether they mean the third render of one shot or the third round they reviewed. None of this is carelessness. It happens because the system did not separate what a thing is from which attempt it is and when the client saw it.

How should shot codes work?

Number shots in tens, never renumber, and never reuse a code.

Numbering in tens (010, 020, 030) leaves room to insert shots later: a new shot between 020 and 030 becomes 025, and nothing else moves. This is an old convention because it works. A few rules make it hold:

  • A code belongs to a shot for life. If shot 040 moves to the end of the edit, it is still 040. Order in the edit and identity of the shot are different things.
  • Omitted shots keep their code. Mark them as omitted; do not hand the number to a new shot.
  • Add a sequence or film prefix when you need one. A long film or a campaign with several films can use a prefix such as SQ010 or a film code before the shot number. Decide this at the start, not halfway.
  • Use the same code everywhere: the shot list, the folder, the file name, the slate on the render, and every client note.

How should versions work?

One version count per shot (and per task, if departments work in parallel), padded, increasing, never reset.

A version is something you make: every export that leaves your own machine gets a new number. MASV’s naming guide from February 2026 recommends three-digit padding (v001, v002), because a long project can go past v99. Two more rules prevent most confusion:

  • Never reuse a number. If v006 was wrong, the fix is v007, not a new v006.
  • Never use “final”. PremiumBeat’s file naming guide made this point back in 2012, because clients come back for changes long after a file was called final. MASV’s guide makes the same point in a different way: it treats “final” as a point in the edit rather than something a version number can express. Use the version number for the file and keep the status somewhere else, because statuses change.

Put the version in the file name and in a burn-in or slate on the image itself. A screenshot in an email then still says what it is.

Why keep review rounds separate from versions?

Because a round is an agreement with the client, and a version is a file you made.

In one review round the client might see v007 of shot 030, v003 of shot 040 and v012 of shot 060. Between rounds, a shot can go through five internal versions that the client never sees. If you count rounds with version numbers, those internal versions either disappear from the record or eat up the client’s rounds.

CounterBelongs toWho moves itExample
Shot codeThe shot itselfThe producer, once030
VersionThe shot (and task)The artist, on every exportcomp v007
RoundThe client momentThe producer, when a round is agreed and openedRound 2

How many rounds a project includes, and what makes a round count, is covered in what counts as a revision round.

What does a full file name look like?

A fixed order of short elements, from general to specific, with no spaces or special characters.

For work in progress, a common order is project code, shot, task, version, and for image sequences the frame number. For deliverables, the elements change: the client cares about length, aspect ratio and language, not about the task. MASV’s guide suggests dates in the YYYYMMDD format so they sort and read the same in every country, and recommends leaving out spaces and characters such as slashes, colons and brackets.

ElementWork in progressDeliverable
Project codeRIVRIV
Shot or deliverable030master
Task or lengthcomp30s
Aspect ratio16x9
LanguageEN
Version or datev007v003 or 20261127
ExampleRIV_030_comp_v007.1001.exrRIV_master_30s_16x9_EN_v003.mov

RIV is an invented project code. Use a short code per project rather than the client’s full name: it keeps file names short and does not put a client name on every file that leaves the building. The deliverables list is a good place to fix the deliverable names before anyone exports.

Where should the system live?

On one page, shared on day one, and ideally in a tool that enforces part of it.

Write the convention down: the element order, the separator, the padding, the shot numbering rule and two examples. Give it to every freelancer on their first day, together with the rest of the setup described in running a job with a changing crew. A convention that lives only in the head of the person who invented it ends when they go on holiday.

Tools can take some of the discipline off people’s hands. In Kadrenta, made by the same team behind The Production Brief, shots in a breakdown are numbered in tens, and a shot keeps its number when others are added around it. Each shot keeps its own work-in-progress versions in separate chains for image, video, 3D and documents, so a new still does not push the latest video version aside. Send to review turns a shot version into a draft review round, numbered v1, v2 on the review item, so the version count on the shot and the round count with the client stay separate. It does not rename your files on disk, so the naming convention for files outside the tool is still yours to agree.

How do you introduce a system mid-project?

You usually don’t. Start it on the next project.

Renaming hundreds of files halfway through a job breaks links in scene files, edit projects and notes. Keep the current project as it is, write down the new convention, and start the next job with it from the first shot. If one rule is worth adopting immediately, make it “never renumber a shot”. It costs nothing and stops the most expensive kind of confusion today.

Frequently asked questions

Should a version number reset when a shot moves to the next department?

Not if the version lives in the same chain. Many studios keep one version count per shot and task, so comp v004 and lighting v004 are separate, but neither ever goes back to v001.

What do we do with a shot that is cut from the edit?

Mark it as omitted and keep its code. Reusing the number for a new shot makes old notes and file names point at the wrong thing.

Underscores or hyphens?

Either works, as long as everyone uses the same one. Many studios use underscores between elements and keep hyphens or nothing inside an element.

How long can a file name be?

Short enough to read in an editing panel without scrolling. If a name needs more than six or seven elements, some of them belong in the folder path or the metadata.

Sources