Why memory cards fail — failure modes, prevention, and how to recover the data

Your camera says "card error". Your phone says the SD card "needs to be formatting". You plug it into the laptop and the photos are gone — or it shows up empty, or doesn't show up at all. Before you click anything: stop writing to that card. That one decision, made in the first thirty seconds, decides whether your files come back. This guide covers why cards actually fail, how to prevent most of it, and the exact recovery workflow that gives you the best odds.

How do I recover photos from a corrupted SD card?

Short version, because this is the question people arrive with: stop using the card, make a read-only image of it, then run a free recovery tool on the image — not the original. Image with GNU ddrescue, carve files with PhotoRec, rebuild a broken partition with TestDisk. If the card is physically broken or the computer can't see it at all, don't keep trying — go to a professional. The rest of this page explains each step and why the order matters.

The real failure modes

"My card died" covers several very different problems, and the fix depends on which one you have.

File-system corruption is the one most people actually hit, and the good news is it's the most recoverable. It happens when a write is interrupted — you pull the card out of the camera or reader while the light is still blinking, or the device loses power mid-write. The data blocks may be perfectly intact; what's broken is the index (the FAT/exFAT directory that says where each file lives). The "needs formatting" message is the device finding an index it can't parse. The files are usually still on the card — which is exactly why formatting at that moment is the worst thing you can do.

Counterfeit cards fail in a sneaky way: a card remarked as "256 GB" that's really 32 GB writes fine until you pass the real capacity, then new files overwrite old ones or come back as garbage. The fix is to never trust the label — test the real capacity before you rely on a card. A genuine card of the stated size simply doesn't have this failure mode.

NAND wear-out is the slow death of the flash itself — every block survives a finite number of erase cycles, and a card pushed past its rating starts throwing errors or goes read-only. We won't re-derive the endurance math here; it's covered in full in high-endurance vs consumer microSD, and the matching question of how long a card holds data once it's worn or sits cold is in data retention explained. The practical point for recovery: a card going read-only from wear is actually a gift — read-only means you can still image it and pull the data off.

Controller and firmware failures are the true "dead card" — the tiny processor that translates between the SD interface and the raw NAND stops responding, and the card disappears from the computer entirely or reports zero bytes. There's little a home user can do here; the NAND chip may be fine but only specialist equipment can read it directly.

Physical damage — a cracked card, snapped corner, or bent reader pins — speaks for itself. Don't force it; a professional with the right tools is the only path.

Prevention: the short checklist

Most failures above are avoidable. None of this is exotic:

1. Always safe-eject. Wait for the camera's write light to go dark, and on a computer use "eject" / "safely remove" before pulling the card. This single habit prevents the most common failure — corruption from an interrupted write.
2. Format in the device that uses the card, not in the PC, and ideally with the SD Association's own SD Memory Card Formatter, which formats to the SD spec rather than a generic OS layout [5]. A camera and a card that agree on the file system corrupt far less often.
3. Don't fill past about 90%. Flash needs free blocks to wear-level and manage writes; a card run at 100% full is more prone to corruption and slowdown.
4. Match the grade to the job. Continuous recording (dashcam, security camera, body cam) chews through a consumer card — use a high-endurance grade. See choosing a microSD for dashcams and security cameras.
5. Keep it out of heat. A card baking in a parked car ages faster and loses retention margin. Don't store important media hot.
6. Buy verifiable cards from a known source and write-verify a sample, so a counterfeit never enters service in the first place.
7. Keep a second copy. No card is a backup. The only card that never loses your data is the one whose data also lives somewhere else.

The recovery workflow

If a card has already failed, work in this order. The order is the whole point — get it wrong and you can destroy recoverable data.

Step 1 — Stop writing. Right now.

Pull the card out of the device. Don't let the camera "repair" it, don't click format, don't run chkdsk/Disk Utility "repair", don't save anything to it. Every write risks landing on top of the data you want back. From here on, the card is read-only as far as you're concerned.

Step 2 — Image the card before you touch it

Make a sector-by-sector copy of the whole card to a file on a healthy drive, and do all recovery on that image, never the original. This protects you: if a tool makes things worse, you still have the pristine image, and you can keep the failing card out of harm's way.

The standard free tool is GNU ddrescue, which copies block devices and is built specifically to keep going past read errors — it copies the good areas first and retries the bad ones, which is exactly what a dying card needs [4]. On Linux/macOS the call looks like ddrescue -d /dev/sdX card.img card.log (where /dev/sdX is the card — get the device name right). The log file lets it resume if interrupted. If the card is failing physically, imaging it once with ddrescue and then working only from the image avoids stressing it further.

Step 3 — Recover the files

Now run a recovery tool against the image (or the card, if you couldn't image it).

• PhotoRec (free, open-source, from CGSecurity) ignores the broken file system entirely and carves files out by recognising their signatures — JPEG, RAW, MP4, documents and hundreds more — which is why it works even after a format or heavy corruption [1]. It writes recovered files to a separate drive. CGSecurity publishes a step-by-step walkthrough [2]. PhotoRec recovers the contents but usually loses original filenames and folder structure — expect a pile of recup_dir files to sort through. For most "photos are gone" cases this gets them back.
• TestDisk (same author) works at the other level: it rebuilds lost partitions and repairs FAT/exFAT/NTFS boot sectors and directory structures [3]. Use it when the card shows up as unpartitioned, "needs formatting", or the wrong size, and you want the original file/folder layout back rather than carved blobs. If TestDisk can repair the file system, the card mounts normally and your files appear with their names intact.

A reasonable approach: try TestDisk first if you want the structure back; fall back to PhotoRec to brute-force the file contents if the structure is too damaged to repair.

Step 4 — Know when to stop and call a pro

DIY recovery is for cards the computer can still see. Send it to a professional service — and stop trying yourself — if:

• the card is physically damaged, or
• the computer doesn't detect it at all / it reports 0 bytes (likely controller failure), or
• the data is genuinely irreplaceable.

Repeated DIY attempts on a failing card can heat it, wear it further, or overwrite data, and can turn a recoverable job into an impossible one. A professional can read the NAND directly with equipment you don't have. The honest trade-off: pro recovery costs real money, so it's worth it for irreplaceable data and not for a card of holiday snaps you can let go.

Step 5 — Only now, format and test (or retire)

Once your data is safe, the card itself is suspect. If the failure was a one-off corruption, reformat it in the device (SD-spec formatter [5]) and run a few read/write cycles to confirm it's stable. If errors come back, or the failure was wear-related, retire it. A card that has thrown errors is not worth trusting with the next irreplaceable shot.

Bottom line

The order is everything: stop writing, image first, recover from the image, escalate to a pro for physical or controller failures. Most card failures are file-system corruption or counterfeits — both far more recoverable than people fear — and almost all of them are preventable with safe-eject, in-device formatting, headroom, the right grade, and cool storage. The cheapest recovery is the one you never need: buying genuine, right-grade cards and keeping a second copy stops most of this before it starts. We supply verifiable, right-grade cards and will tell you which grade matches your duty cycle — so the cards don't end up on this page.