AI Memory & Personal Archive

Local-First Photo Storage: Owning Your Memories in 2026

Local-first photo storage means your files live on your hardware first, your cloud second. Here's a practical guide to setting it up without losing your mind.

Local-first means the master copy of your photo library lives on hardware you own, and the cloud is just one of several backups. Not the source of truth. Not the only key to your own memories. A drive on your desk, a NAS in a closet, a folder you can ls into when the internet is down.

It’s a boring idea. It’s also the only photo strategy that survives a vendor going dark.

Why this matters now

We’ve spent ten years pretending that “the cloud” is a place. It isn’t. It’s a billing relationship with a company that can change its mind. When that company shuts down a service, your photos don’t migrate themselves out. Sometimes you get an export window. Sometimes the export tool is broken. Sometimes the email goes to spam.

The original Narrative Clip is the textbook case. The hardware shipped, the cloud ran for a couple of years, and then in 2016 the service was retired and a lot of people lost photos they never thought to download. We wrote about that in detail in the Narrative Clip cloud shutdown, and the broader pattern in the risks of cloud-only photo storage. Read either if you need the receipts.

The fix is not to abandon the cloud. The fix is to demote it.

The hardware

There are two reasonable tiers, and one wildly expensive one we’ll ignore.

Tier 1: an external SSD. A 2 TB Samsung T7 or Crucial X9 runs about $130 in 2026 and holds roughly 400,000 phone photos at typical iPhone JPEG sizes. Plug it into your laptop, copy everything over, eject. For most people with one phone and a decade of pictures, this is the whole answer. Buy two of them, actually, and keep one at a friend’s house or in a desk drawer at work. A drive that lives in the same room as your laptop is one coffee spill from being a single drive.

Tier 2: a NAS. A Synology DS224+ or a QNAP TS-264 with two 8 TB drives in mirror gives you about 8 TB of usable space and survives a single-disk failure. Budget around $700 to $900 for the box plus disks. If you want to go further, a small self-built server running TrueNAS or Unraid handles more drives and costs less per terabyte, but it asks more of you. The NAS sits on your network and accepts uploads from every device in the house.

Skip the cloud-branded “personal cloud” devices. They tend to require an account with the vendor, which is exactly the dependency you came here to escape.

The software

Two paths, and they’re not mutually exclusive.

Immich, for the app experience. Immich is an open-source, self-hosted photo manager. You run it on the NAS (or a Raspberry Pi, or a small mini-PC), install the mobile app, and it auto-uploads from your phone the way Google Photos does. Face recognition, search, shared albums, a clean timeline view. The project is moving quickly and is still pre-1.0 as of mid-2026, which means: it’s good, it’s not boring infrastructure yet. Pin your version, read the release notes before upgrading, and back up the database.

Plain folders, for the boring path. A directory tree organized by YYYY/MM with original filenames preserved. No app, no database, no migration when the next app comes along. The cost is no face search and no fancy timeline; you navigate with Finder or your file manager of choice. For people who mostly want their photos to exist and occasionally get scrolled through, this is the most durable option in human history. JPEGs from 1999 still open today. Whatever proprietary library format you adopted in 1999 probably does not.

A reasonable hybrid: keep plain folders as the canonical archive, and point Immich at them in read-only mode for the nice viewing experience.

The cloud backup leg

Off-site backup is non-negotiable. A house fire takes the NAS, the SSDs in the desk drawer, and the laptop. You need at least one copy in a different building.

Three options that don’t trap you:

The point of this leg is not convenience. It’s survival. You don’t browse your photos from B2; you browse them from your local copy. The cloud is the smoke alarm.

Local backup checklist

A photo archive that lives only on a vendor's cloud is a photo archive waiting to disappear. Use the 3-2-1 rule: three copies, two media, one off-site.

  • Copy 1: the original on your camera or phone (keep until backups are verified).
  • Copy 2: an external SSD or hard drive plugged directly into your computer.
  • Copy 3: an off-site copy — encrypted cloud, a NAS at a family member's house, or a drive in a desk drawer at work.
  • Filenames keep the camera-generated timestamp (e.g. 2026-05-11_073412.jpg) so dates survive re-uploads.
  • One year from today, open a random folder and verify the files still open.
  • Write the password for the encrypted copy on paper and store it where the executor of your estate can find it. People skip this. People also lose decades of photos.

For a longer walkthrough see how to back up lifelogging photos and local-first photo storage.

Pulling photos out of iCloud and Google Photos

This is the part everyone delays for years, so block out a weekend.

For Google Photos, use Google Takeout. Pick “Photos” only, choose the .tgz format with the largest part size your machine can handle (50 GB is usually fine), and request the archive. Google emails you a download link, typically within a day. Download every part before it expires (usually a week). Then run immich-go or a similar tool against the unpacked folder to merge the JSON sidecar metadata back into each image’s EXIF, because Takeout strips the original timestamps in a way that breaks naive imports.

For iCloud Photos, sign in at privacy.apple.com and request a copy of your data. Apple sends a download link when the archive is ready, usually a few days later. The archive uses HEIC for newer photos; you may want to convert to JPEG for compatibility, or keep HEIC and accept that some older software won’t read it.

Either way: do the export, verify the file count roughly matches what the service claimed you had, and only then turn off the cloud sync. Don’t burn the boat from the dock.

The trade-offs

Local-first asks more of you. You’ll run a backup job on a schedule. You’ll replace a drive every five to seven years. You’ll occasionally type a command. When something breaks, no support line picks up, because you are the support line.

In exchange, no vendor can lock you out. No subscription can quietly start charging more. No “we’re winding down the service” email lands in your inbox with a sixty-day countdown. The library is yours in the same boring way a shoebox of prints in the attic was yours in 1995.

Pick the tier you’ll actually maintain. A perfect setup you abandon after three months is worse than a 2 TB SSD you remember to plug in every Sunday.

Frequently asked questions

What is local-first photo storage?

It means the primary copy of your photos lives on hardware you physically own, like an external SSD or a NAS at home. Cloud services become optional backups, not the master copy. If a vendor disappears, your library still works.

Do I need a NAS to go local-first?

No. An external SSD plus an off-site backup is enough for most people. A NAS makes sense when you want a phone-friendly app like Immich, multi-device sync, or storage past 4 to 8 TB. Start small and upgrade only when the SSD setup actually frustrates you.

What is Immich?

Immich is an open-source, self-hosted photo and video app. It runs on a NAS or a small Linux box and gives you a Google Photos-style interface: mobile upload, timeline view, face grouping, search. Your files stay on your hardware. The project is active and improving fast, though it's still pre-1.0 as of 2026.

How do I export my Google Photos library?

Use Google Takeout. Request a one-time archive of Google Photos, choose the largest .tgz chunk size your machine can handle, and download every part. Once it's on disk, you'll want a tool like immich-go or a metadata script to re-attach the JSON sidecar timestamps to each image. Budget a weekend.

What's the cheapest local-first photo setup?

A 2 TB external SSD (around $130 in 2026), a folder structure organized by year and month, and a Backblaze B2 bucket holding encrypted Restic snapshots for off-site. Total first-year cost lands around $180 to $220 depending on library size. No NAS, no subscriptions to a photo app.

Is local-first more reliable than the cloud?

Only if you actually run the backups. A single drive in a drawer is less reliable than iCloud. A local primary plus an automated off-site backup plus a tested restore is more reliable than any single cloud, because no vendor can shut you down. The reliability comes from the discipline, not the hardware.