The first decision in how to recover camera data is not which tool to install — it is which of six failure types you are facing, because the correct path diverges sharply between them and the wrong path can end the recovery before it begins. Running a repair utility on a card that only needed a scan is the most common way people destroy their own footage.
This page is a dispatcher. It classifies the failure, maps each type to the method that actually works for it, gives a realistic expectation of what comes back, and states the boundary conditions where no software will help. Read the classification section, then jump to the playbook that matches your situation.
Classify the Failure Before You Open a Tool
Six failure types cover almost everything that arrives at a recovery bench. The classification takes two minutes and determines everything that follows.
A. Deleted. The card works, the camera reads it, and specific files are gone — one photo, a folder, or everything after a “Delete All.”
B. Formatted. A format ran in the camera or on a computer, either deliberately or by a slip of the thumb.
C. File system damaged. The card mounts but reports a RAW file system, prompts you to format it, refuses to be read, or shows a capacity that is obviously wrong. Files may be visible with names like FILE0001.CHK or may not appear at all.
D. Files present but unreadable. The directory is intact, the thumbnails may render, but opening a file gives a corruption error, a gray or blocky image, or a video that stops after a few seconds.
E. Card not detected. Nothing appears — no drive letter, no mount, no entry in Disk Management, or an entry that shows 0 MB or a few dozen megabytes regardless of the card’s real capacity.
F. Physically damaged. Cracked, snapped, bent, water-exposed, heat-damaged, or a card whose controller has failed electrically.
Three triage questions narrow the case further:
- Does the card enumerate at all? If the computer cannot see the device, no file-recovery software can either. That is category E, and the path leads either to imaging at a hardware level or to a lab.
- Does it enumerate with the correct capacity? A 128 GB card that reports 32 MB has a controller problem, not a file problem.
- Has anything been written to the card since the loss? This is the single strongest predictor of success. Everything deleted or formatted can be recovered while it remains uncovered; nothing recovers once the space has been reused.
Categories A, B, and C are software problems. D is software plus file repair. E and F are hardware problems. Internal camera memory and phone libraries form a seventh category that behaves differently, and it is handled separately below.
The Five Recovery Paths and What Each One Can Actually Do
| Path | What it is | Best suited to | Cost | Realistic expectation | Boundary condition |
|---|---|---|---|---|---|
| Operating system built-ins | Recycle Bin, Trash, File History, Time Machine | Files deleted from a computer or an external drive | Free | High, when a copy still exists | Never applies to in-camera deletion; cameras have no trash can |
| Free and open-source tools | PhotoRec, TestDisk, Recuva, ddrescue | Formatted cards with little use afterward; imaging before scanning | Free | Good for stills, weaker for video | No meaningful previews; output has no names or folders; video reconstruction is limited |
| Command-line utilities | chkdsk, fsck, diskutil, ddrescue, exiftool | Imaging, file-system inspection, metadata documentation | Free | Depends entirely on the command | chkdsk /f writes to the card and can consume the very structures a scan needs |
| Commercial recovery software | Deep scanning, previews, RAW and video handling | Cards used since the loss, large shoots, mixed photo and video | Paid license | High on uncovered data | Cannot repair physical damage, bypass encryption, or restore overwritten sectors |
| Professional laboratory | Cleanroom work, controller repair, chip-off | Physical damage, water, dead controllers, encrypted media | Hundreds to thousands | Case-dependent | Slower, and worth starting only after a proper diagnosis |
The most damaging misunderstanding in this table involves the third path. chkdsk is a repair tool built for a working file system, and its purpose is to make a volume consistent again — which may include discarding directory entries it considers invalid, converting a damaged FAT chain into a clean empty volume, or writing a new file system over the old one. On a card holding the only copy of a shoot, a repair attempt can turn a straightforward recovery into an impossible one. Image the card first; repair afterward, on the copy, if at all.
Free tools are genuinely capable, and for a freshly formatted card that has not been reused they often return everything. They fall down on preview-driven selection, on vendor RAW formats, and on video that needs its container rebuilt.
If you are on Windows and the card is still detected by a computer, a purpose-built recovery tool such as XRecovery (xappset.com) can scan SD, microSD, and other memory cards for deleted or formatted photos and videos. As with any recovery tool, stop writing to the card first and always save recovered files to a different drive.
Playbooks by Failure Type
Playbook A: Files Deleted in the Camera
Deletion removes the directory entry and frees the clusters; the image data stays put. Because the camera has already marked that space as available, the correct response is speed rather than technique: power the camera off, remove the card, and put it in a card reader instead of tethering the camera over USB, which lets the camera’s firmware keep writing. A deep scan then returns the files with their names intact as long as the entries were not reused. The mechanics are laid out in what deletion actually changes on a card.
Playbook B: Formatted Card
Determine which kind of format ran. An in-camera format is a quick format that rewrites the boot record, the allocation table, and the root directory while leaving the data region alone. A quick format on a computer behaves the same way. A full format, a low-level format, or a secure erase writes over every sector and leaves nothing to find.
The format’s duration is the diagnostic. A 128 GB card that formatted in a second was quick-formatted inside a camera; the same card taking twenty minutes on a computer was fully written over. If it was quick, treat the card exactly as in Playbook A and expect partial recovery only if new files have since been written into the freed space. The comparison is set out in in-camera format versus a computer format, and the working procedure is in recovering files after a memory card format.
Playbook C: The Card Reports RAW or Demands Formatting
Refuse the prompt. Windows offering to format an unreadable volume is offering to make it consistent by emptying it, and accepting converts a recoverable card into an empty one. The same applies to any camera or app that offers to “repair” the card.
Two sub-cases exist. If the file system structure is damaged but present, a partition-level tool such as TestDisk can sometimes restore the original directory tree, which preserves file names and folders. If the structure is gone, a deep scan carves files by signature. Either way, image the card before doing anything else — the reasons to image before scanning apply most strongly here, because this is the case where a wrong first move is permanent. The full procedure is in recovering a corrupted SD card.
Playbook D: Files Are There but Will Not Open
Separate the file from the software before assuming damage. Open one of the problem files on a second device and in a second player; decoder tolerance varies enough that a clip which fails in one application plays normally in another. For stills, a file that renders as a gray block or half an image is partially overwritten and will not fully recover, while a file that fails to open at all may be intact with a damaged header. Repair is a distinct discipline from recovery, and it starts with why recovered files often will not open.
Playbook E: The Card Is Not Detected Anywhere
Move the card to a different reader and a different computer before drawing conclusions; readers fail more often than cards. If the card appears in Disk Management with the correct size but no drive letter, the hardware is alive and imaging is a realistic option. If it appears with a fixed, tiny capacity — 30 MB, 32 MB, 0 bytes — the controller is likely reporting its own firmware area instead of the flash, which is a hardware failure that software cannot reach.
Do not run a file-system repair on an undetected card, and do not subject it to repeated power cycles. Work through the decision tree for a card the computer cannot see, and if the card stays invisible, treat it as a laboratory case.
Playbook F: Internal Camera Memory, Drones, and Phone Libraries
Onboard storage on a camera or drone is not a card, and the rules differ. Some models expose internal storage over USB and allow a normal scan of the mounted volume; others lock it behind the device’s own firmware, and it can only be extracted through a vendor utility. Certain enterprise and cinema devices encrypt internal storage, in which case the recovery depends on the device still being able to unlock it — no recovery tool bypasses an encrypted partition, and any product claiming otherwise should be treated with suspicion. Where the device cooperates, extracting data from internal camera memory describes the approach.
For phone libraries, check the application’s own trash first. The iOS Photos app keeps deleted items in a “Recently Deleted” album for 30 days, and Android gallery apps have equivalents. This is not a recovery mechanism — those are complete, intact files that were never unlinked — but it is the fastest possible fix. Emptying that album is the act that removes the directory entry, and after it has been emptied on a modern phone, the operating system may already have issued a discard operation to the storage, which is why phone recoveries succeed far less often than card recoveries.
Matching the Method to the File Type You Are Chasing
The failure type tells you which path to take; the file type tells you how well that path will perform.
| File type | Recovery behavior | What limits the result |
|---|---|---|
| JPEG | Carves reliably; self-contained with a start and end marker | A partially overwritten file decodes with gray bands |
| Vendor RAW (NEF, ARW, CR3, RAF) | Carves by TIFF-based header | Damaged raw data is unreadable, but the embedded JPEG preview often survives |
| MP4 / MOV | Carves by ftyp box; needs the metadata index to play | A missing index makes the clip unplayable even when every frame is intact |
| Chaptered action-cam clips | Each chapter is a separate file | One lost chapter breaks the sequence; the series must be rejoined |
360 footage (.insv) | Two fisheye streams plus gyro metadata in one file | Not viewable without stitching; preview players show a distorted frame |
| Cinema RAW (BRAW, R3D, ProRes) | Proprietary containers with sidecar metadata | Usually needs the originating toolchain; a lab is often the better route |
| HEIC / HEVC | Carves by brand identifier | Older repair tools cannot parse the codec and report a healthy file as broken |
Two entries deserve emphasis. Damaged RAW files are frequently worth attempting even when the main image data is unreadable, because most RAW containers embed a full-size JPEG preview that can be extracted separately — a usable deliverable from a file that appears lost. And cinema formats are the one category where a software-first approach has a poor record: proprietary containers with sidecar metadata frequently need the originator’s own tooling or a lab.
Why Video Fails Differently From Stills
A photograph is a self-contained stream of bytes. A video file is a container holding a media stream plus an index that says where each frame begins, how long the clip runs, and how the audio and video tracks align. The index is written last, when recording stops cleanly.
That single design fact explains the most common video complaint. If power is cut, the battery dies, or the card is pulled while a clip is recording, the frames that were already written are usually all there — but the index was never completed. The file is not damaged. It is unindexed, and players that trust the index refuse to open it. Rebuilding the index, or remuxing the intact stream into a fresh container, produces a playable clip. This is why a recovered video that will not play should be repaired rather than discarded, and the same logic covers the general case of repairing corrupted video files.
The second difference is exposure. Video files are large and occupy many thousands of clusters, so a single new recording that lands on part of the freed space damages a fraction of a clip rather than one whole photo. The practical effect is that after a format plus reuse, a photographer may lose 20 percent of a shoot while a videographer may recover every clip but with several that stop partway through.
Expected Success Rates, and the Cases No Software Can Fix
Honest expectations are more useful than optimistic ones, because they determine whether you stop at software or escalate.
| Situation | Typical outcome | Reason |
|---|---|---|
| Files deleted, card untouched since | Usually complete recovery | Data uncovered; only the directory entry was cleared |
| Quick format, card untouched since | Usually complete recovery | Format rewrote metadata only |
| Quick format, some new files written | Partial recovery | New files claimed part of the freed space |
| Card corrupted, structure intact | Often recoverable with names | Partition-level repair can restore the tree |
| Files present but unreadable | Mixed; depends on the file | Header or index damage is repairable, overwritten data is not |
| Full format or secure erase | Not recoverable | Every sector was physically overwritten |
| Data already overwritten by reuse | Not recoverable | The bytes are gone; no tool reads what is no longer there |
| Encrypted internal storage with a failed key area | Not recoverable by software | Key material is unreachable |
| Physically damaged card, cracked or burnt | Laboratory only | The controller must be addressed directly |
The rule underlying every row: data that has not been overwritten can be fully recovered, data that has been overwritten cannot be recovered by any software, and media that has suffered physical damage requires a laboratory rather than a download. The estimator’s view of that boundary is set out in when data is genuinely unrecoverable, and the cost-benefit comparison for escalating a case is in whether a data recovery lab is worth it.
Escalate to a laboratory when: the card is cracked, bent, or visibly heat-damaged; it has been submerged; it becomes hot to the touch when connected; it is an encrypted professional medium whose key area is damaged; or a first recovery attempt produced nothing at all from a card that should have held data. Do not attempt repeated recovery passes on a failing card — each power cycle is a further test of a device that is already unreliable.
A Ten-Step Sequence That Covers Almost Everything
- Stop using the device. Power the camera off rather than leaving it idle; some models write settings and preview files on shutdown.
- Remove the card and do not put it back. Do not reformat, do not take test shots, and do not accept a format prompt from any operating system.
- Write down the facts. What was lost, when, which operation caused it, and what has been done to the card since. This record shapes every later decision.
- Use a card reader, not the camera. USB tethering gives the camera’s firmware an opportunity to write.
- Image the card before any scan or repair if the contents cannot be replaced, using
ddrescueor an equivalent; work on the image from then on. - Take the cheapest diagnostic first. Does the card enumerate, and with the correct capacity? That single check decides whether you have a software problem or a hardware one.
- Choose your path deliberately using the failure-type tables above, rather than installing whatever tool appears first in a search.
- Scan in deep or signature mode and use previews to select, rather than recovering everything and sorting afterward.
- Save the results to a different drive. Never onto the card and never onto the image.
- Verify, then duplicate. Check that stills open fully and that video plays end to end, then keep two copies of the recovered set. Verification practice is described in how to verify recovered files.
If a step fails, resist the urge to improvise. The actions that feel productive — reformatting to “clear the problem,” running a repair utility, trying three tools in sequence on the original card — are the ones that consume the evidence. The behaviors to avoid are catalogued in recovery mistakes that end a case, and the stills and video workflows themselves are documented in camera photo recovery, camera video recovery, and RAW photo recovery.
Frequently Asked Questions
What is the first thing to do when camera data is lost?
Stop using the device and remove the card. Every additional write reduces what can be recovered. Do not format, do not accept a format prompt, and do not run a repair utility. Remove the card, put it in a card reader, and scan it or image it before doing anything else.
Should I image the card before running recovery software?
Yes, if the files matter. A byte-for-byte image made with a tool such as ddrescue lets every later attempt run on the copy, so a failed scan, a wrong tool, or a corrupted repair costs nothing. The original card stays untouched, which also preserves it as evidence.
Can free recovery software do the same job as paid software?
Sometimes. Free tools such as PhotoRec recover files well from a freshly formatted card that has not been reused. Paid tools earn their cost on cards that have been written to since the loss, on vendor RAW formats, on video that needs its container rebuilt, and wherever previews are needed to choose between hundreds of candidates.
When should I stop trying and send the card to a recovery lab?
Send it in when the card is physically damaged, has been submerged or exposed to heat, becomes hot when connected, reports a tiny fixed capacity, or when a first pass on a card that should have held data returns nothing. Laboratory work is the only route to the flash in those cases.