Footage Backup Checklist: Check Your Copies Before Deleting the Originals

The dangerous moment is often not the shoot. It is the moment you clear a card because a folder with the project name exists somewhere else.

A folder is not proof of a complete backup. Before deleting originals, check which files were copied, whether the copies are usable and whether another independent copy is available. This guide gives you a repeatable record of those checks. It does not guarantee recovery or authorize deleting a client's material.

Identify exactly what must survive

Create a source inventory before moving into the edit. Include camera cards, phone clips, separately recorded audio, screen recordings and any sidecar files your workflow needs.

Use a project ID and source labels that distinguish devices and sessions. Two cameras can produce the same filename. Preserve the original folder structure inside separate source folders rather than dropping every file into one directory.

A simple plan might be:

PROJECT-042/
  originals/
    camera-a-card01/
    camera-b-card01/
    phone-session01/
    audio-session01/
  project-files/
  graphics-and-documents/
  exports/
  backup-record/

This is an organizational example, not a required camera format. Some recording systems depend on their card structure, so preserve it until you understand the specific import requirements.

Copy the originals first. Do not use a move operation or rename everything on the source card while you are still establishing the first verified copy.

Understand what makes copies independent

Three folders on one drive share the same drive-failure risk. A laptop and its external drive stored in the same bag share some theft and damage risks.

The familiar 3-2-1 approach aims for three copies, two storage types or media, and one off-site copy. Backblaze's explanation is a useful starting point from a backup provider. The practical purpose is reducing shared failure risks, not reaching a reassuring folder count.

Choose storage and access controls appropriate for the footage and your obligations. Confidential client work may require encryption, restricted access or an approved provider. A public sharing link is not an acceptable substitute for a private backup.

Do not assume sync is equivalent to an independent historical backup. Deletions or unwanted changes may propagate, depending on the service and configuration. Check version history, retention and recovery behavior before relying on it.

Verify each copy at more than one level

Start with the inventory: expected folders, filenames, file counts and total sizes. A mismatch requires investigation. Matching totals are useful but do not prove that the contents are identical or playable.

Where your copying or verification tool supports checksums, compare source and destination files and retain its verification log. Matching checksums support byte-for-byte consistency; they do not prove the camera originally recorded the correct subject or that every decoder can play the file.

Then inspect the media. Open files from the destination copy, not from a recent-items shortcut that may point back to the original. Check picture and sound, and sample different points in long clips. Important or irreplaceable material deserves more thorough inspection than a casual thumbnail check.

Record the method actually used. “Count and size checked; five clips sampled; checksum verification not performed” is more informative than a generic “verified” checkbox. Do not claim a stronger check than you completed.

If a copy job reports an error, do not dismiss it because most of the footage appears present. Identify the affected files while the source is still available.

Work through a fictional failed-copy check

Suppose a fictional shoot produces 24 camera clips. You create a destination folder and later see the project name in your file browser. That alone tells you nothing about whether all 24 clips arrived.

Your inventory check finds only 23. The missing filename corresponds to the closing demonstration. Keep the card unchanged, locate that source clip and repeat the affected copy and verification. Do not erase the card and assume the editor will work around it.

Now imagine all 24 files are present, but the closing clip opens without its expected audio. Compare it with the original to establish whether the problem exists in the source or the copy. The remedy differs. Verification is not just counting; it is locating the first point where something is missing or unusable.

This is a diagnostic scenario, not a report of a test we performed. The worksheet leaves the result fields blank for your own evidence.

Test recovery before an emergency

A backup is useful only if you can retrieve the material you need. Test the restore process with a small selection before depending on it for an entire project.

Follow your backup tool's current restore instructions. For example, Apple's Time Machine restoration guide explains how to locate earlier backed-up items and restore them. Its default restoration behavior can return files to their original location, so understand the destination and overwrite implications before testing.

Prefer a safe test that cannot replace your current working files. If your tool supports an alternate destination, use a separate test folder and compare the restored files. Otherwise, use its documented non-destructive method or a harmless test item.

Confirm that credentials, encryption recovery information and necessary software remain available to an authorized person. Store recovery secrets securely, not in the same publicly shared project manifest.

Do not confuse handoff with backup

Sending files to an editor does not establish that your own copies are safe. Likewise, a cloud upload finishing does not establish that the recipient downloaded everything and opened the project.

Use the handoff checklist for recipient acceptance: correct version, complete agreed media, required dependencies and a successful open or playback check.

Keep working projects and new assets in the backup plan too. A protected camera card will not restore an edit created a week later if the project file was never backed up. Save identifiable project versions and make sure the locations holding them are included.

Make deletion a separate, documented decision

Before clearing a source, confirm that the required independent, verified copies will remain after that deletion, the verification record is complete and any agreed client or team acceptance has happened. Do not count the card or phone copy you are about to erase as one of the remaining copies. If your policy requires three copies, establish all three without that source before clearing it. If a critical check is unresolved, preserve the source.

Agree retention responsibilities separately: what is retained, where, for how long and who can authorize deletion. There is no universal period that fits every contract, privacy obligation or project.

After an authorized cleanup, update the inventory so it reflects reality. Do not leave a card listed as a live copy after it has been formatted.

The useful habit is a pause between “copy finished” and “original removed.” Use that pause to produce evidence: inventory, checks, independent locations and a known restore path.

FOOTAGE BACKUP CHECKLIST
Project:
Responsible person:
Shoot / ingest date:
Privacy / client restrictions:
Retention agreement location:

SOURCE INVENTORY — duplicate per source
Source ID / device / card:
Original folder structure:
Expected folders:
Expected file count:
Expected total size:
Important clips / audio / sidecars:
Source currently preserved at:

COPY RECORD — duplicate per independent destination
Destination name:
Physical or provider location:
Independent failure risks considered:
Copy start / finish:
Copy errors:
Expected vs actual file count:
Expected vs actual size:
Checksum tool / method / result, if used:
Verification log location:
Playback files and time ranges checked:
Picture / audio result:
Outstanding mismatch and action:
Verified by / date:

RESTORE CHECK
Backup source:
Documented restore procedure:
Safe destination / overwrite precautions:
Test items:
Restored and opened successfully:
Credentials / recovery information securely available:
Limitations / unresolved issues:

FICTIONAL CHECK EXAMPLE
Camera A inventory: 24 clips expected.
Destination A: 23 clips found.
Result: incomplete; original card preserved.
Next action: identify missing filename, copy it and repeat relevant verification.
Do not treat this example as a completed test of your files.

BEFORE DELETING A SOURCE
Required independent, verified copies that will REMAIN AFTER this cleanup (list each):
The source about to be erased is EXCLUDED from this count:
Remaining copies satisfy our backup policy:
If the required copies will not remain, STOP and preserve the source.
All expected media accounted for:
Copy errors resolved:
Actual verification methods documented:
Restore path tested appropriately:
Recipient acceptance complete, if required:
Retention obligations checked:
Authorized person / date:
Exact source approved for cleanup:
Inventory updated after authorized cleanup: