Batch Image Renamer
Rename a whole folder to a pattern, see every change before you commit, and get it back as a ZIP.
Tokens: {n} sequence number · {name} original name
· {date} today · {w} width · {h} height
· {ext} extension
Preview
| Original | New name |
|---|
Files are copied into the ZIP byte for byte — they are not re-encoded, so nothing is recompressed or loses quality.
What the batch Image Renamer does
Renaming a folder of images one at a time is the kind of task that eats an afternoon. Operating systems offer batch rename, but the implementations differ, none of them preview reliably, and none can use the image's own dimensions in the name.
This renamer takes a pattern with tokens and shows you every resulting name before anything is
downloaded. {n} is a sequence number with the padding you choose, {name} is
the original filename, {date} is today, and {w} and {h} are
the image's actual pixel dimensions — useful when you are preparing assets at several sizes and
want the size in the filename.
The cleaning option handles what messy filenames actually contain: accented characters that
percent-encode badly in URLs, spaces that break command-line tools, and the -FINAL,
copy and (2) suffixes that accumulate on any real folder. It also
lowercases by default, because most web servers are case-sensitive and a stray capital in a filename
is a broken image waiting to happen.
Collision detection matters when renaming in bulk. If a pattern maps two different files onto the same name, the second would silently overwrite the first in most tools. Here they are numbered apart and the count is displayed, so you can decide whether the pattern needs a sequence number in it.
The key technical point: files are copied into the ZIP byte for byte. They are not decoded and re-encoded, so a JPEG stays exactly the JPEG it was, with no quality loss and no metadata stripped. Only the name changes.
How to use it
- Select all the images you want to rename — a whole folder at once is fine.
- Choose a pattern, or click one of the examples and edit it.
- Check the preview table and the collision count.
- Download the ZIP and unpack it. The original files on your disk are untouched.
A worked example
Twelve product photos straight off a camera, renamed for a web store:
| Pattern | Produces |
|---|---|
{name}-{n} | img-4021-01.jpg — keeps unhelpful camera names |
meridian-stability-4-{n} | meridian-stability-4-01.jpg — descriptive and ordered |
{name}-{w}x{h} | hero-1920x1080.jpg — size in the name |
{date}-{n} | 2026-09-07-01.jpg — sorts chronologically |
The second row is what you want for a product listing: the filename becomes an image-SEO signal and the sequence keeps the order stable. The third is for a design system, where the same asset exists at several sizes and the filename needs to say which is which.
Frequently asked questions
Does renaming re-encode my images?
No. The original bytes are copied into the ZIP unchanged, so a JPEG remains bit-for-bit the same JPEG, with its quality and metadata intact. Only the filename differs.
Are my original files modified?
No. Browsers cannot write to your disk directly. The tool reads your files and produces a new ZIP; everything in your source folder is untouched.
What happens if two files get the same new name?
The tool detects it and appends a number to the second one, then shows the collision count so you know it happened. Adding {n} to your pattern prevents it entirely.
How many files can I rename at once?
Practically, a few hundred. Everything is held in memory while the ZIP is assembled, so several hundred large photographs may exhaust a phone's memory. Work in batches if you hit a limit.