QuokkaPix
Home Batch rename

Batch rename

Rename image batches with a repeatable pattern

Batch rename is file hygiene, not pixel editing. Use it when camera filenames, downloaded names or mixed folders need a predictable sequence before upload, review or delivery.

Numbered namesCatalog cleanupZIP output
Open live editor Batch rename
The button below opens the QuokkaPix editor with this tool already selected.

Good fits

1
Turn camera names into catalog-friendly filenames.
2
Create a numbered product upload queue.
3
Keep processed outputs separate from originals.

Workflow

1
Switch to batch mode.
2
Choose the rename tool and naming pattern.
3
Combine with resize, compression or metadata cleanup if needed.
4
Download the renamed output package.

Limits to check

1
The browser cannot rename source files in place.
2
QuokkaPix creates new downloaded outputs.
3
Avoid filenames that expose private catalog data.

FAQ

Does it modify my original files?

No. It creates new output files and leaves the selected originals unchanged.

Can rename be part of a scenario?

Yes. Rename can run with resize, convert, compress or metadata cleanup in a repeatable workflow.

Practical QA notes

Naming checks

1
Use sortable numbers with consistent zero padding.
2
Keep names short enough for downstream systems.
3
Avoid characters that break upload forms, scripts or ZIP extraction on another operating system.
4
Confirm the result manifest maps each sourceName to the intended outputName.

Collision and sequence checks

RiskWhat to checkFix
Duplicate output namesTwo sources would export to the same filename.Change the prefix, suffix, start number or padding before running the batch.
Unsortable numberingNames sort as 1, 10, 2 instead of 001, 002, 010.Use zero padding for catalog or handoff batches.
Lost source mappingA reviewer cannot tell which original produced the output.Keep a source-name token or use the result manifest during QA.
Private catalog dataA SKU or internal note appears in a public filename.Use a neutral public naming pattern for external delivery.

Before handing off renamed files

1
Open the ZIP and sort by filename to confirm the sequence is readable.
2
Check the first, last and any skipped source files against the manifest.
3
Use the same naming pattern for all files that belong to one upload job.
4
Keep the original filenames available when the catalog team may need to trace a source image.

Batch rename QA is about names, not pixels

A rename workflow should not be reviewed like a visual export. The pixels stay the same; the important checks are collisions, numbering, extension handling, forbidden characters and whether the new names still map to the original files. For product catalogs, include a stable product code or sequence only when it matches the downstream system. Before downloading the ZIP, inspect the result list and confirm that no two outputs would overwrite each other.

1
Check sourceName to outputName mapping.
2
Avoid characters rejected by operating systems, CMS tools or marketplaces.
3
Keep extensions consistent with the actual file format.