Weak and better file names for product photos
| Photo | Weak file name | Better file name |
|---|---|---|
| Main image of a black dress | IMG_4021.JPG | lea-midi-dress-black-front.jpg |
| Back view of the same dress | IMG_4022 copy final.jpg | lea-midi-dress-black-back.jpg |
| Close-up of the fabric | detail.png | lea-midi-dress-black-fabric-detail.jpg |
| The dress on a model | model1.jpg | lea-midi-dress-black-on-model.jpg |
| The same dress in green | lea2.jpg | lea-midi-dress-green-front.jpg |
Every better name answers the same questions in the same order: which product, which color, which view. That is all a file name needs to do. It does not need the store name, the season, a date or a list of search terms.
What Google actually says
Google's image SEO guidance is specific and modest about file names. It says Google extracts information about the subject matter of an image from the content of the page, including captions and image titles, and that the file name can give Google very light clues about the subject. It recommends file names that are short but descriptive, gives the example of my-new-black-kitten.jpg being better than IMG00023.JPG, and asks you to avoid generic names like image1.jpg, pic.gif or 1.jpg when possible.
The same page says Google uses alt text together with computer vision and the contents of the page to understand what an image shows. So the order of importance is clear: the page and the alt text carry most of the weight, and the file name adds a small signal.
Google also notes that the file extension should match the real file type. A WebP file saved as .jpg, or the other way round, is a small mistake that some export tools make when you convert formats.
Why file names still matter in a fashion store
A very light SEO signal is not the main reason to name files well. The bigger benefits are practical.
- You can find the image again. A media library with thousands of IMG files is hard to search. A library where every file starts with the product name is easy.
- Variants stay matched. When the color is in the file name, it is hard to attach the green photo to the black variant by mistake.
- Your team and freelancers follow one system. A naming pattern is easy to explain and easy to check.
- Image addresses look clean. On most platforms the uploaded name becomes part of the image address. You can check yours by opening an image in a new tab and reading the address bar.
Wizia's own help center gives the same advice for images you generate and download: name the files descriptively before uploading, for example dress-lea-black-1.jpg, because it helps both your store's SEO and a tidy media library.
A naming pattern for clothing photos
Start with the product name
Use the short product or style name shoppers see, such as lea-midi-dress. Add the brand only if shoppers search for it.
Add the color
Use the same color word as the variant name in your store, so files and variants match.
Add the view
front, back, side, detail or on-model. If you have several of one view, add a number at the end.
Use lowercase and hyphens
No spaces, no underscores, no special characters. Hyphens separate words in a way people and systems read easily.
Keep the right extension
End with the real file type, .jpg, .webp or .png, matching the format you exported.
Write the pattern into your photo guide next to your master image size and background rules. A pattern that lives in one person's head breaks the first time someone else uploads a collection.
Stores in other languages and alphabets
Many stores in Central and Eastern Europe sell in Bulgarian, Greek, Serbian or another language with its own alphabet or accented letters. Google's guidance covers this: if you localize your images, translate the file names too, and follow URL encoding guidelines when you use non Latin or special characters.
In practice that leaves two sensible options. You can name files in the shop's language and alphabet, which matches the page but produces long encoded addresses when a file is shared or copied. Or you can transliterate into Latin letters without accents, the way many stores already handle product URLs. Either works; what matters is choosing one rule and using it for the whole catalog.
If you run the same product in several language versions of your store with separate images, translate the file names for each version, just as you translate the alt text. If all language versions share one set of images, a neutral Latin name is the simplest choice.
Common file name mistakes
A few mistakes show up again and again in store media libraries:
- Camera or phone names. IMG_4021 and DSC00187 say nothing about the product and are the names Google explicitly calls worse.
- Words like final, new or copy. dress-final-2-new.jpg tells you about your editing history, not the garment.
- Spaces and capitals. Spaces become %20 in addresses, and mixed capitals make names harder to type and match.
- The same name for different products. Two files called front.jpg in different folders end up as front-1.jpg and front-2.jpg after upload, and nobody knows which is which.
- Very long names. A name that repeats the product title, the brand, the category and several search terms is no more useful than a short one, and Google asks for short, descriptive names.
Fixing these at export time takes seconds per collection.
Should you rename images that are already live?
Usually not, at least not as a project of its own. The SEO gain from a better file name is, in Google's words, very light, and renaming a live image changes its address. Google's guidance asks sites to reference an image consistently with the same URL so it can cache and reuse it, and a new address means the image has to be discovered again.
A better rule is to name well from now on. Every new product and every reshoot gets proper names at upload. When you replace an old product's images anyway, because they were low quality or inconsistent, the new files get good names as part of the replacement.
The exception is a catalog where file names are actively misleading, for example images named after the wrong product or color. Fix those, because they confuse your team as much as any search engine.
Naming hundreds of images at once
Google's guidance suggests that a site with thousands of images might consider automating the naming. For a fashion store that usually means one of these approaches:
- A spreadsheet of products. List style name, color and the views you shoot, and generate the file names from it before the shoot or before export.
- Batch rename in your editor or operating system. Most photo editors and file managers can rename a folder of images with a pattern and a number.
- Export with names set. Many editing tools let you set the output name pattern at export, so the files leave the editor already named.
Do the renaming before upload. Renaming on your computer is quick; renaming inside a store's media library is slow and can change image addresses.
Naming AI generated product images
AI generated images arrive with whatever names the tool gives them, so plan a quick rename step. In Wizia AI Studio you can download the shots of a product one by one or all at once as a ZIP archive, at the 1K, 2K or 4K quality you chose. Unzip the folder, rename the files with your pattern, then upload them into the product's media in your store, where you also add the alt text for each product image.
Because every shot of one generation shows the same product in the same scene, naming them by view is straightforward: front, back, side, detail and on-model. If you are still deciding on sizes, read our guide to the best image size for an ecommerce website first, so you rename and upload each file only once. Generating an image costs 1 credit at 1K or 2K and 2 credits at 4K; see plans and prices for monthly credits.