How to Name Image Files for SEO: 7 Rules and Examples

Set your expectations from Google's own sentence: the filename "can give Google very light clues about the subject matter of the image". Getting it right costs nothing while the file is still on your desktop; fixing it after it goes live costs you a URL. To check the form of a single name, paste it into the free image filename SEO checker.

What Google actually says about image file names

Google's image SEO documentation, last updated on 2 March 2026, gives filenames one paragraph. Use names that are "short, but descriptive": my-new-black-kitten.jpg beats IMG00023.JPG. Avoid generic names such as image1.jpg, pic.gif and 1.jpg. If you have thousands of images, consider automating the naming, and if you localise your images, translate the filenames too. A separate section adds that it is "a good idea" for the extension to match the file type.

The page sets no length limit and no keyword rule, and mentions no penalty for a poor name.

The more useful answer came from a podcast. On Search Off the Record in October 2022, Lizzi Sassman asked John Mueller what would happen if she renamed every image on the site. Descriptive filenames are good, he said, but "I don't think you would see a significant change if you already do the other things around images, like the alt texts, the text surrounding the image. Those are really, really strong signals."

Then the exception: "if you don't do the alt text, or if you don't have good surrounding text, then, of course, the filename might be the only place where you mention what this image is about." A gallery photo with no caption and no alt text has one description on the page, and it is the filename.

Put Google's advice together and one good name looks like this, with what WordPress does to a careless one underneath.

Seven rules for naming an image file

All seven happen before you upload.

1. Describe the picture, not the page. Spend the name on what the image shows: oak-dining-table-front.jpg, not dining-furniture-guide-image-2.jpg.
2. Hyphens, never underscores or spaces. Google recommends hyphens instead of underscores, "as it helps users and search engines better identify concepts in the URL", and says underscores are "commonly used for denoting concepts that should be kept together". A space cannot travel in a URL as itself, so it arrives as %20 or + (MDN). Wix's home page is carrying Frame%202147239390.jpg as I write this.
3. Lowercase, the whole thing. The same page says Google "treats both /APPLE and /apple as distinct URLs with their own content". Mixed case also breaks links: on a server that is strict about case, a link to oak-table.jpg will not find Oak-Table.jpg.
4. Three to five words. Google sets no limit and asks only for "short, but descriptive". Under three words you have rarely described anything (table.jpg). Past 50 or so characters, the extra words are usually about the sale, not the picture.
5. Make the extension match the real format. Google calls it "a good idea". A PNG saved as .jpg still displays, but it misleads any tool that trusts the name.
6. Keep every name unique across the site. Duplicates are one reason a platform rewrites your name: Shopify adds a unique identifier when "a file with the same name already exists in your store", so upload four files called hero.jpg and three can come back with names you did not choose.
7. Leave out dates, camera codes and version numbers unless they are the subject. -v3, -final and -copy-2 describe your afternoon, not the photograph.

Here is one photo of an oak table under six names, from the camera default to the one worth keeping. The long one is the trap: solid-oak-dining-table-for-sale-best-price-uk-free-delivery.jpg is 63 characters, one table and then a sales pitch. Google's warning about keyword stuffing names the alt attribute rather than the filename, but the reasoning carries over: it "results in a negative user experience and may cause your site to be seen as spam".

Good and bad image file names, side by side

Every name in the first column comes off a real phone, design tool, camera or browser. The middle column is how the name is served if the platform leaves it alone: spaces and brackets get encoded. The second row is live on wix.com, and the last row on Squarespace's own Hester template demo, beside a file called pickels.jpeg.

How to name image files for SEO in four steps

The order matters: two of these steps hand the file back with a name you did not pick.

1. Resize and compress first. Get the file to the right width and file size before you think about the name. The free image size compressor takes one JPEG, PNG or WebP at a time, up to 10MB, and always hands back a JPEG.
2. Convert, if you are converting. The image to WebP converter turns a JPEG or PNG into WebP. Do it before the rename, not after.
3. Rename on save. Both tools save the result under a fixed name of their own, whatever you uploaded: the converter's is image_to_webp_converter_by_grigora.webp and the compressor's is image_size_compressor_by_grigora.jpg. Then check the new name with the image filename SEO checker.
4. Upload, then write the alt text. This is the part that carries weight, so give it the sentence the filename cannot hold. The image alt text generator drafts one from a JPG, PNG or WebP, aiming for under 125 characters; add the context it cannot see.

The image filename SEO checker scores a name out of 100. Given my-awesome-photo.jpg, as in the screenshot, it splits the name into three words and 16 characters, finds no issues and one warning (the main subject should come first) and passes it at 97. Read the score with that in mind: it checks the form of a name, not whether the words describe the picture. It takes 10 points off for each issue, such as capitals, spaces, underscores, the characters @, #, % and &, a generic start like IMG, photo or screenshot, or more than 60 characters before the extension, and 3 for each warning, such as a date, a stop word or the same word three times. It never sees the image, so it cannot tell you whether the extension matches the file.

Naming hundreds of product photos without losing a day

Google suggests automating the naming once you have thousands of images. A pattern that scales is product-variant-view, so that within one product only the view changes: oak-dining-table-front.jpg, then -detail, then -in-room.

Batch rename on your own machine with Finder or any bulk renamer, not in the admin afterwards, and keep every name unique so the platform has no collision to resolve. Do it before the import, whether the catalogue lands in Grigora Commerce or anywhere else. The copy beside each photo carries more weight than its name; for how much of it to write, see how long a product description should be.

What your website builder does to the file name after you upload it

You type a name, the platform stores something else, and the URL a crawler sees is not the one you wrote. Here is what six platforms had done to images on live sites on 23 September 2026.

• WordPress runs every upload through sanitize_file_name(), which replaces spaces and consecutive dashes with a single dash and strips characters such as brackets, # and &, but leaves capitals alone. Since 5.3 it also scales down any image wider or taller than 2560px and adds -scaled to the name, so oak-dining-table-front.jpg becomes oak-dining-table-front-scaled.jpg. TechCrunch's home page shows what survives: GettyImages-1225201409.jpg, 54657380116_66c449690d_k.jpg (a Flickr download) and Screenshot-2026-08-26-at-12.45.18-PM.png.
• Shopify keeps your name and appends a cache-busting query, which is why Allbirds serves its logo as /cdn/shop/files/logo-seo.jpg?v=1753720776. Its documentation is unusually specific: a unique identifier can be added when a name collides, an underscore should not sit immediately before dimensions (product-image-5x4.jpeg, not product_image_5x4.jpeg), and a name cannot end in words such as thumb, small, medium, large or grande, which the CDN can mistake for resize requests.
• Squarespace keeps your name but files it behind a site ID and an upload ID, then adds ?format=1000w. Its own Hester template demo serves pickle-perfection-v1.jpg and download+%287%29.jpeg.
• Wix inverts the order: a hash comes first, your name is tacked on the end after the resize instructions, which is where online%20portfolio.jpg and website_security.jpg sit on wix.com's own home page.
• Webflow prefixes a 24-character asset ID, so a file uploaded as agency-d-2.webp is served as 6a904cdb0f76d625a477188f_agency-d-2.webp.
• Next.js sites, this blog included, percent-encode the whole path into a query string: /_next/image/?url=%2Fblog%2Ffigures%2F...png&w=1200&q=75.

On all six, the part you choose is the name you type before upload; the platform decides the rest. A hotlinked stock photo carries a name you cannot choose at all, one more reason to host your own copy.

Should you rename images that are already on your site?

Usually not. Use good names for every new upload, but renaming the old ones tends to cost more than it returns.

Mueller's reasoning in the same podcast: "when we crawl images, we tend not to crawl them as often, because usually, they don't change a lot." So a site-wide rename does not look like a rename to Google. It looks like the old images vanishing and unfamiliar ones arriving slowly: "a couple of months at least" of being "kind of annoying in Image Search", for something that "probably would have minimal effect". When Google moved its own blog off Blogger, Mueller thinks the images were simply ported over, names and all.

Three cases where it is worth doing:

• The page is being rewritten anyway, so the images move regardless.
• You are migrating platforms, the exception Mueller gave himself: when the files change URL anyway, fix the names on the way through.
• The name is wrong: the wrong product, or a client name in a file about to be published.

If you do it, go one template or one collection at a time, and put a permanent redirect on the old URL wherever your host allows one. Google follows a permanent redirect and uses it as a signal that the target should be canonical, which is how the old file gets connected to the new one. Then fix every page that embeds it.

Shopify is the awkward case. Renaming a file there means editing its URL Handle, and its documentation says "the previous URL for that file no longer works". It mentions no redirect for the old address.

File name, alt text and caption do three different jobs

Write each one for the reader it actually has.

• The filename is a weak hint that also becomes part of the image URL. Three to five words is plenty.
• The alt text is the strong signal and the accessibility requirement. Google calls it "the most important attribute when it comes to providing more metadata for an image", and grades its own examples: missing and keyword-stuffed alt text are bad, alt="puppy" is better and alt="Dalmatian puppy playing fetch" is best.
• The caption is the only one sighted readers read, so it carries what the picture does not show: the date, the source, the point. In hand-written markup it sits in a <figcaption>, one of the tags worth knowing for blog posts.

Mueller's rule for alt text is worth copying: not "a photo of a beach" but "the beach before the chemical spill happened". People searching images, he said, "want information which is attached to that image".

The accessibility case is stronger than the SEO one. WebAIM notes that when an image is the only content inside a link and its alt is empty or missing, screen readers "might read the image filename or the URL of the linked page". DSC_0042.JPG read aloud is the real cost of a lazy name.

Coverage is worse than it looks. In the July 2025 crawl behind the Web Almanac 2025, the median mobile page had alt attributes on 60% of its images, and 15% of its images carried a blank alt; at the 90th percentile, 90% were blank. The image alt text extractor pulls every img tag and its alt attribute from a list of URLs into a CSV, and lists a blank alt as missing. It reads the HTML as served, so it misses images added by JavaScript and CSS backgrounds, and Google does not index CSS images either.

What else is inside the file: EXIF and IPTC

Google reads IPTC photo metadata embedded in the file itself: Creator, Credit Line, Copyright Notice, Web Statement of Rights, Licensor URL and Digital Source Type, the field that can mark an image as AI-generated. Google Images uses them to show who made an image and how it can be licensed, including the Licensable badge, and structured data on the page does the same job if the embedded metadata does not survive your tools. If the photo is someone else's, read whether you can use any image on your website first.

EXIF is a privacy question rather than an SEO one. An iPhone embeds the coordinates where a photo was taken whenever Location Services is on for the Camera app, as Apple explains in its personal safety guide. Grigora's compressor and WebP converter already drop all metadata, EXIF and IPTC alike. If you skip them, run the image metadata cleaner before you rename, not after: it also saves under a name of its own: image_metadata_cleaner_by_grigora, with the extension of the format it hands back.

How to read other advice on image file names

While writing this I opened the images on one of the dedicated guides to image filename SEO. Its hero is served as Image_File_Names_for_SEO_c0d4be9d0f.png: capitals, underscores between every word, a CMS hash on the end. The author photo beside it is uros_ccceff3608.jpg. That is not a gotcha, it is the point: both images carry alt text, the page reads perfectly well, and the writing does the work the names do not.

One claim to ignore while you read around: the share of all searches that supposedly happens on Google Images. It rests on clickstream data Jumpshot collected in 2018 from US browsers, with Android as the only mobile source, and Avast announced it was winding Jumpshot down on 30 January 2020.

So name the file properly because it takes thirty seconds, not because it will move a ranking. Spend the time you save on the alt text and the copy around the image, which is where the signal is. On Grigora that means naming the file on your desktop, then filling in Alt Text on the image block after upload. The trial runs 14 days, no card.

Image file name FAQs