A useful filename helps distinguish projects and exported versions without depending on a folder being remembered forever. When a file lands in an email or a download folder, the name is often the only context it has.
What to do
Choose a stable project identifier, date convention and sequence. Test the naming scheme on a small copy set before applying it broadly. Keep original-to-export relationships clear.
Think about how you will search. If you often look for photos by client, date or event, those words should appear in the name in a consistent position.
Building a pattern
A reliable pattern tends to follow a few habits:
- Date format that sorts: year first, then month, then day, so files sort in order.
- Short project code: a few characters or a short word, not a long sentence.
- Sequence number with leading zeros: so that file ten does not sort before file two.
- Safe characters: letters, numbers, hyphens and underscores, avoiding spaces and symbols that some systems reject.
- Consistent separators: choose one style and stay with it.
- Version suffix: a short tag for the use, such as web or print, on exported copies only.
Write the pattern down in a short note so you or a colleague can follow it months later.
A mistake to avoid
Renaming files outside a catalog can break its references. Use the catalog’s supported workflow and preserve a backup before a large reorganization. Many catalog programs can rename on import or from within the program.
A detail worth checking
Include a version or delivery identifier when exports serve different purposes. A filename should help distinguish a web copy from a print-ready copy without pretending that a renamed file has changed its actual dimensions.
Try this practical check
Try a pattern such as project-date-sequence on one completed session. Search for an image using only those identifiers and revise any ambiguous part. Ask a colleague whether they can find a file from the name alone.
Common questions
Should I keep the camera’s original numbers?
Many people keep them as part of the name to preserve the link to the original capture. Decide this early and apply it consistently.
Is it safe to rename lots of files at once?
Do it on a copy first, and use the tool your catalog supports. Keep a backup until you are sure everything still links.
How long should a filename be?
Short enough to read easily and fit in lists, long enough to identify the project and version.
Related reading
3-2-1 Backup Rule: A Simple Plan for Your Files (2026)
