My camera froze and crashed while saving photos, and now the SD card shows as corrupted and unreadable. I’m trying to recover my pictures and figure out if the card can be repaired without losing everything. What should I do first, and are there any safe SD card recovery steps that actually work?
I’ve had SD cards fail at the dumbest times. End of a shoot. Last clip on a trip. Right when I sat down to copy files off. If your card suddenly reads as corrupted, slow down for a minute. The order matters a lot here if you want your files back.
The first trap is the system prompt. Windows loves showing “You need to format the disk in drive X: before you can use it.” Phones do the same thing with “SD card is corrupted” and a big repair button. Don’t hit Format. I did this once years ago on a cheap card and made recovery way harder than it needed to be. Formatting removes the file system info your device uses to track files. Quick Format is still bad news. Full Format is worse. If the photos or video matter, close the prompt and stop poking at the card.
The rule I stick to is simple. Recover first. Repair after. If you try to fix the card before copying data off, you risk changing the structure on disk and overwriting stuff you still need.
For recovery, I’ve had the best results with Disk Drill. What made the difference for me was the byte-to-byte backup feature.
Here’s why I care about that part. A corrupted SD card is often either a damaged file system or a card with hardware starting to fail. Each read puts more load on it. If you scan the original card over and over, you’re rolling dice. I’ve seen cards vanish mid-scan. Making a full image first, sector by sector, gives you a safer copy to work from on your computer. Then you scan the image, not the card. If the original dies later, your recovery shot is still alive. After scanning, check the previews and save recovered files to a different healthy drive.
Only after your files are safe should you try fixing the card itself. This is the sequence I follow.
1. Run CHKDSK
Start with Windows’ built-in check tool. It fixes file system issues and sometimes brings a card back without much drama. Open Start, type cmd, then run Command Prompt as administrator. Enter chkdsk X: /r and swap X for your SD card’s drive letter. The /r part tells Windows to scan for bad sectors and recover readable data where possible. On bigger cards, this drags a bit. Let it finish.
2. Try TestDisk
If the card shows up as unallocated, or the partition is missing, CHKDSK often won’t help much. This is where TestDisk comes in. It’s open source, old-looking, and kind of ugly, but it works on problems newer tools sometimes skip over. I used it once on a card my laptop wouldn’t even show in File Explorer, and it found the lost partition table after a deeper scan. If your partition got wiped or broken, TestDisk has a shot at rebuilding it.
3. Format the card
If neither of the first two fixes gets the card stable again, then format it. At this point your files should already be recovered elsewhere. In File Explorer, right-click the card and choose Format. I’d skip Quick Format and do the full one. It takes longer, but it checks the card more thoroughly. For file system, exFAT is usually the right pick for modern SD cards, especially if you record larger video files. FAT32 tends to get annoying fast with file size limits.
If the card starts working again after all this, I wouldn’t trust it for important stuff. Once an SD card starts corrupting, I treat it like a warning, not a one-time fluke. I keep those cards for throwaway transfers or testing, if I keep them at all. For anything important, I replace them.
One last thing. Eject the card properly every time. I know people skip it. I skipped it too. Then I paid for it. “Safely Remove Hardware” exists for a reason, and a lot of card corruption starts with pulling storage out while writes are still finishing.
2 Likes
First, stop using the card. Don’t shoot more photos, don’t let the phone or PC “repair” it, and don’t copy anything onto it. New writes kill recovery odds fast.
I agree with @mikeappsreviewer on one big point, recover first. I disagree a bit on running CHKDSK early. If the crash happened mid-write, CHKDSK sometimes “fixes” the file system by removing broken entries, which is bad if those entries point to your missing photos. I treat CHKDSK as a later step, not step one.
What I’d do:
-
Try the card in a diffrent reader.
A lot of “corrupted” cards are bad USB readers. Use a decent USB 3 reader if you have one. -
Make an image of the card first.
Disk Drill is good for this because it lets you scan the image instead of stressing the original card again and again. Best move if the card is flaky. -
Recover files from the image.
Save recovered photos to your computer or another drive, never back to the SD card. -
If photos are fragmented, try camera-specific recovery tools too.
For RAW and video files, sometimes PhotoRec pulls files other apps miss. File names and folders will be a mess, but pics are pics. -
After recovery, full format the card in the camera, not Windows.
Cameras often write the folder structure they expect, like DCIM and vendor-specific stuff. If the card fails again, toss it. SD cards are cheap, reshoots are not.
If the card is not detected anywhere, or shows 0 bytes, that points more to hardware failure. At that point software recovery gets iffy.
If you want a quick walkthrough on Disk Drill recovery steps, this video is useful:
watch this Disk Drill photo recovery guide
One more thing, if your camera battery died or froze during buffer flush, some files might be recovered but not open cleanly. I’ve had JPEGs come back half-gray and RAWs recover fine, so test evrything.
Don’t try to “repair” it first. That’s the part I’d push back on a little, even though @mikeappsreviewer and @sternenwanderer are right about stopping use immediately. If the camera crashed mid-write, the card may be fine physically and only the file allocation got scrambled. The safest move is to treat it like evidence, not storage.
What I’d add:
- Clean the contacts and reseat it. Seriously. A dirty SD contact can fake corruption.
- Check Disk Management on Windows or Disk Utility on Mac. If the card shows the correct size, that’s a way better sign than if it shows 0 bytes.
- If your camera brand has its own recovery utility, try that after imaging. Canon, Nikon, Sony, etc sometimes produce files with weird metadata that generic tools don’t rebuild perfectly.
I’d still use Disk Drill, mostly because it handles photo recovery well and lets you work from a disk image instead of the original card. That matters a lot if the card keeps disconnecting. Also sort recovered files by type and timestamp, because after a crash the folder structure is often toast but the images are still there.
One thing I disagree with a bit: if this card mattered enough for paid work or irreplaceable family pics, I would not “repair and keep using it” afterward. Nah. Retire it. Cards are cheap, regret is expensive.
If you want a walkthrough, this corrupted SD card recovery and repair video guide is pretty easy to follow.
If it reads 0 MB, asks to insert disk, or disconnects constantly, that’s probly hardware failure and software fixes get real shaky fast.
Big thing I’d add to what @sternenwanderer, @techchizkid, and @mikeappsreviewer already covered: check whether the damage is logical or physical before you do anything heavy.
A quick triage:
- If the card mounts, shows roughly the right capacity, and just says “needs formatting,” that usually means file system corruption.
- If it shows 0 bytes, wrong size, vanishes during reads, or gets unusually hot, that smells like hardware failure.
I actually disagree a little with the “try every tool” instinct. Too many repeated scans on a dying card can make a bad situation worse. If the card is unstable, do one controlled pass only, ideally to clone/image it.
Also worth trying:
- Lock the SD card’s write-protect switch before inserting it into a computer. It is not perfect, but it can prevent accidental writes.
- Use the camera only to test detection, not to repair. Some cameras will offer to “recover database” or similar, and that can help for video, but I would only risk that after copying data elsewhere.
- On Linux or macOS, sometimes a card that Windows refuses will still mount read-only long enough to copy files.
About Disk Drill since it came up:
Pros:
- easy imaging workflow
- solid photo preview support
- beginner-friendly
- good for scanning a card image instead of hammering the original
Cons:
- not my first pick for deep partition repair
- can miss some oddly fragmented video files
- paid features may be needed depending on what you recover
So my order would be: stabilize, identify whether the card is physically failing, make one image if possible, recover from that image with Disk Drill or another tool, then retire the card if it ever corrupted during an in-camera write. Even if you “fix” it, I would not trust it again for important shoots.