Batch Rename Product Images for Uploads

Quick answer-first workflow

This page is for teams who already have product media and need filenames that align with catalog keys before upload. Use this sequence: map the catalog identity, choose a fixed naming template, stage files by product and variant, run a dry run rename, and only then write final names after checks. If names must include platform limits, platform slug rules, and SEO priorities, apply them before renaming so you do not rework files later.

Scope and practical setup

Before touching files, decide the exact destination rule set. This includes platform target, file system behavior, and catalog source of truth. Keep scope tight to one upload batch only: one store, one campaign, or one supplier feed. Do not mix legacy imports and active campaigns in the same rename job. It increases accidental overwrites and makes traceability difficult.

• Use a single primary ID field such as SKU, internal item code, or variant code. If multiple IDs exist, pick one master and keep others in notes.
• Set naming rules for platform constraints, for example lowercase-only, max length, dash usage, and extension policy.
• Collect required metadata before the rename: colorway, angle, image type (main, flat, detail), and resolution requirements.
• Keep original files read-only in their source folder during the first pass so revert is easy.

Canonical naming pattern

Use the same order for every filename so downstream systems can parse it consistently. Start with the fields that define uniqueness and then append versioning details.

Recommended base pattern:

{sku}_{variant}_{angle}_{seq}_{platform}_{ext}

• {sku} should be stable and source-of-truth aligned, for example ABC-1021.
• {variant} should be explicit and short, such as red or 32gb.
• {angle} should define visual order, such as front, side, detail.
• {seq} is zero padded, for example 01, 02, etc., so sorting is predictable.
• {platform} is optional if you upload to one sink; include it only if platform naming affects ingestion.
• {ext} should match the final export format, usually jpg for standard product photos.

Example output sequence:

• ABC-1021_red_front_01_shopify.jpg
• ABC-1021_red_side_02_shopify.jpg
• ABC-1021_red_detail_03_shopify.jpg

Step by step practical workflow

1. Import your raw export folder into a dedicated working directory. Do not rename in place until checks are in place.
2. Sort images by product, then by shot type, then by preferred display order. Remove obvious rejects with clear reasons.
3. Create a mapping sheet with columns for original name, proposed name, product id, variant, angle, and sequence.
4. Write one naming template and validate it against at least two edge cases: single image products and products with multiple variants.
5. Run a preview rename or dry run so you can inspect sequence order, number padding, and duplicate detection without changing filesystem state.
6. Review filename characters for prohibited symbols and remove spaces, double separators, and ambiguous punctuation.
7. Apply the rename to a staging copy only. Keep originals untouched until final signoff.
8. Run a second pass that checks for missing or duplicate sequence numbers, unpaired variants, and files that miss required fields.
9. Export the final CSV mapping and attach it to the handoff package so another operator can confirm each output file quickly.
10. Move files into the upload folder only after the stop condition is met.

Decision rules

• If two images share the same intended name, add a deterministic suffix before export, such as _a and _b, and record the exception.
• If a product has one canonical shot and one style shot, keep both if the destination requires variants; if not required, drop extras before renaming.
• If a SKU contains spaces or special characters, normalize using a shared conversion rule and document the exact transformation.
• If upload requires strict case, convert to a single case rule and apply across all products.
• If a file has multiple edits for the same shot, choose the latest approved render only and mark earlier versions as superseded in notes.

Common mistakes and how to fix them

• Missing stable identifier. Symptom: names use color only and duplicate across products. Fix by forcing {sku} to front of every filename.
• Wrong sequence logic. Symptom: image order appears random after upload. Fix with fixed padding and explicit sort rule, such as angle then sequence.
• Inconsistent angle labels. Symptom: front appears as frnt or fnt. Fix with a controlled vocabulary and reject unknown labels.
• Over-renaming. Symptom: extra conversions and reformatting beyond naming. Fix by keeping this workflow limited to filenames and metadata, not visual edits.
• No traceability. Symptom: team cannot confirm which original became final. Fix by keeping the CSV mapping and original file list in one handoff bundle.
• Final write before validation. Symptom: wrong names in production. Fix by requiring checklist completion before final output folder is considered authoritative.

Stop condition

Stop and do not continue renaming when all required conditions are satisfied:

• Every output filename includes a source-traceable identifier and no duplicates remain.
• Sequence and variant order are deterministic and match the approved product order.
• CSV mapping exists for 100 percent of outputs and uses the same column names for all rows.
• Platform checks show no disallowed characters and no extension mismatch.
• The destination upload destination is ready for intake with unchanged originals still preserved.

If any item fails, pause and fix before export replacement. Do not add optional optimization passes at this point. This prevents avoidable defects when the batch is consumed by a catalog importer.

Related tool handoff

Batch Image Renamer is the right tool for the mechanical rename run. Use it after your mapping is locked, then validate the renamed output using the same checklist before replacing source files.

Handoff package should include:

• Approved rename mapping CSV with all columns used in your workflow.
• Final upload folder and any exclusion notes for rejected images.
• Decision notes on duplicates, skipped shots, and platform-specific overrides.
• Reviewer initials, validation time, and a short confirmation of readiness for upload.