Local-First Photo Organizing: Why You Don't Need the Cloud

Most photo software assumes the cloud is the point. Upload everything, and in exchange get access from any device, automatic sync, and a company handling the infrastructure so you don't have to think about it. That's a genuinely good trade for a rolling camera roll. It's a much less obvious trade for a family archive of decades-old photos that already lives on a drive you own — and it's worth treating "we don't upload your photos" as a design decision to evaluate on its merits, not an apology for a missing feature.

Not uploading your family's photos isn't a limitation to work around. For an archive like this, it's the point.

The case for keeping it local

A few reasons local-first is a deliberate, defensible architecture for this specific job, not a corner cut:

Privacy. Nothing leaves your drive. There's no server somewhere with a copy of forty years of your family's photos, no third party's data-handling practices to trust, no account to be breached. The only copy that exists is the one you already control.
No ongoing cost as storage grows. Cloud photo storage is priced per gigabyte, and a multi-decade family archive is a lot of gigabytes. A local tool that reads files already on a drive you bought once has no metered storage bill that climbs every year the archive grows.
No dependency on a company staying in business. A cloud service can raise prices, change its terms, get acquired, or shut down. None of that touches files that were never uploaded to begin with — the archive keeps working exactly as it did on day one, indefinitely, regardless of what happens to the company that made the software.
Works with no internet connection. A drive plugged into a Mac with no network at all still works completely. For an archive you might only look at occasionally — the holidays, a family reunion, a big anniversary — there's no reason it should have a runtime dependency on connectivity at all.

An external hard drive connected to a MacBook on a desk — Photo by Arina Krasnikova via Pexels

Cloud service vs. local, read-in-place

Laid out side by side, the actual architectural difference is simple, even though the marketing language around each side often isn't:

Cloud photo service

Files live on the provider's servers. The provider (and anyone they're compelled or choose to share with) can technically access them. Cost is an ongoing subscription that scales with storage used. Requires an internet connection to view or sync.

Local, read-in-place

Files stay on your own drive, exactly where they already were. No one but you has access, because nothing was ever sent anywhere. Cost is whatever you paid for the drive and the software, once. Works completely offline.

Neither model is universally "better" — they're built for different jobs. A cloud service is the right tool when the job is a rolling camera roll you want synced across every device the moment you take a photo. A local tool is the right one when the job is organizing an archive that already exists on a drive, and where "access from anywhere, instantly" matters a lot less than "still works exactly the same in twenty years, and no one outside the family has ever had a copy."

The honest tradeoffs

A local-first tool gives up two real things, and pretending otherwise wouldn't match how we try to talk about this product:

No automatic phone access away from home. A local tool reading a drive plugged into a Mac doesn't give you the same phone-in-your-pocket access a cloud service does when you're at your in-laws' house and want to pull up a photo. If that kind of anywhere-access matters more to you than the tradeoffs above, that's a real reason to lean toward a cloud-synced service instead — and it's a genuinely fine thing to want.

All Our Years isn't built for automatic phone-to-cloud backup, and it isn't trying to be — that's a different job, and Apple Photos or Google Photos already do it well. It's built for the specific job of organizing an archive that's already sitting in folders on a drive.

Local is not the same thing as backed up. This is the tradeoff most worth being precise about. "We don't upload your photos" describes how the organizing software works — it says nothing about how many physical copies of the files exist. A local-first archive on one drive is still exactly one drive away from a very bad day: a failed disk, a fire, a theft. The classic answer is the 3-2-1 rule — a second copy on a different drive, and a third copy stored somewhere offsite — and it applies here at least as much as it would to any other photo library. We cover offloading and backing up phone photos specifically in our iPhone backup guide, and we're planning a dedicated, deeper post on 3-2-1 backup strategy for a family archive — this one intentionally keeps that part brief.

A pile of old photo albums and loose prints spread across a table — Photo by Thiago José Amaral via Pexels

Sharing without a cloud sync

"Local" doesn't mean "no one else can ever see these photos." It means sharing is a deliberate, manual act instead of an always-on background sync. Export a folder for a specific event, send someone a copy, hand a relative a duplicate of the drive at a family gathering. It's less automatic than a cloud service's instant multi-device sync, and for a lot of families that's a fair trade: you decide exactly what leaves your drive and when, rather than everything being synced everywhere by default.

How this shows up in All Our Years specifically

All Our Years reads an existing folder of photos on a drive you already own, in place. It never moves, renames, uploads, or modifies the original files, there's no cloud component, and no account is required to use it. It's also a one-time purchase rather than a subscription — which follows naturally from not having ongoing server costs to cover for your archive. The tradeoff is the one above: no automatic sync to your phone away from home, and it's Mac only. If either of those is a dealbreaker for your household, it's worth knowing that going in, and our Mac-specific buying guide covers the platform question in more depth. If you haven't yet consolidated a scattered archive onto one drive in the first place, start with our step-by-step organizing guide.

Weighing this against the other options?

See the full comparison of Apple Photos, Google Photos, and All Our Years in our buyer's guide.

See how it works

FAQ

Is local-first photo software less convenient?

In one specific way, yes: you don't get automatic access from your phone when you're away from the drive, the way a cloud photo service gives you. In exchange, nothing about the archive depends on a company staying in business, keeping its pricing the same, or having an internet connection at all.

Can I still share photos with family if everything is local?

Yes, just manually rather than automatically. Export a folder, send it, or hand someone a copy of the drive. What you lose is the always-on sync of a cloud service; what you keep is control over exactly what leaves your drive and when.

Does local mean no backup?

No — those are two different things, and it's worth being precise about the difference. Local-first means your organizing software doesn't upload anything as part of how it works. It says nothing about how many physical copies of your files exist. You still need a real backup — ideally following the 3-2-1 principle — exactly as much as you would with any other photo software.

Why would software NOT use the cloud?

Because for an archive of decades-old family photos, the cloud model's main selling points — access anywhere, automatic sync — matter less than its costs: an ongoing subscription that scales with storage, a company that has to keep existing and keep its terms the same, and files that live somewhere you don't fully control. For this job, local-first trades a convenience you may not need for independence you probably do.

Does All Our Years upload my photos anywhere?

No. It reads a folder of photos on a drive you already own, in place, and never uploads, moves, or renames the originals. There's no cloud component and no account.