Batch Image Conversion — Naming and Folder Conventions

The deploy broke hero images — banner.webp, banner (1).webp, banner-final.webp, and banner_final_v2.webp in the same folder. CMS expected homepage-hero-1200w.webp. Nobody remembered which batch script made which.

Batch conversion without naming rules is entropy at scale.

Quick answer

The deploy broke hero images — banner.webp, banner (1).webp, banner-final.webp, and banner_final_v2.webp in the same folder. CMS expected homepage-hero-1200w.webp. Nobody remembered which batch script made which.

Principles

1. Masters immutable — originals never overwritten
2. Predictable pattern — machine and human sortable
3. Format visible — extension matches actual file
4. Variant explicit — width, purpose, or density in name
5. One convention per project — document in README

See also Batch Renaming Before Upload.

Filename pattern template

{project}_{asset}_{variant}_{width}w.{ext}

Examples:

• adsense_hero_desktop_1200w.webp
• adsense_icon_search_32w.png
• blog_phishing-diagram_featured_1600w.jpg

Lowercase, hyphens preferred for URLs importing to static hosts.

Folder structure

assets/
  originals/
    hero.psd
    hero-master.png
  export/
    webp/
    jpeg/
    png/
  archive/
    2026-10-batch/

Or route-based:

public/images/blog/phishing-pdf-attachments/
  featured-1200w.webp
  diagram-metadata-800w.webp

Batch conversion tools

Browser tools — WebP Converter, PNG to JPG, JPG to PNG, Resize Image — one at a time for small sets.

CLI for volume:

# illustrative — adjust tools to your stack
for f in originals/*.png; do
  cwebp -q 85 "$f" -o "export/webp/$(basename "${f%.png}").webp"
done

Log conversions to manifest.csv — source, output, date, quality.

Responsive sets

Retina Images 2x — export 1x and 2x with width in filename.

Image CDN vs Browser Resize — if CDN handles variants, simplify local names.

SVG to raster batches

SVG to PNG When Needed — logo.svg → logo-512w.png explicit.

Compression pass

After convert, Compress Image — don't compress before naming final output or traceability breaks.

How Image Compression Affects Quality.

CMS and import pitfalls

• Spaces → %20 URL ugliness
• Uppercase extensions break Linux deploys
• Overwriting same name in CDN cache — version suffix hero-v3.webp or content hash

Dark mode pairs

Dark Mode Screenshots — suffix _dark / _light: docs-editor_dark_1200w.png

Troubleshooting

How should I name files in a batch image conversion? Use consistent pattern: project_asset_variant_size.format — example: homepage_hero_desktop_1200w.webp. Include width or purpose in name when exporting responsive variants. Avoid spaces; use hyphens or underscores consistently.

Should I keep original files after batch conversion? Yes in a separate originals/ or masters/ folder untouched. Convert outputs to dist/ or publish/. Never overwrite masters without backup — re-export needs source quality.

What folder structure works for batch image exports? project/originals/, project/export/webp/, project/export/jpeg/, or by page route: /blog/post-slug/images/. Mirror CMS import paths in folder names to reduce upload errors.

Limitations

Browser-based workflows for batch image conversion depend on file size, browser memory, and how the source file was created. Very large files, password-protected inputs, or unusual encodings may fail without a desktop alternative. Always keep an original copy before batch processing.

When not to use this approach

Skip browser-only processing when compliance requires audit logs, when files exceed practical browser limits, or when you need features your browser tool does not expose (bookmarks, form fields, digital signatures). In those cases, use dedicated desktop software or an approved enterprise pipeline.

Related tools

• WebP Converter
• PNG to JPG
• JPG to PNG
• Resize Image
• Compress Image

Conclusion

originals/ + pattern + manifest before batch convert fifty PNGs to WebP.

homepage-hero-1200w.webp beats banner (1).webp when production breaks at 11 PM. Name like someone else will deploy blind.

Git LFS vs committed binaries

Repos exceeding 500 MB image assets — Git LFS with pointer files; CI pulls LFS on build. Filename conventions even more critical when assets distributed across LFS.

Checksum in manifest

Add SHA-256 column to conversion manifest — detect corrupted re-copy. sha256sum Linux, CertUtil -hashfile Windows.

Deprecation workflow

hero-v2.webp active, hero-v1.webp in archive/ — calendar reminder delete v1 from CDN after 90 days if no rollback need.

Worked example: blog image batch

Imagine publishing a post with eight screenshots. Without conventions you get image1.png through image8.png. Six months later, which diagram shows the merge dialog?

Better pipeline:

1. Save masters to originals/blog-merge-guide/
2. Crop each in Crop Image
3. Export merge-guide_step-01_upload_800w.webp through step-08_download
4. Log in manifest.csv with source hash and quality setting
5. Reference in MDX: ![Upload step](/images/blog/merge-guide/merge-guide_step-01_upload_800w.webp)

When Google Search Console shows an old image URL still indexed, you know exactly which file to replace without renaming guesswork.

Collaboration rules for agencies

Agencies delivering assets to clients should document naming in handoff PDF — one page in deliverables folder NAMING-CONVENTION.md. Client dev teams inherit structure; arguments drop 90%. Include examples of wrong names with red X — humor helps compliance.

Automation pitfalls

Watch folder scripts that auto-convert on drop sometimes fire twice, creating file.webp and file-1.webp. Debounce script or move source to processed/ after conversion. Failed conversions should log error not silent skip — silent skip produces missing images in production build that CI doesn't catch if MDX references wrong path.

Putting this into practice this week

Pick one workflow from this article and run it on a real task today — not a hypothetical. If the guide covers PDF export, export one document you already need for work. If it covers image naming, rename one messy folder. Knowledge retained from doing beats knowledge retained from reading.

Questions to ask before you delegate

When handing a process to a teammate or virtual assistant, ask: "What would break if you skipped step three?" If they can't answer, the process isn't documented enough. Add the missing step to your internal wiki with a link to this guide and the relevant tool page.

How this connects to the broader site

Utility-first sites win when guides and tools reinforce each other. Bookmark the tool URL alongside this article. Share the article link when onboarding someone who'll use the tool weekly — context reduces support messages asking the same formatting question twice.

Common "it worked yesterday" causes

Software updates change export defaults. Browser updates change PDF print behavior. CDN cache serves old image after you uploaded new asset. When workflows break without code changes, check version changelogs before blaming user error. First troubleshooting step: reproduce in clean browser profile with extensions disabled.

When to escalate to a specialist

Tax, legal, medical, and enterprise security topics in adjacent guides sometimes require professional advice. Articles like this explain operational literacy — not professional services. Escalate when stakes exceed convenience (court filing, audit response, M&A data room, HIPAA-covered PHI).

Quick reference checklist

Before you close the tab, confirm the basics from this guide:

• You know which tool or export path applies to your exact file type
• You've tested output on the device or platform your audience uses
• Filename, margins, or metadata won't embarrass you in a professional context
• You've linked related guides for the next step in the workflow
• Sensitive data stayed in the processing tier your policy allows (browser vs cloud)

Print or save this checklist for onboarding teammates — utility workflows fail from skipped verification, not missing features.

Related reading on this site

Browse the blog category cluster this article belongs to for deeper dives. Tool pages linked in-body are the fastest path from reading to doing. If something in the workflow still feels fuzzy, that's a signal to run one real file through the pipeline and note where friction appeared — then re-read the section that matches that step.

Final reminder

Good document and media hygiene compounds. An extra ninety seconds at export time prevents ninety minutes of rework when a client, professor, printer, or auditor sends the file back. The tools exist to make that ninety seconds painless — use them deliberately rather than hoping defaults match your stakes.