My SD card suddenly shows as corrupted and I can’t access my photos and files. It was working fine earlier, and now my phone and computer either won’t read it or ask me to format it. I need help figuring out the safest first step to recover the data without making the SD card corruption worse.
I hate this one because I’ve had it happen right after a full shoot, when all I wanted was to dump the files and go to sleep. You insert the SD card, your laptop or phone throws up 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.
If you care about the files, formatting is the wrong first move. It rewrites the file system info your device uses to locate your photos and video. A quick format already makes recovery harder. A full format digs the hole deeper. When I see those prompts, I back out, remove the card, and treat recovery as the only job.
The order matters. Recover first. Repair later. If you try to fix the card before pulling your data off it, you risk changing the layout of the card and losing what was still recoverable.
For recovery, I’ve had the best results with Disk Drill. The part I care about most is the byte-to-byte backup feature. If a card is failing, each extra read can push it closer to dead. I learned this the ugly way on a 128GB card that started disconnecting mid-scan. A normal scan kept choking. Making an image first was what saved the files.
So, instead of hammering the SD card directly, create a full image of it on your computer. Sector by sector. Then scan the image, not the physical card. That cuts the risk a lot, especially if the card keeps dropping out, mounting weird, or showing random errors. After the scan, preview what you find and recover everything to a different drive. Not back onto the same SD card. I know it sounds obvious, but people do it.
Only after your files are safe should you try to make the card usable again. This is the sequence I stick to.
1. Run CHKDSK first
On Windows, open Start, type cmd, then run Command Prompt as administrator. Enter chkdsk X: /r and swap X for the SD card’s drive letter.
The /r part is the one you want. It tells Windows to look for bad sectors and attempt to recover readable data from them. If the issue is file system damage and not full hardware failure, this sometimes gets the card back into a readable state. It can take a while, esp on larger cards, so let it finish.
2. Move to TestDisk if the partition looks gone
If the card shows as unallocated, or the partition vanished from File Explorer, CHKDSK often won’t get you far. That’s where TestDisk comes in. It’s old-school and not pretty, but I wouldn’t write it off because of the interface. It’s one of the few tools I’ve seen pull a missing partition table back into place.
You step through menus, let it analyze the card, and if it finds the lost partition, it gives you the option to write the structure back. I’ve used it on cards and USB drives that looked empty even though the data was still sitting there. Bit nerve-racking the first time, but it works if you follow the prompts carefully.
3. Format the card only if recovery is done and repair failed
If CHKDSK does nothing and TestDisk doesn’t fix the layout, then format it. Right-click the card in File Explorer, choose Format, and I’d skip Quick Format. Full format takes longer, but on a sketchy card I want the system checking the surface instead of rushing through.
For file system, exFAT is the safer pick for most current SD cards, especially if you shoot large video files. FAT32 still exists, sure, but it becomes annoying fast with bigger files.
If the card starts working again after all this, I still wouldn’t trust it with anything important. 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 paid work or family photos, I replace them.
One last thing, because this gets ignored way too often. Use Eject or Safely Remove Hardware before pulling the card. A lot of corruption starts with yanking storage out while writes are still finishing. It feels minor until you lose a whole day’s files over one impatient click.
2 Likes
First move, stop using the card. Don’t take more photos, don’t copy stuff onto it, don’t let your phone ‘repair’ it. Every write lowers your odds.
I agree with @mikeappsreviewer on one part, recover before repair. Where I differ is CHKDSK as an early step. If your photos matter, I would not run a repair tool first. CHKDSK changes file system records. Sometimes it helps. Sometimes it makes photo recovery messier, esp if the card has bad sectors or the folder structure is already broken.
What I’d do first:
-
Try a different card reader.
A lot of ‘corrupted’ cards are bad readers, dirty contacts, or weak USB ports. Use a diffrent reader and a different USB port on a computer, not your phone. -
Check if the card shows the right size in Disk Management.
If Windows sees the full capacity, recovery odds are better.
If it shows 0 bytes, no media, or keeps disconnecting, the card itself is failing. -
Make an image of the card, then scan the image.
This is where Disk Drill makes sense. It’s easier than a lot of other recovery tools, and imaging first is the safer play if the card is unstable. Recover files to your PC or an external drive, never back to the SD card. -
If you want a walkthrough, this video is decent:
see how Disk Drill recovers files from a damaged SD card -
After recovery, test the card.
Use H2testw on Windows or F3 on Mac/Linux. Fake or worn-out cards often pass for months, then fail all at once. If errors show up, toss it. No second chances, imo.
If the card is unreadable on multiple devices and won’t stay connected, skip repair attempts and focus on recovery fast. If Disk Drill or similar tools can’t read it at all, you’re getting into hardware failure territory.
First thing I’d try is the boring physical stuff before doing any “fix.” I know @mikeappsreviewer and @ombrasilente already covered recovery-first pretty well, and I mostly agree, but I’d add this:
Clean the card contacts gently with a dry microfiber cloth, then test it in a USB reader on a desktop or laptop. Not through a cheap hub. I’ve seen “corrupted” cards turn out to be bad contact, low power from a flaky port, or the phone itself being weird.
Also check whether the little lock switch on the SD adapter got slid by accident. Sounds dumb, happens alll the time.
If the card mounts even briefly, copy the most important files first manually before doing a full scan. Start with DCIM or your project folders. Sometimes you only get one stable read session.
If it keeps dropping, then yeah, Disk Drill is a solid next move, esp if you can image the card and work from that instead of stressing the original media. I would avoid “repair” prompts completely until the files are off.
One more thing people skip: look at the card in Device Manager or System Information. If the controller is identifying inconsistently or under the wrong size, that smells more like hardware death than simple corruption.
And if you want a visual walkthrough, this is pretty on-point:
how to recover data from a corrupted SD card and fix it safely
If the data matters a lot, retire the card after recovery. These things lie, then fail again.
Skip one thing I often see missed: check SMART-like behavior is impossible on most SD cards, so you need to judge health by symptoms. If the card changes capacity, shows RAW sometimes, or disconnects under light reading, treat it as failing hardware, not just corruption. In that case I actually disagree a bit with the “try every software fix” route from @mikeappsreviewer. Too much poking can waste the little life it has left.
My order would be:
- Read-only attempts only if possible. Some readers respect write protection better than phones.
- Use a Linux live USB and see if the card mounts there. Linux sometimes reads media Windows refuses.
- If it mounts, copy only the irreplaceable files first.
- If it does not, image it and recover from the image.
Disk Drill is fine for that because it is easier than TestDisk for most people.
Pros of Disk Drill:
- simple interface
- byte-to-byte backup option
- good for photo recovery
- preview is useful
Cons:
- not the cheapest
- deep scans can take ages
- less transparent than command-line tools about what it is doing under the hood
One more practical thing: if this card came from an online marketplace or unknown seller, assume counterfeit until proven otherwise. After recovery, verify it with H2testw or F3 and retire it anyway. @ombrasilente and @sternenwanderer are right to prioritize recovery first.