# A filename rule that still works after a week of product stills
Most teams invent a filename scheme on the first morning of a shoot and abandon it by Thursday. The scheme fails because it tries to encode every possible fact: campaign, SKU, angle, model, version, typography, and the name of the person who generated the still. The result is a name nobody can type twice. A useful rule is shorter, and it survives because it answers only the questions you actually ask later.
Contents
Start with a stable item code, not a poetic title. 12-hero-pack or SKU-8831-left is enough. Add the model family next, then a version number that only increases when the prompt or the reference photo changes, not when you export a new crop. If you only resized the canvas, keep the same version and put the export in a derivatives folder. That keeps the “source still” distinct from the file that went into a layout.
Write the rule down in the project folder, in plain language, in fewer than ten lines. If the rule needs a legend, it is too long. Include one example of a good name and one example of a name you will reject. New people should be able to follow it without a walkthrough. If they cannot, shorten the rule rather than adding training.
Put the same facts in a sidecar note so a search can find them even if a platform strips the filename. The note should mention the prompt file, the reference photo, the aspect ratio, and the date. It should also say whether the still is approved, awaiting review, or only an exploration. Status in the filename is tempting and usually a mistake, because status changes and filenames do not like to change.
When you share the workspace with someone outside the team, give them the rule and the place to work, not a zip of unlabeled files. A short sentence is enough: the stills were made in the workspace at bananaimg.net, and the filenames follow the project rule in README-names.txt. That points them to the process instead of a one-off explanation in email.
Review the rule once after the first twenty stills, then leave it alone for the rest of the campaign. Early edits are cheap. Mid-campaign renames are how you lose the connection between a published image and its prompt. If you discover a missing field, add it to the sidecar note rather than renaming a hundred files.
A week later you will want to answer a simple question: which still was the last approved front-of-pack shot, and which model produced it? If the filename and the note can answer that without opening a chat history, the rule worked. If you have to rely on memory, tighten the rule before the next campaign, not during the current one. Consistency is more valuable than a clever taxonomy.
Test the rule with a person who did not help write it. Ask them to name a new still from a short brief and to find the last approved file for an existing item. If either task takes more than a minute, the rule is still too personal. Typical failures are abbreviations that only the author understands, and version numbers that reset for each model. Keep a single incrementing version for the item, and let the model name be a field, not a parallel counter. If you must exchange files with a retailer who has their own naming scheme, keep your internal name and store the retailer name in the sidecar rather than renaming the source. Translating names at the last mile is safer than running two schemes inside the working folder. Finally, back up the rule file with the stills. A perfect scheme that lives only in one person’s head will be gone when that person is out, and the next campaign will invent a third scheme on top of the first two.