How to Back Up Lifelogging Photos in 2026

A wearable camera produces an inconvenient amount of data. Two photos a minute for ten waking hours is about 1,200 photos a day. At 3 to 5 MB each, that is 10 to 15 GB a week, 50 to 70 GB a month, and somewhere between 600 GB and 900 GB a year. None of the standard “free 5 GB cloud” suggestions make sense at that volume. You need a plan built for the scale.

The good news: the rules have not changed. The classic 3-2-1 backup rule still works. You just have to size everything correctly and automate the steps you will otherwise skip.

Step 1: get the photos off the camera

This is where most people lose data, and they lose it because Wi-Fi is slow. A 15 GB week transferred over the Insta360 GO 3S Action Pod’s Wi-Fi can take an hour and will probably stall once. The same transfer over USB-C, with the camera or its dock plugged directly into a laptop, is done before your coffee is.

Make cable transfer the default. Buy a short USB-C cable, leave it in your bag, and dump the camera every night or every other night. If you wait a week, the transfer becomes an event and events get postponed.

If the camera uses a microSD card, pull the card and use a reader. SD-card readers move data at roughly twice the speed of in-camera USB, and the camera battery does not drain during the transfer.

Step 2: an active library

Pick one app where the photos actually live. This is the library you open on a Sunday evening and scroll through, the one your phone syncs to, the one that runs face recognition so you can find pictures of your kid.

For most people that is Apple Photos (via iCloud) or Google Photos. Both handle hundreds of thousands of photos without complaining, both have decent search, and both cost roughly US$10 to US$30 a month at lifelogger volumes.

If you want to own the software end-to-end, Immich is the realistic open-source option in 2026. It runs in Docker on a NAS or a mini-PC, the interface borrows heavily from Google Photos, and the face and semantic search run on your hardware. We covered the trade-offs in more depth in Personal Archive Tools and Photo Organization AI.

The active library is not your backup. It is the front door. Backups are what stand behind it.

Step 3: a local backup

A photo archive that only exists on someone else’s server is not an archive, it is a tenancy. The fix is boring: an external SSD or a NAS in your home.

An 8 TB external SSD is the right purchase for most lifeloggers in 2026. It will run between US$300 and US$450 depending on brand and read speed, it fits in a coat pocket, and it will hold roughly a decade of photos at typical wearable-camera output. Plug it in monthly, let your backup tool (Time Machine on macOS, File History or a tool like Arq on Windows, restic or Borg on Linux) run, unplug it, put it in a drawer.

A NAS is the upgrade. A two-bay Synology or QNAP with 8 to 16 TB usable runs US$600 to US$1,000 once you buy drives, and it gives you continuous backups over the network without remembering to plug anything in. If you are already running Immich, the same box does double duty.

The single most common mistake here is leaving the external drive plugged in 24/7. Don’t. A drive that is always mounted is a drive that ransomware can encrypt, that a power surge can fry, and that an accidental rm -rf can wipe. Plug it in to back up. Then unplug it.

Step 4: off-site

The drive in your drawer protects you from a dead laptop. It does not protect you from a fire, a flood, or a burglary that takes the laptop and the drawer.

The off-site copy can be a cloud bucket — Backblaze B2 and Cloudflare R2 are the obvious choices in 2026, both at roughly US$5 to US$6 per terabyte per month, both with sensible egress pricing. Encrypt the upload with restic or rclone’s crypt remote so the provider cannot read your photos. A year of lifelogging stored encrypted on B2 costs roughly US$50.

If you object to giving any cloud your photos, the analog version works too: a second external drive at a parent’s or sibling’s house, rotated once or twice a year. It is less convenient and less continuous, but it is real off-site storage and it costs nothing per month.

The 3-2-1 rule in lifelogger terms

The 3-2-1 rule says: three copies of your data, on two different types of media, with one copy off-site. For a wearable-camera library that translates to: the working library on your computer or NAS, an external drive nearby, and a cloud bucket or relative’s-house drive far away.

Pruning is part of the system

You do not need to keep every photo. You probably do not want to.

A camera that fires every 30 seconds produces an enormous amount of redundancy: the same hallway, the same dashboard, the same patch of sky. Keeping all of it inflates your storage bill, slows down search, and makes the meaningful photos harder to find. The honest move is to cull, and to cull often.

Once a quarter, sit down with a week’s photos and delete aggressively. Burst sequences keep their best frame. Indistinct hallway shots get tossed. Anything blurry beyond rescue goes. You will keep maybe 20 to 30 percent of what came off the camera, and the library will be better for it. The Narrative cloud, when it existed, did some of this work automatically with its “moments” feature. Without that crutch you have to do it yourself, and frankly, the editing process is where lifelogging becomes memory rather than telemetry.

Old Narrative Clip exports

If you have a folder full of ZIPs from Narrative’s 2016 export window, here is how to fold them into the system above.

Unpack each ZIP to a dated parent folder — narrative-export-2016/ is fine. The JPEGs inside have correct EXIF timestamps, which means any modern photo library will slot them into the right place on your timeline when you import. Drop the folder into your active library (Apple Photos, Google Photos, or Immich). Run face recognition on them; you will be surprised what surfaces. Then include the same folder in your local and off-site backup paths so the archive you rescued in 2016 finally has the three-copy redundancy it should have had then.

The Narrative cloud is gone and is not coming back — we wrote about that in the cloud shutdown explainer. But the photos people downloaded before the lights went out are still good files. Treat them like any other decade-old photo set: import, tag, back up, and stop relying on the company that took them.

Frequently asked questions