Guide
Name client photo files that survive delivery
Client-project, date, zero-padded sequence — with hyphens, not spaces. Your filename is exactly what your client saves, so make it one that travels well.
Last updated
The convention, up front
Use a predictable pattern for your delivered files: client or project name, date in YYYY-MM-DD format, and a zero-padded sequence number. For example, smith-wedding_2026-06-14_001.jpg or smith-wedding-2026-06-14-001.jpg. Separate words with hyphens or underscores instead of spaces, and avoid special characters entirely.
This structure matters because the filename you export is exactly what your client downloads and saves. When clients download a ZIP archive of their originals, those filenames must unpack cleanly across Windows PCs, Macs, iPhones, and Android phones.
The pattern to copy
Pattern on the first line, a real example on the second.
{client}-{shoot}_{YYYY-MM-DD}_{seq}.jpg
smith-wedding_2026-06-14_001.jpgWhy it matters
Delivered photos cross multiple operating systems and end up stored in client archives for decades. Default camera names like IMG_4021.jpg mean nothing to a client, and they collide as soon as you shoot another event or work with multiple cameras on the same day.
A clear naming pattern organizes files chronologically and makes searching practical years later. When a client contacts you to order a print or ask a question about an image, having distinct, descriptive filenames saves you both from confusing guesswork.
The rules that survive everywhere
- Start with the client or project:
smith-wedding, notfinal selects - Date as YYYY-MM-DD so files sort chronologically and read unambiguously
- Zero-pad the sequence:
001,002, …147— so files sort in order - Hyphens or underscores, never spaces — spaces break in some ZIP extractions, web links and scripts
- No special characters — Windows forbids
\ / : * ? " < > |, and# & %can break links - Keep the extension lowercase:
.jpg,.png
Rename at export, not by hand
Rename your files during export rather than renaming them by hand after the fact. You can configure an automated template using our Lightroom export guide. To draft and preview your naming structure before applying it to a delivery, use the free photo filename planner.
Common questions
Should I keep the camera filenames?
No. Camera names like IMG_4021.jpg are meaningless to clients, collide across different sessions, and make referencing specific images during support questions difficult.
Spaces or hyphens in filenames?
Use hyphens or underscores. Spaces cause errors during ZIP extraction on some operating systems, break when shared in web links, and complicate basic file scripts.
How long can a filename be?
On shoots.page, photo filenames can be up to 255 characters. Keep them much shorter in practice so file paths remain readable and stay well clear of operating system length limits.
Does the client see my filenames?
Yes. With shoots.page photo delivery, downloads are byte-for-byte the exact files you uploaded, meaning your client sees and saves the exact filename you exported.