A photo file can get corrupted at the moment you take it when the camera loses a clean “end-to-end write” to the memory card—most often from power interruption, a flaky card/contact/reader, or a card that’s wearing out and failing internally. The fix is to stop writing to that card immediately, try a safe recovery workflow, and then either reformat with the right tool or retire the card if errors repeat.

Memory card corruption during a shot: what’s actually breaking

When you press the shutter, the camera doesn’t “place a finished picture” onto the card in one instant. It streams data from the sensor into an internal buffer, builds the final file (JPEG/RAW), then writes that file to the card in chunks. If anything interrupts that chain, you can end up with:

• A file that exists but won’t open (header or internal structure missing).
• A file that opens partially (image cuts off, blocks, odd colors).
• A file that never properly “lands” (directory entry points to the wrong place, or the file size is wrong).

Corruption can happen at two levels at once:

1. The file itself (the data for that one image is incomplete).
2. The card’s file system (the “table of contents” for where files live becomes inconsistent).

The most common reasons it happens right when taking the photo

1) Power interruption during writing

If the camera loses power while it’s still writing—battery eject, dead battery, sudden shutdown, or even some crashes—you can get an incomplete file or file-system damage. This is why cameras warn you with a write LED/activity icon: it’s not decoration.

Typical symptom: the last photo (or the last few) are broken; sometimes the whole card becomes “needs formatting.”

2) Removing the card (or opening the door) while the camera is writing

Many cameras cut power to the card interface when you open the card/battery door, even if the camera looks “on.” If the camera is mid-write, that’s effectively yanking the plug.

Typical symptom: one fresh file is corrupted, plus you may see “card error” after reinserting.

3) Unreliable card-to-camera connection

Dirty contacts, worn card pins, flex in the slot, or a card that doesn’t seat firmly can cause intermittent disconnects. The camera thinks it’s writing to a stable device; the device disappears for a fraction of a second; the write ends badly.

Typical symptom: corruption appears randomly, often worse if you move the camera, bump it, or shoot in vibration-heavy situations.

4) The card is slowing down or “hanging” under burst load

If you shoot bursts or high-bitrate RAW, the camera buffer fills quickly and the card must sustain a minimum write speed. If the card can’t keep up (or its controller stalls), the camera can time out, crash, or fail a write sequence.

Typical symptom: corruption happens during long bursts or right after, sometimes paired with freezing or long “busy” times.

5) Internal wear or failing flash memory (the card is dying)

Flash memory wears out with write/erase cycles. Quality cards manage this well; failing cards don’t. Some devices switch into a protective read-only mode when the controller detects it can’t safely write anymore (you can’t fix that with “format again” if the hardware is protecting itself). (Sandisk)

Typical symptom: repeated corruption, sudden “write protected” behavior, or errors across multiple cameras/readers.

6) Formatting and file-system mismatch

Cards used across different cameras, phones, drones, and computers can end up with odd formatting edge cases. Quick-formatting on a computer can also create layouts that some cameras handle poorly.

Typical symptom: the card works for a while, then starts throwing errors after device switching; or it’s “fine on PC” but weird in-camera.

7) Problems during transfer that look like “camera corruption”

Sometimes the on-card file is fine, but corruption occurs when copying to a computer: bad USB cable, unstable hub, flaky card reader, or a computer crash mid-transfer. That produces a broken file on your computer while the original on the card may still be intact.

Typical symptom: the file copied to the computer won’t open, but the same image still previews in-camera.

What to do immediately when you notice corruption

1. Stop using the card right away. Do not shoot “one more test,” do not delete anything, and do not format yet. Any new writing can overwrite data that recovery tools might otherwise reconstruct.
2. Protect what’s still good. If the camera can still play back older photos, leave the card alone until you can copy data in a controlled way.
3. Try a different, known-good path for reading.
   • Use a different card reader (preferably a direct USB port, not a hub).
   • Try another computer if available.
   • If your camera supports USB file transfer reliably, you can try copying via the camera (this can be slower but sometimes more stable than a cheap reader).
4. Copy everything you can before “repair attempts.”
   • If simple drag-and-drop works, copy the entire DCIM folder to a new folder on your computer.
   • If the copy fails partway, copy in smaller batches (by date folders or file ranges) so one bad file doesn’t stop everything.

Safe recovery vs. risky “fixes”

Safer first steps (lower chance of making things worse)

• Try multiple readers/ports/computers. You’re ruling out a transfer-side problem.
• Copy whatever is readable first. Recovery is easier when you already saved the good files.

Riskier steps (can change the card’s structures)

• Running file-system repair tools can rewrite directory structures and “orphan” fragments. This can help, but it can also make deep recovery harder if you do it too early.
• On Windows, tools like CHKDSK can fix logical errors when used with repair flags, but it’s important to understand it may modify the file allocation structures to make the drive consistent again. (Microsoft Learn)

A practical approach:

• If you have critical photos: recover/copy first, then consider repair tools only after you’ve extracted what you can.
• If nothing critical is on the card and you just want it usable again: you can skip straight to a proper reformat workflow.

Getting the card reliable again (or deciding to retire it)

Step 1: Reformat the right way (after copying/recovery)

For SD/microSD cards, the SD Association provides an official formatter designed to format cards to the SD file system specification. This is often more compatible than random quick formats. (SD Association)

After using that formatter, format once more in the camera that will use the card (so the camera creates its preferred folder structure cleanly).

Step 2: Stress-test your trust in the card

A card that corrupts once due to an obvious interruption (battery pulled mid-write) might be fine after a clean format. A card that corrupts again later—especially without a clear cause—should be treated as unreliable.

Retire the card if:

• Corruption repeats on the same card after clean formatting.
• The card suddenly becomes write-protected or read-only unexpectedly. (Sandisk)
• Errors happen across multiple devices and readers.

Step 3: Change the habits that most often trigger corruption

• Don’t remove the battery/card or open doors until the write light is fully done.
• Keep batteries healthy in cold conditions; low voltage events increase shutdown risk.
• Avoid ultra-cheap readers/hubs; direct ports reduce transfer errors.
• Don’t “delete a few” on the card repeatedly for months; periodically back up and format in-camera.

Why does this matter

A corrupted file isn’t just “one lost photo”—it’s often a warning that your capture pipeline (power, card integrity, or write process) is unreliable, and the next failure may be worse if you keep using the same setup.

Sources

• SD Association — SD Memory Card Formatter (SD Association)
• SanDisk Support — why a card may enter write protection to prevent data loss (Sandisk)
• Microsoft Learn — CHKDSK behavior and repair implications (Microsoft Learn)