File organization that works for photographers is simple: keep one predictable folder pattern from camera card to archive, and use a filename that is unique, sortable, and readable without special software. The combination that holds up long-term is date-first folders plus date-first filenames with a shoot or client code and a sequence number.

The goal: find any photo in 10 seconds

A folder and naming system “works” if it does three things every time:

1. Sorts correctly in Finder/Explorer and inside photo apps.
2. Stays unique across years, bodies, cards, and repeat jobs.
3. Survives exports, moves, and delivery without turning into “IMG_4821(3).jpg”.

If your current system fails on any of those, fix it once and keep it boring forever.

Folder structure: one master root, shallow levels

Start with one root folder for everything (on your working drive), and don’t go deeper than you need. Deep nesting looks tidy until you’re in a hurry.

Recommended root

• PHOTOS/

Under that, make one folder per shoot using a date-first format that sorts naturally:

• PHOTOS/2026/2026-02-04_Client-Shoot-ShortTitle/

Why this works:

• Year folders keep the top level from becoming a thousand-item mess.
• YYYY-MM-DD sorts chronologically everywhere.
• The “title” stays human-readable without needing a catalog.

Keep capture files separate from outputs

Inside each shoot folder, keep a consistent set of subfolders. A practical set:

• 00_INBOX/ (temporary: card dumps before you confirm the ingest)
• 01_RAW/ (or 01_CAPTURE/ if you shoot RAW+JPG)
• 02_SELECTS/ (optional, only if you physically separate selects)
• 03_EXPORTS/ (everything you deliver)
• 04_WORK/ (PSD/PSB, layered TIFFs, project files)
• 99_ADMIN/ (shot list, releases, notes, invoices—only if you want)

Key idea: RAW files should never be mixed with exports. When they are, you eventually overwrite something, delete the wrong set, or re-export into chaos.

If you shoot multiple cameras or cards

Avoid splitting by card or camera at the top level. Instead, keep them together and let filenames carry uniqueness.

If you truly need separation (multi-day events, multiple teams), do it one level down:

• 01_RAW/A/ and 01_RAW/B/ (camera bodies)
• or 01_RAW/Day-1/, 01_RAW/Day-2/

Still keep the shoot folder as the single “container” for everything.

Filename rules that prevent future pain

A good filename is:

• Unique
• Sortable
• Portable (works across macOS/Windows/cloud services)

Use only:

• letters A–Z
• numbers 0–9
• hyphen - and underscore _

Avoid spaces if you often upload to web systems (many handle spaces fine, but some don’t). Avoid special characters (&, #, @, /, \, :) and accented letters in filenames.

A naming pattern that covers 95% of real work

Use:

YYYYMMDD_ClientOrShootCode_####

Examples:

• 20260204_ACME_0001.CR3
• 20260204_ACME_0002.CR3
• 20260204_BUDWEDDING_0143.NEF

Why this works:

• YYYYMMDD keeps files sorted even if they’re separated from folders.
• A short code keeps context with the file forever.
• A 4-digit sequence avoids collisions and stays clean for large shoots.

When you don’t have a “client”

Use a shoot code that won’t change later:

• location or event shorthand: BUD_SUNSET, STUDIO_TEST, NYC_STREET
• project name shorthand: PORTFOLIO1

Keep it short. You can store the full description elsewhere (folder name, notes, catalog keywords).

How to handle edits and versions without duplicating chaos

The fastest way to ruin a library is uncontrolled versions: final.jpg, final2.jpg, final_final.jpg.

Use a version suffix that means something, and keep it consistent:

• Master edit files (layered):
  • 20260204_ACME_0001_EDIT_v01.psd
  • 20260204_ACME_0001_EDIT_v02.psd
• Delivery exports (flat):
  • 20260204_ACME_0001_WEB_sRGB_2048px.jpg
  • 20260204_ACME_0001_PRINT_8x10_300dpi.jpg

This stays readable and searchable. If you only ever deliver one set, you can simplify:

• 20260204_ACME_0001_DELIVER.jpg

But don’t call it “final”. Call it what it is.

Keep RAW filenames stable; version the derivatives

A common mistake is renaming RAW files multiple times after edits start. Pick your RAW name once (ideally on ingest), then never change it. Put all future meaning into:

• sidecars/catalog metadata, and/or
• derivative filenames in 04_WORK/ and 03_EXPORTS/

This prevents broken links in catalogs and missing-file headaches.

Ingest: rename once, immediately, automatically

The best time to rename is at ingest (copying from card to drive). Many tools support template-based renaming using variables (date, time, camera serial, etc.). If you rename at ingest, you avoid:

• duplicate IMG_0001 from different cameras
• mixed camera prefixes (DSC_, IMG_, etc.)
• the temptation to batch-rename later (when edits already reference files)

If you shoot multiple bodies and need bulletproof uniqueness, add a short camera token:

YYYYMMDD_Code_Cam##_####

• 20260204_ACME_CamA_0001.CR3
• 20260204_ACME_CamB_0001.CR3

Or use the last digits of the camera serial if your tool supports it.

“Selects” folder: only if it matches your behavior

Some photographers love a physical selects folder; others only flag inside Lightroom/Capture One. Either can work, but don’t mix mental models.

Two clean options:

Option A: No selects folder (simpler)

• All capture files stay in 01_RAW/
• Picks live as ratings/flags in your catalog
• Exports go to 03_EXPORTS/

Option B: Physical selects (if you regularly hand off subsets)

• Copy (not move) chosen RAWs into 02_SELECTS/
• Keep original capture set untouched in 01_RAW/
• Now you can share a subset without breaking the primary set

If you “move” files out of capture folders, you’re more likely to break links in catalogs and lose track of what’s complete.

Consistency beats cleverness

You do not need a different system for weddings, products, sports, and travel. You need one system that absorbs all of them.

If you’re tempted to change patterns for different genres, stop and adjust only the shoot code and folder title. Everything else stays identical.

A quick checklist to validate your system

Pick any random photo you shot 18 months ago. Can you:

• locate the shoot folder without searching inside image software?
• identify the client/event from the folder name alone?
• open 03_EXPORTS/ and immediately see what was delivered?
• see the relationship between RAW, edit master, and export from filenames?

If any answer is “no,” your structure is missing either:

• a stable shoot container (folder), or
• stable, descriptive derivatives (names), or
• a predictable exports location.

Why does this matter

Because the cost of disorganization shows up later—when a client asks for a re-export, a publication requests a specific size, or you need to prove which image was delivered and when.

Sources

• DPBestflow (project): file naming guidance (dpbestflow.org)
• Adobe Help Center: Lightroom Classic catalog and organization basics (helpx.adobe.com)
• Camera Bits documentation: Photo Mechanic variables and batch renaming tools (camerabits.freshdesk.com)