SD card recovery mistakes are the reason most “unrecoverable” cards became unrecoverable. The data is almost never destroyed by the event that lost it — a delete, a format, a power cut all leave the recorded bytes in place. It is destroyed by what happens over the next hour, because the common instinctive reactions either write over the footage or rewrite the structures needed to find it. The single most useful rule is short: the safest card is the one you have stopped touching.
The five mistakes below account for the great majority of permanent losses, and each has a mechanism worth understanding rather than a rule worth memorizing. Where you have already made one, the relevant section explains what is still recoverable and what is not.
Why the wrong first move costs more than the original failure
A camera card loses data in two stages. The first stage makes files inaccessible: the directory entry is removed, the file system is rewritten, or a recording is left unfinished. In this state the image and video data is still physically present in flash memory, and a scan can usually find it.
The second stage makes the loss permanent: something writes to the card. Flash memory cannot be written in place, so every write allocates a fresh block and the previous contents of that block are gone. Once the blocks that held your photographs have been reused, no tool can bring them back.
Everything here is a variation on one theme: preventing writes between the moment the loss occurs and the moment the data is copied off. The full sequence is set out in the camera data loss emergency guide.
Mistake 1: letting the camera “repair” the card
Most cameras offer a recovery or repair option when they detect an unreadable card, and some present it at startup as a prompt. Accepting it is usually the worst available choice.
The camera’s repair routine is a file system rebuild, not a data recovery operation. It rewrites the card’s allocation structures so the card mounts again, and it has no concept of the files it is abandoning. What it reliably achieves is making the card usable, which is the opposite of what you want: an unreadable card is a card whose data has not been touched.
The same applies to letting the camera format the card after a failed shoot. A camera format is a quick format — the directory table and file allocation table are rewritten while the data stays where it is — but the camera immediately creates fresh folders and is ready to record over your files, which is why the difference between in-camera and computer formats matters more than the format itself.
Decline the prompt, power the camera off, and take the card out.
Mistake 2: keeping the card in service
The temptation after a scare is to prove the card still works. Shoot a few frames, check that they appear, carry on. Each of those frames is written to blocks that previously held photographs you wanted.
The risk is easy to underestimate. Free space in flash is not a reserved region: the controller may allocate a new write to any erased block, including one previously used by a deleted file. One test shot can overwrite the start of a JPEG, and a JPEG with a corrupted header does not open at all.
If the shoot must continue, put a different card in the camera. Cards are cheap relative to shoots, and a card that has shown any instability has earned retirement from primary duty regardless of its file system state. The warning signs — write errors, dropped frames, sudden slowness — are catalogued in the article on cameras that corrupt their own cards.
Mistake 3: repeatedly inserting and removing the card to test it
When a card is not detected, the natural diagnostic is to try it again — in another reader, another computer, the camera. This one is more nuanced than the others, because the first insertion in a different reader is genuinely worth doing.
The damage comes from the loop. Each insertion is a power cycle and a controller initialization, and on a marginal controller that is the moment failures become permanent: a weak controller can corrupt the file system structures it rewrites during mount. Contacts on a worn card and reader can also scratch the interface.
The disciplined approach is to test once, in one known-good reader, then stop and decide. If the card does not appear in a single attempt, the problem is either the controller or the file system, and both need a considered decision rather than a fourth insertion. The decision tree for that moment is in the guide to what to do when a card is not detected.
Mistake 4: powering on a wet or physically damaged card
A card that has been through water, dropped in sand, or exposed to heat needs one thing before anything else: it needs to stay switched off.
Applying power to a wet card converts a recoverable situation into an unrecoverable one. Water, especially salt water, is conductive, and contamination between the card’s pads can short a powered circuit. The traces are measured in micrometers, and electrolytic corrosion proceeds quickly once current flows. Cards never powered after a soaking frequently read normally after drying; cards plugged in to “see if they work” frequently do not.
The same logic applies to a card with visible physical damage — a cracked body, bent contacts, or a loose housing. Inserting it can bend the reader’s own pins and short across the card’s contacts. Photograph the damage, bag the card, and treat it as a laboratory case. Both scenarios have their own protocols, covered in the guides to water damaged cards and physically broken cards.
Mistake 5: saving recovered files back to the source card
This is the mistake that quietly destroys the most work, because it happens at the end, when the user believes the job is done.
Every recovery tool offers a destination folder, and the source card is always in the list. Choosing it writes the recovered files to the very medium being scanned, overwriting clusters the scan has not yet reached.
The rule is absolute: recovered files go to a different physical drive. Not a different folder on the same card, not the camera’s internal memory, and not a partition on the same device. A USB drive, an external SSD, or the computer’s internal disk all work. Check the tool’s behavior before starting, and set the destination explicitly rather than accepting a default.
The full list of mistakes, and what to do instead
| Action | What it actually does | Can it be undone |
|---|---|---|
| Accepting the camera’s repair prompt | Rebuilds the file system, abandoning the directory entries | Partially; a deep scan may still find the files |
| Formatting the card in the camera | Quick format; data stays, but the camera writes new folders | Yes, if nothing else is written afterwards |
| Running a file system check or repair utility | Rewrites allocation structures and may convert orphans to .CHK files | Partly; it can make files harder to identify |
| Taking a test shot on the same card | Allocates blocks that may have held deleted files | No |
| Toggling the write-lock switch and retrying | Prevents writes while set, but a physically failing controller still fails | Yes, the switch itself is harmless |
Two rows deserve emphasis. The file system check is the one people perform in good faith after reading that it “repairs” a card. It does repair the file system — which is exactly the problem, because the structures it repairs are the evidence a recovery scan needs. It also writes to the card while doing so. If the files are visible in the file browser, copy them off first; if they are not, a file system repair will not bring them back and may remove the traces that would have.
The write-lock switch is a genuine exception to a common piece of bad advice. Some guides warn people never to touch the lock tab in case it sticks. In practice, setting the lock is the one action on this list that reduces risk: it makes the card read-only at the reader level, so an accidental copy-back or a photo application’s automatic import cannot write to it. If your card has a lock tab, use it.
The correct sequence is short: stop using the card, keep it out of the camera, set the write-lock if the card has one, and copy everything still readable to a different drive. If the files are not visible, image the card once and scan the image so the original is read only a single time.
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. Data that has not been overwritten comes back in full; data that has been overwritten is beyond any tool’s reach.
One distinction matters more than any of the five mistakes: a card that is logically damaged — files deleted, card formatted, recording interrupted — is a software problem, while a card that is physically damaged, submerged, or electrically destroyed is a laboratory problem. Mixing them up is the most expensive mistake of all. The criteria for when data is genuinely unrecoverable are worth reading before either decision.
Frequently Asked Questions
Should I run chkdsk or a repair tool on my SD card?
No, not before copying anything readable. A file system repair rewrites the allocation structures a recovery scan depends on, and it writes to the card in the process. If your files are visible in the file browser, copy them off first. If they are not visible, a repair will not restore them and may destroy the traces that would help.
Will formatting the card again make recovery impossible?
Not by itself. A camera format is a quick format that rewrites the file system and leaves the recorded data in place until it is overwritten. What makes recovery impossible is writing new files. Reformatting is dangerous mainly because a camera immediately creates fresh folders and is ready to record.
Can I shoot on the card while I decide what to do?
No. Each new photograph or clip allocates flash blocks that may hold the deleted files you are trying to recover. A single test shot can overwrite the start of a JPEG or the index of a video clip. Use a different card for anything you still need to shoot.
I already did one of these things. Is my data gone?
Usually not entirely. The decisive question is whether the card has been written to since the loss. If it has not, a scan will normally find the files. If it has, the survivors are those stored in blocks that were not reused, which is often most of them, but the outcome has to be discovered by scanning.