Every technical SEO audit I run turns up the same problem in the media library: hundreds, sometimes thousands, of images named IMG_4821.jpg or Screenshot-2026-03-11.png. On one client site I reviewed recently, over 60% of uploaded images still had their default camera or screenshot names months after publishing. That’s not a huge ranking problem on its own, but it’s a wasted opportunity, and it’s one of the easiest wins in image SEO because you only have to get it right once, at upload.
Here’s how I actually approach file naming, what Google does (and doesn’t) do with it, and where it fits alongside alt text.
What File Names Actually Do for SEO
A descriptive file name is a small relevance signal. Google has said file names are one of many context clues it uses to understand what an image shows, alongside alt text, surrounding page copy, and captions. That’s not a huge ranking problem on its own, but it’s a wasted opportunity, and it’s one of the easiest wins in on-page SEO because you only have to get it right once, at upload.
Where I’ve seen it matter most in practice is Google Images visibility. Descriptive, keyword-relevant file names correlate with better image search performance for product photos and how-to imagery, where the file name is one of the few unambiguous signals on the page telling Google what’s actually depicted.
Naming Convention Rules I Use on Every Site
- Lowercase only. Server file systems can be case-sensitive, and mixed case creates duplicate-URL and broken-link risk if a link references the wrong case.
- Hyphens, not underscores. Google treats hyphens as word separators and underscores as joiners.
divi-global-section-example.jpgreads as three words to Google;divi_global_section_example.jpgcan read as one string. - Descriptive, not stuffed. Name the image for what it shows, not for every keyword you want to rank for.
wordpress-image-seo-checklist.jpgis fine.wordpress-image-seo-checklist-best-image-seo-tips-2026.jpgis stuffing, and it reads that way to both Google and anyone glancing at the URL. - Keep it short. Aim for 3-5 words. Long file names get truncated in some contexts and are just harder to manage in the media library later.
- Skip stop words when you can. “the,” “and,” “of” add length without adding signal. Not a hard rule, but a useful default.
- No special characters or spaces. Spaces get URL-encoded to
%20, which is ugly and occasionally causes issues with certain plugins or CDNs.
Before and After
| Default name | Renamed for SEO |
|---|---|
| IMG_4821.jpg | divi-blog-module-image-crop-fix.jpg |
| Screenshot 2026-03-11 at 10.42.13.png | rank-math-pixel-width-preview.png |
| photo (3).jpg | wp-rocket-cache-settings.jpg |
| asset_final_v2.png | gsc-ai-controls-dashboard.png |
Where This Goes Wrong on WordPress Specifically
Two things trip people up in WordPress:
1. Renaming an image after it’s published breaks its URL. Once an image is live and indexed, uploading a renamed version creates a new URL rather than updating the old one, unless you set up a redirect. If the image is already ranking or getting referral traffic in Google Images, don’t just swap the file. Rename before you upload, or rename and 301 redirect the old image URL to the new one if it’s already indexed.
2. Bulk import and migration tools ignore this entirely. If you’re migrating content or bulk-uploading from a stock photo library, the default behavior is to keep the source file name. I’ve had client sites where an entire product catalog import came in as 1234567-image.jpg sequential IDs from the source system, because nobody set a naming step in the import pipeline. Worth checking before a bulk upload, not after.
There’s no reliable one-click “rename everything” fix inside WordPress core for images already in the media library and referenced across dozens of posts. For a handful of images, rename manually and update the reference. For hundreds, it’s a database-level job, and worth doing carefully with backups rather than trying to shortcut it with a plugin that touches post content directly.
File Names vs. Alt Text vs. Captions
These three get confused constantly, and they do different jobs. File names help Google and crawlers understand context before the image even loads. Alt text describes the image for accessibility and for Google when the image can’t be displayed. Captions are for the human reader looking at the page. I go through this distinction in more depth in Alt Text for Images in WordPress — worth reading alongside this one since the two work together, not as substitutes for each other.
Quick Checklist
- Lowercase, hyphenated, descriptive, 3-5 words
- Named before upload, not after
- No keyword stuffing
- Bulk imports checked for source-system file names before they go live
- Redirect in place if renaming an already-indexed image
Frequently Asked Questions
Does renaming image files actually improve SEO rankings?
Not by itself. It’s a minor contextual signal that works alongside alt text, surrounding content, and captions. The bigger, more measurable benefit is usually in Google Images visibility rather than standard search rankings.
Should I rename old images that are already ranking?
Generally no, not without a redirect. Renaming creates a new URL. If the image already has search visibility or backlinks, set up a 301 redirect from the old image URL to the new one rather than leaving it broken.
Are underscores really worse than hyphens for SEO?
Yes, based on how Google has described word-boundary detection: hyphens are treated as separators between words, underscores are treated as joining characters. Hyphens are the safer default.
How long should an image file name be?
3-5 descriptive words is a good target. Long enough to be specific, short enough to stay manageable and avoid looking like keyword stuffing.
Should I include my brand name in image filenames?
Usually only when it’s relevant. Product images, logos, or branded graphics can include the brand name naturally. Don’t add your brand to every image filename just for SEO.
