Why RAW Files Need a Deliberate Backup Plan
A RAW file exists in exactly one place until a photographer copies it somewhere else. Unlike a JPEG shared to social media or a gallery link handed to a client, the original capture usually lives on a single memory card, then a single working drive, and nowhere else, until someone decides otherwise. That single point of failure is the real risk in a photography business: not a missed shot or a bad edit, but a drive that fails before the work behind it is protected. A backup strategy is not about anticipating every possible disaster. It is about making sure that whichever one happens, a failed drive, theft, fire, accidental deletion, a corrupted file system, does not take irreplaceable client work down with it. For a broader look at organizing the files themselves once they are safely backed up, see this guide to managing a RAW file library.
The 3-2-1 Rule, and Why It Holds Up
The 3-2-1 rule is the standard reference point for backup planning because it is simple enough to actually follow and resilient enough to survive most real failure scenarios:
- 3 copies of every file that matters: the working copy plus two backups.
- 2 different storage media types, so a single manufacturing defect or firmware issue cannot take out every copy at once (an internal SSD and an external HDD, for example, rather than two drives from the same batch).
- 1 copy offsite, physically separate from the location where you shoot and edit.
The logic behind each number matters more than the number itself. Three copies survive the loss of any one drive. Two media types survive a systemic hardware or firmware problem that could otherwise affect identical drives at the same time. One offsite copy survives the events that take out an entire location at once: a house fire, a burglary, a flooded office. Photographers who stop at "I have a backup drive" have solved for the easiest failure and left the more damaging ones uncovered.
Building the Local Backup Layer
Your working drive is copy one. Copy two should be a separate physical drive, connected to the same workstation but on independent hardware, that mirrors your working files automatically rather than depending on memory. Tools like rsync (Linux and macOS), FreeFileSync (Windows, macOS, and Linux), and Time Machine (macOS) can run on a schedule, daily or even hourly during an active shoot season, without a manual trigger. Label drives clearly with a purchase date and rotate aging drives out of the backup chain every few years rather than waiting for a failure to reveal that a drive has outlived its reliable service life.
For working photographers, the habit that matters most is import discipline: RAW files should be copied to at least two physically separate drives before a memory card is formatted and reused. A local backup that only updates once a week leaves an entire week of shoots exposed if the working drive fails on day six. A fuller walkthrough of organizing and protecting a growing photo library, not just backing it up, is covered in this guide to backing up and organizing a photo library.
Getting a Copy Offsite
The offsite copy is the one photographers skip most often, usually because it takes more setup than plugging in a second drive. Two approaches work well, and many photographers run both at once:
- Cloud object storage: Services built for large file archives, rather than consumer document-sync tools, upload a folder to the cloud automatically and keep working in the background while you edit locally. This kind of storage is typically priced per terabyte per month, so the cost scales with the size of the archive rather than being a flat subscription regardless of usage.
- A physically separate drive: An external drive stored at a different location entirely, a family member's house, a safe deposit box, a second office, updated on a rotating schedule (weekly or monthly, swapped out and brought home to refresh, then returned).
Consumer sync folders, the free tiers bundled with general-purpose cloud drives, are usually too small to hold a working RAW archive and are built for document syncing rather than for archiving terabytes of image data. They can supplement a real backup plan, but they should not be the only offsite copy a business depends on.
Cold Storage for Finished Work
Once a project is delivered and unlikely to be touched again, it does not need to live on an expensive, fast working drive. Cold storage, cheaper and higher-capacity media meant for infrequent access, is the right home for completed archives. LTO tape remains the professional standard at large studios because of its cost per terabyte and long shelf life, but the setup cost of a tape drive plus media only makes sense at real scale. For most independent photographers, a dedicated archive HDD, or M-DISC optical media rated for very long data retention under proper storage conditions, is a more practical choice. For photographers standardizing on a single archival RAW format across multiple camera bodies before long-term storage, converting to DNG can simplify cold storage, since DNG is a documented, openly specified format that is less dependent on a single manufacturer's software surviving for decades. The key discipline either way is moving delivered projects out of the active working set on a schedule, monthly or quarterly, rather than letting the working drive quietly fill up with years of completed jobs.
What to Protect First
When time or budget is limited, back up in priority order rather than trying to protect everything at once:
| Priority | Asset | Why it matters |
|---|---|---|
| 1 | RAW originals | Irreplaceable; cannot be recreated once lost |
| 2 | XMP sidecars and processing settings | Represents editing time already invested |
| 3 | Delivered exports (JPEG/TIFF) | Needed for reprints and reference without reprocessing |
| 4 | Contracts and shoot metadata | Legal and business record, not just image data |
RAW files sit at the top of that list for an obvious reason: a lost edit can be redone from the RAW file, but a lost RAW file cannot be reconstructed from anything else. If a backup window is short, an external drive with limited space, a slow upload connection during a busy week, RAW originals are the non-negotiable priority, and everything else can wait for the next backup cycle.
Testing the Backup You Already Have
A backup that has never been restored is an assumption, not a safeguard. Most backup failures are discovered at the worst possible moment, when a drive has already failed and the "backup" turns out to be empty, corrupted, or years out of date because a sync job silently stopped running. Schedule a quarterly restoration test: pick a folder at random from a backup copy, restore it to a separate test location, and confirm the files actually open and match the originals. This single habit catches silent failures, a sync job that stopped running months ago, a drive developing bad sectors, before they matter, rather than during a client emergency.
Keep a simple log of test dates and results, even a plain text file next to the backup drive is enough. Over a year or two, that log becomes useful evidence of which drives are aging out and which backup routines are actually reliable versus which ones only look reliable because nobody has checked them.
Common Mistakes That Undermine a Backup Plan
The 3-2-1 rule is simple in theory, but in practice a handful of avoidable habits quietly weaken it:
- Treating the memory card as a temporary backup. Formatting a card as soon as files copy to one drive leaves exactly one copy in existence during that window. Wait until at least two independent backups are confirmed before reusing a card.
- Buying both drives at the same time, from the same batch. Drives manufactured together can share the same latent defects and tend to fail in a similar timeframe under similar use. Staggering purchases reduces the odds of two drives failing close together.
- Letting the offsite copy fall out of sync. A rotated drive that only gets updated "when there's time" can end up months behind the working set. Put a recurring reminder on the calendar rather than relying on memory.
- Backing up the wrong folder. A sync tool pointed at the wrong directory will run successfully and back up nothing useful. Verify the actual folder contents after setting up any new backup job, not just that the job completed.
- No documentation of the plan itself. If a backup system only exists in one person's head, a studio with employees or a partner is exposed the moment that person is unavailable. Write down where each copy lives and how it gets updated.
Where Local Processing Fits Into the Backup Picture
Tools that sync everything to the cloud create an incidental extra copy as a side effect of how they work. imagic does not: it processes photos entirely on the local machine, and files never leave the computer they are opened on. That is a deliberate privacy choice rather than an oversight, but it means the safety net a cloud-synced tool provides by accident has to be built deliberately instead, with a real backup plan of your own. In practice this changes nothing about the 3-2-1 rule itself; it just means the offsite copy cannot be assumed to already exist because "the software handles it." After a cull and edit pass in imagic, export the keepers to a folder your backup software already monitors, so the processed selects get swept into the next backup cycle automatically rather than sitting unprotected on the working drive. That trade-off, more control over where files live, less automatic redundancy as a byproduct, is worth thinking through when evaluating any photography software, a theme covered more broadly across our industry insights coverage.
Frequently asked questions
How many backup copies do I actually need for client work?
Three total copies is the practical minimum: the working copy plus two backups, with at least one of those two stored offsite. Studios handling irreplaceable event work, such as weddings and one-time ceremonies, often keep a temporary fourth copy during the highest-risk window between the shoot and final delivery, then consolidate back down to the standard three.
Is a NAS a good second backup location?
A NAS with redundant drives protects against a single drive failure, but it is still one physical location, so it satisfies the different-media part of the 3-2-1 rule without satisfying the offsite part on its own. Pair a NAS with a genuinely offsite copy, cloud storage or a rotated external drive, rather than treating the NAS alone as a complete backup strategy.
Should I back up RAW files or just the edited exports?
Always back up the RAW originals, not just the exports. Edited exports are convenient for quick access, but they cannot be reprocessed if a client requests a different crop, a reprint at higher resolution, or a style update years later. RAW files are the source of truth; exports are a derived convenience copy that depends on the original still existing.