How Professional Photographers Name, Organize, Back Up, and Deliver Their Photos
After more than 20 years as a photographer, I’ve learned that taking the photograph is only part of the job.
You also need to be able to find it five years later.
That becomes surprisingly difficult when you’ve photographed hundreds of clients, created thousands of folders, and accumulated more images than you’d ever admit publicly.
A good photography workflow doesn’t need to be complicated. It needs to be consistent.
Here’s a simple system for naming, organizing, backing up, and delivering photographs that works whether you photograph portraits, weddings, commercial campaigns, or personal projects.
Start With a Consistent Folder Structure
There is no single “correct” way to organize photographs.
The best system is the one you can understand immediately without having to remember what you were thinking three years ago.
I prefer organizing projects chronologically, then by client or project:
Year → Client → Project → Files
For example:
2026 / Client Name / Campaign Name / 01 RAW / 02 Selects / 03 Retouched / 04 Delivery
The numbered folders keep everything in the same order from project to project.
01 RAW
Original files from the camera. These should remain untouched. I never want my only copy of an original photograph mixed in with exports, edits, or client deliverables.
02 Selects
The photographs that make it through the initial edit or culling process.
03 Retouched
Finished working files, layered files, or final high-resolution masters.
Depending on your workflow, this may include PSD, TIFF, or other working files.
04 Delivery
The actual files delivered to the client.
For some jobs, I’ll divide this further into folders such as:
HIGH RES
WEB
SOCIAL
The exact folders matter less than using the same logic on every project.
When every job follows a predictable structure, you don’t have to reinvent your workflow every time you pick up a camera.
How Should Photographers Name Their Files?
Your camera probably gives you something like:
DSC_4837.NEF
or:
IMG_8392.CR3
That works while the photograph is sitting on a memory card.
It becomes significantly less useful when you have hundreds of thousands of photographs in an archive.
I prefer filenames that give me useful information at a glance.
A simple structure might look like:
client-project-date-image-number.jpg
For example:
acme-summer-campaign-2026-08-14-001.jpg
For a portrait:
john-smith-portrait-2026-08-14-001.jpg
For a wedding:
smith-wedding-2026-08-14-001.jpg
You don't necessarily need every piece of information in every filename. The goal isn't to create the world's longest filename.
The goal is to make it predictable, unique, and understandable.
Hyphens, Underscores, or Spaces?
Photographers spend far more time debating this than they probably need to.
For most workflows, consistency matters more than punctuation.
For files being published on the web, I generally prefer hyphens:
commercial-portrait-photography-jeff-rojas.jpg
Google recommends hyphens rather than underscores as separators in URLs, and descriptive filenames can also provide search engines with additional context about an image.
That doesn't mean stuffing every keyword you can think of into a filename.
Name the photograph descriptively when it makes sense.
For internal files, you can use hyphens, underscores, or another consistent convention that works with your workflow.
What I try to avoid is chaos:
FINAL_FINAL_USE_THIS_ONE_v7_NEW.jpg
We’ve all been there.
The solution isn't a perfect naming system. It's having a system before you need one.
Separate Your Originals From Your Deliverables
One of the easiest ways to make an archive confusing is to put RAW files, Photoshop files, JPEG exports, social-media crops, and client deliverables into the same folder.
Separate them.
Your original capture is one thing.
Your working file is another.
Your final master is another.
And the JPEG you exported at a specific size for Instagram is another.
Treat them accordingly.
This also makes it considerably easier to return to an old project.
If a client contacts you three years later asking for a new crop, larger file, or additional usage, you know exactly where the master file lives.
Name Client Deliverables Professionally
Your internal naming system doesn't necessarily need to be your client's naming system.
Before delivery, think about how the client will actually use the photographs.
A commercial client might appreciate:
brand-campaign-product-001.jpg
A wedding client may simply need:
rojas-wedding-001.jpg
Nobody wants to receive:
DSC_9374-Edit-FINAL-v2.jpg
The filename becomes part of the deliverable.
It's a small detail, but small details are often what make a professional workflow feel professional.
Don't Confuse Syncing With Backup
This is one of the more important lessons in this entire article.
Cloud storage and synchronization are not automatically the same thing as having a backup strategy.
If you accidentally delete or overwrite something and that change synchronizes across your devices, your beautifully organized folders aren't going to save you.
A commonly recommended approach is the 3-2-1 backup strategy:
3 copies of your data
2 different types of storage
1 copy stored off-site
Your exact setup will depend on the amount of photography you produce and how long you're responsible for retaining it.
The important part is redundancy.
If your entire photography career exists on one laptop or one external hard drive, you don't have an archive.
You have a single point of failure.
Build Your Archive for the Photographer You'll Be Five Years From Now
This is the part people underestimate.
When you're starting out, you might remember every shoot you've done.
Twenty years later, you won't.
You may remember the photograph but not the year.
You may remember the client but not the project.
You may remember someone's face but have absolutely no idea what their name was.
That's why good organization compounds.
Every properly named project makes your archive more valuable.
Every consistent folder makes future searches easier.
And every redundant backup makes it more likely that the work you're creating today will still exist decades from now.
My Simple Photography File Workflow
If you want to simplify everything in this article, start here:
1. Create a consistent folder structure for every shoot.
Year → Client → Project → RAW / Selects / Retouched / Delivery
2. Give finished photographs descriptive, predictable filenames.
client-project-date-number.jpg
3. Keep original files separate from working files and exports.
4. Rename client deliverables so they're clean and understandable.
5. Maintain multiple copies of important files, including an off-site backup.
That's it.
You don't need an elaborate digital asset management system to become more organized.
You need a system simple enough that you'll actually use it.
Final Thoughts
Photographers naturally obsess over the visible parts of the job: cameras, lighting, composition, retouching, color, and the final image.
But a professional photography career is also built on all of the invisible systems behind those photographs.
File organization is one of them.
Your system doesn't need to look exactly like mine. It should make sense for the type of work you create, the clients you serve, and the way you work.
Just make it consistent.
Because the real test of a photography archive isn't whether it looks organized today.
It's whether you can find the photograph you're looking for years from now.