Your camera or computer suddenly calls your memory card corrupted — do not click Format. Messages like “you need to format the disk,” a RAW file system label, or “card not recognized” describe the card’s ability to organize files, not whether your photo data still exists. Usually the data is intact, and corrupted SD card recovery is a software problem, not a lost cause. This guide diagnoses each symptom and marks the boundary where software stops helping.
“Memory Card Needs to Be Formatted” — What the Message Really Means
When you insert a card, the host reads two small structures first: the partition table and the boot sector of a FAT32 or exFAT volume. If either is damaged, the card no longer looks formatted, so the system assumes it is blank and offers to format it. That message says nothing about the photos sitting in the data region behind those structures.
The counterintuitive part: this pop-up is often the strongest signal that your data is present. The damage behind it — an interrupted write, a battery dying mid-recording, a card yanked during a transfer, a flaky reader — corrupts bookkeeping first and photo bytes last. Formatting would erase the one damaged structure that recovery tools can read around, which is why recovering without formatting is the correct first move.
Don’t Click Format. Do This First
None of these steps writes to the card:
- Close any format dialog and remove the card from the device.
- Try a second reader and a different USB port; a failing reader or marginal connection produces the same messages as a damaged card.
- Open Disk Management on Windows or Disk Utility on macOS: does the host show a healthy FAT32/exFAT volume, a RAW volume, an unallocated disk, or nothing? That single reading selects your path below.
- If the card went read-only on its own, treat it as protective — scans still run, since recovery tools never write to the source.
A card that mounts nowhere but reports the correct capacity still behaves like a file-system problem; the moment Windows lists a disk of roughly the right size, software can usually work with it. For the full loss-scenario map, see our camera data recovery overview.
Symptom 1 — The Card Shows RAW or “Unformatted”
Windows labels a volume “RAW” when it can read the disk but finds no file system it recognizes. RAW is a status descriptor, not a file format, and it is unrelated to RAW photo files such as CR2, NEF, or ARW — see recovering RAW photos for that separate topic. A RAW label usually means the partition entry or boot sector is damaged, or a format was interrupted partway.
The first route repairs the map without deleting anything. TestDisk finds the lost partition or boot-sector parameters and rewrites them so the card mounts normally again; your files stay where they are. Because it does write to the card, working from a sector-level image first is the cautious approach — our free memory card recovery guide shows the exact flow. If the card reached this state right after a format, the format type decides what is still findable; see quick versus full formatting first.
The second route ignores the file system entirely. A deep signature scan reads the card at sector level and rebuilds photos from their content markers, so it works even when the partition is destroyed. It is slower and returns generic filenames, but it never depends on damaged metadata. Do not run chkdsk on a RAW volume: Windows refuses with “the type of the file system is RAW,” and on other damaged volumes chkdsk can write while repairing — the opposite of what you want before recovery.
Symptom 2 — The Camera Reports “Card Error” or Demands a Format
Cameras and computers apply different tolerances. A camera validates file systems and card health more strictly than a desktop host, so a card that triggers “card error” or a format demand in the body may mount fine in a reader. Use that gap: if the card reads on a computer, recover the files first, then let the camera reformat if it insists. Confirming the camera’s format prompt destroys the file-system map that a fast scan could still use — and it does not fix a genuinely faulty card anyway.
Symptom 3 — The Card Is Not Detected at All
A card no device enumerates has moved into hardware or interface territory, and the recovery math changes. Rule out the cheap causes first: test several readers and devices, reseat the card, and lightly clean the contacts with isopropyl alcohol. If exactly one device reads it, copy the data out through that device immediately.
If nothing enumerates, two possibilities remain: controller or firmware failure — the flash controller that presents the NAND died, often after the card read as 0 bytes or vanished mid-session — or physical damage such as cracked casing, bent contacts, or water exposure. For water or impact damage, stop powering the card and skip heat drying; a lab reads the chips directly. Chip-off recovery costs from hundreds into thousands of dollars, so weigh it against the value of the files.
Software Fixes vs Firmware Failure — Where the Line Is
File-system corruption — every symptom above — is a software problem, and recovery software handles it. Firmware failure is not, and that distinction is where most confusion lives.
Software talks to the card through its controller. If the controller cannot initialize, no program can reach the data behind it, no matter how the tool is marketed. Vendor “repair” utilities that reinitialize a controller treat the card as blank and are not a recovery path. With a dead controller, only a lab with chip-off capability can remove the NAND chips and read them directly.
Rule of thumb: if an OS lists a disk of roughly the correct capacity, scan it as a file-system problem. If nothing enumerates, plan for a laboratory instead of buying more software.
Free First, and When a Paid Scanner Earns Its Keep
TestDisk covers partition repair and PhotoRec covers file carving, both free, and both are documented step by step in our free memory card recovery guide. On corrupted cards their cost shows up around the scan: no previews means identifying hundreds of recovered files by hand, and long deep scans are less guided. When that time matters, a paid scanner with previews and broad format coverage is a fair upgrade; the best camera data recovery software comparison covers the leading options.
If you are on Windows and the card is still detected by a computer, a purpose-built recovery tool such as XRecovery (xappset.com) can scan SD, microSD, and other memory cards for deleted or formatted photos and videos. Stop writing to the card first and save recovered files to a different drive.
Frequently Asked Questions
What does it mean when an SD card shows a RAW file system?
It means the host can read the disk but finds no recognized file system on it, usually because the partition entry or boot sector is damaged. The photo data itself is typically still present and recoverable by scanning around the damage.
Can I recover files from a corrupted SD card without formatting it?
Yes. Recovery tools read the card rather than write to it, so formatting is never required to scan. Formatting would destroy the damaged file-system structures that tools like TestDisk could otherwise restore, so recover first and format later only if you want to reuse the card.
How do I fix a corrupted memory card without losing data?
Repair the metadata with TestDisk so the card mounts again, or run a deep signature scan that ignores the file system and saves copies elsewhere. Make a sector-level image of the card before either route if you can.
Why does my camera say “card error” when the card works in a computer?
Cameras validate file systems and card health more strictly than desktop hosts. Move the files off through whatever device reads the card before letting the camera reformat.
Should I run chkdsk on a corrupted SD card?
Not before recovery. Windows refuses chkdsk on RAW volumes anyway, and on other damaged volumes it can write while repairing, so scan first and reformat later.