A product photo file name needs three parts: the product's identifier, exactly as your business already writes it, a view code that says which shot it is and one separator you never use for anything else. KN-2041-OAT_1.tif is the whole pattern. The part that matters most isn't the format, though; it's timing. The identifier has to be in the file name before the first frame is shot, because every step after capture depends on it.
This guide walks through the system, how to get names in at capture, how folders fit around it and how channel-specific names like Amazon's are made from it. The examples use made-up products from a fictional fall knitwear shoot.
Why the name has to be right before the first frame
Here's the rule the whole system rests on:
If the product's identifier isn't in the file name before the first frame is shot, everything downstream is reconciliation work.
Think about what happens after capture. Selects get made. Files go out for retouching and come back. Versions get exported for several channels. Someone uploads them. At every one of those steps, a person or a script has to know which product an image shows.
If the file is called IMG_4471.CR3, the only way to know is for someone to look at it and match it by eye against a list. Do that for a few hundred products a day and mistakes will happen: the navy shirt's photo ends up on the black shirt's listing, and nobody notices until a customer does.
If the file carries the product identifier from the moment it's captured, that matching step doesn't exist. Every later step, by hand or automated, just reads the name. That's why it's best treated as a contract: everyone and everything in the workflow agrees the name is the truth, and nobody changes it on a whim.
The three-part file name
KN-2041-OAT_1.tif
\_________/ |
product view
identifier1. The product identifier. This part is non-negotiable. If your business already has an identifier for each product, such as a SKU, a style-and-color code or a barcode number, that exact identifier goes in the name, character for character. Don't abbreviate it, and don't tidy it up. KN-2041-OAT stays KN-2041-OAT, not KN2041oat or 2041-oatmeal.
2. A view code. Which shot of the product this is. Something as simple as _1 for front and _2 for back works. Channel codes, like Amazon's MAIN and PT01, are applied later, when you export for that channel, not at capture.
3. One reserved separator. In the example, the underscore only ever separates the identifier from the view. Hyphens can appear inside the identifier; the underscore never does. That single rule is what lets a script split any file name back into its parts reliably: everything before the last underscore is the product.
Where your convention leaves room, add things that make files easier to find later, such as a color, a season or a shoot date. Never at the expense of the identifier.
Keep the characters boring
Letters, numbers, hyphens and one underscore. That's the full character set.
| Use | Avoid |
|---|---|
| Letters A–Z, a–z | Spaces |
| Numbers 0–9 | Slashes ( / \ ) |
| Hyphens inside the identifier | Apostrophes and quotes |
| One underscore before the view code | Accented characters (é, ñ) |
| Extra periods before the extension |
Different systems fail on different characters, and Amazon's bulk upload rejects file names with spaces or extra characters outright (checked September 2026). The boring version works everywhere.
[Image to add: A file browser showing a clean set of names (KN-2041-OAT_1.tif, KN-2041-OAT_2.tif, KN-2041-CHAR_1.tif) next to a messy set (IMG_4471.CR3, oat sweater FINAL v2.tif, KN2041 oat (1).jpg)]
Folders that match the names
File names and folder names should carry the same identifier. Every shoot gets its own folder, named with the date first, then a short name anyone on the crew would recognize. Inside it, one subfolder per product:
20261006_FALL-KNITS/
KN-2041-OAT/
(raw captures, selects, and later the finished files)
KN-2041-CHAR/
KN-2042-OAT/
...The date goes first as YYYYMMDD, so shoots sort in the order they happened without anyone thinking about it. The product subfolders use the same identifier as the files inside them. Raws, selects and finished retouched files all live in the same product folder, so six months later anyone can open one folder and find every version of that product.
This is also what makes automation possible. When the folder name and the file name both carry the identifier, a script can file thousands of images correctly in seconds.
Getting the name in at capture
There are three ways to get the identifier into the name before the first frame. They're listed from most to least automatic.
Scan it. Put a barcode on each product's tag, or on a card that travels with it, and scan it before shooting. The capture software reads the code and names every following frame with it until the next scan. No typing means no typos. Check what your software supports before printing labels: as of September 2026, Capture One offers barcode naming only in its Enterprise tier and reads standard one-dimensional barcodes, not QR codes.
Type it once, at the top. Most capture software builds file names from tokens: a custom name you type, a counter, the date. Set the custom name to the product identifier before each product, and let the software add the counter or view code. One field to update per product, and someone on set who watches for it.
Rename at selects, before anything leaves. If neither option is possible, the absolute latest point to rename is when selects are made, before a single file goes to retouching or anywhere else. Once every product has exactly one select per view, rename the selects to identifier plus view (_1 front, _2 back). When both sides of a handoff use the same file names, any question about an image ("KN-2041-OAT_2 has a crease") can be tracked in seconds.
Test your naming setup on a few frames before the first real product, and confirm the names match your written convention exactly.
See the system on paper. The free sample of The Product Photography Machine includes the Introduction, Chapter 1 and the File naming worksheet, which walks you through writing your own convention with worked examples for your product types. Get it at productphotomachine.com/free-sample.
Why fixing it later always loses
Matching images to products after the fact means someone looks at every image and compares it with a list. It's slow, it doesn't scale, and it's exactly the kind of task where tired people make quiet mistakes. Similar products, like the same sweater in two close colors, are where it goes wrong, and they're also where it's hardest to spot.
The stakes rise further when every unit is its own product: vintage, resale, handmade, anything with individual wear or finish. There, a mix-up means the customer receives something that doesn't match the photo they bought from. If you sell that way:
- Use a unit-level identifier, usually an inventory number assigned when the item is received, not just the style code.
- Name at capture, always. Renaming from memory doesn't work when items look nearly identical.
- Shoot the tag or label in the first frame of each unit, as a visual record tying the images to the physical item.
What a good name makes possible
Once the identifier is reliably in every file name, the rule-based work after capture can be handed to software.
Filing retouched files. Retouched images often come back as one flat folder. A small script can take everything before the last underscore as the product identifier (KN-2041-OAT_1.tif becomes KN-2041-OAT), find the matching product subfolder in 20261006_FALL-KNITS, and copy the file into it. If a file has no matching folder, the script lists it as unmatched instead of guessing. That list doubles as a free check: it catches a misnamed file or a product that was never shot.
Channel versions. Each channel's file name is made from the studio name at export. For Amazon bulk uploads, that means the product's Amazon identifier plus a variant code, such as B000123456.MAIN.jpg and B000123456.PT01.jpg, with periods as separators. Your studio convention stays the same; the export step translates it.
Automated checks. A script can compare every incoming file name against the day's shot list and flag anything that doesn't match, before it reaches a listing.
Rolling it out: a naming checklist
- Use the product identifier your business already has, character for character
- Pick a view code scheme (
_1front,_2back, and so on) and list every view - Reserve one separator (the underscore) for identifier-to-view only
- Limit characters to letters, numbers, hyphens and that one underscore
- Name shoot folders YYYYMMDD_SHORT-NAME, with one subfolder per product identifier
- Set up capture naming (scan, type once, or at minimum rename at selects)
- Test on a few frames and compare against the written convention
- Make channel names (like identifier.MAIN.jpg) at export, never at capture
- Write the convention down and share it with everyone who touches files
That last item is the one most often skipped. Write the convention down even if it seems obvious. The day a new person joins the crew is the day an unwritten convention quietly changes.
At every scale
Solo. One page, following the three-part pattern. Type the identifier into your capture software's naming field before each product. Never let a file leave your computer with the camera's name on it.
Studio. One person on set owns naming: checks the identifier before each product and watches every file name as frames land. Consider barcode labels if your software supports them. Rename selects before any handoff.
Production. Names come from your product data, not from anyone's typing: scanned barcodes or a production system that pushes the identifier into the capture software. Scripts check every incoming name against the shot list.
[Image to add: Flow diagram from product data (identifier) to capture software to file name KN-2041-OAT_1.tif to product folder to channel exports (amazon, google, ebay, etsy, shopify)]
Start with the free sample. The Introduction, Chapter 1 and the File naming worksheet, free at productphotomachine.com/free-sample.
The full Book + Template Pack ($29.99) adds all 14 chapters plus the shot list template, QC checklist and the script that files retouched images back into product folders.
