SEO-Friendly Filename Renamer
IMG_4021.JPG tells Google nothing. This turns a folder of them into names that do.
Applied to files whose own name carries no meaning.
Renamed
| Original | New filename |
|---|
The rename commands are shell mv lines. Read them before running them, and work on a copy of the folder.
What the sEO-Friendly Filename Renamer does
An image filename is one of the few signals a search engine has about what a picture contains,
alongside the alt text, the caption and the surrounding copy. IMG_4021.JPG contributes
nothing. meridian-stability-4-side-view.jpg contributes a great deal, and costs nothing
to produce.
This renamer takes a list of filenames and cleans them. It strips the suffixes that escape from
people's desktops — FINAL, v2, copy,
(1) — and the timestamps that screenshot tools append. It flattens accents so
Chaussures survives rather than becoming percent-encoded in the URL. It lowercases
everything, which matters because most web servers are case-sensitive and a stray capital in a
filename is a broken image waiting to happen. It replaces every run of punctuation and spaces with a
single hyphen, and normalises .jpeg to .jpg.
Names that carry no meaning at all — the IMG_, DSC and
Screen Shot patterns — are detected and replaced with your descriptive prefix,
since there is nothing in the original worth keeping. Files whose names are meaningful are left
largely intact.
Collision handling matters in bulk. If six camera files all become
running-shoes-flat-feet.jpg, five of them would overwrite the others on upload. The tool
numbers them instead and reports how many it had to resolve — a high number is a sign your
prefix is doing all the work and the images need individual descriptions.
Rename before uploading. Changing a filename after publication changes the URL, which means the old one 404s and any image-search ranking it had starts again.
How to use it
- Paste your filenames, one per line — a directory listing pasted straight in works.
- Set a descriptive prefix for the files whose own names say nothing.
- Check the collision count; if it is high, the images need individual descriptions rather than one shared prefix.
- Copy the new names, or the rename commands, and apply them before uploading.
A worked example
Six typical files:
| Before | After |
|---|---|
IMG_4021.JPG | running-shoes-flat-feet.jpg |
DSC00873.jpeg | running-shoes-flat-feet-2.jpg |
Screen Shot 2026-03-14 at 10.42.31.png | running-shoes-flat-feet-3.png |
Meridian Stability 4 — Side View (FINAL v2).PNG | meridian-stability-4-side-view.png |
photo (1).jpg | running-shoes-flat-feet-4.jpg |
Chaussures_de_running_pour_pieds_plats.JPG | chaussures-running-pieds-plats.jpg |
Four of the six had meaningless names and got the prefix plus a number, which is honest but not
ideal — those four images would each be better with their own description. The fourth row shows
what good input produces: an em dash, brackets, capitals and a FINAL v2 suffix all
removed, leaving a name that describes the photograph.
Frequently asked questions
Do image filenames actually affect SEO?
They are a minor signal for image search, where Google has limited information about what a picture shows. Alt text matters more, and the surrounding page content more still. But a descriptive filename costs nothing and also makes your own media library navigable.
Should I rename images that are already published?
Generally no. Changing a filename changes the URL, so the old one 404s and any accumulated image-search value restarts. Rename before uploading. If you must rename a live image, set up a redirect for the old path.
Hyphens or underscores in filenames?
Hyphens, for the same reason as in URLs: Google treats them as word separators and underscores as joiners. flat_feet may be read as one token, flat-feet as two words.
How long should a filename be?
Three to six words. Long enough to describe the image, short enough to stay readable in a URL. Stuffing a filename with keywords is as detectable and as pointless as stuffing alt text.