Sign in
Back to insights
A person pressing the button on a small machine that takes loose, unlabelled photo files from a bin and turns out neatly labelled ones on a conveyor.

How to Batch Rename Images for SEO Without Doing It One File at a Time

8 min read

There is a contradiction sitting inside the phrase “batch rename images for SEO”, and it is worth naming before you go looking for a tool.

Batch renaming software exists to give a lot of files one name. Select two hundred photos, type a word, and every file becomes that word plus a number. It is fast, it is reliable, and it is the exact pattern Google singles out as the thing to avoid.

So this is not a list of renaming tools. It is which half of the job a tool can take off you, which half it cannot, and how to stop the second half quietly never happening.

What Google asks for

Google’s image SEO documentation is short on this, so here it is in full rather than paraphrased. It says to “use filenames that are short, but descriptive”, offering my-new-black-kitten.jpg as better than IMG00023.JPG. It then names the failure case directly: “Avoid using generic filenames like image1.jpg, pic.gif, 1.jpg when possible.”

Note what that second quote rules out. Not badly chosen words. A name followed by a number. Which is precisely what every built-in rename tool produces.

Be clear about the size of the prize, because plenty of articles are not. Google describes a filename as giving “very light clues about the subject matter of the image”. Very light. It is one small signal among several, and we went through the rest in what actually affects your Google rankings.

Nobody should rename a folder of photographs expecting a traffic spike. You do it because it is cheap, because it compounds across a whole library, and because the alternative is shipping DSC_0042.JPG to a customer.

Two smaller rules from the same documentation are easy to get right:

  • Separate words with hyphens, not underscores. Google’s URL guidance recommends hyphens “as it helps users and search engines better identify concepts”
  • Make the extension match the actual file type. A WebP file called .jpg is a small avoidable mess
  • If you publish localised pages, translate the filenames too, and mind URL encoding if you are using non-Latin characters

The rename tools you already have

Before paying for anything, know exactly what ships with your operating system, because for some jobs it is genuinely enough.

On a Mac, select the files in Finder, right click, and choose Rename. You get three modes. Replace Text swaps one string for another across every selected name. Add Text puts something before or after each existing name. Format throws the old names away and applies a custom name with an index, a counter or a date.

On Windows, select the files in File Explorer and press F2. Type one name and every selected file becomes that name with a number in brackets after it. There is no way to customise that behaviour. Microsoft’s own answer is a separate download: PowerToys includes PowerRename, which does search and replace and regular expression renames across a selection, explicitly so you are not stuck giving every file the same name.

Where the built-in tools stop

Look at what those three Mac modes and PowerRename actually do. Every one of them is a transformation applied uniformly to a selection. Find this, replace with that. Add this prefix. Number these in order.

That is brilliant for a whole category of work, and you should use it without guilt:

  • Stripping a camera prefix off a hundred files at once
  • Swapping underscores for hyphens across a folder
  • Lowercasing everything so your URLs stop being case-sensitive traps
  • Adding a consistent suffix like -detail or -front to a set you have already sorted into groups

What none of them can do is look at photograph 47 and know it shows a navy canvas backpack from the front. A find-and-replace does not have an opinion about content. So the moment your requirement is “each filename should describe what is in that particular image”, a uniform transformation has run out of road, and no amount of clever regex gets you further.

The spreadsheet and script route

The usual next step, and a perfectly good one, is to separate deciding from doing. List the current filenames in a spreadsheet, write the new name beside each one, then let a script apply the mapping.

This works. It is auditable, you can undo it by reversing the columns, and someone non-technical can fill in the names while someone else runs the script. For a team that renames images in occasional large batches it is a sensible arrangement.

It is also honest to say what it has and has not solved. The script handles the mechanical part, which was never the slow part. A human still sits and types two hundred descriptions. You have organised the work rather than reduced it.

The part that does not batch

This is the whole problem in one line. Renaming is mechanical and automates perfectly. Describing is judgement, and it is the bit that actually takes the afternoon.

Which is why image naming has a particular way of not happening. It is not difficult, so it never justifies its own slot in the schedule. It is just slow, and slow tasks with no deadline lose to tasks with one. Most image libraries are not full of IMG_4471.JPG because nobody knew better. They are full of it because the useful version cost four hours nobody had.

A workflow that survives a deadline

The version that holds up is the one where naming happens on the way into the site rather than as a cleanup pass afterwards. Concretely: take the set of images you are about to publish, get a descriptive name and alt text for each one, resize and convert them, and only then hand them to your CMS. One pass, before anything is live, which also means no redirects to think about later.

That is what we built Resiqo to do. You drop in a folder, it proposes a descriptive filename and alt text per image, you edit anything you disagree with, and it exports the resized, converted set as a single zip. Resizing and conversion happen in your browser, so the full-size originals never leave your device. The free plan covers 20 named images a month, and resizing, conversion and export are unlimited for everyone.

If you would rather do it by hand, do it by hand. The argument here is about sequence, not software. Naming images before they are published is dramatically cheaper than naming them after, whoever or whatever is typing.

Renaming images that are already live

Renaming a published image changes its URL, and that has consequences a rename tool will not warn you about.

You will need redirects from the old image URLs to the new ones, and you will need to update every page that references them, or you are trading weak filenames for broken images. Google’s redirect documentation describes what happens next: one URL becomes canonical and “the other URL becomes an alternate name of the canonical URL”, and Google “will continue to occasionally show the old URLs in the results, even though the new URLs are already indexed”.

On how long that takes, we are not going to give you a number, because Google does not. Its documentation offers no timeline for reprocessing a redirect, and any article confidently telling you it takes two weeks is telling you something it cannot know.

Given that, retrofitting an entire back catalogue is rarely the best use of an afternoon. A more defensible order of work is to get the process right for everything you publish from now on, then revisit old images only where the page genuinely matters and you are editing it anyway.

A short checklist

  • Use the built-in tools for uniform work: prefixes, case, hyphens, stripping camera junk
  • Do not use them to give a folder one name plus a counter. That is the pattern Google names as the thing to avoid
  • Describe what is in the image, in plain words, hyphen separated
  • Match the file extension to the actual file type
  • Name images before publishing, so there are no redirects to manage
  • For images already live, redirect old URLs and update the pages that reference them, or leave them alone
  • Expect a small, compounding gain, not a spike. Google calls the filename a very light clue

Questions people ask

Is it worth renaming hundreds of old images?

Usually not as a standalone project. Each rename needs a redirect and a reference update, the payoff per image is small by Google’s own description, and there is no published timeline for how quickly the change is reflected. Fixing your process for new images costs less and compounds.

Do underscores really matter?

Google recommends hyphens over underscores in URLs, in its own words because it helps identify concepts. It is a recommendation rather than a penalty, and it costs nothing to follow, so follow it.

Should the filename include my target keyword?

Only if the keyword is genuinely what the image shows. Naming every photo after the same head term stops being descriptive, which is the only quality Google’s documentation actually asks for.

Does the file format affect naming?

Not the name itself, but make the extension honest. Google supports BMP, GIF, JPEG, PNG, WebP, SVG and AVIF for images in an img tag, and advises that the extension should match the file type.

Sources: Google Search Central, image SEO best practices and URL structure best practices; Google Search Central, redirects and Google Search; Apple Support, renaming files on Mac; Microsoft Learn, PowerRename. Every quotation above was checked against the page it came from before publishing.