How to Store and Back Up Family History Files Digitally (Without Losing Everything)

Why “Saving It to My Computer” Is Not a Backup

A file saved only to your laptop is not backed up — it is stored. Those are not the same thing. Hard drives fail. Consumer drives have a median lifespan of three to five years, and failure is rarely announced in advance. One day the drive works; the next, it does not. If the only copy of your grandmother's interview recording or your great-grandmother's naturalization certificate lived on that drive, it is gone. Data recovery services exist, but they are expensive, partial, and not guaranteed.

The laptop-in-a-flood scenario is not hypothetical. Fire, water, theft, and simple mechanical failure take out home computers regularly — and they take out everything stored only on those computers. The same applies to external drives stored in the same physical location as the primary device. A flood that gets your laptop gets the external drive sitting next to it.

There is also the subtler “I had it somewhere” failure: files scattered across old phones, old computers, multiple cloud accounts, a USB stick from 2015. When no one knows where the authoritative copy lives, the archive is functionally inaccessible even if the files technically exist somewhere. The goal is not just survival — it is findable, organized survival.

The 3-2-1 Rule (And Why It Works for Family Archives)

The 3-2-1 rule is the standard backup framework used by data archivists, IT professionals, and anyone who has lost something they can't replace. The numbers stand for: three copies of every file, stored on two different types of media, with one copy kept off-site. Once you hear it, it sounds obvious. Most people who lose things had zero of these in place.

3 copies.

Not two. Three. The reason is that any two-copy system fails the moment both copies exist in the same place or on the same type of media. Three copies means a single failure — hardware, disaster, account lockout — leaves you with two remaining copies and a path to recovery.

2 different media types.

Two copies on two different external hard drives is not a redundant backup — it is the same failure mode duplicated. Two media types means physical plus cloud, or internal plus external. The point is that a failure mode that destroys one type (a drive corrupting, a cloud account going dark) does not automatically destroy the other.

1 off-site copy.

This is the one people skip. Off-site means physically somewhere else — a cloud service, a drive at a family member's house in another city, a safe deposit box. If a fire or flood takes out your home, it does not take out your off-site copy.

Applied to a family archive, the 3-2-1 rule looks like this:

• Primary copy: External hard drive (2TB or larger), kept at home, plugged in when you need it and stored safely when you don't.
• Second copy (off-site, cloud): A cloud storage account used specifically for this archive — not your general Google Drive, a dedicated account or service for family history files.
• Third copy (second off-site): A second physical drive stored at a trusted family member's home in a different location, updated every six to twelve months. Or a second cloud account on a different platform.

This is not expensive or technically complex. A 2TB external drive costs $50–$80. Cloud storage at the archival tier costs fractions of a cent per gigabyte per month. The investment is time and intention, not money.

Cloud Storage Options: What Works and What to Avoid

Not all cloud storage is the same, and the differences matter for a family archive that is meant to last decades.

Google Drive / Dropbox / iCloud

These services are convenient and familiar, and they work well for sharing and access. They are not archival. Google Photos compresses images on upload — your TIFF masters become degraded JPEGs without warning. All three are dependent on you maintaining an active account: inactivity policies have locked people out of accounts with years of data inside. Company policies change. Services get discontinued or restructured. For day-to-day access and sharing, these services are fine. For your only off-site backup of irreplaceable files, they are not reliable enough.

Backblaze B2 or Amazon Glacier

These are true archival cold storage services — designed for long-term storage of files you rarely access but cannot afford to lose. Backblaze B2 costs approximately $0.006 per GB per month; Amazon Glacier is even cheaper for deep archive tiers. A 50GB family archive costs under a dollar a month to store on either platform. These services do not compress your files, do not have inactivity lockouts, and are built specifically for long-term preservation. The tradeoff: they are less convenient to use than a Google Drive folder, and initial setup requires a bit more technical comfort. For anyone serious about preserving masters long-term, they are the right choice.

Family tech sharing (a family member's Google Drive)

This is a common approach and a common mistake. Storing your archive in a folder shared to a cousin's Google Drive means your archive's survival depends on that cousin maintaining their account indefinitely, not changing their storage plan, not getting locked out, and not one day deciding to clean up their Drive. None of those are guaranteed. A family member as your physical off-site backup (an external drive at their house) is reasonable; their cloud account as your only off-site copy is not.

The concrete recommendation: Primary storage — external hard drive at home. Off-site cloud backup — Backblaze B2, or a Google Drive account you control and maintain specifically for this archive (not your everyday account). Second off-site — a trusted family member's location with a physical drive, updated annually.

File Formats That Last vs. Formats That Expire

Backup strategy handles where your files live. Format strategy handles whether you can open them in thirty years. These are separate problems, and both matter. A file backed up in three locations in a format that software no longer supports is still effectively lost.

A note on photos: if you are scanning old family photographs, scan masters as TIFF and export JPEG for sharing. Never save over your TIFF with a JPEG. JPEG uses lossy compression — every time you open and resave a JPEG, it loses a small amount of quality. TIFF does not compress. Your archive masters should never be JPEG.

For documents and transcriptions: PDF/A is the archival variant of the PDF format, specifically designed for long-term preservation — it embeds all fonts and metadata, and it is the format used by national archives and libraries. For written transcriptions of oral history interviews, plain text (.txt) or Markdown (.md) files are the most durable options — they open in anything, forever. Word documents and Google Docs exports depend on software ecosystems that can change. If you are transcribing oral history recordings, save the final transcript as a plain text file alongside the audio master.

For audio and video: WAV is the lossless standard for audio masters. MP3 and AAC are compressed but widely supported and archivally acceptable if you do not have a WAV version. The formats to avoid are platform-native ones: WhatsApp saves voice messages as .opus files, iMessage stores voice memos in a proprietary format, and some call-recording apps create containers that only their own software can read. If you have recordings in these formats, convert them to MP3 or WAV immediately — do not leave them in the original format.

Folder Structure and File Naming That Survives Time

You will not remember what IMG_3847.jpg is in twenty years. No one will. File names generated by cameras and phones are sequential numbers assigned by a device — they carry no information about the subject, the date, the family, or the context. When an archive full of auto-named files gets handed off to the next generation, it becomes a sorting problem rather than a resource.

The naming convention worth adopting — used across the Thronateeska documentation methodology and described in detail in the guide to organizing family history documents — follows this pattern:

Examples:

• Coleman_Ruth_Portrait_1942_approx.tiff
• Coleman_Ruth_Interview_Recording_2024.wav
• Coleman_James_NaturalizationCertificate_1931.pdf

The approx suffix matters. When you do not know the exact year, say so — do not leave the date blank, and do not guess with false confidence. “1942_approx” tells a future researcher that you made an honest estimate. A blank field tells them nothing was known. A confident wrong date sends them looking in the wrong decade.

The folder structure that works with this naming convention:

The operating principle is the future stranger test: name and organize everything so that a grandchild who never met you — who has no existing knowledge of the family members or the events — can open the folder and understand what they are looking at. If a file requires prior family knowledge to interpret, it is not named or organized correctly. The archive should be self-explanatory.

The One Thing You Can Do This Week

Do not try to back up everything at once. If you have a large family archive in various states of organization, the idea of applying the 3-2-1 rule to all of it is paralyzing enough to guarantee nothing gets done. Start differently.

Pick twenty files. The most important twenty files in your collection right now: a grandmother's photograph with context you know, a recording of an elder who is no longer living, a scanned document that would be difficult or impossible to replace. Twenty files. Apply the 3-2-1 rule only to those twenty files.

Copy them to an external drive. Upload them to a cloud account. Send a copy to a family member in another city. Rename them using the naming convention above while you do it. That is the whole task. Those twenty files are now backed up correctly for the first time. The archive is now meaningfully more protected than it was before you started.

The point of starting with twenty files is not to avoid doing the rest — it is to build the habit before you scale it. Once you have applied the system to twenty files, applying it to the next forty is not a different skill. It is the same action, repeated. Most people who successfully build archival backup habits did not start by backing up everything. They started with what mattered most and expanded from there.

The documentation work matters. The recordings, the scans, the transcriptions, the metadata — all of it represents real research and real time invested in preserving what would otherwise be lost. None of it is preserved if it lives in one place, in a format that can fail or expire, with a name that no one in the next generation will understand. The backup is not separate from the preservation work. It is the final step of it.