A photo folder structure that still works at 10,000 shoots

Most folder structures work fine for two years and then quietly stop working. The top level fills up, the names start disagreeing with each other, and finding a job from 2023 becomes a search. This is the tree we would build from scratch, written out so you can copy it, along with the reasoning behind each level, because the reasoning is what keeps it standing at job number 10,000.

What scales actually means for folders

Almost any structure works when you have shot thirty jobs. The real question is what it does at three thousand. A structure scales if all five of these stay true, and it fails the moment one of them stops being true:

• Findable cold. You can locate any job in about a minute, three years later, while on the phone, without opening a catalog.
• Small listings. No folder ever holds more than a couple of hundred children, which is roughly where file browsers, file dialogs and sync clients start to feel slow.
• Nothing gets renamed. A job changes status many times. A name that has to change along with it will eventually be wrong, and every link pointing at it breaks when it does.
• Rules written once keep working. A backup job, a sync rule or a script you write this year still works in five, because the shape of the path never changes.
• Teachable in a minute. A second shooter or an assistant can put files in the right place after one explanation, with no follow up questions.

Most homemade structures pass the first two and fail the last three. The usual cause is a folder name carrying information that keeps changing, which is the failure this whole article is designed around.

The tree, written out

One root. Everything hangs off it. Copy this exactly, or rename the levels to suit yourself, but keep the shape and keep the depth.

• Photography, the single root, on your working drive
  • 1-Inbox, where cards land, and where nothing stays more than a week
  • 2-Jobs, current and recent work
    • 2026
      • 2026-08-12_ramirez_wedding
      • 2026-08-19_okafor_newborn
    • 2025
  • 3-Archive, delivered and paid jobs, same year folders, on slower and cheaper storage
    • 2024
    • 2023
  • 4-Personal, your own photographs, never mixed into client work
  • 5-Business, logo files, your own headshots, blank contracts, price sheets, insurance documents
  • 6-Catalogs, Lightroom or Capture One catalogs and their previews, kept out of the job folders so a job can move without dragging a catalog with it

And here is one job folder, expanded. Every job gets all six subfolders, even when two of them stay empty all year:

• 2026-08-12_ramirez_wedding
  • 01-raw, everything off every card, from every body, in one place
  • 02-selects, the shortlist, or nothing at all if your tool marks picks in place
  • 03-edited, finished masters at full size
  • 04-delivered, exactly the files the client received, at the size they received them
  • 05-docs, contract, invoice, timeline, shot list, questionnaire
  • 06-extras, album layouts, print orders, social crops, anything made months later

The number prefixes exist for one reason. They force the order you work in, top to bottom, in every file browser on every machine, instead of letting the alphabet decide that delivered comes before raw.

Why the year folder is not optional and the month folder is

The year bucket is doing real work, and it is the level most people skip. Put every job you will ever shoot into one folder and that folder eventually holds thousands of children. Long before you hit ten thousand, opening it stops being instant, save dialogs pause, and cloud sync clients start behaving strangely.

A year folder caps the problem permanently. An ordinary working photographer shoots somewhere between a few dozen and a couple of hundred jobs a year, so a year folder stays comfortably small for the entire life of the business, and twenty years of work is twenty folders at that level. That is a structure you can scroll.

Months are where people overshoot. A month level creates empty folders through your slow season, adds a click to every single path you will ever type, and gives you nothing that a date first folder name has not already given you, since those sort by month inside the year anyway. One level of bucketing, and it is the year.

The honest exception: if you shoot most days of the week, real estate, school or high volume events, a month level starts to earn its place. Judge it by the listing, not by the calendar. When a year folder has grown past a few hundred jobs and you find yourself scrolling to find one, add months. Otherwise leave it alone.

The archive branch matters just as much for a different reason. Splitting working jobs from finished ones means your fast drive only ever holds work in progress, and the bulk of your library can sit on cheap capacity. Our breakdown of cloud storage for photographers covers what belongs in hot storage and what belongs in cold.

The job folder name: three fields and nothing else

2026-08-12_ramirez_wedding. Date, client, type. That is the entire specification, and its value comes from having no fourth field.

What never goes in the name:

• Status. final, done, EDITED, v2, DELIVERED. Status changes, so it belongs to where a folder lives, not to what it is called.
• Money or package. premium, 8hr, deposit-paid. That is your booking system's job, and it is the field most likely to change after you type it.
• Spaces and slashes. Spaces break scripts, some upload tools and some sync clients. A slash is not a character at all, it is a directory separator in disguise, and it will be quietly turned into something else.
• The year twice. The year folder already said it. Repeating it just makes every path longer to read.

The rule underneath all four is one sentence: if a fact about a job can change, it does not belong in the name. Names carry only what was fixed on the day you shot. Everything else is a location, a tag, or a row in your booking system.

File names inside a job are a separate question with a separate answer, since they need to stay unique once a file escapes into an email or a print order. That pattern is in the photo file naming system.

Six rules that keep it standing after year three

The tree is the easy part. These are the habits that stop it drifting back into a mess.

1. One root, no exceptions

If a photo lives outside the root, it does not exist. Desktop and Downloads are not storage, they are waiting rooms. The practical payoff is that your entire backup job collapses into a single rule, back up the root, which is the only kind of rule anyone actually keeps running. The 3-2-1 backup workflow is the version to point at it.

2. The same subfolders in every job, including the empty ones

Predictable beats efficient. An empty 06-extras folder costs you nothing. An unpredictable job folder costs you a search every time you open one, and the searches are what wear you down.

3. Never nest by shoot type at the top level

Types get reclassified. An engagement session becomes part of a wedding's story, a portrait booking turns into a brand shoot halfway through, and a job that is genuinely two things has no home at all. Type is a field in the name, where it can be wrong without breaking anything.

4. Never nest by client at the top level

You will remember the month before you remember the surname. Client folders also scatter repeat clients across two spellings, and they give you an alphabetical list of thousands of names to scroll through when what you actually wanted was last September.

5. Organize by job, never by device

Card 1, Card 2, drone and B-cam describe your gear, not your work. Merge everything into 01-raw at ingest and capture time keeps it all in order, a point the RAW file management guide makes well. The one sane exception is a second shooter: give them a named subfolder inside 01-raw, because whose frame it was is a fact you will want later. Second shooter selection standards covers how to keep their work consistent with yours.

6. Status is a location, not a name

When a job is delivered and paid it moves from 2-Jobs to 3-Archive. It is not renamed. Every sidecar, catalog reference and link that mentions that folder name still points at the same name, so the only thing that changed is which drive it sits on. This single rule is what lets the structure survive a decade.

Where the awkward files go

A structure is only as good as its answers for the odd cases, and these are the ones that come up every season. Decide them once here and you never think about them again.

• Photos the client sends you. Guest phone shots, a logo, a reference image. Those go in 05-docs, never 01-raw. They are not your captures and they must not enter your selection pass.
• A reshoot. A new job folder with the reshoot date, plus a line in 05-docs pointing back at the original. Do not bury it inside the first job, because it happened on a different day and the date is your index.
• Personal frames shot on a job day. They go to 4-Personal. Mixing them is how a client's folder ends up containing your lunch.
• A print order two years later. 06-extras inside the original job, even though that job now lives in the archive. The job folder is the unit of work forever, including for work that happens long after delivery.
• A multi day job. One folder, dated from the first day. A wedding with a rehearsal dinner the night before is one job, not two.
• Two jobs on the same date. The client field separates them, which is the reason the client field exists at all.
• A job that never happened. Keep the folder with the documents in it and no images. A cancellation is still a record, and a deposit dispute is much easier to answer with the paperwork where you expect it.

Adopting it without losing a weekend

Start with the next job. Not the oldest one, not the whole library, just the next card you put in a reader. The structure has to prove itself on live work before you owe it any migration effort.

If you already have a large messy library, that is a different job with a different method, and hand sorting it is the wrong answer. The triage plan is in how to organize thousands of photos you already have, which handles it in tiers so you never spend a Saturday on files nobody will ask for.

Two practical warnings for the move itself. First, if you use Lightroom, move folders from inside Lightroom's Folders panel rather than in Finder or Explorer, or the catalog loses track of where everything went. Second, if your picks come from an app rather than from the catalog, make sure the handoff writes to the right place before you move anything, which we walked through in exporting selections to Lightroom.

One last note on tools, since a structure is only safe if the software you point at it respects it. Kepla clears the obvious misses and marks each one with a reason. It never deletes, moves or renames a file, so a tree like this one stays exactly as you built it. The picking app for iPhone, iPad and Mac is still being built, and while we build it the booking page is live and free.

The measure of all this is not how the tree looks in a screenshot. It is whether, in 2031, a client can call about a shoot from tonight and you can open the folder before they finish the sentence.

FAQ