Product Images Template
Organize your e-commerce product photos with consistent naming for SKUs, product names, and image angles. Perfect for online stores, marketplaces, and product catalogs.
{sku}_{product_name}_{angle}_{counter:00}Template Fields
| Field | Description | Example |
|---|---|---|
{sku} AI | Product SKU or ID if visible | ABC123, WD-5000 |
{product_name} AI | Product name or description | blue-sneakers, wooden-desk |
{angle} AI | Image angle or view type | front, side, detail, lifestyle |
{counter:00} Auto | Sequential number for multiple images | 01, 02, 03 |
Common Angles
front back side top detail lifestyle package 360
How It Works
- 1
Identify product
AI analyzes the image to determine what product is shown and generates a descriptive name.
- 2
Detect SKU/barcode
If visible in the image, extracts SKU codes, barcodes, or product IDs.
- 3
Determine image angle
Recognizes the photo angle (front, side, detail, lifestyle, etc.).
- 4
Apply counter
Numbers multiple images of the same product sequentially.
Examples
| Original file | Renamed to |
|---|---|
IMG_4521.jpg | ABC123_blue-running-shoes_front_01.jpg |
DSC_0042.jpg | ABC123_blue-running-shoes_side_02.jpg |
photo(1).png | WD5000_wooden-desk_lifestyle_01.png |
product_new.jpg | WD5000_wooden-desk_detail_02.jpg |
Who Is This For?
| Who | How they use it |
|---|---|
| E-commerce Stores | Organize product catalogs efficiently |
| Product Photographers | Deliver organized photo sets to clients |
| Marketplace Sellers | Manage inventory photos on Amazon, eBay |
| Catalog Managers | Maintain consistent image libraries |
Why Naming Matters
E-commerce teams routinely manage 50–500 images per SKU across multiple product variants, colorways, and platforms. When every image is named IMG_4521.jpg or DSC_0042.jpg, finding the front shot of item ABC123 means opening dozens of thumbnails. A consistent convention like sku_name_angle_counter puts the answer in the filename itself.
Standardized names also enable automated DAM (Digital Asset Management) ingestion. Most enterprise DAM systems accept structured filenames as metadata, SKU becomes the product identifier, angle becomes the asset type, and counter becomes the sort order. Batch uploads that would otherwise require hours of manual tagging complete without human intervention.
Finally, meaningful filenames prevent client delivery mistakes. When you hand off a folder of 300 product images to a marketplace or agency, a name like WD5000_wooden-desk_front_01.jpg is self-documenting. The recipient can verify completeness and placement without an accompanying spreadsheet.
Alternate Patterns
The default pattern works for most product catalogs. These variants suit specific workflows:
Platform-optimized (single-destination upload)
{sku}_{product_name}_{angle}_{platform}_{counter:00}e.g. ABC123_blue-sneakers_front_amazon_01.jpg
Variant-explicit (color and size in name)
{sku}_{product_name}_{color}_{size}_{angle}_{counter:00}e.g. WD5000_wooden-desk_walnut_72in_front_01.jpg
Simple (no SKU, small catalog)
{product_name}_{angle}_{counter:00}e.g. blue-running-shoes_front_01.jpg
Best Practices
- 1
Agree on angle taxonomy before processing
Inconsistent angle names ("front" vs "front-view" vs "front-shot") create duplicates when sorting and break DAM filters. Define your list, front, back, side, top, detail, lifestyle, white-bg, package, and stick to it.
- 2
Lowercase and hyphenated slugs only
Underscores separate fields; hyphens separate words within a field. "blue-sneakers" not "Blue Sneakers" or "BlueSneakers". This makes the delimiter logic unambiguous when parsing filenames programmatically.
- 3
Process images in product groups and reset the counter per SKU
Running the entire catalog in one batch mixes products. Group by SKU so counter starts at 01 for each product, giving you clean sets for marketplace bulk upload.
- 4
Use "lifestyle" for in-context shots and "white-bg" for studio shots
These are industry-standard terms recognized by most marketplaces and DAM systems. Using them consistently means your angle field doubles as a shot-type filter.
- 5
Add platform suffix only for single-channel assets
If the same images go to multiple platforms, omit the platform field to keep files reusable. Add it only when you're producing platform-exclusive variations (e.g. Amazon requires white background, Instagram allows lifestyle).
- 6
Always include the counter, even for single images
Using
_01on a solitary product shot makes future bulk additions consistent. When you add a second image later,_02slots in naturally without renaming the existing file.
Frequently Asked Questions
If no SKU is detected from the image or accompanying metadata, the {sku} field is omitted and the name falls back to {product_name}_{angle}_{counter}. You can also pre-configure SKU prefixes per product batch so FilesDesk assigns them automatically.
FilesDesk supports JPEG and PNG. HEIC and camera RAW formats (CR2, NEF, ARW, CR3, etc.) are not currently supported. Export your product shots to JPEG or PNG before renaming.
AI identifies the primary or foreground product and names the file accordingly. For composed or flat-lay images showing multiple items, you can manually add a "composed" angle tag in the rename preview, or configure a fallback label for multi-product shots.
Only files you explicitly include in the selection or watch folder are processed. You can exclude already-named files using a filename pattern filter, for example, exclude any file whose name already matches *_front_* or starts with a known SKU prefix.
Related
Download FilesDesk for Mac or Windows. Streamline your e-commerce image workflow.