A photography file named IMG_4872.jpg tells you nothing. It does not tell you which SKU it depicts, which angle it represents, which colorway it shows, or which season it belongs to. Multiply that by 200 SKUs and five angles each, and you have 1,000 files named in a way that guarantees at least a full day of manual renaming before a single image goes live.
File naming is not glamorous. It rarely comes up in conversations about photography quality or turnaround speed. But it is one of the most reliable places where operational time gets lost, and it is entirely controllable. A naming convention agreed on with your studio before the first shoot, built into your brief, and followed consistently, eliminates most of that waste.
This article covers why file naming matters for footwear eCommerce operations, what a practical convention looks like, how to handle multi-marketplace delivery, and how to build the discipline into your studio relationship rather than leaving it as a recurring afterthought.
Why File Naming Causes More Problems Than Teams Expect
The problem is not just the renaming time, though that is real. The deeper problem is errors. When files are renamed manually under deadline pressure, things go wrong. The wrong colorway gets associated with the wrong SKU. The medial view gets labeled as the hero. A file overwrites a previous version because the names are too similar and no one noticed.
Those errors do not always surface immediately. Sometimes a buyer purchases a shoe based on a hero image that is actually showing the lateral side of a different colorway. Sometimes a marketplace rejects a listing because the primary image has a non-compliant filename. Sometimes a team spends two hours in a QA cycle trying to figure out why certain images do not match their product records, because the naming broke at the studio level and was not caught until upload.
"A naming convention is not a bureaucratic formality. It is the thread that connects a physical shoe sample to a published product listing without any human error in between."
The cost of fixing naming errors is almost always higher than the cost of preventing them. Prevention requires a five-minute conversation with your studio at the start of a relationship. Remediation requires hours of file archaeology every season.
The Core Elements of a Useful File Name
A well-structured file name for footwear photography should contain enough information to identify the image unambiguously without opening it. That means it needs to capture at minimum:
- SKU or style number: The internal identifier that connects the image to your product catalog. This is the non-negotiable anchor of every file name.
- Colorway code: Footwear often comes in multiple colors. Each colorway is a distinct product with distinct images. The file name must distinguish between them. Using color names like "navy" or "tan" works but can create ambiguity if your internal codes are more specific. Using your internal colorway code is cleaner.
- Angle identifier: A consistent, abbreviated label for each view: HER for hero, MED for medial, LAT for lateral, HEL for heel, SOL for sole, TOP for top-down, and DET for detail shots. Using consistent abbreviations means anyone on the team can identify the shot type without opening the file.
- Sequence number (optional): If a single angle has multiple images, a two-digit sequence number appended at the end prevents collisions. DET01, DET02, DET03 is cleaner than three files all labeled DET.
A practical format looks like this: STYLECODE-COLORCODE-ANGLE.jpg
For example: BF2200-BLK-HER.jpg (Style BF2200, black colorway, hero image), or BF2200-BLK-DET01.jpg (same style, first detail shot).
That file name tells anyone handling it exactly what they are looking at, which product record it belongs to, and where it goes in the image stack. No guessing, no cross-referencing, no manual QA required.
Adapting Naming Conventions for Multi-Marketplace Delivery
If you sell on multiple platforms, your naming convention may need to accommodate platform-specific requirements. Amazon, for instance, has specific rules about primary image filenames for catalog submissions. Shopify has no enforced naming standard but benefits from a consistent internal convention. Wholesale platforms and retailers often request files named to their own system.
The practical approach is to standardize on your own internal convention for all files coming out of the studio, then transform the naming at the point of delivery to specific platforms. This means the studio delivers files in your format, and whoever handles the marketplace upload applies the platform-specific transformation as part of their workflow, not as an ad hoc task each time.
If you are managing this manually, a simple spreadsheet mapping your internal SKU and colorway codes to each platform's required identifier keeps the transformation fast and error-free. If you are operating at high volume, a basic script that renames files in batch from one format to another eliminates almost all of the manual work.
Folder Structure: The Other Half of the Problem
File naming without a consistent folder structure solves half the problem. If correctly named files land in a flat directory of 1,000 images, finding the right one still requires search. A folder structure that mirrors your product hierarchy eliminates that friction.
A workable folder structure for footwear photography looks like this:
- Season (e.g., SS2027)
- Style code (e.g., BF2200)
- Colorway (e.g., BLK)
- Individual image files
With this structure, locating the hero image for a specific style and color takes five seconds, not five minutes. When you need to replace a single image after a QA correction, you navigate to the right folder, swap the file, and you are done. There is no risk of touching an image from a different style in the same folder.
Build this folder structure into your brief, and ask your studio to deliver files pre-organized into it. Most professional studios will accommodate this with no difficulty, particularly if you specify it clearly upfront. It requires a few minutes of extra organization on their end and saves hours on yours.
Managing Version Control When Images Are Revised
Revisions happen. A shot needs to be relit. A retouching error needs to be corrected. A sample had a defect that was not visible during the shoot and needs to be replaced. When revised files are delivered, version confusion is a real risk if the naming convention does not account for it.
The simplest approach is a versioning suffix. When a file is revised, the new file is named with a version indicator appended: BF2200-BLK-HER-v2.jpg. Your team knows to use the highest version number as the authoritative file. Once the revision is confirmed and uploaded, the v1 file is archived rather than deleted, in case you ever need to reference what changed.
Alternatively, a separate revision folder within each style or colorway folder keeps the root directory clean. Original files stay in the main folder. Revised files land in a Revisions subfolder, with the understanding that the Revisions folder contains the current authoritative versions whenever it is not empty.
Either approach works. The important thing is that everyone who touches the files, your team, your studio, and any external upload contractors, understands the convention and follows it. Document it, share it, and revisit it annually.
Building File Naming Into Your Studio Brief
A naming convention only works if your studio knows about it before the shoot, not after. The brief you send to a studio should include a dedicated section specifying exactly how you want files named and organized. That section should cover:
- The exact naming format, with an example for each file type
- The abbreviations you use for each angle
- The folder structure you expect on delivery
- How to handle multi-colorway shoots
- What to do if a sample has a defect visible during the shoot that may require a reshoot
- How revisions should be delivered and named
If your studio regularly photographs footwear at volume, they almost certainly have their own system. The conversation is about aligning their system with yours, or agreeing on a shared standard that works for both. That conversation is far easier to have before a shoot than after a delivery of 800 incorrectly named files.
For brands building a photography brief from scratch, this naming section is one of the most valuable things you can invest time in. It pays off every season, not just the first one. If you need help structuring your brief more broadly, our article on how to prepare shoes for a product photo shoot covers the sample prep side of the equation in detail.
The Compounding Value of Consistency Over Time
A naming convention established in year one becomes the foundation of a searchable, auditable image archive by year three. You can pull every image of a specific style across all seasons. You can audit which colorways have complete image sets and which are missing angles. You can hand off the upload workflow to a new team member and have them productive in an hour rather than a day.
Brands that do not have this foundation find themselves in a different situation: an image archive that is technically complete but practically unusable, where finding anything requires institutional knowledge that walks out the door with the person who built it informally.
The investment required to build a good naming convention is small: a conversation, a document, a section in your brief template. The return compounds across every season and every team member who touches your product imagery. It is one of the highest-leverage operational improvements available to a growing footwear brand, and it costs almost nothing to implement.