Product Image File Naming: A SKU System for Sellers

Product image file naming works best when every file name carries the SKU, the colour, the view and a two-digit order number, all lowercase with hyphens. Keep that as your master name, store files in one folder per SKU, and rename copies to a descriptive SEO name only for your own store.

Most sellers start with camera names such as IMG_4821.JPG. That works for ten products. At three hundred products, across four colours each and six marketplaces, nobody can find the back view of the green kurti, and the wrong file gets uploaded. A naming rule written once and followed every time removes that whole class of mistake.

Why a product image file naming system pays off

• Fewer wrong uploads: the SKU in the name is the same code on your stock sheet and your marketplace template.
• Faster re-shoots: you can see at a glance which views a SKU already has and which are missing.
• Easier hand-offs: a tailor, a cousin or a freelancer can add photos without asking you what each file is.
• Cleaner SEO on your own store, because the descriptive name comes from the same source of truth.

The master pattern

Build the name from five parts, always in the same order, joined by hyphens:

Worked example: one kurti, four views

A green cotton kurti with SKU KRT-0142 and a plain front, back, side and fabric close-up. Source photos are your own; the later shots are edited or generated versions of them.

Notice what stays constant: the master name for the same picture is identical in the shots folder and in every marketplace export folder. The folder tells you where it is going; the file name tells you what it is. If a copy changes in a way that matters, such as a colour fix, you bump the version, so the old file is never silently overwritten.

A folder structure that scales

1. Top level: a folder per season or drop, for example 2026-festive.
2. Second level: a folder per category code, for example kurti, saree, lehenga.
3. Third level: one folder per SKU and colour, for example krt-0142-green.
4. Inside each SKU: 01-source, 02-shots, 03-export (with one subfolder per marketplace) and 04-web.

The numbered prefixes keep the folders in work order. If you use cloud storage, share at the season level and keep the rest private so a stray edit cannot change a file that is already live.

Product image file naming for SEO on your own store

Google's guidance is to use short, descriptive filenames instead of camera defaults, and to avoid generic names such as image1.jpg. We covered what Google says in detail in our image SEO guide. For your own website, make a second name from the same product facts: fabric, colour, garment and view.

• Describe what is in the picture. Do not repeat a keyword five times; a name is not a place for a keyword list.
• Keep the extension matching the real file type.
• Write alt text separately; the filename and the alt text do different jobs.
• Keep a lookup sheet that maps each master name to its SEO name, so you can trace an image back to its SKU.

Naming files that come out of Vastralook

Whether you generate shots yourself (about ₹40–₹50 per 2K image) or place a Create order (about ₹10–₹13 per 2K shot, ready in about 3–4 minutes), rename the downloads into your SKU folder as soon as they arrive. It takes a minute per SKU, and it is much harder to do a week later when the downloads are mixed with other work. Each garment in Catalogue Studio takes up to four of your own photos, so name those four source files by view too, and they will line up with the shots you get back.

• One naming pattern written on a single page and shared.
• SKU first in every file name, matching your stock sheet.
• Lowercase, hyphens, no spaces or special characters.
• A fixed list of colour names and view names.
• Two-digit order numbers so files sort in listing order.
• A version number that changes whenever the picture changes.
• A separate descriptive SEO name for your own website.