Most folder-naming advice is written for a project that lasts a few months. A family photo archive has to survive apps you haven't installed yet, operating systems that don't exist yet, and your own memory of why you named something the way you did, which people underestimate. The system below is plain on purpose, because clever schemes age badly, and this one hasn't needed to change in twenty years of use.
The pattern
A folder per year. Inside it, one folder per event, named with the date first, then the event name.
Two things are doing all the work here. The date prefix (YYYY-MM-DD) means the folder sorts correctly in any file browser, on any OS, forever. No app needs to understand your scheme, because plain alphabetical sort already gets the order right. The event name after the date means a human skimming the list recognizes what's inside without opening a single folder.
Why the date goes first, not last
"Lake House 2019-07-04" and "2019-07-04 Lake House" look similar, but only one of them sorts correctly next to every other folder in that year. Put the date first and the whole year folder falls into calendar order automatically. Put it last, or omit it, and you're relying on either manual reordering or an app that can parse dates out of arbitrary text, a dependency this system is built to avoid.
Edge cases
An event spans two days, or crosses New Year's Eve
Use the start date, one folder. A trip from December 30 to January 2 is 2019-12-30 New Year's Trip, filed under 2019, the year it started in, even though part of it happened in January. Don't split one continuous event across two year folders just because the calendar flipped partway through.
You don't know the exact date (old prints, digitized home movies)
Use your best estimate, at whatever precision you actually have. A bare year (1998) is far better than nothing. If you can narrow it further, do: 1998-summer is a legitimate folder name when that's as specific as the evidence gets. An approximate date you can improve later beats an empty one you'll never fill in.
Multiple contributors, years apart
This is where the pattern earns its keep the most. Because the rule is simple and doesn't depend on any one person's tagging habits or any one app's conventions, a folder a parent named in 2008 and one a teenager named in 2024 sort into the same coherent timeline without anyone reconciling anything by hand.
A folder for photos with no clear single event
It's fine to have a catch-all, but keep it dated and scoped the same way everything else is: 2021 Everyday rather than an undated "misc" folder that accumulates forever and never gets revisited.
Why this pattern also works well with software
The pattern is close to what many families already do by instinct after a few years of dumping camera-roll photos into named folders. The developer note Your folder names were the training data explains why that hand-built structure is such reliable ground truth for automatic event detection, with the engineering detail behind the advice above.
FAQ
What's the best photo folder naming convention?
A year folder containing a dated event folder inside it: 2019/2019-07-04 Lake House. The date prefix sorts correctly in any file browser; the event name lets a human recognize what's inside without opening it.
Dashes, underscores, or spaces?
Any of them work; consistency matters more than the choice. Dashes in the date (2019-07-04) are the de facto standard, matching ISO 8601, which sorts correctly and is unambiguous across regions.
What about an event that spans two days, or crosses New Year's Eve?
Use the start date, one folder, filed under the year it started in. Don't split a continuous event across two year folders just because the calendar flipped mid-trip.
What if I don't know the exact date?
Use your best estimate at whatever precision you have, such as a year alone or a year plus season. An approximate date is far more useful than none, and you can tighten it later.
Do I need to rename individual photo files too?
No. Spend naming effort on folders, which are few, not individual files, which number in the tens of thousands. The folder gives the file its context.