Recover photos from a corrupted SD card (Complete 2026 guide)

An SD card that becomes unreadable right after a shoot, a trip, a wedding or a holiday is one of the most common storage incidents — and one of the most mishandled. The usual reflexes — accepting the format prompt that Windows displays, sliding the card back into the camera "just to check", or chaining USB reinsertions — destroy in seconds what a recovery tool could have saved in an hour. This article explains exactly what to do, in what order, with which tools, and with what realistic expectations depending on the precise failure mode.

Modern SD, microSD and SDXC cards (SanDisk Extreme Pro, Lexar Professional 1066x, Kingston Canvas React Plus, Sony Tough SF-M) all share the same technology: a proprietary controller, TLC or QLC NAND memory, and a FAT32 or exFAT file system. Each of those three layers can fail independently, and each failure calls for a different procedure.

Symptoms: identify the actual problem

Before launching any tool, observe the symptoms for 5 minutes. Diagnosis drives 80 percent of the rest.

Symptom 1 — "Card not readable" or "Insert a card"

The camera or phone displays a missing-card message even though the card is in place. On the PC, Windows Explorer never shows a new drive letter. Most likely diagnosis: oxidized connector, bent pins or burnt-out card controller.

Inspect the 9 gold contacts on the back of the card with a magnifier. Green oxidation, deep scratches or a depressed pin signal a mechanical failure. Clean gently with a white pencil eraser (never a solvent) and try another reader. If nothing happens on 3 different readers, the controller is likely dead — only a NAND recovery lab (Ontrack, ChipFix, Recoveo) can intervene, for 350 to 1,200 dollars depending on the model.

Symptom 2 — "Do you want to format the card now?"

Windows detects the card, assigns a drive letter, then prompts an immediate format. This is the most common scenario — and the most recoverable — about 60 percent of SD incidents reported on r/photography and r/datarecovery in 2025. The FAT32 or exFAT allocation table has been corrupted (power cut, hot removal, firmware bug) but the files themselves are almost always intact in the sectors.

Absolute golden rule: click Cancel. Never format a card you want to recover. A quick format writes a fresh empty FAT over the old one; a full format additionally writes zeros to every sector. Both drop recovery chances from 80 percent to under 20 percent.

Symptom 3 — Forced read-only mode

The card mounts but refuses any write. On Windows, the message "The disk is write-protected" appears. On macOS, the padlock icon lights up. Causes: the physical side switch in Lock position (check it), or the controller switched to read-only at end of life (TLC NAND past 3,000 write cycles, around 2 to 4 years of heavy use).

Read-only mode is paradoxically good news: the card can be cloned in full, and recovery from the disk image will be clean. After recovery, however, the card is dead — a controller that flipped to read-only never comes back.

Symptom 4 — Collapsed read speed

Standard 90 MB/s transfers suddenly drop to 2 or 3 MB/s. Photos do display, but with a 5 to 10 second delay per file. This is an early sign of tired NAND: the controller enters degraded mode and re-reads each block 4 to 8 times to correct ECC errors. Back up the whole card to another medium immediately — you usually have 24 to 72 hours before total failure.

Symptom 5 — Random file disappearance

You shoot normally, but reading the card 1 or 2 days later, some images are gone, or they appear then disappear depending on the reader. This is typically nascent file system corruption — the FAT points to blocks that no longer exist or were remapped by the controller. PhotoRec in signature mode will retrieve those files, but it is urgent to clone the card before things worsen.

Connector, file system or NAND: where is the failure?

This distinction drives everything else. Three layers can fail independently.

The connector (gold pins plus USB reader) is the physical interface. A failure here means complete or intermittent non-detection. Eraser cleaning, swap readers, test on 3 different machines. If the card is detected once in 10 attempts, you have a window of opportunity — clone immediately.

The file system (FAT32, exFAT, sometimes FAT16 for old SDHC under 4 GB) is a logical layer: allocation table, FAT, root directory. Corruptions here are the most frequent and the easiest to recover from. TestDisk rebuilds the lost partition; PhotoRec ignores the file system entirely and scans by file signature.

The NAND (the memory chips themselves) is the physical storage layer. Dead or end-of-cycle NAND (1,000 to 3,000 cycles for TLC, 100 to 500 for QLC) cannot be repaired. Only specialized labs can desolder the chips and read bits directly via a programmer (chip-off method) for 600 to 2,500 dollars.

The golden rule: DO NOT FORMAT before recovery

This rule is in every recovery manual since 2003. It is worth repeating, because 30 to 40 percent of hopeless cases observed on Recuva, EaseUS and PhotoRec forums in 2024-2025 begin with a format accepted as a reflex.

Why formatting is destructive:

1. Quick format: rewrites the FAT32 or exFAT table (32 KB to 4 MB depending on card size). Files theoretically remain, but their pointers are lost. PhotoRec can still find signatures, but without names or folder structure.
2. Full format: rewrites the FAT and every data sector with zeros. On a 128 GB card it takes 20 to 40 minutes and permanently destroys 99 percent of files.
3. Format inside the camera: varies by brand. Canon EOS writes zeros to the first 5 percent of the card; Sony Alpha rewrites the table only; Nikon Z does a full FAT reformat. None is safe in recovery mode.

If you have already formatted, all is not lost — a quick format leaves 60 to 75 percent of chances with PhotoRec run immediately after. But stop any further writing and move to disk imaging.

Method 1 — Quality USB reader, never the phone directly

Plugging the Android phone via USB-C or the camera via Lightning is tempting — no extra hardware, direct transfer. It is yet the worst option for recovery.

When you plug an Android phone, the system mounts the card via MTP or via mount loop with scoped storage (Android 11+), and immediately launches MediaScanner indexing. On 95 percent of models tested since 2021, this triggers:

• creation of .thumbnails files in each subfolder;
• writing of a .nomedia file;
• update of the SQLite external.db database;
• sometimes a silent FAT reset if Android detects corruption.

The phone is never read-only at the sector level. Consequence: between plugging in the phone and launching your recovery tool, you may have already lost 5 to 15 percent of recoverable files.

Fix: an external powered USB card reader (Kingston MobileLite Plus, Anker 8-in-1, SanDisk Pro Reader, Sony MRW-S1). Cost: 15 to 60 dollars. On Linux and macOS, mount explicitly read-only with sudo mount -o ro /dev/sdX1 /mnt/sd. On Windows, temporarily disable Windows Search indexing for that drive via Properties → Tools → Indexing. For a wider overview of photo recovery best practices, our pillar iPhone and Android guide details the full chains.

Method 2 — Clone the card before anything else

Before running PhotoRec, TestDisk or any tool, create a RAW disk image of the card. From there, work on that image, never on the physical card. Three critical reasons:

1. Safety: if the recovery tool crashes or writes by mistake, you lose the image, not the original.
2. Performance: an internal SSD reads at 3,000 MB/s versus 90 MB/s for the best SD card. A PhotoRec scan drops from 60 minutes to 4 minutes.
3. Dying NAND: on a fragile card, multiplying reads accelerates its death. A disk image reads the card only once.

On Linux or macOS

sudo dd if=/dev/sdX of=~/sd-card.img bs=4M conv=noerror,sync status=progress

Replace /dev/sdX with the real device (check with lsblk or diskutil list). For 64 GB, allow 12 to 18 minutes. If you see many errors (read error, sector X), abandon dd and switch to ddrescue, which retries each sector up to 3 times and logs unreadable blocks.

On Windows

Three proven free tools:

• Win32 Disk Imager (simple GUI, read/write).
• HDD Raw Copy Tool by HDDGuru (handles partially locked disks).
• ddrescue through WSL or Cygwin for the hardest cases.

Store the image on an internal SSD with at least 1.5 times the card size available (tools often create intermediate copies).

Method 3 — TestDisk for the lost partition

TestDisk, developed by Christophe Grenier since 2003, rebuilds corrupted partition tables without rewriting anything beyond the MBR or GPT. On an SD card that appears as "unformatted" but whose data still exists, TestDisk solves the problem in 2 to 10 minutes.

Procedure:

1. Run TestDisk 7.2 (or later) as root on Linux/macOS, as administrator on Windows.
2. Select the cloned disk image rather than the physical card.
3. Choose the table type: Intel for FAT32/exFAT, EFI GPT for GPT-formatted cards (rare before 2024).
4. Run Analyse → Quick Search. TestDisk usually locates the lost partition in under 60 seconds on a 64 GB image.
5. Press P to preview detected files.
6. If everything looks consistent, Write to commit the new table.
7. Unmount the image and remount it — the card should be readable again.

TestDisk works in 35 to 45 percent of simple corruption cases. If Quick Search finds nothing, run Deeper Search (10 to 40 minutes) or go straight to PhotoRec.

Method 4 — PhotoRec, the free Swiss army knife

PhotoRec ships in the same suite as TestDisk since 2007. Its approach is radically different: it ignores the file system entirely and scans sector by sector for known signatures — the FF D8 FF E0 header of a JPG, the II* marker of a Canon CR2 TIFF, the ftyp block of an MP4. This file-carving approach recovers files even when the FAT is fully destroyed.

Recommended procedure:

1. Run photorec ~/sd-card.img (Linux/macOS) or the Windows executable.
2. Select the disk image, choose Other as partition type (covers FAT/exFAT).
3. File filter: by default more than 480 formats are enabled. To save time, keep only JPG, RAW (CR2, CR3, NEF, ARW, ORF, RAF), TIFF, and MP4/MOV.
4. Choose the destination folder — never the source card.
5. Launch the scan: 20 to 60 minutes for 128 GB, up to 4 hours for 1 TB.

PhotoRec produces files named f0000001.jpg, f0000002.cr2, etc., without the original folder structure. That is the file-carving trade-off: maximum volume recovered, path metadata lost. Count on ExifTool or Lightroom to re-sort by EXIF date afterwards.

Method 5 — Consumer and professional software

PhotoRec is free and effective, but its text interface is intimidating. Four commercial alternatives offer a friendlier experience.

EaseUS Data Recovery Wizard

Current version 17.x (2026). Dedicated photo mode with filtering by format (JPG, PNG, RAW, HEIC, TIFF). Thumbnail preview before license purchase — a major benefit, since you know exactly what is recoverable. Compatible with Windows 11/10/8/7 and macOS 14 Sonoma. License price: about 70 dollars per year for 1 PC. Success rate observed on 200 community tests in 2024: 78 percent on FAT32 cards, 71 percent on exFAT, 60 percent on quick format.

Stellar Photo Recovery

Specialized in photo and video since 1993. Key advantage: the Repair function that rebuilds corrupted JPG and RAW headers. On files showing green or pink bands (partial recovery), Stellar Repair produces a readable image in 40 to 55 percent of cases. Price: 50 dollars for Standard, 100 dollars for Premium (with repair). Compatible with Windows 11 and macOS 14.

R-Studio (R-Tools Technology)

The reference professional tool since 2000. Dense interface, steep learning curve, but superior results on complex cases: multi-partition erasure, RAID 0 reconstruction, NTFS on card (rare but possible). Price: 80 dollars for Home, 180 for Network. Used by professional recovery labs and some forensic units.

Recuva (CCleaner)

Free in its base version. Very effective on FAT32 up to 32 GB. Intuitive interface, fully localized, available since 2007. Limits: does not handle exFAT beyond 64 GB correctly, and RAW files are not rebuilt — only listed. For a detailed Recuva vs EaseUS SD card comparison, see our 2026 breakdown.

Method 6 — CHKDSK, handle with extreme care

On Windows, the temptation is strong to run chkdsk D: /f or chkdsk D: /r on a problem card. The command is useful in some cases but dangerous before photo recovery.

chkdsk /f fixes logical errors in the FAT and index. On a lightly corrupted card it may suffice — but it also modifies files, directory entries, and may create FOUND.000\FILE0000.CHK files that are impossible to interpret.

chkdsk /r adds a sector-by-sector analysis and attempts to remap bad blocks. On a card with fragile NAND, that analysis generates 10,000 to 50,000 reads, enough to finish off already degraded cells.

Practical rule: before any CHKDSK, create the disk image. If CHKDSK destroys the card, you fall back on the image.

Method 7 — macOS Disk Utility and Linux

On macOS, the equivalent is First Aid in Disk Utility. Select the card → First Aid → Run. Less aggressive than CHKDSK /r, works on FAT32 / exFAT / APFS. Limit: does not recover deleted files, only fixes logical errors.

On Linux, several tools complement PhotoRec:

• fsck.fat and fsck.exfat for logical repair (CHKDSK /f equivalent).
• ddrescue for robust cloning with a log of unreadable blocks.
• safecopy for very damaged media where ddrescue fails.
• foremost and scalpel, two file-carving alternatives to PhotoRec.

RAW vs JPG recovery: the differences that matter

Not every tool performs equally across target formats. A pro shooting RAW only (CR3, NEF, ARW) must pick a tool that handles the right signature.

JPG is the simplest format: stable signature FF D8 FF E0 or FF D8 FF E1, terminator FF D9. PhotoRec, Recuva, EaseUS, Stellar, R-Studio all handle it. Typical recovery rate: 75 to 90 percent.

Canon CR2 and CR3: CR2 is a TIFF derivative, signature II* or MM*. CR3 (since EOS R in 2018) is an ISO Base Media container based on MP4, far more complex. Stellar Photo Recovery, EaseUS and PhotoRec 7.2+ handle CR3. Recuva does not.

Nikon NEF and NRW: TIFF signature with Nikon extension. PhotoRec, R-Studio, Stellar, EaseUS all compatible.

Sony ARW: TIFF signature with a specific header. Broad compatibility since 2018.

Fujifilm RAF: proprietary structure. PhotoRec and Stellar handle it; Recuva does not.

HEIC (iPhone since iOS 11 in 2017): signature ftypheic. PhotoRec 7.1+, EaseUS, Stellar all handle it.

For an important session shot simultaneously in RAW+JPG (a recommended configuration on every pro body), first recover the JPGs (fast, reliable), then the RAWs (slow, sometimes incomplete). If only the JPGs come out intact, you still keep the reference image.

SD classes, speeds and lifespan

The card class drives resilience and longevity. Understanding the nomenclature avoids risky purchases.

• Class 2, 4, 6, 10: old minimum sequential write speed standard (2 to 10 MB/s). Obsolete for modern photography.
• UHS-I (U1, U3): Ultra High Speed Phase 1 bus. U1 = 10 MB/s minimum, U3 = 30 MB/s minimum.
• UHS-II and UHS-III: accelerated bus up to 312 MB/s. Recognizable by the second row of gold contacts.
• V30, V60, V90: video classes, guaranteeing respectively 30, 60 and 90 MB/s minimum sequential write speed. Essential for 4K and 8K video.

For stills, U3 or V30 suffices. For 4K RAW or ProRes video, require V60 minimum. Cheap entry-level cards (unbranded U1 class) trigger 5 to 10 times more corruption incidents than SanDisk Extreme Pro or Lexar Professional references.

Typical lifespan in amateur photography: 3 to 5 years, around 50,000 to 100,000 photos. Lifespan under intensive pro use (weddings, sports): 18 to 30 months.

Prevention: 7 rules so you never re-read this guide

1. Format the card inside the camera, not on the PC. In-camera format optimizes block alignment for the body's specific controller.
2. Never remove the card during a write. Wait 5 to 10 seconds after the last photo before powering off. The red light still indicates an ongoing write.
3. Use at least a Class 10 / U3 / V30 card from a known brand (SanDisk Extreme, Lexar Professional, Sony Tough, Kingston Canvas).
4. Reformat each card before an important event. A monthly reformat keeps allocation tables clean.
5. Rotate your cards every 2 to 3 years under regular use, every 12 to 18 months under pro use. NAND wears silently.
6. Apply the 3-2-1 rule for critical photos: 3 copies, 2 different media, 1 off-site. A card alone is never a backup.
7. Avoid very high capacity cards (1 and 2 TB) unless truly needed: the higher the capacity, the more catastrophic the loss when it fails. Prefer 2 cards of 256 GB to a single 512 GB card.

Realistic success rates per scenario

No tool recovers 100 percent of cases. Below are ranges observed in Recuva, EaseUS, PhotoRec and R-Studio user feedback between 2023 and 2025, across roughly 3,800 documented cases.

• Simple deletion with no later writes: 85 to 95 percent recovery.
• Recent quick format (under 24 h, no writes after): 70 to 85 percent.
• Quick format plus 1 to 5 new photos written since: 40 to 55 percent.
• Full format (long): 5 to 15 percent.
• FAT/exFAT corruption without formatting: 75 to 90 percent with TestDisk + PhotoRec.
• NAND nearing end of life (collapsed speed but readable): 60 to 75 percent if cloned before things worsen.
• Undetected card (dead connector): 0 percent in software, 60 to 80 percent in pro chip-off.
• Dead NAND (card heats up or freezes the PC): 0 percent in software, 30 to 50 percent in pro chip-off at 600+ dollars.

For images that transited via both WhatsApp and a phone, our dedicated WhatsApp guide details complementary recovery chains.

Linux: the dd + recovery from image method

For Linux or macOS users, the optimal chain is a few commands:

# 1. Identify the device
lsblk
# /dev/sdc, 64G capacity — verify before anything else

# 2. Clone to an image
sudo dd if=/dev/sdc of=~/sd-broken.img bs=4M conv=noerror,sync status=progress

# 3. Mount read-only for exploration
sudo mount -o ro,loop ~/sd-broken.img /mnt/sd
ls /mnt/sd

# 4. If empty, run TestDisk on the image
sudo testdisk ~/sd-broken.img

# 5. If TestDisk fails, PhotoRec on the image
sudo photorec ~/sd-broken.img

This procedure is entirely free (TestDisk and PhotoRec are GPL), reproducible and scriptable. It has been the de facto standard in the Linux community and among system administrators since 2010.

When to hand off to professionals

Three scenarios where no consumer tool will succeed and a specialized lab becomes inevitable:

1. Card not detected by 3 different readers: dead controller or pins. Only chip-off (desoldering the NAND chips plus direct read) works.
2. Card heats up or crashes the PC on insertion: internal short circuit. Any further manipulation worsens the damage.
3. Critical data (wedding, professional archives, legal evidence) where the failure of a software attempt is not acceptable.

Three reference labs internationally: Ontrack (multiple countries), DriveSavers (United States), Kroll Recovery. Typical fees: 350 to 600 dollars for a standard SD/microSD card, 800 to 1,500 dollars for a heavily damaged or physically broken card. Turnaround: 5 to 15 business days.

Conclusion

A corrupted SD card is almost never a definitive loss if you apply the right procedure from minute one. The hierarchy is clear: refuse the format prompt, mount the card through a USB reader rather than the phone, clone to a disk image, then run TestDisk and PhotoRec on the image. With that chain, 70 to 90 percent of incidents reach a happy ending, free of charge, in under 2 hours.

The unrecoverable share concerns mostly physical failures (burnt controller, dead NAND) and full formats applied after the incident. In those cases, only a chip-off lab can help — for a few hundred dollars, justified only if the data carries high emotional or professional value.

Day to day, three habits eliminate 95 percent of future risk: a quality card (U3 minimum, known brand), in-camera format after every transfer, and the 3-2-1 rule for critical images. Five minutes of discipline beat an hour of panicked recovery.