Back to Insights
PNG File Naming for Websites: Screenshots, Logos, and Graphics

PNG File Naming for Websites: Screenshots, Logos, and Graphics

Uros Gazvoda
Uros Gazvoda

Give a PNG a name that describes its subject or purpose, such as invoice-folder-template.png, rather than screenshot-final-2.png. Use consistent lowercase words separated by hyphens for new website assets, and retain the correct extension.

PNG files do not have special SEO naming rules. The same descriptive principles apply to other image formats. Google's image guidance says filenames provide a very light clue about an image's subject; they do not guarantee rankings.

For the broader naming workflow, see image file names for SEO.

Practical PNG filename examples

AssetLess useful nameDescriptive name
Tutorial screenshotScreenshot-1042.pngrenamer-template-preview.png
Folder exampleblog-final.pnginvoice-folder-template.png
Logo variantlogo-new-2.pngacme-logo-dark-background.png
Comparison graphicchart1.pngmanual-and-automatic-filing-steps.png
Product detailimage-copy.pngblue-mug-handle-detail.png

These are illustrative names. Use the real product, subject, or workflow shown in your asset.

Name screenshots around the task

A screenshot filename should identify the relevant screen or step. invoice-template-date-field.png is easier to distinguish from invoice-template-preview.png than a set of numbered screenshots with no context.

Keep version or language details where they help your asset workflow. For example, template-preview-en.png and template-preview-de.png can distinguish localized assets.

Do not include a software version merely to make a name look current. Use it when the asset genuinely represents that version and your team needs to distinguish it.

Distinguish logo and graphic variants

Describe meaningful differences such as dark-background use, horizontal layout, or language. Keep internal source assets distinguishable from published exports.

A filename does not establish that a logo is approved or licensed. Use the approved brand source and the intended variant.

For diagrams and graphics, name the subject rather than repeating every label shown. Keep the page's text explanation available to readers who cannot interpret the image.

Keep filenames and alt text separate

The filename identifies an asset. Alt text explains its information or purpose in the page where it appears.

For a screenshot named invoice-template-date-field.png, useful alt text might explain the date field shown or the action the screenshot supports. Copying the hyphenated filename into the alt attribute usually produces awkward text.

Decorative images generally need empty alt text. The appropriate choice depends on the image's role, not whether its extension is PNG.

Naming does not change format or file size

Changing .png to .jpg or .webp in the filename does not convert the image. Use an export or conversion tool and check the result.

Likewise, a shorter or more descriptive name does not meaningfully compress the image. Treat naming, dimensions, format choice, and compression as separate decisions.

Check transparent areas, fine text, edges, and any other important visual detail after exporting. Choose the format that fits the intended use rather than assuming PNG is always required.

A publishing checklist for new PNG assets

  1. Confirm that the image supports the page.
  2. Remove private or irrelevant details from screenshots where needed.
  3. Export at appropriate dimensions and inspect the result.
  4. Apply the naming convention.
  5. Upload the asset and set contextual alt text.
  6. Check the published page and mobile layout.

Keep the original editable source where your team can find it. Published exports and source files serve different purposes.

Renaming PNGs already used on a website

Check whether renaming changes the served URL. Your CMS may generate its own names or maintain several variants.

Identify every use of the asset before replacing it. Update affected references and preserve access from old URLs where your platform supports an appropriate redirect. Verify the page after publication.

Use the existing-image audit checklist when planning a larger update.

Using Renamer.ai for PNG filenames

Renamer.ai can help suggest names from supported image content. For screenshots and graphics, specify the kind of description you want and review the output against the visible information.

An instruction might be: “Describe the main interface screen or illustrated task. Use concise lowercase words separated by hyphens. Do not guess a product name or version.”

Check important details yourself. AI-generated names do not automatically update website references, choose accessibility text, or compress images.

See the current Renamer.ai guides to configure a naming template.

Frequently asked questions

Should PNG names include keywords?

Use a term when it accurately describes the asset. Avoid unrelated promotional phrases or repeated keyword variations.

Should filenames include pixel dimensions?

Only when dimensions help distinguish exports in your workflow. They are not required for a descriptive name and are not a ranking guarantee.

Are underscores invalid?

No. For new website assets, hyphens are a readable convention. Existing working assets do not need an urgent URL change solely because their names contain underscores.

Is PNG better for SEO than another format?

The extension alone does not establish SEO value. Choose a suitable format, use the image in relevant content, provide appropriate accessibility text, and verify delivery.

About the author

Uros Gazvoda

Uros Gazvoda

Uroš is a technology enthusiast, digital creator, and open-source supporter who’s been building on the internet since it was still dial-up. With a strong belief in net neutrality and digital freedom, he combines his love for clean design, smart technology, and human-centered marketing to build tools and platforms that matter.

Founder of Renamer.ai