The practical answer
Use {name}_{index}_{width}x{height} in the image workbench, apply the settings to every image, wait for the whole batch, and download the ZIP. The index distinguishes this batch’s results. After extraction, verify the picture identities, file count, format and real pixel dimensions.
Prepare two same-named images with different content
Keep the originals. Put a copy named catalog.png in each of two separate folders. For our original exercise, both pictures are 320×180 pixels: one has a red background marked A, the other a blue background marked B. The marks identify the practice files; you do not need to add marks to real product photographs.
Open the conversion entry in the image workbench and upload both copies. You can select them separately from their respective folders. Confirm that the queue contains two tasks. Choose PNG, keep the original dimensions, and leave cropping, watermarks and rotation off so that this exercise has a single purpose.
| Check | First item | Second item |
|---|---|---|
| Source name | catalog.png | catalog.png |
| Content identity | Red A | Blue B |
| Exercise dimensions | 320×180 | 320×180 |
| Expected index | 01 | 02 |
Set the template and apply it to the whole batch
Enter {name}_{index}_{width}x{height} in the batch naming field. The name token uses the original base name without its extension. The index starts with two-digit numbering for this export’s successful results, while width and height describe the output dimensions. The chosen output format supplies the extension; leave .png out of this template.
Click Apply settings to all images. Wait until both items have fresh downloadable results, then choose Download all (ZIP). Editing a naming field and immediately downloading an old result makes the workflow difficult to audit. Apply, wait and download in that order, especially after changing the dimensions or output format.
Expected names for this exercise
catalog.png — red A catalog.png — blue B
catalog_01_320x180.png catalog_02_320x180.png
Inspect four things after extraction
Start with the list inside the ZIP, rather than the ZIP’s outer name in your Downloads folder. MDN describes download filenames as suggested names for the browser. Browser download naming and the member names stored inside an archive are separate layers; an added suffix on the outer ZIP does not establish whether an image is missing.
Extract into a new empty folder. There should be exactly two PNG files: 01 showing red A and 02 showing blue B. Open both files and check that each is actually 320×180 pixels. For a real delivery, reconcile every item against your handoff list. A correct first image cannot demonstrate that the rest of the batch is complete.
Acceptance for this particular batch
- Both queued tasks have succeeded and the ZIP contains two images.
- Member names differ and each index matches the expected picture.
- Red A and blue B both exist; neither is an accidental copy of the other.
- The real format and dimensions match the settings, with no extraction overwrite prompt.
Do not use a batch index as a permanent asset ID
The index describes a position within the current export. Reordering tasks, exporting a different successful subset or making a second batch can change it. Wait for the complete batch, and keep a small mapping of source path, recognizable content and result name. Item 01 from one delivery is not automatically the same asset as item 01 from another.
Dimensions in the name also say nothing about readable text or accidentally cropped details. Use the flip and rotation checks when orientation matters. If delivery requires JPG or WebP instead, review the image format guide, then inspect transparency and the actual encoded result separately.
Resolve a failed handoff
Only one image arrived
Check for an unfinished or failed task, reconcile the success count, and export again into an empty folder.
Dimensions look wrong
Check whether you opened an earlier download. Apply the current settings and inspect a fresh archive.
IDs must remain stable
Maintain an independent asset register and mapping. A convenient batch index cannot provide cross-batch identity.
Common questions
Does 320x180 in a filename guarantee the size?
No. It is an inspection aid. Check pixel dimensions in an image viewer or file properties and confirm that you opened the result from the current export.
Will an index always identify the same source?
No. Numbering follows the current successful export set. Changes in task order, successful items or batch boundaries can change the number. Keep a separate asset mapping for long-term identification.
Should I extract directly into an old delivery folder?
An empty folder makes verification clearer. Check count and content there before handing over the batch, so older files and overwrite prompts do not obscure what this export actually contains.
Further reading & sources
Put the guide into practice
Open the relevant tool, preview the result and check your exported file.
