Guides

How Photo File Delivery and Naming Conventions Work

A photo file delivery and naming convention is the system that decides how finished images reach you and what every file is called before it lands in your hands. The honest version is simple: descriptive, lowercase, hyphenated filenames, delivered in a predictable folder structure, in both a high resolution master and a web ready copy. Everything past that is a variation on the same spine.

Most teams skip this and pay for it later. Camera files arrive named IMG_4821.jpg or DSC_0098.NEF, dumped into one flat folder, and six months on nobody can find the hero shot. A convention is cheap to set up once and it compounds every time you reuse the library.

What a naming convention actually controls

A naming convention is a repeatable rule for turning a camera default into a human readable name. The goal is a filename that tells you what the image is without opening it, sorts correctly in any file browser, and never trips up a web server.

Lowercase only. Mixed case causes duplicate files on case sensitive servers and silent broken links when a reference points to Hero.jpg but the file is actually hero.jpg.

Hyphens between words, never spaces or underscores. Spaces become %20 in a URL, and underscores are harder for search engines to read as separate words.

No special characters. Drop apostrophes, ampersands, commas, and accented letters. They break on some systems and have to be escaped on the web.

A fixed order of fields, usually project, then subject, then a sequence number. That order is what makes a folder sort into something you can scan at a glance.

What a clean file delivery looks like

Delivery is the other half of the job. The naming rule covers what each file is called. Delivery covers the formats, the sizes, and the folder tree they sit in. You want master files you can archive and lighter copies you can publish, kept clearly apart so nobody uploads a forty megapixel original to a web page by accident.

The original camera files, RAW or otherwise, kept in their own archive. You rarely touch them, but they are the only true source if a master is ever lost or needs reworking.

A master folder holding full resolution, lightly compressed JPEG or TIFF files for print and long term archiving.

A web folder holding resized, compressed images sized to how they will actually be used, usually a small fraction of the master in file size.

Modern formats where they earn their place. A WebP or AVIF copy for the web alongside a JPEG fallback keeps pages light.

A plain text or spreadsheet manifest listing every file, its subject, and any usage note. This is the index you will thank yourself for having.

Resolution and format, briefly

Shoot and archive at full resolution. Publish at display resolution. The master is your insurance policy, and the web copy is what visitors download. Keeping the two in separate folders means the right file gets used without anyone having to stop and think about it. Display resolution is not a single number. A full width hero needs more pixels than a thumbnail, and screens that pack extra pixels want roughly double the dimensions you see on the page to stay crisp. Export the web copy at the size it will actually be used, then let the page serve smaller versions to smaller screens.

Build a pattern you can actually follow

The best convention is the one your whole team remembers. Keep the field order short and fixed. A pattern that works for most service businesses reads project, subject, variant, sequence.

project: a short slug for the shoot or job, like spring-patio.

subject: what is in the frame, like firepit or crew-install.

variant: an optional qualifier, like wide, detail, or before and after.

sequence: a zero padded number so 01 sorts ahead of 10, like 03.

Put together, that gives you spring-patio-firepit-wide-03.jpg. You can read it, a search engine can read it, and it sorts cleanly next to its siblings. Pick the fields once, write them down, and apply them to every shoot from then on.

Why filenames and delivery feed your findability

Descriptive filenames are a small but durable signal that search engines read, and they matter even more for accessibility and findability. A naming convention is not only an internal tidiness exercise. It is the raw material for alt text, image sitemaps, and the way images get found in both classic search and AI answers.

Search engines read the filename as a hint about the image content. hero.jpg says nothing, while spring-patio-firepit-wide.jpg says plenty.

Clean filenames become clean URLs, which are easier to cite, share, and crawl.

A manifest with per image subjects makes writing accurate alt text fast, and alt text is what both screen readers and image search rely on.

Consistent naming prevents duplicate uploads, a quiet cause of index bloat and wasted crawl budget.

Common mistakes that cost you later

Most delivery problems trace back to a handful of habits. None of them are hard to fix once you have seen the damage they do.

Leaving camera defaults in place. IMG_4821.jpg tells no one anything and guarantees a renaming session right before a launch.

One flat folder with no master versus web split, so the first file anyone grabs is whatever was easiest to find.

Dates in a format that sorts wrong. If you use dates at all, use year, month, day, so files order chronologically on their own.

Renaming after publishing. Once a file is live and linked, changing its name breaks the link and every reference to it.

The handoff, start to finish

When a shoot is delivered well, the handoff is boring, and boring is the goal. Here is the sequence that keeps a library usable for the long run.

Agree the convention before the shoot, not after. Rename in a batch during the cull, while you still remember what each frame is.

Deliver master and web folders separately, each using the same filenames, so a web copy is always traceable back to its master.

Include the manifest and any release or usage notes in the same package, not in a separate email.

Store the whole delivery somewhere versioned, so the next person inherits the system instead of reinventing it.

Questions

What is a photo file delivery and naming convention?

It is the agreed system for how finished images are handed over and what each file is called. In practice that means lowercase, hyphenated, descriptive filenames delivered in a predictable folder structure, with a full resolution master and a lighter web copy. Setting it once keeps a shoot usable long after the photographer has moved on.

Should I use underscores or hyphens in image filenames?

Hyphens. Search engines treat a hyphen as a space between words and tend to read an underscore as joining words into a single token. Spaces are worse still, because they turn into %20 inside a URL. Lowercase and hyphenated is the safe default everywhere.

What file formats should a photographer deliver?

Two tiers. A full resolution master in lightly compressed JPEG or TIFF for print and archiving, and a resized, compressed web copy, ideally with a modern format like WebP or AVIF alongside a JPEG fallback. Keeping the tiers in separate folders stops anyone publishing a giant original by mistake.

Do descriptive filenames actually help with SEO?

In a small but durable way, yes. A descriptive filename gives search engines and AI systems a plain hint about the image, feeds accurate alt text, and produces clean URLs that are easy to crawl and cite. It will not outweigh your content, but it costs almost nothing and compounds across an entire library.

When should I rename the files, before or after publishing?

Before. Rename during the cull, while you still remember each frame, and never once a file is live. After an image is published and linked, changing its filename breaks the link and any reference to it. Name it right the first time and the problem never appears.