Asset management workflow
Ecommerce Image Naming Convention for Sources and Exports
When three people export the same product photo, “final” stops identifying which image to upload. Google's image guidance describes a filename as one small clue about the image. The greater day-to-day payoff is being able to match a store upload to its product, source shot and approved revision.
The quick workflow
Keep camera originals → assign a stable shot ID → record the approved edit → create a named derivative for each slot → verify the store upload. Use a short and readable name, then maintain a simple mapping to the original.
Pick fields that survive revisions
Use the product or SKU, plain-language view, shot number and revision. Add the intended placement or format for exports. Keep the identifier stable even if the marketing title changes. Lowercase and hyphens make filenames easier to read and sort.
[sku]-[product]-[view]-s[shot]-r[revision]-[placement].[ext]Track one photo from capture to upload
For a fictional Alder Works mug, keep the camera file DSC_4182.RAW in the source archive. Assign the stable shot ID s03 to its front view. For revision 2, the store export could be aw17-travel-mug-front-s03-r02-card.webp. A different channel can use a JPEG derivative with the same shot and revision.
Keep approval status outside the filename
Put status, reviewer, revision and source in the proof sheet or asset log. Treat a new crop or material change as a revision. Keep channel derivatives together in an export folder and link back to one approved source entry. An older filename can remain unchanged when its image has already been uploaded.
Write alt text for people
A filename helps the team and provides Google a light clue. For a meaningful product photo, describe the content users need in the alt text, such as “Front view of the charcoal travel mug with lid closed.” Keep the text tied to the actual image and page context. Skip a repeated list of search phrases.
Audit one product before expanding
Pick one SKU, one source image and two derivatives. Ask a colleague to retrieve the original from a store filename and identify the approved revision. If they cannot, add a missing field to the log before renaming a large library. Review CDN and storefront references before changing existing asset URLs.
Resolve a filename collision before the next upload
If two exports have the same name but different crops, assign a new revision or placement value and update the mapping. Do not overwrite the approved reference while someone else is reviewing it. A stable shot ID should still lead to the same original capture.
In Ciyo, keep the shot ID beside the proof as text. Apply the agreed naming convention to downloaded files in your file manager or asset system. This workflow does not depend on a native batch-renaming feature in Ciyo, and changing a filename alone does not establish a search-ranking improvement.
Frequently asked questions
Do I have to rename existing product images?
Start with new uploads and fix the files that cause real confusion. Check references, redirects and platform behavior before changing an existing asset URL.
Should I include dimensions in every filename?
Use dimensions when similar derivatives need a visible distinction. If your placement label already identifies a documented size, it can be enough.
Keep a visual record of each export
Put the source and derivatives next to their shot IDs on a Ciyo board so the upload decision stays easy to verify.