Most photo-app reviews are written by someone testing with a few hundred sample images. That's a reasonable way to judge an interface, but it's a terrible way to predict what happens with a real family archive — the kind built from twenty or thirty years of cameras, phones, scanned prints, and however many contributors, that quietly crosses into the tens of thousands of photos without anyone deciding it should. Problems that don't exist at demo scale show up reliably at that scale, and they're rarely mentioned in the reviews.
This isn't a "best photo app" post. It's narrower than that on purpose: what specifically breaks once a library gets huge, and what software needs to do differently to hold up.
How a family archive gets this big without anyone noticing
No single person accumulates 50,000 photos on purpose. It happens because a family archive isn't one camera roll — it's several, stacked across decades and merged together. A parent's phone since 2011. A partner's phone since roughly the same year. Whatever the kids' devices have generated since. A box of scanned prints from the generation before smartphones existed at all. None of those individually feels enormous. Added together, they cross into a scale that most consumer photo software was never really stress-tested against, because most individual users never get there either.
Those numbers are illustrative examples, not a benchmark for any specific product — the point isn't the exact figures, it's that "huge archive" territory is closer than it feels, and it's a completely different problem than "organize my camera roll."
What actually breaks at that scale
Import time and disk space
A lot of consumer photo software works by importing your files into a proprietary managed library — copying and sometimes converting each photo into its own internal format so the app can index and display it. At a few hundred photos, that import is a coffee break. At tens of thousands, it can be a multi-hour or multi-day process, and worse, it often means the app now holds a second copy of your entire archive alongside the original files. Depending on the app, that can mean needing roughly double the free disk space just to get through the import — space a lot of people don't have sitting around on the drive holding decades of photos.
The app itself gets sluggish
Some consumer apps that feel snappy with a modest library visibly slow down once it crosses a certain size — scrolling stutters, search takes longer to return results, thumbnails lag behind as you scroll. This isn't universal and isn't a knock on any specific app's engineering; it's just a pattern that shows up because most consumer photo tools are built and tuned against realistic single-user libraries, not multi-decade family archives.
Manual tagging stops being a task and becomes a wall
Tagging who's in a photo works fine by hand for the first hundred images. It's a genuinely different task at 50,000 — not slower, but structurally impossible for one person to finish in a reasonable amount of time, especially across a range where the same child looks completely different at three years old versus thirteen. Software at this scale either automates identification or the archive simply never gets tagged.
Duplicates multiply along with everything else
Burst shots, the same event backed up from two different phones, a scanned print that also exists as a digital original from years later — duplicates and near-duplicates scale with the archive, not with your patience for finding them. Manually comparing tens of thousands of photos for repeats isn't a task a person can realistically do; it has to be something the software finds for you.
What a huge-archive tool needs to do differently
Read in place
No import queue, no managed library, no second copy of files you already have safely stored.
Cluster automatically
Group faces and likely duplicates across the whole archive instead of asking you to tag one photo at a time.
Use what's already there
Read the family's own folder names and dates as a signal, rather than starting from nothing.
This is the case for a read-in-place, automatic-clustering approach specifically — not as a universal upgrade over mainstream photo apps, but as the shape of tool that a huge archive actually needs. All Our Years is built around exactly this: it reads a folder of photos on a drive you already own, in place, without moving, renaming, uploading, or duplicating anything, and it automatically detects events and tracks the same person's face across years so you're not tagging tens of thousands of photos by hand. There's no cloud component, no account, and it's a one-time purchase rather than a subscription.
When you don't need any of this
If your library is a few thousand photos from one or two people's phones, everything above is solving a problem you don't have. Mainstream apps like Apple Photos and Google Photos are genuinely good at that scale — well-tuned, familiar, and not worth replacing. The distinction that matters is archive size and number of contributors, not brand preference.
| A few thousand photos, one contributor | Tens of thousands, multiple contributors, decades | |
|---|---|---|
| Import | Fast regardless of approach | Import-based apps can take hours; read-in-place skips it |
| Disk space | A managed-library copy is a rounding error | A second copy of the whole archive may not fit |
| Tagging people | Manageable by hand if you want to | Only realistic if it's automated |
| Duplicates | Easy to eyeball | Needs automatic clustering to be findable at all |
| Best fit | Apple Photos, Google Photos | A read-in-place, auto-clustering tool built for scale |
If you're weighing All Our Years specifically against the mainstream options in more depth, we cover that comparison, including where the mainstream apps actually win, in our buyer's guide to photo archiving apps for families.
FAQ
How many photos is "too many" for consumer photo apps?
There's no official cliff, but complaints about sluggish browsing, slow imports, and search that stalls tend to start showing up once a library gets into the tens of thousands of photos — which is exactly where a multi-decade, multi-contributor family archive usually lands, even though no single person's camera roll ever gets there on its own.
Does importing a huge archive take a long time?
It depends on whether the app imports at all. Apps that build a managed library have to read, convert, and copy every file before you can do anything with it, and that work scales with archive size. Software that reads a folder in place skips that step entirely, because nothing gets copied into a separate library.
Can duplicate detection work automatically at scale?
It has to — manually comparing tens of thousands of photos for near-duplicates isn't realistic for a person, only for software. Automatic clustering is a starting point for review, not a silent deletion tool; it groups likely duplicates and repeated faces for you to look at.
Do I need special software if I only have a few thousand photos?
No. If your library is a few thousand photos from one or two people's cameras, mainstream apps like Apple Photos or Google Photos handle that scale well, and switching to something built for huge archives would be solving a problem you don't have.
Does All Our Years replace my backups?
No. It's an organizing and viewing layer on top of files that live on a drive you already own; you still need your own backup plan, ideally the classic 3-2-1 rule, for the files themselves.