Why Does My SD Card Keep Saying Card Error (September 2026)

Two warnings before you continue. The /f flag in chkdsk rewrites the file system and can discard the recovery of individual damaged files, so image the card first if the data matters. And no software of any kind repairs a physically broken card.

What Card Error Actually Means: Decode the Exact Message You See

The wording of the message narrows the cause considerably. Find your exact string in the table below, read the likely cause, and go straight to the matching fix instead of trying everything in order.

Two entries deserve extra attention. A write-protected message on a card with no lock switch is almost never a file system problem; it is the controller deciding the card is no longer trustworthy. And a card reporting a smaller capacity than its label is not a formatting quirk, it is counterfeit hardware.

Warning Signs Your Card Is Failing

A card that dies without warning is rare. A card that complains for weeks first is the common case, and these are the symptoms worth taking seriously.

• It works in some devices and not others. Intermittent detection is a hallmark of dirty contacts, a marginal reader, or cells that only fail under sustained load.
• Errors appear only during recording. Photos are light writes; 4K video is heavy, continuous, and heat-producing. A worn card usually survives the light work and dies on the video.
• Files come back as 0 bytes or will not open. The write reported success but the data was not stored. This is the clearest sign of failing memory or counterfeit capacity.
• Transfer speeds drop over time. Worn NAND needs more retries per write, so throughput falls. If a card that once wrote steadily now stutters, the endurance budget is spent.
• The device asks to format the card repeatedly. Formatting twice and seeing the same message weeks later means the index is being damaged by something still wearing the card.
• It suddenly became read-only. Wear has crossed a threshold the controller treats as final, and it is a signal to move your data, not to keep reformatting.
• Unknown folders with nonsensical names, or fragments of unrelated files. The controller is misreading blocks, which is a hardware-level fault.
• It is warm to the touch or was stored somewhere hot. Heat accelerates wear, and a card that has been in a hot car has a shortened life.

On r/photography, owners describe the pattern as failure with no prior warning after months of reliable use, which is why the reaction in those threads is anger rather than confusion. In practice there is usually a warning, but it is the warning above, not an error message.

One more signal worth trusting: if a card passes a format and then fails again within weeks, stop troubleshooting. A card that survives a fresh file system was not suffering from a file system problem.

Why Does My SD Card Keep Saying Card Error? The Real Causes

Here is the taxonomy, ordered roughly by how often each one turns out to be the answer.

File system corruption

The file system is the index, and it is the most fragile layer. A write that is interrupted halfway, a card yanked while the device is flushing data, or a power cut during a recording all leave the index inconsistent.

What you see is the device trying to mount an index that does not add up. It reports a card error, offers to format, or shows files that cannot be opened. The data is often still present, which is why recovery before formatting matters.

Write endurance exhaustion and controller failure

NAND flash cannot be overwritten indefinitely. Each cell is erased and rewritten a limited number of times, and every write also consumes a small part of that budget. The controller manages this through wear levelling, spreading writes across cells so none wears out alone.

When the budget runs out, cells stop holding a charge reliably. The controller’s error correction starts failing, the controller can no longer keep the index consistent, and the device sees a card error. This is also why a dying card often goes read-only with no warning: the controller locks writes rather than risk overwriting the data it can no longer replace.

The NAND cycle count matters most here. Published manufacturer figures put SLC in the region of 100,000 program-erase cycles, MLC near 10,000, TLC near 3,000, and QLC below that.

Divide the cycle count by how much you write per cycle. A dashcam or security camera overwriting in a loop runs constantly and exhausts a card in well under a year. A camera shooting a few hundred RAW photos a week gets a much longer run. This is the calculation that answers whether a card is at end of life or merely unlucky, and it is the single most useful thing to understand when a card fails again after a fresh format.

Users on Tom’s Hardware forums treat a card that repeatedly refuses to format as already dead, describing the controller as faulty or failing. That is the correct read on a card that has already exhausted its budget.

Physical damage, contact corrosion, and static discharge

A bent contact, a cracked shell, a card that has been forced into a slot, or a card that fell out of a pocket onto concrete can all produce a card error that no software touches. The contact pins corrode or bend, and a reader that pushes too hard can damage a card that fit fine yesterday.

Static is the version people do not expect. A dry winter, a synthetic jacket, and a card handled without touching anything grounded can discharge through the card. One widely reported case involved 250 irreplaceable photos lost to a static discharge in a dry Canadian winter, and it is why grounded reader housings matter more than they seem to.

Power loss and improper ejection

This is the most common preventable cause, and it is usually someone’s fault rather than the card’s.

Pulling a card while a camera is writing, or ejecting it from a computer without the safe-eject step, truncates whatever write was in progress. On a FAT or exFAT volume that can damage the allocation table, and on a loop-recording dashcam, an abrupt power cut does the same thing to whatever clip was being written.

The pattern is always the same. The card is fine until one interrupted write, then the index is damaged and the device asks for a format. The card did not get worse; the file system did.

Counterfeit cards and fake capacity

This one is under-recognised, and it connects directly to the corruption symptom.

A counterfeit card is often a small, genuine memory die paired with a controller programmed to report a much larger capacity. Writes past the real capacity wrap around and overwrite data that is already stored, so the files that appear corrupt are the ones written in the region beyond the true limit. On r/AskADataRecoveryPro, users describe data written past the card’s real capacity as always corrupt, showing up as zero-byte or oddly named files.

The tell is capacity reporting or behaviour. A 64GB card showing 39GB, files that vanish after the first few gigabytes, or corruption that always begins at the same offset all point at fake capacity. A 32GB card showing 29.8GB is not counterfeit, it is decimal versus binary capacity reporting and it is completely normal.

Free tools such as H2testw on Windows and F3 on macOS write a known pattern across the whole claimed capacity and verify it, which exposes a counterfeit card in about fifteen minutes. If the card fails that test, the answer to your corruption problem is a replacement card, not a repair.

Cross-device format conflicts

A card formatted on a computer is a frequent culprit for an error that appears in a camera. Many cameras expect FAT32 up to 32GB and exFAT above that, and some older models accept only FAT32, which is hard to create directly on a modern computer without third-party tools.

The NTFS case is worse. Some devices refuse NTFS cards outright, and a card written by a phone or tablet in a vendor-specific format may be unreadable in a camera even though the card itself is healthy. Formatting the card from inside the device that is complaining removes this whole class of problem, and it is the correct answer far more often than people expect.

Malware

Ransomware and card-malware families historically write autorun files to removable media, and a card that moves between a Windows machine and a camera can carry corruption back and forth. A full antivirus scan on the computer side is a cheap step, and a card formatted inside the device clears whatever the scan did not remove.

Fragmentation and the 4GB file size limit

FAT32 cannot store a single file larger than 4GB, which is why long 4K recordings on a FAT32 card break into fragments. A card filling up in scattered small blocks also makes index operations slower and more failure-prone. Formatting the card in the device restores a clean, contiguous file system and is the standard remedy.

A Two-Minute Triage: Card, Reader, or File System?

Run this before any command that writes. It tells you which of the three layers failed and saves you from formatting a card whose hardware is already gone.

Step 1. Is the card detected at all? If no device, no reader, and no laptop sees it, the hardware layer is gone or the contacts are dead. Go to the physical checks and cleaning in the next section. If cleaning does not produce a detection, stop, and read the conclusion, because nothing software-side will help.

Step 2. Does it appear in Disk Management on Windows? Open Disk Management and look under Disk drives. Present with a drive letter means the controller and NAND are answering. Present but unallocated or RAW means the file system is unreadable while the data is probably still there, which is the best case for recovery. Absent means the card is not enumerating.

Step 3. Does a second device read it? A card that works in a phone and not a camera points at the device’s file system or speed expectations, not the card. A card that fails everywhere points at the card.

Step 4. Does a second reader read it? If the same card works in a different reader, the reader is your problem, and no repair step is needed.

After those four answers, run the same test on macOS with Disk Utility. If Disk Utility lists the card and Info shows the capacity, the card is alive and the file system is the problem. If the card is not listed there either, treat it as failing hardware.

How to Fix an SD Card Error Step by Step

A corrupted SD card can be fixed in most cases, but the honest version of that sentence is: fixable when the hardware still answers, and the data is only preserved if you act before the index is rewritten. A physically broken or fully worn card cannot be fixed by software and has to be replaced.

The steps below escalate by risk. The data-loss warning comes before the destructive step, not after it.

Step 1: Check the card and the slot physically

Remove the card and look at it in good light. Check for a cracked shell, a bent or recessed contact edge, a discoloured or grimy contact band, and on full-size cards the write-protect lock switch in the side. Blow gently on the contacts and clean the slot with a dry, soft brush; compressed air and alcohol are not worth the risk here.

For microSD cards, check the adapter. This is the answer to a startling number of “card failed” reports, and readers on forums consistently point to the adapter as a source of intermittent false failures. Reseat the card in the adapter properly, or use a reader that accepts microSD directly.

Step 2: Try different hardware

Move the card to a different reader, a different USB port, and a different device. Use a direct port rather than a hub, and avoid a port that is simultaneously charging something, since those negotiate lower current and fail under sustained write load. This step takes two minutes and eliminates the most common false positive in the whole process.

Step 3: Check for a lock switch or read-only state

On a full-size SD or an SD adapter, slide the lock tab away from the label. If the card is read-only with no switch involved, the controller has set that state deliberately, usually because it no longer trusts the NAND. Back everything off the card and treat it as end-of-life rather than hunting for a fix.

Step 4: Repair the file system on Windows

This step can destroy recoverable files. If the data matters, image the card first, and only then run it.

Insert the card, note its drive letter from File Explorer, and open an elevated Command Prompt. Run chkdsk X: /f /r, replacing X with that letter. The /f flag repairs file system errors, and /r locates bad sectors and recovers readable data from them. Expect a prompt asking to schedule the scan for the next restart on some Windows versions; letting it run is the correct choice.

For a card that will not accept a drive letter, open Command Prompt and use DiskPart. Type diskpart, then list disk, then select disk N using the number for your card, then attributes disk clear readonly. If the card shows as RAW with no usable letter, format fs=exfat quick writes a fresh index, which permanently removes the old one. Only run that after a recovery attempt.

Step 5: Repair the file system on Mac

Open Disk Utility, select the card in the sidebar, and click First Aid followed by Run. This is the Mac equivalent of chkdsk, and it repairs the volume or the file system depending on what it finds. If First Aid reports the volume could not be repaired, use the Recovery option on the same card, which rebuilds the file system from the directory data.

Most troubleshooting guides for this error are Windows-only, which leaves Mac users with no path. Disk Utility handles the majority of file system damage.

Step 6: Assign a drive letter and rebuild the partition

On Windows, if the card appears in Disk Management but has no letter, right-click its partition and choose Change Drive Letter and Paths, then Add. If there is no partition at all, right-click the unallocated space and choose New Simple Volume, letting Windows assign the letter and pick exFAT.

That last option writes a brand-new index and the old one is not recoverable afterwards, so treat it as a format rather than a repair.

Step 7: Rebuild the partition table with TestDisk

TestDisk is free, open source, and reads the raw device without writing to it. Run it, pick the card, and use its partition table analyser to search for lost partitions. It frequently finds and restores a partition header that a damaged file system hid.

TestDisk writes partition metadata, so treat it as semi-destructive, and make sure you select the card by capacity rather than by name. If TestDisk finds nothing, move to a file carving tool.

Step 8: Scan the card and check its true capacity

Run a read-only surface scan. On Windows, H2testw writes a pattern across the entire claimed capacity and verifies it, which both tests for fake capacity and surfaces bad blocks. On macOS, F3 does the same job. On Linux, dd to a file and compare its checksum, or badblocks in read mode.

A card that fails verification has either counterfeit capacity or memory that can no longer hold data. Both are replacement decisions, and neither responds to a format.

Step 9: Format the card in the device that owns it

Once the data is backed up or declared unrecoverable, this is the step that actually solves the message. Use the camera’s or phone’s own format function rather than a computer wherever possible, because it writes the file system and the file size rules the device expects.

The rule for file systems is simple. FAT32 for 32GB and below, exFAT for 64GB and above, and never NTFS on a card that goes into a consumer camera. A full-size SD card with a physical lock switch is fine with exFAT; the lock switch is mechanical and only stops writes from a host that respects it.

Step 10: Replace the card

If the card cannot be detected, cannot hold a valid file system, fails a capacity test, or repeats the same failure after a fresh format in the owning device, it is finished. The GoPro community response to repeated card errors is consistently to recover what you can and replace the card, and that is the correct call.

Quick Format vs Full Format vs Low-Level Format

These three get described as equivalent and they are not. Knowing the difference tells you which one you can safely use.

The practical advice is to use a quick format, or the device’s own format function, and avoid low-level formatting on a card you intend to keep using as storage. A low-level format on removable media buys you nothing that a full format does not, and it destroys recovery options.

Device-Specific Fixes

The general steps above apply everywhere, but each device has one or two quirks worth knowing. Most troubleshooting pages cover Windows only, so the device-specific paths are gathered here.

Digital cameras, GoPro and DJI drones. Format the card from the camera’s own menu before blaming the card. Cameras check the file system and the speed class at power-on and refuse a card that does not match, so a computer-formatted exFAT card can be rejected by a camera that expects FAT32. For video specifically, the card must meet the speed class the camera asks for at your resolution; a card that passes photo tests and drops out during 4K recording is usually under-rated for the write rate rather than defective.

Android phones and tablets. Use Settings, Storage, then Format SD card, or the option inside the card’s own settings page; the path varies by brand. Formatting through the phone writes the file system the phone expects and avoids the file system conflict entirely. If the phone offers a repair or mount option, try that first, and avoid any third-party app that claims to repair SD cards for you.

Mac. Disk Utility is the whole toolset. First Aid repairs the file system, Restore and Erase are a full format, and the card’s Info pane tells you whether the hardware is still answering. If the card does not appear in the sidebar at all, the hardware has stopped enumerating and there is nothing further to try in software.

Consoles such as the Nintendo Switch. Format through the console’s system settings, and expect a strict capacity ceiling; the Switch also refuses cards below a minimum speed. A card that the console accepted and then began rejecting during a save is usually at end of life, and the console’s own error message is about the save data, not the file system.

Dashcams and security cameras. These are the hardest case because they write constantly. Loop recording means a power cut or a sudden shutdown interrupts a write and damages the index, so the card ends up prompting for a format on every start. Set the loop length short, format the card in the camera itself, and treat any card that has been running a dashcam for a year or more as due for retirement, since the endurance math in the table above applies with full force here. On r/EufyCam, users argue at length about whether the camera firmware or the card is to blame when write cycles accumulate, which is really a question about who owns the failure rather than how to fix it.

Raspberry Pi and other single-board computers. Cards run 24 hours a day with logging, swap, and database writes pointing at them, so they consume endurance faster than any other use. Check the file system in lsblk and the kernel log with dmesg for I/O errors, which report a card that is dying before the file system even complains. Mount it read-only while diagnosing, and use a card rated for sustained write workloads rather than a general-purpose one.

Recovering Files Before You Format

This section matters more than any repair step, because every repair above can destroy the index that points at your files. The order is not optional: connect, stop writing, image, scan, then recover to a different drive.

Step 1: Stop writing immediately. Do not shoot more, do not delete anything, and do not let the camera or phone use the card. Every new write consumes space the recovery tools may need, and a card that has failed once is already fragile.

Step 2: Take a full image. Copy the entire card to a drive on your computer, sector for sector, including the areas the file system does not describe. On Linux, dd if=/dev/sdX of=cardimage.img bs=4M status=progress does it, and on Windows a disk imaging utility can do the same. The image protects you because every later scan runs against a copy, and a card can fail mid-scan.

Step 3: Scan the image with carving tools. PhotoRec recovers files by signature, ignoring the file system entirely, which is exactly what you need when the index is gone. R-Studio, DMDE and TestDisk’s PhotoRec companion are all free or have free tiers. For photos, files come back with generic names but intact contents. For GoPro and DJI footage, the moov atom is often stored at the end of the file, so a recording that will not play may still be recovered by copying the tail of the file into a repaired container.

Step 4: Recover to a different drive. Always write recovered files to your computer’s storage or an external drive, never back to the card.

For photos from a corrupt card, recovery is often possible. For a long video that dropped out mid-write, the missing portion is usually gone, and a carving tool may recover the intact segments with no way to stitch them back together. If the footage is a wedding or a once-in-a-lifetime trip, professional recovery is worth pricing, because the difference between recovered video and a placeholder file is the whole point. Professional services cannot beat a dead card either; they charge for clean extraction from difficult cases, and the honest question is whether the value of the footage justifies the quote.

Preventing the Next Failure

Every fix above is a repair. The durable answer is not to create the situation again, and five habits cover nearly all of it.

Back up before you format anything, and back up more often than feels necessary. The full cycle of shooting, copying to two places, verifying the copies, then formatting the card in the device takes a few minutes and removes the panic from every future error. Users on r/Cameras describe losing fifteen minutes of footage to a card error, and the thread response is always the same: recover what you can, then replace the card.

Eject safely, always. On a computer, use the system eject or unmount. On a camera, power the device down before removing the card rather than swapping during recording. On a dashcam, set a short loop length so an interrupted write damages one short clip instead of the whole index.

Match the card to the workload. Photo work and 4K video have very different demands, and loop recording is heavier than both. Check the speed class your device specifies, and treat a card that slows down over months as a card to retire on your schedule rather than during a paid shoot.

Track write volume against the cycle table. Cards in dashcams, security cameras and always-on logging devices burn endurance continuously. A rough lifetime comes from dividing the NAND cycle count by how much you write per cycle, and a card that has been running as a dashcam for a year deserves replacing even if it has not failed yet.

Handle the card like a component. Touch the edges, keep it out of pockets with keys and coins, keep it away from heat and direct sun, and do not use a bent or loose microSD adapter. Formatting it in the owning device on a schedule, say every few months, keeps the file system clean and stops fragmentation from making write operations more failure-prone.

Finally, if a card has already been formatted in the owning device and still fails, do not keep formatting it. Storage manufacturers note that a nontrivial share of files on removable media can corrupt over time, which is the argument for backups rather than for repair.

Frequently Asked Questions

Conclusion: When to Stop Fixing and Replace the Card

Why does my SD card keep saying card error? Because one of its three layers has failed, and the fix depends on which one. If a card is undetected everywhere, will not hold a file system, fails a true-capacity test, has become read-only on its own, or repeats the same failure after a fresh format in the owning device, it is finished. Recover what you can, then replace it.

If it still enumerates and Disk Utility or Disk Management lists it, the file system layer is intact enough to work on, and the escalating steps above are worth the ten minutes. Whichever way it ends, copy everything off the card before you do anything that writes, because the files are often still there.

Reviewed and updated for 2026.