I pulled my SD card out of my phone without safely ejecting it, and now some photos and videos are missing or the card isn’t reading right. I really need help figuring out the safest way to recover data from the SD card without making things worse.
I’ve been there, and yeah, deleting a whole set of photos off an SD card feels bad fast. The small upside is this. Deleting usually removes the file system record, not the photo data itself. The images often stay on the card until new files land in the same space and overwrite them.
Before you install anything, I’d check a few plain things first.
- Stop using the SD card now. This applies in every case. Pull it out of the camera, phone, or reader. If you keep shooting or copying files onto it, your old photos get replaced and recovery odds drop.
- Check Trash or Recycle Bin. This only matters if the card was connected to your Mac or PC when you deleted the files. Sometimes the delete happened through the computer, not on the card itself.
- Look at cloud sync apps. If the card was used in an Android phone, or you had sync turned on through something like Google Photos, Dropbox, or OneDrive, there might be copies sitting there already.
- Try another card reader or USB port. I’ve seen bad readers make half a card vanish, then show up fine on a different port. If the card looks empty or incomplete, don’t assume the files are gone yet.
If none of that helps, recovery software is the next move. One thing I would not do is run CHKDSK on Windows or First Aid on macOS for deleted photo recovery. Those tools fix file system issues. They are not meant for bringing back deleted files, and they sometimes make the card worse.
If you want the easiest route, I’d start with Disk Drill. I used it on camera cards before, and it tends to be less annoying than the command-line stuff. It also has an Advanced Camera Recovery mode aimed at memory cards from cameras and phones.
What I’d do, step by step:
- Install Disk Drill on your Windows PC or Mac.
- Put the SD card into a dedicated card reader, then plug the reader into your computer.
- Don’t connect the camera itself over USB if you can avoid it. In my expereince, direct camera connection sometimes limits how well recovery apps read the raw storage.
- Open the app, pick the SD card from the drive list, and start the scan.
- Wait for the scan to finish. Preview the photos it finds. If the preview opens cleanly, the file is usually recoverable and not broken.
- Select the files you want back, then recover them.
- Save everything to your computer’s internal drive, not back onto the SD card. Writing recovered files to the same card is how people ruin a second shot at recovery.
If you don’t want to use Disk Drill, there are other options, though each one has some catch.
PhotoRec and Windows File Recovery cost nothing, which sounds great until you use them. They rely on terminal commands instead of a normal interface. PhotoRec also tends to strip file names and folder layout, so you end up sorting a pile of files by hand. I did this once with vacation pics and it was a dumb waste of time.
If all you have is an Android phone, DiskDigger exists. The issue is root access. Without root, you often get low-res cached thumbnails instead of full photos. For proper recovery, I’d still use a desktop tool if you have any path to one.
Main thing is simple. Stop using the card, scan it through a reader, and recover the files onto a different drive. If the photos have not been overwritten, your odds are usually good.
Unsafe removal often corrupts the file system, not the photo data. That matters. Missing files after yanking an SD card from a phone are often recoverable if you stop writing to it now.
I agree with @mikeappsreviewer on one big point. Do not keep using the card. I disagree a bit on repair tools though. If the card has important data, make an image of the card first, then test repairs on the image or a copy. Running fixes first on the original media is where people get burned.
What I’d do:
- Put the SD card in a USB card reader on a PC.
- If it reads at all, clone it first with a tool like USB Image Tool, Win32 Disk Imager, or dd on Mac/Linux.
- Work from the clone, not the original card.
- Check the DCIM folder and also hidden folders. Phones sometiems leave files with broken indexes but intact data.
- On Windows, look in Disk Management. If the card shows the right size but no letter, assign a drive letter. If it shows RAW, skip repairs for now and go to recovery.
- Run recovery software against the clone. Disk Drill is a solid pick here because it handles SD cards well and previews media before recovery.
- Recover files to your computer drive, never back to the SD card.
If the card is unreadable, reports 0 bytes, disconnects randomly, or gets hot, stop. That points to hardware failure. Software won’t fix that. A lab is the safer route.
If you want a quick visual explainer, this covers deleted file recovery from storage cards and phones pretty well: watch this short guide to recovering deleted photos and videos
Small tip most ppl miss. Check for .nomedia files and hidden content. Android apps sometimes hide media from gallery apps, so the files exist but the phone stops indexing them.
I’d add one thing neither @mikeappsreviewer nor @voyageurdubois really stressed enough: if the card still mounts even briefly, copy the entire visible folder structure off first before doing any deep scan. Sometimes after unsafe removal, the issue is just a messed-up media database or directory entry, and the actual JPG/MP4 files are still sitting there in DCIM or Android/media. People jump straight to recovery tools and skip the easy win.
Also, I would be careful with putting the card back into the phone to “see if it fixes itself.” Phones love to auto-write stuff, rebuild folders, and make recovery harder. Kinda rude tbh.
What I’d do:
- lock the SD card if it has a physical write switch
- use a PC with a decent card reader
- see if files are visible in normal File Explorer/Finder first
- if yes, copy everything off immediately
- if no, then use recovery software
If you need recovery software, Disk Drill is a solid option for SD card recovery because it handles corrupted cards and missing photos/videos pretty well without being a total pain to use. I like it more for this than messing around with half-broken phone apps.
One more thing: if videos come back but won’t play, don’t assume they’re dead. Unsafe removal often leaves video containers unfinalized, especially MP4 files. Sometimes they need separate video repair after recovery.
Also worth checking this thread for extra camera card recovery tips: best Reddit advice for recovering deleted SD card photos.
If the card starts disappearing, asks to be formatted, or reads as RAW, stop poking at it too much. That’s where ppl make it worse fast.
One angle I’d add to what @voyageurdubois, @yozora, and @mikeappsreviewer already covered: check whether this is actually a file system problem or a phone indexing problem before doing anything invasive.
Unsafe removal often leaves the card fine, but the phone’s media database gets confused. On a computer, look for these:
DCIM/CameraPicturesMoviesAndroid/media- oddly named folders with dates or app names
- files that suddenly became 0 KB
If the photos/videos are there but not showing on the phone, that is a very different situation from true data loss.
I slightly disagree with the “repair later” advice only in one case: if the card is non-critical and you already made a full byte-for-byte image, testing a file system repair on the copy can sometimes restore original folder names faster than raw recovery. The key part is on the copy, never the original.
A few extra checks people skip:
- Compare used space vs free space on the card. If most space is still “used,” your files may still exist but the directory is damaged.
- On Linux or macOS, see if the partition table is still visible. If the partition vanished entirely, recovery becomes more about carving than normal undelete.
- If videos are missing, search by file signature or extensions beyond
.mp4, including.3gp,.tmp, and app-specific temp video formats. - If the card was used as Android adoptable storage, normal recovery is much harder because contents may be encrypted.
For software, Disk Drill is reasonable here if the card is readable enough to scan.
Pros:
- easy UI
- good preview for photos/video
- decent with SD card corruption
- can recover to another drive without much fuss
Cons:
- not the cheapest route
- deep scans can return lots of junk on badly damaged cards
- sometimes weaker on preserving original filenames than file-system-first recovery
If Disk Drill misses stuff, the fallback is usually PhotoRec or R-Studio, depending on whether you care more about simplicity or deeper analysis.
One hard stop: if the card capacity shows wrong, changes between inserts, or the reader keeps reconnecting, quit experimenting. That smells like failing flash or controller trouble, not just unsafe eject corruption.

