My SD card suddenly stopped working and now my phone and computer both say it needs to be formatted before I can use it. It has important photos and videos on it that I haven’t backed up, so I’m trying to recover the files before doing anything that could erase them. I need help with safe SD card data recovery steps and tools that actually work.
I found out the annoying way that an SD card doesn’t need much to go bad. One moment it mounts fine, next it throws an unreadable error and you’re stuck staring at your files like they already left the room. I’ve had it happen after a camera freeze, a transfer cut short, a battery dying mid-recording, and once from pulling the card too fast. Dumb mistake, yep.
The part people miss is this. Corruption does not always mean the photos, videos, or docs are gone. A lot of the time the mess is in the file system, while the actual data is still sitting there.
First move, do not accept the instant fix popup. If Windows, Android, your camera, or anything else tells you to format the SD card, stop there. Don’t hit format while your files still matter.
Pull the data off first.
I usually start with Disk Drill. It’s been one of the less painful options for busted cards, and I like being able to make a byte-for-byte image before scanning. That matters. You scan the backup image instead of hammering the original card over and over. Once your recovered files are copied somewhere else and you’ve checked they open fine, then deal with repairing the card.
After I’ve got the data safe, I usually go through fixes in this order.
Method 1: Run CHKDSK on the File System
This is the plain Windows route. CHKDSK goes after file system damage, not failing flash chips, so it’s a decent first try when the card suddenly won’t open, shows weird errors, or keeps asking for a format.
Here’s the process:
1. Put the SD card into your PC.
2. Open File Explorer and check which drive letter it got.
3. Open the Start menu and search for Command Prompt.
4. Right-click it and run it as administrator.
5. Type chkdsk X: /r, then swap X for your SD card’s drive letter.
6. Press Enter and leave it alone until it finishes.
Large cards take time, so don’t assume it froze after two minutes. If the issue is damaged file system records, CHKDSK sometimes brings the card back without much drama.
Method 2: Rebuild the Lost Partition with TestDisk
If CHKDSK does nothing, or the card shows up as unallocated space, missing capacity, or a vanished partition, I move to TestDisk.
This tool goes after partition structure problems. Different problem, different fix. Sometimes the files are still on the card, but the map pointing to them is broken, so the system treats the card like empty junk.
What I do:
1. Download and open TestDisk.
2. Pick the SD card from the drive list.
3. Use the partition table type it suggests.
4. Select Analyze.
5. Run Quick Search and wait.
6. Check the partitions it finds.
7. If the missing one looks right, choose Write to restore the partition table.
8. Restart the computer if it asks.
Yeah, the interface looks ancient. Still works. I’ve had cards look fully dead, then TestDisk found the partition and brought them back.
Method 3: Format the SD Card
If neither of those fixes gets the card working again, formatting is the last repair step.
By then, your files should already be recovered and copied somewhere safe. At this point, formatting is not about saving data. It’s about rebuilding the file system so the card has one last shot at being usable.
Steps:
1. Open File Explorer.
2. Right-click the SD card and choose Format.
3. Pick exFAT unless your device needs something else.
4. Leave allocation unit size on Default.
5. Click Start.
6. Wait for it to finish.
If the format works and the card behaves normally after, fine. If it keeps corrupting again, I stop wasting time. Repeated corruption usually points to hardware wear, not some one-off software glitch. Flash memory dies in a boring, messy way. When a card starts doing this more than once, I replace it and move on. Learned tht one after trusting a flaky card twice. Bad idea.
1 Like
Do not write to the SD card again. No new photos, no repair apps on the phone, no format prompt. Every write lowers your odds.
I agree with @mikeappsreviewer on one big point, image the card first if the reader still detects it. I disagree on running CHKDSK early if your photos matter a lot. CHKDSK is a repair tool. It changes the file system. On a shaky card, I’d rather recover first, repair later.
What I’d do:
-
Try a different card reader, and a different USB port.
A bad reader causes fake corruption all the time. Seen it more than once. -
Check Disk Management on Windows.
If the card shows the right size, even as RAW or unallocated, recovery odds are often decent. -
Make an image of the card, then scan the image.
Disk Drill is solid for this. It handles corrupted SD cards well, and scanning an image is safer than rescanning the card over and over. If you want a plain-English take, this Disk Drill review for SD card and photo recovery covers the basics. -
Save recovered files to your PC, never back to the SD card.
Sounds obvious, people still do it. Then stuff gets overwritten. Oof. -
If the card disconnects, gets hot, or reads at 0 bytes, stop messing with it.
That points more to hardware failure than file system damage.
One more thing. If your videos come back but won’t play, don’t assume they’re dead. Some recovery apps restore fragmented video files with broken headers. Those sometimes need a repair tool after recovery.
If the photos are irreplaceable, skip DIY after the image attempt and go to a recovery shop. Bit expesnive, but cheaper than losing wedding pics or baby videos forever.
I’d be a little more cautious than @mikeappsreviewer on repair-first stuff, and mostly with @himmelsjager on this one: treat the card like evidence, not a thing to “fix” yet.
What I’d add is this: check whether the card is actually failing at the hardware level before you spend hours on file system tools. If Windows hangs when you click it, the card randomly disconnects, or capacity shows up wrong one time and normal the next, that’s a red flag. In that case, every extra read can make things worse.
A few things I’d do that haven’t really been stressed enough:
- Slide the little lock switch on the SD adapter to read-only if you’re using a full-size adapter. It’s not perfect, but it can help prevent accidental writes.
- Try reading it on a Linux machine or a Linux live USB. Sometimes Linux will mount a card that Windows just calls RAW and refuses to touch.
- If it mounts even briefly, copy the most important folders first manually before doing deep scans.
- Check for hidden files. Sometimes corruption is less dramatic than it looks.
If you can still detect the card, making an image and scanning that with Disk Drill is probly the safest DIY route. That part I do agree with. Also save recovered files to an internal drive, not another flaky USB thing.
If recovered videos won’t open, they may need separate video repair afterward. That happens a lot with interrupted recordings.
Also, this video guide to fix a corrupted SD card and recover lost files is worth a look.
One blunt truth: if the card reads as 0 bytes or is not detected consistently across devices, stop poking at it. That’s where DIY gets real sketchy, real fast.
One thing I’d push harder than @himmelsjager, @nachtdromer, and @mikeappsreviewer is checking the card’s health behavior before any long scan. If reads are painfully slow, the card vanishes mid-copy, or the system freezes when opening it, stop doing “just one more try.” That usually means physical failure, not simple corruption.
My order would be:
- Use a decent USB reader, ideally another brand.
- If the card appears at the correct size, clone it once.
- Work from the clone or image only.
- Sort recovered files by type and preview a few immediately so you know whether recovery is real or just filenames.
I slightly disagree with using repair tools too soon even if the card still mounts. A card that is barely readable can get worse fast.
Disk Drill is fine for this because imaging + recovery in one place is convenient.
Pros:
- easy image creation
- good photo/video recovery
- preview helps verify files
Cons:
- not the cheapest
- deep scans can take a while
- results drop hard if the card has hardware failure
If the card is unstable or 0 bytes, skip DIY and go to a lab.