SD Card Not Readable — Recover First: What It Means and How to Fix It (2026 Updated Guide)

Quick answer

Your SD card has lost its file system, but the photos and files on it are almost always still recoverable. The right order is: stop using the card, recover what you can to a different drive, then decide whether to format or replace the card. Do not click Format when Windows offers it. Do not run repair tools on the card before recovery. Do not write any new data to it.

Before you start

Five rules for the next ten minutes:

  • Take the card out of the camera or phone. Don’t shoot or save anything else to it. Each new write reduces what’s recoverable.
  • Don’t click “Format” if Windows offers. Whatever else you do, that button is the wrong button.
  • Don’t run CHKDSK yet. It can destroy data on a damaged file system. We’ll get to it later, on a different drive copy.
  • If the card is in a phone, copy via the phone first if you can — not by removing the card. Phone manufacturers sometimes use proprietary partitions that Windows can’t read.
  • If the data on the card is irreplaceable — wedding photos, one-off video shoots, family pictures — and you’re not confident with recovery software, stop now and consider a professional recovery lab. Each failed attempt makes the next one harder.

What this error means

You’ll see one of several variations:

You need to format the disk in drive X: before you can use it.

The disk is not formatted. Do you want to format it now?

X: is not accessible. The volume does not contain a recognized file system.

Sometimes the card mounts but appears empty when you know it shouldn’t be. Sometimes the camera says “Card Error” or “Memory Card Cannot Be Accessed.” Sometimes the file count is correct but every file shows as 0 bytes or fails to open.

All of these mean the same thing: the index that tells the device where each photo or file lives is corrupted. The actual photo data is still on the flash chips. What’s broken is the FAT32 or exFAT header that maps file names to storage locations.

This is recoverable. Most of the time. The exceptions are physical damage (snapped card, water, fire) and write-after-failure (continuing to shoot photos onto a corrupted card, which overwrites the recoverable data).

Where this error appears

This shows up across pretty much every device that uses SD or microSD cards:

  • Cameras — Canon, Nikon, Sony, Fujifilm, GoPro, action cams. Often after a battery died mid-write or the card was pulled before the write light went off.
  • Smartphones — Android phones using microSD as expandable storage. Less common since most flagship phones dropped SD support, but mid-range Androids and rugged phones still use it.
  • Dashcams — Constant write/erase cycles wear out the cards faster than any other use case. Failure here is a question of when, not if.
  • Drones — Same as cameras, often after a crash or battery loss mid-flight.
  • Nintendo Switch — Game data corruption usually shows up as “card not detected” rather than the format prompt.
  • Raspberry Pi — When a Pi loses power without a clean shutdown, the SD card’s file system is regularly corrupted. This case overlaps with general drive recovery.

Common causes

By a wide margin, the dominant causes are:

  1. Removed without safe-eject. Pulling the card from a camera before the write light goes off, or from a card reader without using “Safely Remove Hardware.” This is the leading cause.
  2. Battery died during write. Camera or phone died with the card inserted, mid-write. The file system was being updated and the update never completed.
  3. End-of-life wear. SD cards have finite write cycles. Cards used for years in dashcams, security cameras, or constant-recording setups eventually fail. Cheap or counterfeit cards fail much faster.
  4. Card reader, cable, or USB port problem. The card itself is fine; the path between the card and Windows is broken. Try a different reader, cable, and port before assuming the card is dead.
  5. File system mismatch. The card was formatted by a Mac, Linux machine, Android phone, or older camera using a file system Windows doesn’t recognize. Not corruption. Read it on the original device.
  6. Counterfeit cards. A larger problem than most people realize. Fake cards report a fake size to the operating system but only have a fraction of that storage. Files appear to write successfully then fail to read back. If your card came from an unfamiliar source at a suspiciously low price, this is worth checking.

The decision before recovery

Two questions to answer before installing any tool:

Question 1 — Is the data already backed up somewhere?

  • Did you copy photos to a computer or cloud after the last shoot? If yes, just use those copies. Stop and consider whether recovery is worth the risk.
  • Are the files synced via Google Photos, iCloud, OneDrive, or similar from a phone? Check there first. The cloud copy is usually identical to what was on the card.
  • For Raspberry Pi or system cards: do you have a recent image backup? If yes, restore from that and skip recovery.

Question 2 — Is the card itself worth keeping?

  • If the card is more than a few years old, has been used heavily, or has thrown errors before — it’s at end of life. Recover the data, then throw the card away. Don’t trust it again.
  • If the card is brand new and this happened on first use — it may be counterfeit. Recover what’s there, then verify the actual capacity using a tool like H2testw or F3 before trusting it.

Recover your data first

Pick the method that fits the data and your patience.

Method 1 — Try a different card reader and port

Before anything more involved, eliminate the basic causes:

  1. Remove the card from the current reader.
  2. Wipe the gold contacts gently with a clean, dry cloth. Don’t use anything liquid.
  3. Try a different card reader if you have one. Built-in laptop slots are often less reliable than external USB readers.
  4. Try a different USB port on the computer.
  5. Try a different computer if practical.

A surprising number of “dead” cards are actually fine — the reader, cable, or port was the problem. This costs you nothing to check.

Method 2 — Photo-specific recovery (PhotoRec)

PhotoRec is a free, open-source tool from CGSecurity, the same project as TestDisk. It’s built specifically for recovering photos and videos by reading the raw flash chip and finding image file headers, ignoring the broken file system entirely.

It’s the right tool when:

  • The card contains mostly photos and videos
  • You don’t need original file names back (PhotoRec recovers content but not original names)
  • The card shows in Disk Management even if marked RAW
  • You’re patient with a text-mode interface

PhotoRec is what professional recovery shops often use as a first pass before reaching for paid tools, because it’s reliable and free. The trade-off is the lost file names — recovered files come back as f0001234.jpg, f0001235.jpg, and so on. For most photo recovery cases, that’s acceptable: you’re getting your pictures back; renaming them is the easy part.

Always recover to a different drive than the source. Never recover to the card itself.

Method 3 — GUI recovery (Recuva)

Recuva is a free, GUI-based tool from CCleaner. It’s better than PhotoRec when:

  • You want to preview files before recovering
  • You want to keep original file names (it usually can)
  • The damage is to the file index, not the partition table
  • You’re uncomfortable with command-line tools

Recuva works on most card scenarios. Run it, point it at the card, choose “deep scan” if the quick scan misses files, and recover to a separate drive.

Method 4 — Paid recovery software

For cases where free tools recover partial data but miss the files you actually need, paid recovery software (Disk Drill, EaseUS, Stellar, MiniTool, R-Studio, and others) sometimes does better — particularly with RAW cards, fragmented video files, or partial overwrites. We don’t recommend specific products in this guide; “best recovery software” comparisons online are typically affiliate marketing, not editorial reviews.

The one universal rule: always run the free preview before paying. Every reputable paid recovery tool offers a scan mode that shows what’s recoverable before you spend a cent. If the preview can’t find your files, the paid version probably can’t either, and you’ve saved yourself the cost.

Method 5 — Professional recovery lab

For physically damaged cards (snapped, burned, water exposure beyond a brief drip), software won’t help. A lab desolders the flash chips and reads them directly with specialised hardware. This is expensive — often hundreds of dollars at minimum, sometimes more. It’s worth it for irreplaceable data and not worth it for anything else.

Reputable labs quote you after evaluation, before charging for recovery. Be wary of any service that demands payment up front before telling you what’s recoverable.

Advanced fixes (only after recovery, or if data is replaceable)

Once your data is somewhere safe — only once it’s somewhere safe — you can decide what to do with the card itself.

Run CHKDSK

CHKDSK can sometimes restore enough of the file system that the card mounts again. It can also write changes that make further recovery harder, which is why we run it after recovery, not before.

Open Command Prompt as administrator:

chkdsk X: /f

Replace X: with the card’s drive letter. If you get “The type of the file system is RAW. CHKDSK is not available for RAW drives,” skip to formatting.

Format the card cleanly

If the card is going to be reused (and you’ve decided it’s worth keeping):

  1. Open Disk Management (right-click Start → Disk Management).
  2. Locate the card.
  3. Right-click the volume → Format.
  4. Choose exFAT for cards 64GB and up, or FAT32 for cards 32GB and below. This is the convention cameras and most devices expect.
  5. Leave allocation unit size at default.
  6. Tick Perform a quick format.
  7. Click OK.

Quick format is appropriate. Full format takes much longer and writes zeros to every sector, which is unnecessary for an SD card and wears out flash cells faster.

Use the camera or device to format, not Windows

For cards used in cameras specifically: after recovery, format the card in the camera, not in Windows. Cameras sometimes use proprietary directory structures (DCIM/100CANON, etc.) and reserved sectors that Windows formatting doesn’t replicate. Camera-side formatting writes the structure the camera expects.

This is a small detail but can prevent future “card not initialized” errors in the camera.

If you are on a work or school device

If the SD card is for personal use but you’re recovering on a work laptop, two things to consider:

  1. Endpoint protection software may quarantine recovery tools. Tools like TestDisk and PhotoRec read disk sectors directly, which is exactly what some endpoint security products flag as suspicious. Your IT admin can permit specific tools, but expect friction.
  2. Photos may be subject to acceptable use policies. If you’re recovering personal photos on a work device, that’s usually fine, but check policy first if your organization has one.

If the card itself contains work data — survey footage, client photos, regulated material — contact your IT admin first. Most organizations have specific data handling procedures for portable media.

When to stop

Stop and seek professional help if:

  • The card is physically damaged — snapped, bent, contacts visibly worn or burned, water damage. Software won’t help. Each attempt with software risks finishing the damage.
  • Your first recovery attempt failed and the data is irreplaceable. Each subsequent attempt costs more recoverable data than it returns.
  • The card was used for sensitive content that legally requires controlled handling — medical imaging, body camera footage, regulated photography. Recovery on personal hardware may itself be a problem.
  • You suspect the card is counterfeit. Recovery from counterfeit cards is unreliable because the underlying flash is often defective. Recover what you can with one tool, accept partial results, and replace the card.
  • You’re not confident. Genuinely. Paying once for a professional recovery is cheaper than paying twice — and far cheaper than losing the photos entirely.

Official references

FAQ

Why does my camera say my SD card needs to be formatted when there are clearly photos on it? The photos are still there, but the camera can’t read the file system that points to them. Don’t format from the camera. Take the card out, put it in a card reader, and follow the recovery steps in this guide first.

Will recovery software work on a microSD card the same as a full-sized SD card? Yes. The form factor doesn’t matter — recovery software reads the flash chip the same way regardless of the card’s physical size. The same tools work on both.

Can I recover photos after formatting the card? Quick format — usually yes, with recovery software, if you haven’t taken new photos since. Full format — generally no, especially on Windows 11, which writes zeros to every sector. Photos taken after formatting overwrite older photos cell-by-cell.

My SD card shows the wrong size — is that the file system corruption? Probably not. That’s the signature of a counterfeit card. Real cards report their actual capacity. Fake cards advertise a fake size, which Windows trusts. Test the real capacity with a tool like H2testw or F3 before reusing the card.

Should I keep using a card after this happens? For dashcam, security camera, or anything that records continuously — no. End-of-life is the most common cause of these errors and the card will fail again, probably soon. For photo cards used occasionally, one error isn’t necessarily end-of-life, but if it happens twice, retire the card.

Why do recovered photos have weird names like f0001234.jpg? Tools that recover by file signature (like PhotoRec) read the photo data from the flash chip directly, ignoring the broken file system. Original file names are stored in the file system, which is what’s broken. The photo content is intact; the names aren’t recoverable. Tools that recover via the file system (Recuva on a less-damaged card) often keep original names.

↑ Back to top