If your card looks empty but Windows still reports most of the space in use, stop and read this before doing anything else. That combination is one of the best-case scenarios in camera data recovery: space still occupied is the strongest practical signal that the photo bytes physically remain on the card. What broke is the directory, the index that tells the camera and computer where each file starts. Fix that visibility problem, or scan around it, and the photos usually come back.
Used Space Means Your Photos Are Probably Still There
Deleting a photo on a camera card does not erase it. The camera marks the directory entry as free, but the actual JPEG or RAW bytes stay on the flash chips until new data is written over the same clusters. SD and microSD cards do not run TRIM, the background wipe that solid-state drives perform, so nothing silently scrubs your pictures after deletion.
Apply that to your situation. When a card’s used space is still close to what it was before the photos vanished, those clusters are allocated to something, and in most cases that something is your photos. Only the directory entries pointing to them became unreadable, deleted, or overwritten. If the card had really been emptied or formatted, the used-space bar would have dropped to near zero. This is the difference between a corrupted SD card and a card that only looks empty, and it is why recovery here usually succeeds.
What Usually Happens: Broken Directories, Not Broken Photos
The most common cause is an interrupted operation: the card was pulled while the camera was still updating its file table, the battery died during a save, or the card was ejected mid-write. If that moment lands while the directory is being modified, the directory ends up damaged even though the photo data region is untouched.
Other causes look the same from outside:
- The folder structure itself was damaged, so the DCIM folder is missing or empty even though its contents are still allocated.
- Files were flagged hidden or system by an odd device, a cleanup tool, or malware, so they do not show in a normal listing.
- Files were deleted through a card reader on a computer, which bypasses the Recycle Bin, and the space stays allocated until a new write.
None of these destroy photo bytes. That tells you the real recovery target: not the data, but the directory. For the deleted-photo side of this problem, see our camera photo recovery guide.
Before You Scan: Two-Minute Quick Checks
Try these first; they occasionally resolve everything in seconds.
- Put the card back in the camera. Cameras sometimes still display files a computer cannot. If the photos show up there, copy them to a computer immediately.
- Try another card reader and another computer. Readers fail and drive letters go missing. A second reader is the cheapest diagnostic tool in photography.
- Enable hidden files. In File Explorer, open View and tick “Hidden items.” If entries appear, the files were simply flagged hidden.
- Clear hidden, system, and read-only attributes. If files are present but invisible, open a Command Prompt as administrator and run:
“bash attrib -h -r -s /s /d X:\. “
Replace X: with the card’s drive letter. This clears the hidden, read-only, and system flags from every file and folder in every subdirectory. It changes attributes only, so it is safe, but it helps only if the files are actually there and merely flagged.
If the card does not show up in Explorer at all, or Windows offers to format it, treat it as a card error rather than a missing-photos problem, and do not click format.
The Recovery Workflow That Brings Disappeared Photos Back
When the quick checks fail, the directory damage is real and you need a scan that works around it.
- Stop using the card now. No new photos, no format, no “repair this drive” prompts. Every write shrinks the odds.
- Use a card reader, not the camera’s USB cable. Camera firmware can write to the card while connected.
- Run a recovery scan. A quick scan finds files whose directory entries survive but are hidden or orphaned. A deep, signature-based scan recognizes photos by their file headers, which is what you need when the directory itself is damaged. Several of the free recovery methods handle this scenario well.
- Filter by size and date. Sort candidates by size to spot JPEGs and RAW frames, and by date when the software preserved it, then preview to confirm content.
- Save to a different drive. Recovered files must never be written back to the card they came from.
If you are on Windows and the card is still readable 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 save recovered files to a different drive.
If Photos Come Back With Names Like f0000001.jpg
When directory damage is severe enough that no file system scan can rebuild names and folders, signature-based carving takes over. Carving tools such as PhotoRec recognize photo content byte by byte and dump results into folders named recup_dir.1, recup_dir.2, and so on, with generic filenames like f0000001.jpg. Every recovered photo loses its original name, folder, and sometimes its modification timestamp.
Do not panic; the content is what matters. Sort the recovered set by each file’s embedded EXIF capture date, which survives deletion and carving, rather than by filename. Add the “Date taken” column in File Explorer, group by day, preview in batches, and delete duplicates, which appear when one photo is found both by its directory entry and by its signature. RAW shooters face the same renaming in NEF, CR2, and CR3 files; see our guide to recovering RAW photos before you start.
Frequently Asked Questions
Why does my SD card show used space but no files?
The space is occupied by data whose directory entries were damaged, hidden, or deleted. Flash deletion does not erase bytes, and SD cards have no TRIM to wipe them, so the photos usually remain fully recoverable.
Did a virus or my camera delete the photos?
Malware sometimes hides files on removable drives, which is why the attrib command is worth running first. More often the cause is an interrupted write, such as pulling the card while the directory was being updated.
Is it safe to run attrib or chkdsk on the card?
The attrib command only changes file attributes and is safe. Avoid chkdsk’s automatic repair mode before recovery, because it may move or rewrite directory entries on a card it considers damaged. Recover first; repair the file system later if you still want to reuse the card.
How long does a deep scan take?
A signature scan of a 64 GB card typically takes 15 to 30 minutes; larger cards and slower readers take longer.
My card is now completely empty and Windows wants to format it. What happened?
The file system itself became unreadable, which is corruption rather than a visibility problem. Do not format. Follow corrupted-card recovery guidance, scan with signature-based recovery, and treat any format prompt as a last resort.