How Much Storage Do You Need for Years of Wearable Camera Photos?

Summary. A wearable camera produces a surprisingly predictable amount of data once you know your capture rate, JPEG size, and video habits. The hard part is that those numbers compound for years. This guide gives you the assumptions worth using, a year-by-year table for three honest capture levels, an interactive calculator you can run with your own inputs, and a buying path that gets you from 2 TB to 24 TB without throwing away the drives you already own.

The assumptions

The estimates in any storage calculator depend on four numbers. None of them are exotic, but each one quietly doubles or halves the answer.

Capture rate. Most modern wearables — the Insta360 GO 3S in interval mode, second-generation clip-style cameras, Memoto-style timelapse devices — fire roughly every 30 seconds when actively shooting. That is two photos a minute. Across ten waking hours of wearing, that lands at about 1,200 photos a day. Lower interval rates or a camera worn for shorter sessions can drop the figure to 200 to 400 photos a day.

JPEG size. Wearable cameras in 2026 produce JPEGs between 3 and 5 MB at their default quality settings. Glasses-style cameras (Ray-Ban Meta, Solos) tend toward the smaller end; chest-mounted units with larger sensors push the upper end. Picking 4 MB as a working average is reasonable for most setups.

Video minutes. Video is the multiplier. 4K/30 video on current wearables runs roughly 90 MB per minute. 1080p/30 sits closer to 25 MB per minute. A camera that records ten seconds every time you tap it might add 50 MB a day; one that captures a daily five-minute walk adds 450 MB. The same archive looks completely different at those two video budgets.

Years of capture. A wearable-camera archive does not stay one size. It grows linearly, and that linearity is what catches people off guard at the end of year two.

The math is dull. The units matter. This article and the calculator use the decimal units printed on consumer drives: 1 GB = 1,000 MB and 1 TB = 1,000 GB. At 1,200 photos and 4 MB each, that is 4,800 MB or 4.8 GB a day. Over a year, it comes to 1.75 TB before video.

Year-by-year, three capture levels

The table below uses three realistic profiles. Light is a camera worn for short sessions or at a longer interval — 200 photos a day, no video. Typical is a clip worn through the working day at two-per-minute, 1,200 photos a day, no video. Heavy is the same typical rate plus five minutes of 4K/30 video a day. All figures assume 4 MB per JPEG, 90 MB per minute of video, and decimal storage units.

A few things to notice. A “light” archive fits on a single consumer external SSD for the entire decade. A “typical” archive overruns 8 TB by year five. A “heavy” archive needs serious capacity planning from year one — and the gap between typical and heavy is smaller than the gap between light and typical, because photos still dominate the volume.

The interactive calculator

Enter your own numbers below. The calculator starts on a typical-capture preset and updates on every change.

The calculator multiplies daily photo bytes plus daily video bytes by 365 and then by the number of planning years. It adds 20% working headroom before rounding up to a common drive size. The backup budget is twice the projected archive, leaving room for a full second copy and version history. That number is a capacity target, not an instruction to buy one enormous drive.

Recommended capacity tiers

The tiers below match the three profiles in the table. Each pairs a working-library option with an off-site backup option, because either one alone is half a system. We cover the broader case for each side in NAS vs cloud for photo archives and the best cloud storage for lifelogging.

Light (under 3 TB across ten years)

A single external drive will hold an entire light archive for the decade. The right purchase is a 4 to 8 TB portable SSD plus a small cloud bucket for off-site insurance.

Typical (around 8 to 10 TB at year five)

This is where a NAS starts to pay for itself. The default preset reaches 8.8 TB in five years, so the calculator rounds the working tier to 12 TB and budgets 20 TB for backup and versions. A mirrored two-bay NAS therefore needs 12 TB or 16 TB CMR drives; two 8 TB drives would already be too small.

Heavy (about 9.6 TB at year five)

At the heavy preset, five years comes to 9.6 TB. Ten years comes to 19.2 TB. Add working headroom and the five-year estimate lands in the 12 TB tier. If you expect to keep that pace, start with a four-bay NAS and size the usable pool from the calculator. Each independent backup target still needs room for the complete archive.

The upgrade path

Most lifeloggers do not buy their final setup on day one. They buy what they need, fill it, and migrate. Three transitions are worth planning for in advance.

2 TB to 8 TB. This usually happens at the end of year one or early in year two for a typical archive. The cheapest move is to keep the 2 TB drive as a snapshot of the early library and buy an 8 TB external as the new working volume. Copy everything over, verify the file count, label the old drive with a date, put it in a drawer. Do not delete it for at least six months — a dead 8 TB drive in week one of ownership is rare but not impossible.

8 TB to 16 TB. This is the moment to consider a NAS if you have not already, because mirrored drives in a two-bay box give you 8 TB usable with redundancy, and you can swap each drive for a 16 TB unit later without changing the chassis. If you are already on a NAS, this transition is one drive swap, a resilver, a second drive swap, a second resilver, and a volume expansion — a weekend job, not a panic.

16 TB to 24 TB and beyond. At this scale you are running a four-bay NAS or a small server. The transition is no longer about drives; it is about whether you want to keep growing the same library or split it into a hot working set and a cold archive. Splitting tends to be cleaner. The cold archive can live on slower, larger drives without affecting the speed of the photos you actually scroll through.

Pruning is part of the math

An unculled lifelogging archive doubles unnecessarily. A camera that fires every 30 seconds catches the same hallway, the same windshield, the same patch of sky a hundred times a year. Storage planning that ignores this is planning to buy drives for visual noise.

The realistic number is somewhere between 30 and 50 percent kept after a serious cull. Quarterly is the right cadence — a session every three months is short enough to remember the context and long enough that you can see redundancy clearly. The interactive calculator above includes a pruning factor for exactly this reason. Set it to 40 and watch the ten-year typical archive drop from 17 TB to about 7 TB. That is the difference between needing a NAS upgrade and not.

Pruning is not destruction. It is editing. The frames that survive a cull are the ones doing memory work; the rest are telemetry. An archive that holds telemetry forever is a library that hides the real photos inside its own bulk.

Related reading

• Best cloud storage for lifelogging
• NAS vs cloud for photo archives
• Best NAS for a photo archive
• 3-2-1 backup for lifelogging
• Build a home photo archive
• Object storage vs consumer cloud

Frequently asked questions