Imagyc›Articles

How to name images for SEO and organize your files

Published October 9, 2026 · 6 min read

A filename such as blue-running-shoe-side-view.webp explains an image more clearly than IMG_8472.webp. It helps a team find the file and gives search engines a clue about the subject.

Google describes filenames as a small clue and recommends short, descriptive names.¹ Naming is part of optimization, but does not guarantee rankings. The image also needs a relevant page, crawler access and value for visitors.

A useful convention identifies what the image actually shows. You do not need to turn the filename into advertising copy or repeat every product keyword.

Start with the image content

Before saving, identify the main subject. For an online store, that may be the product and a distinguishing feature such as color, model or viewing angle. For an article, it may be the object or action shown.

A side view of a blue shoe can become blue-running-shoe-side-view.webp. A white version needs a name describing the correct color. Do not label every photo “blue” just because the page targets that search.

Avoid claims the photo cannot demonstrate. “Best,” “cheap” and “number one” usually describe a sales promise rather than visual content.

A practical check is whether someone looking only at the name can identify the file. If they have to open ten photographs to find it, the convention can improve.

A useful structure for catalogs

One workable structure is: main subject + relevant feature + view or purpose + extension.

For a handbag, that might be brown-leather-handbag-front-view.webp. If the catalog requires an identifier, add it without replacing the description: brown-leather-handbag-front-sku742.webp.

Not every field is necessary. A dental practice photo can simply be dental-practice-reception.jpg. Adding a product code that serves no purpose complicates the process.

For large collections, a consistent order prevents random naming. Teams can generate names from reliable fields such as product type, color, view and SKU. Review exceptions so different photographs do not receive the same combination.

Separating words and choosing characters

Google recommends hyphens to separate words in URLs.² Since a published filename forms part of an image URL, green-cotton-shirt.webp is clearer than greencottonshirt.webp.

Lowercase is a practical standardization choice. URLs can be case-sensitive, so Photo.webp and photo.webp can be different addresses.² Consistency reduces reference errors.

For a simple workflow, use letters a to z, numbers and hyphens in the base name, with a period before the extension. This is an editorial convention, not a rule that Google accepts only those characters.

Accents and other writing systems can appear in URLs when correctly encoded. Google advises percent encoding where needed.² There is no basis for claiming a file is penalized simply for containing “ç” or “á.”

Choosing uncomplicated names can still make transfers between systems easier. Keep natural spelling in page copy and alternative text.

Avoid characters such as ? and # in the base name: they have specific URL roles associated with queries and fragments.³ Spaces also need proper handling. A simple convention lowers the chance of malformed links.

Examples of clearer filenames

These are illustrative examples. Describe the actual content of each file.

“Final” and “approved” can help an internal workflow, but do not explain the subject to a visitor or search engine. Keep approval status in your management system or use version codes only when needed.

How many words to use

Use enough words to identify the image without an unnecessary sequence of terms. Google recommends brevity but does not prescribe a magic word count in that guidance.¹

Four or five terms may cover many cases, such as round-wooden-table-top-view.jpg. Some files need fewer or more. Let clarity determine length rather than a keyword-density target.

A name such as running-shoe-sports-shoe-blue-shoe-buy-cheap-shoe.jpg piles up repetitions and mixes description with commercial intent. It is cumbersome to maintain and does not establish stronger relevance.

Prefer a stable descriptive core. To distinguish export sizes, add consistent suffixes: blue-running-shoe-side-640.webp and blue-running-shoe-side-1280.webp.

These numbers organize versions. They do not replace HTML dimension descriptors or instruct the browser to choose a particular source.

Filename alternative text and caption are separate fields

The filename identifies the file. Alternative text, supplied through alt, communicates information or function to people who cannot see the image. A caption appears on the page and adds context.⁴

Do not automatically copy the hyphenated filename into alt. For blue-running-shoe-side-view.webp, natural wording could be “Blue running shoe with a white sole shown from the side.”

Alternative text depends on purpose. If an image acts as a button or link, its description should explain the action. W3C guidance says functional images should communicate the control's purpose.⁵

Purely decorative images may appropriately use alt="".⁶ This is a considered accessibility decision based on the image's role.

For complex charts, an organized filename and short sentence are not enough. Include the explanation or data needed to understand the information in the page content.⁷

Page context matters too

A chair photograph makes more sense on that product's page than on a generic page repeating “chair” many times. The title, product description and nearby text should explain why the image belongs there.

Google's SEO guide recommends descriptive alternative text and images near relevant content.⁸ Use these elements to tell visitors what they need to know without creating an artificial keyword list.

A caption can highlight something specific, such as “Height adjustment detail.” It does not need to repeat the full product name under every photo.

Maintain sufficient image quality for both thumbnails and the page. A precise name cannot fix a dark, unfocused photo or compression that obscures the detail it should demonstrate.

The extension should match the actual format

The part after the period indicates the file type, such as .jpg, .png or .webp. Renaming photo.jpg to photo.webp does not convert it.⁹

Export with a tool that creates the desired format and keep the matching extension. The server's content type should also represent the delivered file.

Descriptive names can remain consistent between formats: brown-handbag-front.jpg and brown-handbag-front.webp. Choose formats based on quality, compatibility and performance, as covered in the image formats article.

Naming images on multilingual websites

For Portuguese, English and Spanish pages, adapt descriptions to the page language. Filenames can follow localized versions while retaining a predictable convention.

For example: bolsa-marrom-frente.webp, brown-handbag-front.webp and bolso-marron-frontal.webp. This is an asset organization choice, not a requirement to change the photo's pixels for each language.

If a central image system reuses one source, describe its purpose correctly on each page. Decide whether to duplicate or share files according to the CMS and caching strategy as well as naming.

For site content, Google recommends separate URLs for language versions and a clear language on each page.¹⁰ That differs from putting three languages into one image filename.

Renaming images already published

Renaming a published image may change its URL. References to the old address need updating, including pages, responsive candidates and sharing metadata.

For a permanent change, assess redirecting the old URL to the new one. Google documents redirects as part of handling URL changes.¹¹ The website administrator should configure them.

Do not rename an entire collection merely to alter a minor detail with no clear benefit. Broken links can harm the experience more than the old name affected organization.

Apply the convention to new files before publishing. Starting consistently is easier than repairing thousands of addresses later.

What to check beyond the name

Confirm that the image loads through an accessible URL and can be discovered on the page. An image sitemap can help Google find files when needed.¹² It does not replace page quality or guarantee indexing.

Check dimensions, format, file size and loading. A thumbnail does not need the source intended for zoom. Reserve layout space and test on a phone.

Then monitor results over time: queries, impressions and clicks from image search where available in Search Console reports.¹³ Do not attribute the entire outcome to a naming change when other parts of the page changed too.

An effective convention makes files easier to find, publish and maintain. Describe the subject clearly, use consistent separators and let the other optimization measures work alongside the name.