There is no universally correct way to organize photos. There is, however, a way that survives contact with reality — and several that look elegant on paper and fall apart in about eight months.
The failure mode is always the same. Someone builds a beautiful nested system of categories, uses it faithfully for a while, then hits a photo that belongs in three folders at once, hesitates, drops it in Downloads "for now," and the system quietly dies.
The structures below are the ones that don't do that.
The test a good structure has to pass
Before comparing options, here's the standard. A folder structure works if:
- Every photo has exactly one obvious home. No judgment calls, no "well, it's kind of both."
- Filing takes under three seconds per batch. If you have to think, you'll stop doing it.
- It works without special software. If your library only makes sense inside one app, you're one subscription cancellation away from chaos.
- A stranger could find something in it. Which matters more than you'd think — someday a family member will inherit this.
Topic-based structures fail test one immediately. A photo of your daughter's birthday party at the beach with the dog in it belongs in Family, Vacations, Events, and Pets. That's why they collapse.
Structure 1: Year / Event (the default recommendation)
This is what most people should use.
PHOTOS/
2023/
2023-01 New Year at Mom's/
2023-03 Ski Trip/
2023-06 Graduation/
2023-07 Nova Scotia/
2023-misc/
2024/
2024-02 Kitchen Renovation/
2024-05 Emma Wedding/
2024-misc/
2025/
2025-misc/Why it works: every photo has exactly one date, so the top level is never ambiguous. The YYYY-MM prefix on event folders forces chronological sorting inside the year, so a folder list reads like a timeline.
The misc folder is the secret. Most photos aren't events. They're a Tuesday, the dog on the couch, a receipt you photographed. Without a catch-all, those photos have nowhere to go and the system stalls. With one, you never hesitate — if it isn't clearly an event, it goes in misc.
Who it's for: families, casual shooters, anyone with fewer than about 50,000 photos.
Structure 2: Year / Month (the low-effort version)
PHOTOS/
2024/
2024-01/
2024-02/
2024-03/
...No event names at all. Everything sorts by month automatically, which means most photo software can do the entire job for you with zero human input.
Why it works: it's the only structure that requires literally no decisions. Import, and the software files it. That makes it the right pick for anyone who has abandoned two previous organization systems.
The tradeoff: you lose the ability to scan a folder list and see "oh, that was the Nova Scotia trip." You're relying on your memory of roughly when things happened, plus search.
Who it's for: high-volume shooters, people who've failed at organizing before, and anyone whose photo app has good search and face recognition (which does most of the finding work anyway).
A good middle ground: use Year/Month as the automatic default, then rename only the two or three folders per year that were genuinely memorable. 2024-05 becomes 2024-05 Emma Wedding. Ten seconds of effort, most of the benefit.
Structure 3: Year / Event with a Projects branch (for people who shoot for a reason)
If some of your photos are personal and some serve a purpose — a business, a blog, a hobby — split those apart at the very top.
PHOTOS/
Personal/
2024/
2024-05 Emma Wedding/
2024-misc/
Projects/
Etsy Product Photos/
2024-03 Spring Collection/
2024-09 Holiday Listings/
Blog/
Kitchen Renovation Series/
House Records/
Roof Damage 2024-04/
Appliance Serial Numbers/Why it works: work photos have a completely different lifecycle from personal ones. You edit them, version them, delete them when a listing ends. Mixing them with your family archive means your backup strategy has to treat 400 shots of the same coffee mug as precious.
Under Projects, chronology often isn't the right axis — organize by project, then by date within it.
Who it's for: small business owners, sellers, bloggers, hobbyists documenting anything ongoing.
Structure 4: The photographer's structure (capture / select / export)
If you shoot RAW and edit, you have three genuinely different classes of file and they should not share a folder.
PHOTOS/
01-Originals/
2024/
2024-05-18 Hendricks Wedding/
RAW/
JPG/
02-Working/
2024-05-18 Hendricks Wedding/
catalog + sidecars
03-Delivered/
2024-05-18 Hendricks Wedding/
full-res/
web/
client-proofs/Why it works: 01-Originals is write-once and never touched again — which means it's the only folder that truly needs bulletproof backup. 02-Working is churn. 03-Delivered is what you'd need to re-send a client in three years, and it's small.
Being able to say "back up folder 01 forever, folder 03 for seven years, folder 02 weekly" is a real operational advantage once your library gets big.
Who it's for: anyone shooting RAW, event photographers, sellers producing a lot of edited product imagery.
What to do about videos
Two schools of thought, and both are defensible.
Mixed in: videos live in the same event folders as photos. Chronologically honest, and how your phone naturally exports things. Downside: your video files are 50x the size of your photos, which makes folder sizes wildly uneven and complicates syncing.
Split at the top: a parallel VIDEOS/ tree with the same year structure. Makes it easy to keep video off a laptop's small SSD while photos sync everywhere.
For most people, mixed in is fine until video becomes a real portion of the library. Then split.
Naming the folders
Two rules cover it:
Lead with the date, formatted YYYY-MM or YYYY-MM-DD. This is the only format that sorts correctly alphabetically. 2024-05 sorts after 2024-04. May 2024 sorts next to March 2023. This one convention does more work than everything else combined.
Use plain words after the date. 2024-05 Emma Wedding, not 2024-05_EW_FINAL_v2. You will not remember what EW meant.
Avoid characters that break on other systems: / \ : * ? " < > |. Spaces are fine on modern systems, but if you ever plan to put this on a web server or a Linux NAS, hyphens save you grief.
The archive folder nobody mentions
Add one more folder at the top level:
PHOTOS/
_ARCHIVE/The underscore keeps it sorted to the top. This is where you put things you're not ready to delete but don't want cluttering the main library: the 400 near-identical burst shots, the old library from a phone you already extracted the good photos from, the folder from your ex's camera.
Having an archive means you can be decisive during culling without the anxiety of permanent deletion. That anxiety is the reason most people's photo cleanup sessions end after twenty minutes.
Picking one
If you're deciding right now and don't want to read further: use Year / Event with a misc folder. It's the right answer for roughly 80 percent of people, and it's easy to upgrade to Structure 3 later by dragging your work photos into a new Projects/ branch.
The worst structure is the one you keep redesigning. Pick one this week, apply it to everything, and don't touch the design again for a year.
Next in this series: How to Find and Delete Duplicate Photos on Any Device