How to Back Up Photos: The 3-2-1 Rule, Drives, Cloud and Test Restores

To back up photos, follow the 3-2-1 rule: keep three copies of every file, on at least two separate devices or kinds of storage, with one copy in a different building. For most people that means the working library on a computer, an automatic copy on an external drive, and a versioned cloud backup or a second drive kept elsewhere. Then prove it works by restoring some files every few months.

Folder structure and naming are covered in photo file management, and long-term care of a shared collection in the family photo archive guide. This page stays with the backup itself: how each kind of drive fails, why sync is not backup, how to cover phones, catalogs and trips, how to test a restore, and what to do with old drives and discs.

The 3-2-1 rule and what each copy protects against

The rule is easy to recite and easy to get subtly wrong, so it helps to match each part to the kind of loss it prevents. Photos are lost in five ways: a device dies, a person deletes or overwrites something, software or malware damages files, a thief takes the equipment, or a fire or flood destroys the room.

No single copy covers every row. That is the whole argument for three. Read the rule this way:

• Three copies means the working copy plus two backups. Two folders on one drive are one copy. A file that exists only on the backup drive, because you moved it there to free space, is not backed up at all.
• Two kinds of storage means the copies should not share a weakness: not two partitions of one disk, not two drives in one enclosure on one power supply, not two accounts with one provider.
• One offsite means far enough away to survive what happens to your home. A cloud backup counts. So does a drive at a relative’s house or a workplace, swapped every month.

Add one refinement: at least one copy should keep old versions or be offline. A backup that faithfully mirrors every change will also mirror a deletion or a corrupted file within hours.

Drive types and how they fail

Every storage device fails eventually. Knowing how each one tends to go tells you what to use it for and what warning you will get.

Hard drives

A hard drive stores data on spinning magnetic platters read by a moving arm. It offers the most capacity for the money, which makes it the usual choice for backups and large libraries. Its weak point is mechanical. Failures cluster in two periods: early, from manufacturing faults, and after several years, from wear. In between, the main risk is a knock or drop while it is spinning.

Hard drives often give notice. Warning signs are clicking or grinding, files that take a long time to open, copy errors, and a rising count of reallocated or pending sectors in the drive’s built-in health report, which free disk utilities can read. Treat any of these as an instruction to copy the data off now and retire the drive. A drive stored unplugged on a shelf should be powered up and checked about once a year.

Solid state drives

An SSD stores data as electrical charge in memory cells, with no moving parts. It is fast and shrugs off bumps, so it suits a working library and travel. It fails differently. The memory cells wear with writing, though normal photo use rarely reaches that limit. The more common failure is electronic: the controller dies and the drive vanishes from the computer in an instant, with no noise and no warning. Recovery from a dead SSD is harder than from a hard drive, and deleted files are usually wiped for good within moments.

SSDs are also a poor choice for a copy that sits unpowered for years, because the stored charge slowly leaks away, faster in heat and on heavily used drives. Use them for copies that are plugged in regularly.

Memory cards, USB sticks and burned discs

Cards and sticks are small, easy to lose and built for transport, not for keeping. Move files off them and treat the card as a temporary extra copy until your backups have run. The memory card guide covers card care. Home-burned CDs and DVDs rely on a dye layer that degrades with light, heat and time, and computers that can read them are becoming scarce.

NAS, and what RAID is not

A NAS (network attached storage) is a small box holding several drives that every computer in the house can reach over the network. It usually runs RAID, which spreads data across the drives so that the box keeps working when one drive dies. In a mirror, two drives hold identical data. In parity layouts, the equivalent of one or two drives’ worth of space is given over to recovery information, so one or two drives can fail without loss. A striped layout with no redundancy is the opposite: it loses everything if any single drive fails.

RAID keeps you working through a drive failure. It is not a backup, because all the drives are one device in one place under one set of software:

• Delete or overwrite a file and RAID removes it from every drive at once.
• Ransomware, a software bug or a failed enclosure affects the whole array.
• Theft, fire, flood and power surges take the box, not one drive.
• Drives bought together age together. Rebuilding after one failure works the remaining drives hard for many hours, which is when a second one is most likely to fail.

A NAS is a good home for a library or a good first backup. It still counts as one copy, and it needs its own backup to something outside the box.

Old drives, discs and cards in the drawer

Old media is a backup problem in disguise: photos that exist only on a retired laptop, a stack of burned discs or a phone in a drawer have one copy, on a device that is getting harder to read.

1. Copy everything into the current library now, while you still own a cable, reader or disc drive that works. Put each source in its own dated folder and sort later.
2. If a drive clicks, stalls or is not recognised, stop. Repeated attempts can make it worse. See the guide to recovering deleted photos for the next steps.
3. Let the backups run, then verify that the copied files open.
4. Wipe before you dispose. Deleting files or a quick format leaves the data recoverable. Overwrite a hard drive fully, use the built-in secure erase command on an SSD, and physically destroy any drive that no longer works. Take the remains to electronics recycling.

Plan the same move for your current drives. Replace any drive that holds an important copy after about five years, copying to the new one while the old one still works. Original prints and negatives are a separate job, covered in how to store old photos, and scanning them is covered in digitizing old photos.

Cloud backup versus cloud sync

These two services look alike and behave in opposite ways when something goes wrong.

Sync is useful, and with version history turned on it gives some protection. But it only counts as your offsite backup if you can answer yes to all of these: does it keep deleted files for longer than it would take you to notice they are gone? Does it keep earlier versions? Is a full-size original stored, not a compressed one? Is the whole library included, not one folder?

Check these points on any cloud backup before relying on it:

• Retention. How long are deleted files and old versions kept? Thirty days is too short for a photo library, where a missing folder can go unnoticed for a year. Choose the longest option offered.
• External drives. If the library is on an external drive, confirm that the drive is included, and find out what happens when it is unplugged for weeks. Some services drop files they have not seen for a set period.
• File types and sizes. Make sure RAW files, video and very large files are not excluded by default.
• The first upload. Estimate it: file size in megabits divided by upload speed. One terabyte at 20 megabits per second takes about four and a half days of non-stop uploading. Until it finishes, you have no offsite copy, so keep a drive elsewhere in the meantime.
• The restore route. Find out how you would get everything back, how long the download would take, and whether you hold an encryption key that must not be lost.
• Account security. Use a unique password and two-step sign-in. An attacker in your account can delete the backup.

If cloud backup does not suit you, because of a slow connection or a very large library, rotate two drives instead. Keep one at home receiving backups and one in another building. Swap them on a fixed day each month. You risk at most a month of work, and the away drive is offline, which protects it from malware.

Backing up phones and photos on the road

Phone photos

The photo library service built into a phone is sync. Delete a picture on the phone and it disappears from the cloud and from every other device, after a short stay in a recently deleted album. With the storage-saving option on, the phone keeps only small previews and the full-size originals exist in one place: the provider’s servers. That is one copy, tied to one account.

1. Leave the cloud library on. It protects against a lost or broken phone, the most common way phone photos disappear.
2. Bring originals into your main library on a schedule. Once a month, import from the phone to the computer by cable, or set the computer’s photo app to download full-size originals. Once they are in the main library, your normal backups cover them.
3. Choose “originals” when exporting. Many export options hand over a smaller or converted file. Keep the original HEIC or RAW file, plus the video part of any motion photo if you want it.
4. Save what arrives in messages. Pictures sent through chat apps are usually compressed and live only inside the app. Save the ones that matter to the photo library, and ask the sender for the original.
5. Check before you trade in or reset a phone that the latest photos have finished uploading and are present on the computer.

Travelling

A trip compresses the whole problem into a bag. The same rule applies, with smaller parts. The step-by-step version is in backing up photos when travelling. The short form:

• If the camera has two card slots, record to both.
• Bring enough cards that you never need to format one during the trip. The used cards are your first copy.
• Each evening, copy the day’s files to a portable SSD, directly from a laptop, tablet or phone with a card reader. That is the second copy.
• Keep the copies apart: cards in a pocket or money belt, the drive in a different bag or the room safe. Never put both in checked luggage.
• When the connection allows, upload the day’s best frames, or everything if you can. That is the offsite copy.
• At home, import, let both backups run, spot-check, and only then format the cards.

Backing up catalogs and edits

Most editing programs do not change your image files. They record your adjustments, ratings, keywords and albums somewhere else, and if that record is lost, the photos survive but years of work on them do not. Find out which of these your software uses:

• A catalog or library file: one database holding the edits for every photo. It is the most valuable single file you own after the images. It must be inside a folder that both backups cover.
• Sidecar files: small text files, usually ending in .xmp, saved next to each image. They are backed up automatically with the photos, as long as your backup does not skip them.
• Edits stored in the cloud account: common with phone and web editors. Export finished versions, because the edits exist only while the account does.

Four habits protect the work:

1. Use the program’s own catalog backup, and point it at a different drive from the catalog. The default location is often the same folder, which guards against a damaged database but not a dead drive. Keep the last few dated copies and delete older ones.
2. Let file backups run when the editor is closed. A database copied while it is being written can be inconsistent. Scheduling the backup overnight solves this.
3. Write edits into the files as a second layer. Many catalog programs can save metadata and adjustments to sidecars or into DNG files. With that on, a lost catalog costs you albums and history, not every edit.
4. Export finished pictures. A full-size JPEG or TIFF of your best work can be opened by anything, on any computer, with no catalog. The image file formats guide explains the choice, and export settings covers the options.

Preview and cache folders can be left out of backups to save space. The program rebuilds them. Do include presets, profiles and any custom keyword lists. If you ever relocate the library, follow the steps in moving a catalog and photos so the links between catalog and files survive.

Verifying backups, test restores and a schedule

Backups fail quietly. The drive fills up, the software stops after an update, a password expires, the library moves to a folder the backup does not watch. Nothing tells you until the day you need the files. Verification is how you find out early.

Three levels of checking

• Is it running? Open the backup program and read the date of the last completed backup and any error list. This takes a minute.
• Is it complete? Compare the number of files and total size of the library with the backup. They should be close. Then look for the newest thing you shot. If last week’s folder is there, the backup is current.
• Are the files good? Open a handful of files from the backup itself, from different years, including RAW files and videos. For a stronger check, use a backup or copy tool with a verify option, which reads every file back and compares it with the source. Checksums, described in the family archive guide linked above, catch silent corruption in files that have not been touched for years.

How to run a test restore

1. Pick one folder from an old shoot and one recent one.
2. Restore both from the backup to a new, empty folder, not over the originals. Do the cloud backup and the local drive in turn.
3. Open ten files from each restored folder at full size. Check that sidecar files came back too.
4. Restore the newest catalog backup to the same test folder and open it. Confirm that edits and ratings appear.
5. Note how long it took, then delete the test folder.

The timing matters. If a small folder takes an hour to come down from the cloud, the whole library will take weeks, and you will want the local backup to be the one you restore from first.

A schedule that holds up

Automate every row you can. A step that depends on memory will be skipped in exactly the busy month when you shoot the most.

Common mistakes

Moving photos to an external drive and calling it a backup. The files now exist only on that drive. Fix: a backup is a second copy. If the library lives on an external drive, back that drive up to another one.

Relying on a phone’s cloud library alone. It is sync, with one account as the single point of failure. Fix: import originals to the main library every month.

Backing up images but not the catalog. The pictures return unedited and unsorted. Fix: include the catalog folder and write edits to sidecars.

Mirroring with no history. A file deleted by mistake vanishes from the mirror at the next run. Fix: use a backup that keeps versions and deleted files for a long period.

Never restoring anything. The first restore attempt happens during the emergency. Fix: run the test restore every three months.

Try this

A 15 minute audit. Take a sheet of paper and draw three columns headed Copy 1, Copy 2 and Copy 3.

1. Write down one folder of photos you would hate to lose. Under each column, write where a copy of it is right now, naming the actual device and the building it is in.
2. Do the same for the photos taken on your phone in the last month, and for your editing catalog.
3. Circle any row with fewer than three entries, any row where all entries are in one building, and any entry that is sync without version history.
4. For one backup, open the software and write down the date of its last completed run.
5. Restore a single photo from that backup to the desktop and open it.

The circles are your to-do list, in order of how few copies each row has.

Frequently asked questions

What is the best way to back up photos?

Use two automatic backups of one organised library: a local one to an external drive for fast recovery, and an offsite one (a versioned cloud backup or a rotated drive) for disasters. Test both by restoring files a few times a year.

Is cloud storage enough on its own?

No. It is one copy, dependent on one account, one provider and your ability to sign in. Accounts get locked, providers change their terms, and sync services pass on deletions. Keep at least one copy on a drive you control.

How long do hard drives and SSDs last?

There is no reliable figure for a single drive. Many run for years beyond five and some fail in the first months, which is why the plan is built on copies, not on any one device lasting. Replacing important drives at around five years is a common precaution.

Should I back up RAW files or only the finished JPEGs?

Back up both if you have the space. The RAW file is the original and cannot be recreated, while a JPEG can be exported again as long as the RAW and the edits survive. If space forces a choice, keep the RAW files and the catalog. See RAW versus JPEG for the differences.

Related guides

• Photo file management: folders, file names and keeping an archive tidy enough to back up.
• Family photo archive: checksums, open formats and making sure relatives can open the collection.
• Recover deleted photos: what to do when a card or drive has already lost files.
• How to organize photos: getting scattered pictures into one library first.
• Backing up photos when travelling: the routine for cards, drives and uploads on a trip.
• How to store old photos: protecting the physical prints and negatives behind your scans.