Batch Rename Images

Replace text, add prefixes or suffixes, or generate sequences in bulk. Duplicate names are checked live and every image stays in your browser.

Why Rename Images in Bulk?

Camera and phone exports arrive as IMG_0001.jpg, IMG_0002.jpg, and so on — names that say nothing about what's in the shot and sort in an order that has nothing to do with a shoot's chapters or a product line's SKUs. Design and dev teams hit the same wall with asset dumps: hero-final-v3-USE-THIS.png next to Untitled-2.png, dropped into a shared folder where nobody but the original author can tell them apart. A content calendar or e-commerce catalog needs filenames that match a naming convention a CMS or ad platform will actually parse — a consistent prefix per campaign, or a strict sequence like product-001.jpg through product-240.jpg. Doing that one file at a time in a system file manager is slow and error-prone the moment you're past a handful of images; a single rule applied to fifty or five hundred files at once removes both the tedium and the chance of a typo breaking the pattern halfway through.

Turn IMG_0001-style exports into a readable naming scheme
Apply one Find/Replace or sequence rule to hundreds of files at once
Catch duplicate names before they collide, not after export
Keep original file extensions intact automatically

How to Batch Rename Images

The rule you set applies live to every loaded file, so you can watch the resulting names update before committing to anything.

1

Load your images, then open Set a naming rule to choose Find/Replace, Prefix/Suffix, or a numbered sequence

2

For Find/Replace, enter Find and Replace with text and toggle Case sensitive if the match should respect letter case; for a sequence, set Base name, Start, Step, and Zero padding

3

Check the live preview list — any name that collides with another is flagged, and under When filenames conflict you can accept the Auto-adjusted number or switch to Manually edited to type your own

4

Export the batch once every name is unique; ZIP entries cannot overwrite each other and original extensions are preserved automatically

Frequently Asked Questions

The tool checks for duplicates live as you type your rule, not after you export. Any name that collides with another gets flagged, and by default it falls back to Auto-adjusted, which appends a number to keep every entry unique. You can override that per file by switching its conflict setting to Manually edited and typing an exact name instead.
No. Original extensions are preserved regardless of which naming rule you use — a .jpeg stays .jpeg and a .png stays .png even if your Find/Replace pattern happens to match text that looks like an extension. The rule only ever touches the portion of the filename before the final dot.
Each export uses one rule type at a time — Find/Replace, Prefix/Suffix, or Sequence — rather than layering all three in a single pass. If you need a compound result, such as a common prefix and a sequential number, run the batch through Sequence with a Base name that already includes your desired prefix text, since the sequence mode builds names from Base name plus the incrementing counter directly.
Prefix/Suffix always adds text at a fixed position — the very start or the very end of the existing filename — and leaves the rest of the name untouched. Find/Replace instead searches for a specific string anywhere in the name and swaps it out, which is what you want when you need to correct or standardize text that already appears inconsistently across your files, like replacing 'draft' with 'final' wherever it occurs.
Zero padding sets the minimum digit width of the counter, so a padding of 3 turns the numbers 1, 2, and 10 into 001, 002, and 010, keeping every file the same character length for correct alphabetical sorting. Start sets the first number in the sequence and Step controls the increment between consecutive files, so a Start of 10 with a Step of 5 produces 010, 015, 020, and so on.
This tool only changes filenames — it does not touch pixel dimensions, quality, or format, so images go in and come out visually identical. If you're preparing files for upload and also need to shrink dimensions or file size, run them through Resize or Compress first, then load the results here to apply a consistent naming pattern before the final export.
No. Renaming is just relabeling — it happens entirely in your browser's memory, and the image data itself is never sent to a server. That also means very large batches are limited only by your device's own memory, not by an upload connection.
You can for a handful of files, but Finder and Windows Explorer offer no live duplicate checking, no pattern-based Find/Replace across a set, and no zero-padded sequence numbering — batch renaming there usually means selecting all files and getting an auto-numbered suffix with little control over the format. This tool also previews every resulting name before you export, so you catch a bad pattern before it's applied to the whole set instead of after.

More Image Tools

Explore other powerful tools for your image editing needs