Before you tap OK on a camera card error message, know what the button does. On almost every camera, the dialog next to “Card cannot be used” or “This card is not formatted” offers exactly one action: format the card. Accepting it rewrites the file system metadata a recovery tool needs to reconstruct your file list. The photos are usually still there underneath — the dialog just makes them harder to find.
This page is a dictionary. Each entry gives the message’s real meaning, a severity rating, the state of your data, and the correct first action, grouped by which stage of the storage pipeline failed.
Read Every Camera Card Error as a Stage Report
A camera reports failures from only three places, and the wording tells you which one.
Stage one: initialization. The camera applied power and tried to complete the SD or CFexpress handshake. If this fails, the camera never sees a volume at all. Messages are terse: no card, cannot recognize, insert another card. This is the only class of error that can indicate genuine hardware failure.
Stage two: volume mounting. The handshake succeeded and the camera read the boot sector, but the file system would not parse. Messages here mention the card not being formatted, or being damaged, or needing a format.
Stage three: file and metadata operations. The volume mounted and the camera can read and write. Failures here are about individual files, the folder counter, or the camera’s own media database. Messages mention specific files, folders, or databases.
The distinction matters because stage three errors are almost never card failures. They are camera software or file-level problems, and they are the most recoverable of the three. The camera storage explained article covers the underlying pipeline if you want the full model.
The Error Message Dictionary
Every message below is real text reported by cameras from major manufacturers. Wording varies slightly by model and firmware version, but the meaning is consistent within a manufacturer.
| Message | Source | Real meaning | Severity | First action |
|---|---|---|---|---|
| No card in camera | Canon, Nikon, Sony | Card absent, unseated, or failing initialization | Low to high | Power off, reseat, test with a second card |
| Cannot recognize the memory card | Sony | Initialization handshake failed; controller did not respond | High | Try another reader; if unchanged, assess for physical damage |
| Card cannot be used | Canon, Panasonic | Volume mounted but failed filesystem validation | Medium | Power off, remove card, do not format |
| Card may be damaged | Nikon | Same failure with an explicit damage warning | Medium | Read the card in a computer reader first |
| Card error | Canon, Panasonic | Generic volume-level failure, usually metadata | Medium | Remove card, stop shooting, scan from a reader |
| This card is not formatted | Nikon, Panasonic, Sony | Boot sector or allocation table is not a valid volume | Medium | Decline the format; the data is usually intact |
| Disk not readable by this computer | macOS | Host could not parse the volume | Medium | Choose Ignore, then image the card |
| You need to format the disk in drive X | Windows | Same volume-level parse failure | Medium | Click Cancel, never OK |
| Card is write-protected | Canon, Nikon | Tab is set, or the controller forced read-only | Medium | Check the tab; if it is fine, copy data now and retire the card |
| Switch off camera and remove card | Nikon | Companion text for a write-protect condition | Low | Follow it, then check the tab |
| Folder cannot be created | Nikon, Sony | Root directory allocation failed; FAT and directory disagree | Medium | Stop shooting; this is corruption, not a full card |
| Unable to display image | Most brands | File opened but did not decode; header damaged | Low | Do not delete it in camera; repair it on a computer |
| Image Database File error. Recover? | Sony | The camera’s clip catalog disagrees with the files present | Low | Answer Yes; image data is untouched |
| Writing to the memory card is not possible | Sony | Camera issued a write and the card rejected it | High | Stop recording; the card is failing |
| Buffer overflow / writing too slow | Sony, Canon | Card cannot sustain the required bitrate | Low | Not a fault; use a faster-rated card |
| SD ERR | GoPro | Card initialization or write failure | Medium to high | Power off, remove card, refuse any reformat |
| FILE REPAIR | GoPro | Last file was not finalized after an abnormal stop | Low | Let the camera try; repair on a computer if it fails |
| SD card not formatted / full | DJI, GoPro | Invalid volume, or FAT has no allocatable clusters | Medium | Decline the format and read the card externally |
| File or directory is corrupted and unreadable | Windows CHKDSK | Directory entries failed a consistency check | Medium | Stop CHKDSK; it writes to the volume as it repairs |
Two rules apply to every row: decline format prompts, and remove the card from the device before attempting anything. The mistakes that make recovery impossible page explains why each of those two actions is decisive.
“Card Is Write-Protected” Is Not Usually About the Tab
This message deserves its own section because the standard advice is incomplete.
On a full-size SD card, a small sliding tab on the left edge makes the card report itself as write-protected to any host. Clearing the tab and reinserting solves it, and if that is your situation you are done.
A microSD card has no tab and physically cannot present a mechanical write-protect state. If a camera claims one is write-protected, the message comes from the card’s controller, which has detected an internal failure — a bad block it cannot remap, a NAND die that stopped responding — and has deliberately locked the volume to prevent further damage. The same happens on full-size cards whose tab is correctly set.
That makes “write-protected” both the most alarming and the most recoverable message on this page. The card is at the end of its life, but it is also in the safest possible state for recovery, because nothing can overwrite the clusters holding your files. Copy everything off it immediately on a computer and treat the card as consumed afterward. Do not format it, do not run a repair, and do not put it back in a camera. Counterfeit cards often trigger the same message when their real capacity is smaller than the reported capacity — the counterfeit cards article explains the mechanism.
Errors That Are Not About the Card At All
Some messages send photographers down a recovery path they do not need.
“Image Database File error. Recover?” is a Sony-specific message about the camera’s own catalog of clips, stored on the card alongside the media. It tracks which clips have been played and how they are grouped, and it is entirely separate from the video files. Answering Yes rebuilds the index and costs nothing. The clips were never at risk.
“Unable to display image” in playback means the camera cannot decode a file whose header is incomplete. On a card where you know a shot was taken, this signals that the file exists on the flash but was never finalized. Do not delete it from the camera; a repair pass on a computer has a good chance with it.
Thermal and buffer warnings (“writing too slow,” “buffer overflow”) mean the camera or card cannot sustain the current write rate. These are performance messages, not corruption messages, but they are the most common precursor to a real failure. A card that produces slow-write warnings in a mode it previously handled comfortably is telling you its write performance has degraded, which is a wear symptom.
Severity Levels and What Your Data Is Doing Right Now
| Level | Signals | State of the data | Realistic expectation |
|---|---|---|---|
| Green: performance | Slow write, buffer warning, overheating | Intact, files finalized normally | No recovery needed; use a faster card |
| Yellow: file level | Unable to display, FILE REPAIR, database error | Present; one or more lack a valid index | High success rate with targeted repair |
| Orange: volume level | Card cannot be used, not formatted, card error | Metadata damaged; image data untouched | High success rate with a signature scan |
| Red: initialization | No card, cannot recognize, cannot access | Card not completing handshake | Uncertain; try another reader, then a lab |
| Red: hardware terminal | Write-protected microSD, physical damage, water | Flash may be fine but the controller is offline | Software cannot reach it; a lab may not either |
The orange row matters most. Volume-level errors — the majority of alarming camera messages — leave the photo and video data physically untouched. The camera simply cannot find it, because the map was destroyed while the territory was not. The SD card corruption causes article covers how those maps get destroyed.
The Correct First Move for Every Message
Regardless of which message you are looking at, the first three actions are identical.
- Stop writing. Power the camera off. Do not record a test clip, do not take a throwaway photo, and do not let the camera format anything.
- Remove the card and read it on a computer with a dedicated card reader rather than the camera’s USB port. Direct readers bypass the camera’s firmware, one of the two systems reporting the error.
- If the card mounts, copy what is still readable first — files the file system can resolve are the easiest to save.
After those three steps the path splits. If the card mounts and files are missing, that is a recovery job. If the card mounts but files are damaged, that is a repair job. If the card does not mount at all, the SD card not detected decision tree walks through the branches in order.
Two special cases leave the software path entirely. A card that is cracked, bent, scorched, or water-damaged needs a laboratory, not an application — the physically broken card guidance covers the handling rules. A card whose controller has gone offline, whether through write-protection or a failed handshake, cannot be read by any consumer tool.
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. As with any recovery tool, stop writing to the card first and always save recovered files to a different drive.
For volume-level errors specifically, the corrupted SD card recovery workflow applies. If you accepted a format prompt before finding this page, in-camera formatting rewrites metadata but leaves image data in place, so the recovering photos after a camera format process still applies. Files that vanish after a scan completes are covered in photos disappeared from an SD card.
Frequently Asked Questions
What does “Card error” mean on a camera?
Almost always a file system problem, not a card failure. The camera mounted the volume, read the boot sector, and found structure it could not validate. The photo and video data on the flash is normally intact. Remove the card, decline any format prompt, and scan it from a computer card reader rather than formatting in the camera.
Is a write-protected SD card dead?
Not necessarily broken, but treat it as end of life. If the physical tab is set correctly and the card still reports write-protected, the controller has locked the volume after detecting an internal fault. That state protects your data from being overwritten, so copy everything off and retire the card.
Should I let the camera format the card when it asks?
No, not if the card holds files you want. The format prompt appears when the camera cannot read the file system, which is exactly the condition under which a recovery scan succeeds. Accepting the prompt rewrites the metadata a tool needs to rebuild your file list. Cancel the dialog, power off, and work from a computer.
Can photos be recovered after the card was formatted in the camera?
Usually yes, if nothing has been written to the card since. In-camera formatting is a quick format: it writes a new file system structure but does not erase the data clusters. A signature-based scan that ignores the file system can typically rebuild the JPEG, RAW, and video files. Recovery becomes unlikely once new recordings occupy those clusters.