Need help recovering files from a corrupted SD card after camera error

My camera suddenly showed an error while I was taking photos, and now my SD card looks corrupted. I can’t open the card on my camera or computer, and I’m trying to recover important photos and videos that weren’t backed up. What’s the safest way to recover data from a corrupted SD card after a camera error without making things worse?

I hate this error because it never shows up on a lazy Sunday. It shows up after a long shoot, when your battery is low, or when you finally sit down to copy footage and go to bed. I’ve had SD cards fail on me more than once, and the pattern is always the same. Panic makes people click the wrong thing first.

If your laptop, phone, or camera throws a message like “You need to format the disk in drive X:” or “SD card is corrupted, tap to fix,” stop there. Don’t hit Format. Don’t hit Fix. Pull your hands off the keyboard for a sec. Formatting rewrites the file system info your device uses to locate files. A quick format still makes recovery harder. A full format digs the hole deeper. If the files matter, leave the card alone until you’ve tried recovery.

The order matters. I learned this the hard way. Recover first. Repair after. If you try to repair a damaged card before pulling your data off it, you risk changing the structure of the card and losing the stuff you were trying to save.

For recovery, I’ve had the best luck with Disk Drill. What made the difference for me was its byte-to-byte backup option.

Here’s why I care about that feature. When an SD card starts glitching, the issue is often one of two things. The file system is messed up, or the card itself is wearing out. If the hardware side is going bad, every read attempt adds stress. I’ve seen cards drop off mid-scan. So instead of scanning the card over and over, make an image first, a full sector-by-sector copy to your computer. Then scan the image, not the original card. That way the physical card gets one heavy read pass instead of a bunch of repeated pokes. It’s safer, and in my expereince, more consistent. After the scan, preview what you recover and save it somewhere healthy, not back onto the same SD card.

After your files are safe

Only after recovery is done should you try to make the card usable again. This is the order I follow.

1. Run CHKDSK on Windows

Start with the built-in repair tool. Open Start, type cmd, then run Command Prompt as administrator. Enter:

chkdsk X: /r

Replace X with the drive letter for your SD card. The /r switch matters because it checks for bad sectors and tries to recover readable data from them. On a big card, this can take a while. Let it finish. Don’t interrupt it halfway because you got impatient.

2. Try TestDisk if the partition is gone

If Windows shows the card as unallocated, or the partition vanished, CHKDSK often won’t help much. This is where TestDisk earns its keep. It’s old-school and ugly, no pretty interface, but it does serious work with broken partition tables and lost partitions. I’ve used it on cards that didn’t even show up properly in File Explorer. If it finds the missing structure, it can write it back and make the card readable again.

3. Full format as the last move

If neither repair step gets you anywhere, format the card. At this stage your files should already be copied somewhere else. In File Explorer, right-click the card and choose Format. I uncheck Quick Format. It takes longer, but it checks the storage more thoroughly, which is what you want on media that already threw errors. For most newer SD cards, exFAT is the file system I’d pick, especially if you store large video files. FAT32 hits size limits fast.

If the card starts working again after all of this, I still wouldn’t trust it with important work. Once an SD card starts corrupting, I treat it like a sketchy spare tire. Fine for throwaway transfers, not for weddings, travel footage, or anything you’d hate to lose. I replace it and move on.

One more thing, because I learned this one by being careless. Use Eject or Safely Remove Hardware before pulling the card. A lot of corruption starts with yanking it out while data is still being written or cached. It feels small until you lose a whole batch of files over it.

4 Likes

First move, stop trying the card in different devices. Every mount attempt writes logs or retries reads. On a failing SD card, extra reads are not your freind.

I agree with @mikeappsreviewer on one big point, recover first. I disagree a bit on CHKDSK timing for flaky cards. If the card is dying at the hardware level, CHKDSK is rough on it and can make later recovery worse. I save repair tools for after I pull files off, or after I give up on recovery.

What I’d do:

  1. Use a different card reader.
    A lot of “corrupt SD card” cases are bad USB readers. Cheap readers fail all the time. Try a known good USB 3 reader, and if the card is microSD, try a different adapter too.

  2. Check how the card appears in Disk Management.
    If Windows shows the right size, even as RAW or unallocated, recovery odds are still decent.
    If it shows 0 bytes, no media, or keeps disconnecting, the card itself is failing.

  3. Make an image, then work from the image.
    Disk Drill is good for this because it lets you back up the whole card first, then scan the image file instead of hammering the SD over and over. That matters more than people think. A 128 GB card read once is better than read six times while you test random fixes.

  4. If Disk Drill finds files, recover to your PC or another drive.
    Do not save anything back onto the SD card. I know, obvious, but people still do it and then wonder why recovery got worse.

  5. If normal scan misses videos, try file carving tools too.
    PhotoRec is ugly, but it pulls files by signature and ignores the broken file system. Downside, filenames and folder structure are often gone. Upside, I’ve seen it recover MP4 and JPG files from cards Windows refused to open.

If the files are once-in-a-lifetime stuff, stop DIY after the image attempt and send it to a pro lab. If the card clicks, vanishes, overheats, or drops to 0 bytes, don’t keep poking it.

If you want a quick walkthrough on using Disk Drill for SD card recovery, this video helps: how to recover photos and videos from a corrupted SD card with Disk Drill

And yeah, even if you get it working again, I would retire the card. SD cards are cheap. Lost shoots are not.

Don’t keep reinserting it into the camera. That part I slightly disagree on with the usual “test everything” instinct. Cameras can be picky and sometimes will keep trying to write metadata, which is the last thing you want right now.

What I’d check first is whether the card is actually being detected at the hardware level. On Windows, open Device Manager and see if the reader/card shows up there even if File Explorer won’t open it. On Mac, check Disk Utility and System Information. If the card appears with the correct capacity, that’s a better sign than people think. If it shows nonsense size, 0 bytes, or keeps dropping out, that’s when I’d stop messing with it.

Also, if these are camera photos/videos, try software that understands media file structures instead of just generic file copy logic. Disk Drill is a solid pick for corrupted SD card recovery because it tends to find both deleted and inaccessible camera files pretty well. I’d also pay attention to whether your videos are fragmented, since some tools recover the clips but they won’t play right after. That’s not always total loss, just more repair work later.

One thing @mikeappsreviewer and @sterrenkijker didn’t really stress is to check the card reader cable/port power situation. Weak USB ports and flaky front panel readers cause a stupid amount of fake “corruption” cases. Plug directly into a rear motherboard port if you can.

If you want a visual walkthrough, this is pretty relevant: step-by-step corrupted SD card recovery and repair video

If the card gets hot fast, disappears mid-read, or makes the system freeze, quit DIY stuff pretty quik. That usually means the card is physcially failing, not just logically corrupted.

I’m with @sterrenkijker on one key thing: if the card is unstable, repeated attempts are the enemy. Where I slightly differ from @caminantenocturno and @mikeappsreviewer is this: I would also avoid letting Windows auto-mount it if possible. If you have access to Linux, a read-only pass there is sometimes gentler and gives you a cleaner shot at cloning the card before the OS starts “helping.”

A couple things not mentioned yet:

  • Clean the SD card contacts with isopropyl alcohol and let it dry fully. Sounds basic, but dirty contacts can mimic corruption.
  • If it is a microSD in a full-size adapter, replace the adapter first. Those fail constantly.
  • Check whether your camera wrote files in a proprietary folder structure. Some video files need sidecar data or intact folder paths to play properly after recovery.

About Disk Drill: good choice if you want something easier than TestDisk/PhotoRec.

Pros

  • simple interface
  • can create a byte-for-byte backup
  • decent preview support for photos and some videos
  • easier for beginners than command-line tools

Cons

  • not the cheapest option
  • deep scans can take a long time
  • carved recovery may lose original filenames/folders
  • sometimes finds too much junk, so sorting results is annoying

If the recovered videos won’t play, keep them anyway. Corrupt MP4/MOV files can sometimes be repaired later if the raw data was recovered intact.

One more blunt take: if this card held paid work, don’t experiment for hours. One solid imaging attempt, then pro recovery. Cards that suddenly fail during shooting are often already on the way out.