How to Name and Version Files on a Creative Team

Key Takeaways

• The test for any convention: can someone who joined yesterday sort the folder correctly without opening a file? If not, the names are decoration.
• Dates go in `YYYY-MM-DD` form, because that is the only format that sorts chronologically as text.
• Version numbers only increase. `final`, `final2`, `FINAL_real` is not a versioning system, it is a record of despair.
• Zero-pad version numbers (`v03`, not `v3`) or your tenth version sorts between the first and the second.
• Put the constant at the front and the variable at the back, so alphabetical sorting groups the way you actually browse.
• The convention is worth roughly nothing until it is written down somewhere a new freelancer will find it in their first hour.

The Stranger Test

Every naming argument resolves the same way if you apply one test.

Imagine someone joins the project tomorrow. They have the folder open and no context. Can they tell which file is the current one, which project it belongs to, and what stage it is at, without opening anything?

If yes, the convention works, regardless of how ugly it looks. If no, it does not work, regardless of how sensible it felt when you named things.

This test kills most of what people argue about. Whether you use hyphens or underscores does not matter. Whether the client name or the project name comes first barely matters. What matters is that the current file is identifiable at a glance and that sorting produces a useful order.

The stranger is usually you. Not a new hire, you in four months, opening a project you have completely forgotten because you have made eleven things since. The convention is not bureaucracy imposed by a producer. It is a message you are leaving for yourself at the exact moment you will be least equipped to reconstruct anything.

Dates: Only One Format Works

If a date goes in a filename, it goes in `YYYY-MM-DD`.

This is not a style preference. It is the only common date format that sorts correctly when treated as text, which is what every file browser does. `2026-08-10` sorts after `2026-07-31` automatically. `10-08-2026` and `Aug 10 2026` do not sort into any useful order at all, and by the thirtieth file you will notice.

Use a date when the file is a point-in-time artifact: a shoot day's footage, an export sent to a client, a meeting recording, a backup. Use a version number instead when the file is a document that evolves. Using both is fine and often correct on client deliverables, where you want to know both which version it is and when it went out.

Do not use relative words. `latest`, `current`, `new`, `updated` are true for about a day and misleading forever after. `new_logo` is one of the most reliably wrong filenames in existence.

Versions: Numbers That Only Increase

The `final` problem is universal and the fix is trivial.

Use `v` plus a zero-padded number. `v01`, `v02`, `v03`. Zero-padding matters because `v10` sorts before `v2` in every alphabetical listing, and you will hit version ten on any project worth doing.

The number never goes down and never gets an adjective. There is no `v03_final`. If v03 was approved, that fact lives in your project tracker, in the folder it was moved to, or in the email that approved it. It does not live in the filename, because approval is a state that can change and filenames should not.

Increment on send, not on save. Every time a file leaves your machine for someone else's eyes, it gets a new number. Internal saves do not. This gives you a version history that maps exactly onto the conversation history, which is what you actually need when someone says "in the version you sent Tuesday".

Two useful additions, if the project needs them. A short suffix for the variant (`_16x9`, `_9x16`, `_captions`) and a short suffix for the recipient when you cut client-specific versions. Keep them at the end so they never disturb the sort.

Order: Constant First, Variable Last

A filename sorts on its first character, so whatever you put first determines how the folder groups.

The general shape that works: `Project_Thing_Version_Variant`.

`AcmeLaunch_HeroFilm_v04_16x9.mp4` groups every Acme Launch file together, then every hero film file together, then orders the versions correctly, with variants beside each other. Someone browsing sees structure without reading.

Invert it and you get chaos. `16x9_v04_HeroFilm_AcmeLaunch.mp4` sorts by aspect ratio first, which is never how anyone browses.

If folders already carry a piece of information, do not repeat it in the filename, with one exception: files leave folders. Anything that will be emailed, uploaded or handed over should carry the project name in the filename even if the folder says it, because the folder will not travel with it. A client who receives `v04_final.mp4` has no idea what it is by next week.

Folders: Two Levels, Then Stop

Folder structures fail in the opposite direction to filenames. Filenames fail by being too vague; folders fail by being too deep.

Two levels below the project is enough for most creative work. Project, then stage or asset type, then files. Every level beyond that is a decision someone has to make correctly every time they save something, and they will not.

Name folders for stages people recognise, not for abstractions. `01_Brief`, `02_Footage`, `03_Edit`, `04_Delivery` is legible. `Assets/Working/Misc` is where files go to be lost.

Number the folders if they have an order. Zero-padded, same as versions. It puts them in workflow order rather than alphabetical order, which is the order people actually think in.

Have one obvious place for the current thing. A `_Current` or `04_Delivery` folder that contains exactly what a stranger should grab. The single most common failure on handover is not that files are missing, it is that nine plausible candidates exist and none is marked.

A Worked Example

Abstract rules are hard to apply, so here is a real folder in both states.

Before, which is what most project folders actually look like:

``` Acme stuff/ edit/ hero final.mp4 hero final v2.mp4 HERO_FINAL_USE_THIS.mp4 vertical.mp4 new music version.mp4 from client/ logo.png logo new.png notes.docx notes 2.docx misc/ thumbnail.psd Untitled 3.psd ```

Nothing here can be sorted correctly without opening it. There are three candidates for the current master and the tiebreaker is capital letters. The vertical cut has no version, so nobody knows which master it came from. Two logos differ by the word "new", which was true in April.

After, using the shape from this article:

``` AcmeLaunch/ 01_Brief/ AcmeLaunch_Brief_v02.pdf AcmeLaunch_ClientNotes_2026-06-14.docx AcmeLaunch_ClientNotes_2026-07-02.docx 02_Assets/ AcmeLaunch_Logo_Primary.png AcmeLaunch_Logo_Reversed.png 03_Edit/ AcmeLaunch_HeroFilm_v03_16x9.mp4 AcmeLaunch_HeroFilm_v04_16x9.mp4 AcmeLaunch_HeroFilm_v04_9x16.mp4 AcmeLaunch_Thumbnail_v02.psd 04_Delivery/ AcmeLaunch_HeroFilm_v04_16x9.mp4 AcmeLaunch_HeroFilm_v04_9x16.mp4 ```

Read what changed. The version numbers make the current file obvious without opening anything. The vertical cut now declares which master it came from, so a note about v04 applies to both. The two sets of client notes are dated and therefore ordered. "New" and "final" are gone, replaced by facts that stay true. The delivery folder contains exactly what a stranger should grab, and the same files exist in the edit folder without ambiguity because the names match.

Note what did not change. The folder depth is the same, two levels. Nothing was invented to make the structure look thorough, and no file was renamed to describe how anyone felt about it.

Write It Down, Or It Does Not Exist

This is the part that separates teams who have a convention from teams who have an opinion.

One page, five lines, somewhere a new person will hit it in their first hour. The filename shape with one real example, the date format, the version rule, the folder structure, and where the current version lives. That is the entire document.

Real examples beat rules. People pattern-match from an example far more reliably than they parse a rule. Show `AcmeLaunch_HeroFilm_v04_16x9.mp4` and almost nobody gets it wrong.

Say what happens when someone deviates, and keep it low-stakes: the file gets renamed, no drama. A convention enforced through irritation dies quickly. A convention where the producer quietly renames the occasional stray file survives for years.

Do not retro-fix the archive. Renaming eighteen months of old projects is a large job with almost no payoff, and it breaks any link that pointed at the old name. Apply the convention to new work and leave history alone.

What This Does Not Solve

A naming convention answers where a file is and which one is current. It cannot answer why the file is the way it is.

`AcmeLaunch_HeroFilm_v04_16x9.mp4` tells you nothing about why v04 dropped the second interview, that the client asked for it in round two against the original brief, or that v02 is the one everyone secretly preferred. That context lives in email threads, a call nobody recorded, and someone's memory, and it is the thing people actually ask about when they reopen a project.

Storyflow is our product and it is worth being plain about the fit here. It is not a file manager, it has no folder tree, no versioning of your media, and no place to store working files. Your assets belong in Dropbox, Google Drive, Frame.io or an NLE project, and this article's whole subject is outside what Storyflow does. It appears for one adjacent job: holding the brief, the references, the rejected directions and the decisions on one board so that the reasoning behind v04 is recoverable. Paid-only during early access, with the Free plan landing before the end of 2026, and anyone a paid member invites to a board joins free now.

The Bottom Line

This is a small discipline with a payoff that shows up entirely at the worst moments: handover, a rush delivery, a project reopened a year later.

Apply the stranger test. If someone who joined yesterday cannot sort the folder and identify the current file without opening anything, the convention is not working.

Dates as `YYYY-MM-DD`, versions as zero-padded numbers that only increase, no state words, constant first and variable last. That is the whole system.

Two folder levels, numbered when they have an order, with one obvious place for the current version.

Then write it down on one page with a real example, because a convention that lives in people's heads is a convention that lasts until the next freelancer.

And remember what it cannot do. A filename is a message to a stranger, and the stranger is usually you in four months. It can tell that person which file to open. It cannot tell them why the file is the way it is, and that is the question they will actually have.