Workflow & Guides Updated August 16, 2026 · 11 min read
A structure is only good if it still makes sense after ten thousand shoots, three computers and one hard-drive failure. This is the one that does — including the multi-camera event version, and how to rebuild an existing mess into it without moving a file by hand.
A messy hard drive kills creativity. When you are staring at a Finder window filled with New Folder (2), Final_Edit_V3 and loose .JPG files, your brain spends its energy on digital clutter instead of on the edit.
But "be organised" is useless advice. What you need is a single structure you can apply without thinking, that works whether you shoot landscapes alone or a wedding with a second shooter, and that still reads clearly when you open the drive in 2046. That structure has three properties: it is chronological, it is shallow, and the computer builds it for you.
Almost every photographer's first instinct is to organise by client or by project: Nike_Commercial/, Smith_Family/, Iceland_Trip/. It feels natural, and it fails within two years, for one reason: you always remember roughly when, and rarely exactly what it was called.
Six months later you are looking for "that corporate thing in the spring". You do not remember whether you filed it under the client name, the agency name, or the product. But you know it was spring. A date-first tree turns that vague memory into a two-click lookup. A client-first tree turns it into a search.
Dates have a second advantage that matters more over time: they are already inside the files. Every camera writes a capture timestamp into EXIF. That means a date-based tree can be rebuilt automatically from the photos themselves, forever, on any machine. A client-based tree exists only in your head — lose the folder names and the information is gone.
Client and project names do not disappear. They go in the folder name, after the date, where they are searchable but not structural.
2026_Photos folder. Finding a file means endless scrolling, and the folder eventually gets slow to open.Nike_Commercial or Smith_Family. Your computer sorts alphanumerically, so without a date prefix your projects scatter randomly across the drive.Raw_Files/ folder makes colour matching tedious and culling slower, because you cannot isolate one body's output.2026/05/25 folders with no project context, and if the catalog corrupts you are left with a tree you did not choose.Two levels above the project, and a numbered lifecycle inside it.
The root directory:
2026/ Master year 2026-01/ Month 2026-02/ 2026-03/
Inside the month, one folder per shoot:
2026-05-25_Nike-Ad_AgencyName/ Date + context
01_RAW/
Sony_A7IV/
Fuji_X100VI/
02_Video/
03_Audio/
04_Assets/ Logos, music, briefs
05_Project_Files/ Catalogs, NLE projects
06_Exports/
High_Res/
Web/
YYYY-MM-DD prefix forces oldest-to-newest ordering in every file manager on every operating system, with no configuration.01_ stays at the top, 06_ stays at the bottom, and the folder reads in the order you actually work.01_RAW is irreplaceable. Everything else can be regenerated, which makes backup decisions obvious — see the photo backup workflow for what that means in practice.A wedding breaks the standard template, because a wedding is not one shoot — it is four, back to back, covered by two people. Twelve hours of coverage across two shooters and several cards produces four to eight thousand RAW files that all belong to the same date. Sorting them by day gets you one enormous folder, which is where you started.
The fix is to insert a moment level between the event and the camera:
2026-06-14_Smith-Johnson/
01_Getting-Ready/
Canon-R5/
Sony-A7IV/
02_Ceremony/
Canon-R5/
Sony-A7IV/
03_Portraits/
04_Reception/
05_Exports/
Client_Gallery/
Print/
Three things follow from this, and they are the whole reason event photographers bother:
Nobody wants to sort four thousand files into moments by hand, and you should not have to: the moments are already implied by the timestamps. FolioSort's Events feature takes the day's timeline — Getting Ready 10:00–13:00, Ceremony 14:00–15:30, Portraits 16:00–17:30, Reception from 18:00 — and files every frame from both cards into the right moment folder by EXIF capture time. You define the schedule once; the app does the rest in seconds, and your Lightroom import is already structured.
This is the failure that ruins event structures, and it is worth its own section because it is silent. If your camera and your second shooter's camera are four minutes apart, every timeline-based sort is wrong by four minutes — and at the boundary between the ceremony and the portraits, that means frames land in the wrong folder.
Two defences, in order of preference:
Correct the offset before you sort into moments, not after. Sorting first and shifting second leaves files sitting in folders that no longer match their own timestamps, which is worse than the original problem because it now looks correct.
DSC_xxxx or _IMG_xxxx names. If a catalog corrupts and you have to relink, matching original filenames is what saves you. Rename exports, never originals.01, 02, 10 — otherwise 10 sorts before 2.2026-05-25, not 25-05-2026 and not 05/25/2026. It is the only format that sorts correctly and the only one that is unambiguous to a reader in another country.2026-05-25_Nike-Ad keeps chronological order while staying searchable by name.Do not attempt this by hand. Years of accumulated photos cannot be dragged into shape in an evening, and half-finished migrations are how files get lost.
The mechanical version: point an EXIF-based organiser at the old Misc_Photos folder and let it read the capture date embedded in each file, then rebuild the Year → Month → Day tree from that. FolioSort does this with a preview of the resulting tree before anything is written, and in Copy mode so the original folder stays untouched until you are satisfied — see organising photos by date taken.
Two things to check before you run it on everything:
.json sidecars, so a plain date sort files your whole library under the day you downloaded it. Repair the metadata first — the Takeout import handles that step.Macintosh HD/Users/Desktop/Untitled Folder/DSC_0041.ARW — unsearchable, unbacked, one accidental drag from gone.External_SSD/2026/2026-05/2026-05-25_Nike-Ad/01_RAW/Sony_A7IV/DSC_0041.ARW — you can find it from the date alone, and the backup rule for 01_RAW is obvious.The structure is only half the decision. The other half is which disk it sits on, and getting that wrong is how people end up with two competing trees.
2026/ across whole and create 2027/. Nothing is reorganised, because the structure is identical on both.The rule that keeps this honest: the same path should work on every disk. If your archive uses 2024/Weddings/ while your working drive uses 2026/2026-06/, you now maintain two mental models and will eventually file something in the wrong one. Move the tree, do not redesign it.
Mixed shoots are where most structures quietly break, because video does not behave like stills. Clips have no meaningful "capture date" in the sense a camera JPEG does — some formats write it, some write only a file creation time, and drone footage often carries a flight log alongside the media rather than inside it.
The tree does not need to change. The 02_Video/ slot already exists; what changes is what goes underneath it:
2026-05-25_Nike-Ad/
01_RAW/
02_Video/
A-Cam_FX3/
Drone_Mavic3/
Proxies/
03_Audio/
Lavs/
Ambient/
Two habits keep it clean. Keep proxies inside the project, not in a global scratch folder, so deleting the project deletes its proxies with it. And keep drone media in its own subfolder rather than merged with the A-camera — the file numbering restarts per flight and will collide with your main body's clips otherwise. If drone work is a large part of what you shoot, there is a longer treatment in organising drone footage.
Should the year folder live on the drive root or inside a Photos folder?
Either, as long as it is consistent and the path is short. What matters is that the year is the first level that varies. Putting Photos/2026/ on an external SSD is fine; putting 2026/ inside four levels of nesting is not.
What about ongoing personal photos that are not projects?
Drop the project level. Personal libraries work well at Year → Month, optionally with a camera or location level below. The event and client structure only earns its complexity when you are delivering work to someone.
How do I handle a shoot that spans midnight?
File it under the date it started, and let the folder name carry the truth: 2026-12-31_NYE-Party. Splitting one event across two date folders because the clock rolled over is the one case where strict chronology works against you.
Should the second shooter's files go in a separate camera folder or a separate shooter folder?
Camera body, not person. The body is written into EXIF and can be sorted automatically; the person is not. If you need to know who shot what, the body tells you, as long as you do not swap kit mid-day.
How deep should subfolders go?
Four or five levels maximum. Beyond that, path lengths start causing errors on Windows and with some cloud backup clients, and navigating becomes slower than searching.
Do I need software for this, or can I just be disciplined?
You can build it by hand and many people do. Discipline fails at exactly the wrong moment — the night you get back from a twelve-hour wedding with eight thousand files. Automating the tree means the structure survives the days you have no energy for it.
Download FolioSort free. Organize up to 100 files per operation with no account required.