Most advice about organizing photos assumes you're starting from zero: one camera roll, a clean slate, pick a system and stick to it. That's not the situation if you're the person in the family who ended up holding twenty years of photos. Yours are already scattered: a dead laptop in a closet, three generations of iPhones, a couple of external drives nobody has plugged in since a move, a shoebox of prints someone's grandmother took. A guide that starts with "first, pick a naming convention" skips the hard part.
The archive already exists, in pieces. The goal is to merge what's there into something that works, without losing anything or spending six months of weekends on it. Here is the order that gets there.
Step 1: Get everything onto one drive, unsorted, first
Resist the urge to sort as you go. Photo-organizing projects mostly stall because people try to decide structure while doing the mechanical work of copying files off five devices. Separate the two. This step has one job: get every photo, from every source, onto one external drive, in its original folder structure, untouched.
- Old phones: if it's an iPhone, our step-by-step offload guide covers getting full-resolution originals off, including the ones hiding in Messages that a normal camera-roll export misses.
- Old computers: copy the whole Pictures folder (or wherever the OS was dumping camera imports) as-is. Don't reorganize on the way out. Making that decision twice, leaving the old machine and arriving on the new drive, is how folders get duplicated or silently dropped.
- Loose drives and old backups: plug them in, copy the whole thing into its own dated folder (
_incoming/2011-laptop-backup/), and don't try to merge it into anything yet. An unsorted folder with everything in it beats a half-sorted folder with gaps you won't remember later. - Prints and slides: a flatbed scanner or a phone scanning app gets you digital files; a local photo shop or mail-in scanning service is worth the cost for anything pre-1990, where the negatives are the only surviving original. Either way, the output joins the same consolidation drive as everything else.
Step 2: Pick one folder structure (year, then dated event)
Once everything is in one place, it needs one structure. The one that survives every app, every OS, and every decade you haven't lived through yet is the simplest one: a folder per year, and inside it, a dated folder per event.
So: 2019/2019-07-04 Lake House/. The date prefix means folders always sort correctly no matter what file browser or OS is looking at them; the event name means a human skimming the list actually recognizes what's in there without opening it. It is close to what families who have dumped camera-roll photos into hand-named folders for a decade already do by instinct. If that's you, you're formalizing a system you half-built. See the full naming pattern, including edge cases, or the developer note on why this habit is such reliable ground truth.
Two intuitive structures don't hold up at this scale. Organizing by person fails because most photos have more than one person in them (where does a birthday photo with both siblings go?). Organizing by photo type, such as vacations, birthdays, and everyday, fails because categories are a judgment call applied thousands of times, and different family members judge differently. Date is the one property every photo has exactly once, so let it be the folder. Who is in a photo and what kind of event it was can be searched or tagged instead of pre-sorted.
Step 3: Cull, but conservatively
Twenty years of photos includes a lot that doesn't need to survive: screenshots, saved memes, eleven near-identical shots from one burst where only one is worth keeping. Clearing those out makes the archive faster to browse and easier to hand to family members who don't want to wade through clutter.
Be conservative about everything else, especially anything from before digital cameras made photos free to take. A slightly out-of-focus photo of a grandparent who has died is not the same kind of bad photo as a blurry parking lot. If a photo's only flaw is technical quality, keep it. Storage is cheap, and a moment you can't get back is not.
Step 4: Don't try to tag every face by hand
This is where many organizing projects die: someone decides the archive should be searchable by person, opens the first folder, and starts tagging faces by hand. It works for about forty photos. It doesn't work for forty thousand, across twenty years, where the same kid looks nothing alike at three and at thirteen.
Whatever tool you use for this step, the folder structure from Step 2 is what makes it possible. Software that has to guess at dates and events from scratch does worse than software that starts from a family's own naming decisions.
Step 5: Back it up properly, now that it's actually organized
One organized archive on one drive is far better than five scattered partial ones, and it is still one drive away from a very bad day. Once the structure exists, back it up: a second copy on a different drive and ideally a third offsite. That is the 3-2-1 rule. It matters here because, unlike a document, a family photo has no second author who can recreate it.
Step 6: Make sure someone besides you can actually find things
The point is photos that get looked at again, not a tidy drive. Once the archive is organized, make it easy for other family members to browse it: a shared folder, a simple viewer, anything that turns "ask the one person who understands the folder structure" into "open it and look."
FAQ
How long does this actually take?
Consolidating (Step 1) is usually a weekend, mostly spent waiting on file copies rather than doing active work. Structuring and a first culling pass (Steps 2 and 3) take a few evenings by hand. Identifying everyone in every photo by hand (Step 4) realistically never finishes, which makes it the part worth handing to software.
Person or date: which should the folders be organized by?
Date. A photo happened at one time but usually has more than one person in it, so date is the only property that doesn't force an arbitrary choice. Let who is in it be a search or tag layer on top of a date-based structure.
Should I delete duplicates and blurry photos?
Clear out the obvious junk (screenshots, memes, near-identical burst shots), but be conservative with everything else, especially anything old enough that a "bad" copy might be the only one. When in doubt, keep it.
Do I need to rename every file?
No. A good folder structure makes renaming thousands of files unnecessary. Spend naming effort on folders, which number in the hundreds, not files, which number in the tens of thousands.
What's the actual best folder structure?
Year, then a dated event folder inside it, such as 2019/2019-07-04 Lake House. It sorts correctly everywhere, reads clearly to a human, and outlives whatever app or OS you're using today.
Can't I just dump everything into Apple Photos or Google Photos and let it sort itself out?
You can, and both are good at a single person's day-to-day camera roll. The strain shows up at family-archive scale: importing decades of files from several contributors into one proprietary library is a slow one-way door, and neither app is built around folders you organized by hand. See our comparison of the options.