A safe photo and video ingest workflow from card to backup
Use a repeatable card-to-computer workflow that creates verified copies, protects catalogs and project files, and prevents accidental card erasure.
1. Prepare cards, folders, and destinations before the job
Use a consistent card label and a simple job identifier before capture begins. Confirm that the laptop or ingest station has enough free space for every card plus working headroom, and connect two independent destinations when the work cannot be recreated.
Create the job folder once, then use the same structure on both destinations. A date, client or project name, camera identifier, card number, audio, documents, and exports can be separated without renaming camera originals during the first copy.
2. Make two copies before formatting anything
Copy the full card structure, including sidecar, metadata, proxy, and audio folders that may sit beside the obvious image or video files. Do not selectively drag only the files you recognize unless the camera maker documents that workflow.
The second destination must be independent. Copying from a card to two folders on the same physical drive does not protect against that drive failing. When possible, leave the card locked or clearly marked as not ready to format until verification is complete.
| Stage | Action | Do not proceed until |
|---|---|---|
| Identify | Record job, camera, and card number | The source card is unambiguous |
| Copy A | Copy the complete card to the primary destination | The transfer finishes without errors |
| Copy B | Copy to a separate drive or storage system | A second independent copy exists |
| Verify | Compare file counts, sizes, and preferably checksums | Both copies match the source |
| Open | Spot-check representative photos, video, and audio | Files open and play correctly |
| Release | Mark the card safe to format | The backup policy for the job is satisfied |
3. Verify more than the progress bar
A completed copy dialog shows that the operation ended; it does not prove every destination file is identical to the source. At minimum, compare item counts and total sizes and open representative files. A checksum-aware copy or verification tool provides stronger evidence by comparing content.
For video, test clips from the beginning and end of each card and include long or high-data-rate takes. For photography, open several RAW files from different parts of the sequence. Verification should happen before cards are reused, not after a missing file is discovered during editing.
4. Protect the catalog and the originals
Editing applications often store organization and edit instructions in a catalog, library, project database, or sidecar files. Those records can be as important as the originals, but backing them up does not necessarily back up the image and video files they reference.
Adobe states that Lightroom Classic catalog backups contain the catalog, not the photos. Place catalog backups on a separate disk from the working catalog and include both the media and project metadata in the wider backup plan. Preserve final deliverables and any assets that would be difficult to rebuild.
5. Separate ingest, working storage, and archive decisions
A fast portable SSD can make ingest and editing convenient, but it is still one device. After the immediate job is safe, move or replicate work into the normal automated backup system and create the offsite copy required by your policy.
Document when cards may be formatted, how long client originals are retained, which exports are archived, and who checks backup failures. A short written checklist is more reliable under deadline pressure than trying to remember a perfect process after a long shoot.
Frequently asked questions
Can I format the card after copying to my laptop?
Not if the laptop is the only other copy. Wait until at least two verified destination copies exist and the job's backup requirement is met.
Should I rename files during ingest?
It can be safe in a controlled, verified import workflow, but preserve unique filenames and avoid creating collisions. Keeping untouched camera originals during the first copy simplifies verification.
Does backing up a Lightroom catalog include my photos?
No. Adobe states that Lightroom Classic catalog backups do not back up the photos referenced by the catalog; the photos require their own backup.
Primary references
Technical standards can change. We use the relevant standards organizations as primary references and recommend checking the device maker's current manual.