Rename Images and Web Assets with SEO-Friendly Filenames Before Deployment
Web assets exported from design tools or downloaded from stock libraries arrive with filenames that are useless for search engine indexing — shutterstock_1847392.jpg, export_2x.png, image (3).webp. Google uses image filenames as one signal for understanding image content and context, and a filename like blue-ceramic-coffee-mug-handmade.jpg outperforms IMG_0047.jpg for image search visibility. Deliteful's Batch Rename Files tool applies descriptive, slug-style naming to an entire asset set before deployment, at scale.
Google's image SEO documentation explicitly lists descriptive filenames as a best practice for image indexing. For e-commerce sites, blogs, and content-heavy web properties, image search drives a measurable share of traffic — particularly for product photography, editorial images, and how-to content. Renaming assets one at a time in a file manager before uploading them to a CMS or CDN is a task that gets skipped because it is tedious, not because it is unimportant. The result is a site where hundreds of images are indexed under meaningless names.
Deliteful processes JPEG, PNG, and WebP files up to 50MB each in batches of up to 50 files. A practical workflow for a content team renames images by article slug or product category before CMS upload — article-slug-hero-1.jpg, article-slug-inline-2.jpg — creating a direct association between the image filename and its page context. The same approach works for product photography (product-name-color-angle-1.jpg) or any asset category where descriptive naming supports both search indexing and internal asset management.
How it works
- 1
Identify the page or context each image belongs to
Descriptive filenames are most effective when they reflect the page slug or product name the image will appear on — decide on naming before uploading.
- 2
Set a descriptive, hyphenated prefix
Use lowercase, hyphen-separated words that describe the subject — matching the style of URL slugs — rather than underscores or CamelCase, which are less conventional in web asset naming.
- 3
Upload images in the order they appear on the page
Sequential numbering maps naturally to image position on the page — hero image gets _1, inline images get _2, _3, and so on.
- 4
Download and upload directly to your CMS or CDN
Renamed files are ready for direct upload; no further renaming step is needed before or after CMS ingestion.
Frequently asked questions
- Does Google actually use image filenames as a ranking signal?
- Yes. Google's own image SEO documentation states that descriptive filenames help Google understand image subject matter. Filenames are one of several signals alongside alt text, surrounding content, and structured data. Descriptive naming is a low-effort improvement with compounding benefit across large image sets.
- Can I rename JPEG, PNG, and WebP files in the same batch?
- Yes. All three formats are supported in one batch. Each file retains its original extension after renaming.
- Should I use hyphens or underscores in web asset filenames?
- Hyphens are the conventional separator for web asset filenames and URL slugs. Google treats hyphens as word separators in filenames, which aids keyword parsing. Underscores are treated as character joins rather than separators by some parsers, making hyphens the safer choice for SEO purposes.
- What is the file size limit for web images?
- Image files up to 50MB each are supported. Web-optimized images are typically well under 1MB, so the practical limit for web asset workflows is the 50-file batch count, not the size limit.
Sign up free with Google and give every image on your next content publish a filename that works for search engines, not just your file manager.