Marketplace Image ToolkitLocal batch image prepUpload images

Batch tool

Bulk Image Renamer

Prefix, SKU, zero-padded sequence, your separator. See every resulting filename before a single byte is exported, and get a folder tree that matches what you planned.

  • Templateprefix + SKU + number + extension
  • Padding1–6 digits
  • CollisionsAuto-suffixed, never overwritten

Drop product photos here

Or . JPG, PNG, WebP, GIF, BMP or AVIF — up to 20 images, 20 MB each.

Nothing leaves your device. Files are decoded and re-encoded in this browser tab.

Output targets

Pick one or several. Each gets its own folder in the ZIP.

Letter case
Filename preview

Upload images to see the generated names.

Settings apply to every image in the batch once you upload.

Export

0 source images × 1 target = 0 files

Platform check

The custom output target applies no marketplace rules. Select Amazon, Etsy or Shopify to see their size, format and file-size checks.

How it works

  1. Upload and set a SKU per image

    Each thumbnail has its own SKU field. That is the part that makes a renamed file traceable back to a product, so it is per-image rather than one value for the batch.

  2. Build the pattern

    Prefix first, then SKU, then the sequence number. Empty parts are skipped entirely, so you never get a stray double separator.

  3. Check the preview, then export

    The Filename preview and the folder tree show the exact names that will be inside the ZIP. What you see is what gets written.

The naming template

The output name is assembled from the parts you enable, joined by your separator:

[prefix] + [separator] + [SKU] + [separator] + [number] + .ext

SS26-WIDGET-001-007.jpg
 │     │      │   └─ sequence, zero-padded to 3
 │     │      └───── separator
 │     └──────────── per-image SKU
 └────────────────── prefix

Illegal filesystem characters (\ / : * ? " < > |) are stripped from every part, leading and trailing dots are removed, and the extension comes from the actual output format — so a WebP export never ends in .jpg.

Collisions are planned, not discovered

Two photos named IMG_0001.jpg in one batch would normally fight over one filename. The export planner walks the list before processing starts, tracks which names are taken per folder, and appends -2, -3 on collision. Because the plan is computed up front, the preview cannot disagree with the ZIP.

Why renaming matters for marketplace bulk uploads

Amazon’s bulk image upload and most feed-based workflows match images to products by filename. A folder of DSC_0421.jpg files means manual matching; a folder of SKU-0421-001.jpg files means a feed that works. The sequence number keeps multiple angles of the same SKU in a predictable order.

Questions

Does renaming change the image itself?

The name is metadata on the exported file. The pixels go through the normal render pipeline, so if you have not changed any settings the image content is the same as a re-encode of the original.

Can I rename without resizing?

Yes. Choose the Custom output target and leave the resize mode on the source size. The output keeps the original dimensions and only the filename changes.

What happens if I leave the SKU empty?

The SKU part is skipped, not filled with a placeholder. A batch with no SKUs still gets clean sequential names like IMG-001.jpg.

Are Unicode filenames supported?

Yes. Names are passed through as-is apart from the illegal-character strip. Be aware that some upload pipelines still choke on non-ASCII names, so ASCII SKUs remain the safer choice.

Can I keep the original filename as well?

Turn on Include original filename. It is appended as another part of the template, which is useful when you want both traceability and a clean prefix.

Related tools