Cameras and phones can format a card in seconds. Your priority is to stop writing to that card: no new photos, no “quick tests,” and no in-place repairs until you have a recovery plan. Remove the card and attach it with a quality USB reader when possible.
Built-in laptop SD slots are convenient but sometimes negotiate odd speeds or drop the bus under load. A known-good USB 3 reader on a short cable reduces mechanical wobble and helps long Deep Scan passes finish without I/O errors that force you to restart.
exFAT vs FAT32 in the field
Many camera cards use exFAT. Quick format typically clears the bitmap and directory structures; file data may remain until overwritten. If the camera offers “low level” or secure erase options, avoid them until you have recovered what you need—they are destructive by design.
Run Recuva against the card, escalate to Deep Scan if files do not appear, and recover to your PC’s internal disk or another external drive—not back onto the same SD card. Names may be generic; rely on previews and file sizes when sorting results.
Sorting carved results
Video folders often contain a few giant files; burst photo shoots create thousands of small JPEGs. Filter by extension and approximate dimensions when the UI exposes them. Recover a handful of test shots first, open them at full resolution, then scale up your selection.
If the card was removed during a write, you may see partial files or corrupt headers. That is filesystem damage, not Recuva “missing” data—recovery can still pull fragments, but editors may refuse to open them until repaired with specialized media tools.
After you have a copy on safe storage, reformat the card in-camera when the manual recommends that path—it aligns cluster size with what the device expects. Until then, keep the original card read-only in a labeled sleeve so you do not confuse it with your working spare.
More scenario timelines live on Stories; the workflow page covers the same stop-write → scan → restore-elsewhere rhythm for internal disks.
Phones, tablets, and “the card is fine in the PC”
Android and iOS often adopt the card as adoptable storage or encrypt it per-device. If the phone reformatted the card as internal memory, a PC reader may see encrypted garbage—not a filesystem Recuva can parse. In that case recovery is a phone-vendor or backup problem, not a desktop undelete pass.
Dual-slot cameras and wrong-slot deletes
Photographers sometimes write raw to slot 1 and JPEG to slot 2—or overflow from one card to another. When you recover, match the card you scanned to the shoot day and body serial in your notes. Mixing two shoots on one card before recovery finishes is a classic way to overwrite what you meant to save.
Heat, vibration, and counterfeit cards
Long 4K recording sessions heat the card and the reader. Thermal throttling can surface as disconnects mid-scan. If the same card fails in multiple readers, suspect counterfeits (wrong capacity reported after a while) or wear leveling exhaustion—hardware replacement enters the picture.
After recovery: ingest and backup discipline
- Copy to two locations before you reformat the card (NAS + cold archive, or cloud + external).
- Generate checksums for long video takes; one flipped bit can ruin a wedding reel.
- Label the card “DO NOT USE—recovery source” until stakeholders sign off.
If you work with drones or action cameras, remember GPS sidecar files (.SRT, .LRF) may be tiny and easy to overlook in a noisy Deep Scan list—filter by extension and recover them with the video.