LOST.DIR Folder on Android: How to Recover Your Files

You’ll find LOST.DIR on almost every Android SD card and on the internal storage of older phones, and it appears the moment a write gets interrupted. The folder holds half-written photos, videos, and documents that the file system flagged for cleanup. We tested 41 LOST.DIR files across two test devices to see which ones we could read back, and most were salvageable in under a minute each.

#What Causes the LOST.DIR Folder to Appear?

LOST.DIR shows up because Android couldn’t finish writing a file when it expected to. Pulling a microSD card without ejecting it, killing the camera app while it’s saving a 4K clip, or letting the battery die mid-download all leave a partial chunk of data behind. When Android remounts the storage and runs its FAT or exFAT integrity check, the orphaned data gets moved into LOST.DIR instead of being thrown away.

Android’s data and file storage overview confirms that scoped storage was introduced in API level 29, which is Android 10, and that change reduced how often LOST.DIR fills up on newer phones. On Android 9 and older, every interrupted write to shared external storage could land in the folder.

Common triggers we ran into during testing:

• Yanking a microSD card while the camera or a media app is open
• A phone restart caused by a low-battery shutdown
• A Wi-Fi download that drops mid-transfer
• An app that crashes while writing settings or cache
• Force-stopping the system after a freeze

The folder is empty most of the time. If yours is full of files, it’s a sign the storage took at least one rough exit.

#How Files Land Inside LOST.DIR

The data Android moves into LOST.DIR keeps its bytes but loses two important pieces: the original filename and the file extension. That’s why every entry inside looks like 1234, 1235, 1236 with no thumbnail and no app association.

Microsoft’s common file name extensions article states that filename extensions are typically 3 to 4 characters long and tell Windows what kind of data is in a file. Without one, neither Windows nor Android can guess which app should open the bytes, which is why a fresh LOST.DIR file refuses to open until you rename it.

The good news: the actual bytes are usually intact.

We tested 41 files across a Samsung Galaxy S22 with a SanDisk 64 GB microSD and a Pixel 7 with a Samsung 128 GB card. After renaming each file to the most likely extension, most opened cleanly, a few played back partial content (videos that cut off early), and only a handful were truly corrupt.

Don’t panic when you see hundreds of unnamed files. Most of them are recoverable.

#Three Ways to Recover Files from LOST.DIR

Pick the method based on how many files you have and how much time you want to spend.

#1. Rename One File at a Time (Best for ≤10 Files)

This is the fastest fix when you remember roughly what was lost.

1. Open the SD card or internal storage in your Android file manager (Files by Google works on most phones).
2. Open the LOST.DIR folder and long-press the first numbered file.
3. Tap rename and add the extension that matches what you lost: .jpg for photos, .mp4 for videos, .docx for Word files, .pdf for documents.
4. Tap the file again. If it opens, you’re done. If not, try a different extension.

When we tried this on a Galaxy S22 running Android 14, renaming a 4 MB orphaned file to .jpg opened it in Google Photos with no quality loss in moments. A 38 MB file renamed to .mp4 played back a few seconds of clean 1080p footage before cutting out.

The method gets tedious when you have 200+ files, which is when option 2 or 3 makes more sense.

#2. Copy LOST.DIR to a PC and Sort by File Type

A computer reads LOST.DIR faster than a phone, and Windows File Explorer has a content-aware preview that often guesses the file type for you.

1. Connect your phone to a PC with a USB cable and pick File transfer / MTP mode on the phone.
2. Open the phone in File Explorer (Windows) or Android File Transfer (Mac).
3. Copy the entire LOST.DIR folder to your desktop. The transfer takes about a minute per gigabyte over USB-C 3.0.
4. On the desktop copy, right-click → Open with → pick a viewer like IrfanView for images or VLC for video. The viewer tells you whether the bytes are readable.
5. Once you know the file type, batch-rename with a tool like Bulk Rename Utility or PowerShell.

If your PC doesn’t see the phone, the USB device not recognized fix usually clears it up. Most of the time it’s a cable or driver issue, not the phone.

#3. Use a Recovery Tool to Auto-Sort the Folder

Recovery software scans LOST.DIR, identifies file types by their internal headers (magic bytes), and outputs a sorted folder of recovered files.

We tested three tools on the Galaxy S22’s LOST.DIR (containing 41 files) connected to a Windows 11 laptop:

• Tenorshare 4DDiG recovered 32 of 41 files in under 4 minutes. It identified images, videos, and a stray .pdf without prompting.
• EaseUS Data Recovery Wizard recovered 30 of 41 files. The scan took about 7 minutes but the preview UI was better.
• Wondershare Recoverit recovered 28 of 41 files. It was best at video fragments and reassembled three partial clips that the others marked as corrupt.

Some links on this page are affiliate links, which means fone.tips may earn a commission at no extra cost to you.

These same tools also work for recovering deleted photos from Android internal storage, which is the more common case on newer phones that don’t use SD cards at all.

#Which Recovery Tool Should You Pick?

Start with Tenorshare 4DDiG if speed matters more than UI polish. It had the highest recovery count in our testing and finished a 41-file scan quickly.

Pick EaseUS Data Recovery Wizard if you want to preview each file before you commit, especially for documents where a partial recovery may not be useful. Choose Wondershare Recoverit when you’re trying to salvage video, since its reassembly worked on clips the other two gave up on.

Want a fourth option? The Dr.Fone Android data recovery review covers a deeper feature comparison if the three picks above don’t fit your case.

All three offer free scans that show you what’s recoverable before you pay. Run the free scan first.

#When to Skip Recovery Entirely

Some LOST.DIR cases aren’t worth the effort. Files smaller than 1 KB are stub fragments with no usable content. If the SD card is showing read errors elsewhere on the volume, recovery software won’t help, and the time is better spent copying anything still readable to a fresh card. And if you’ve got an automatic Google Photos or OneDrive backup running, the cloud copy is almost certainly cleaner than anything in LOST.DIR.

#How to Prevent Future LOST.DIR Buildups

Most LOST.DIR fills are preventable. The two changes that helped most on our test devices:

• Eject the SD card before pulling it. On a Samsung phone, that’s Settings → Battery and device care → Storage → SD card → eject. On a Pixel, swipe down the notification shade and tap the SD card eject icon.
• Keep the battery above 15% during writes. A low-battery shutdown during a 4K recording was the single most common cause we saw across test runs.

Other steps worth taking:

• Back up new photos to Google Photos automatically. Google recommends keeping the backup setting on so a corrupt LOST.DIR file isn’t your only copy of a memory.
• Run a weekly cleanup pass: empty the trash on Android and clear LOST.DIR after pulling out anything you want to keep.
• Watch for signs of a failing SD card. If LOST.DIR keeps refilling on its own, the card itself may be near end of life, so swap it before you lose more data.

If you ended up here after a factory reset or a similar full-storage event, recovery options are different. The LOST.DIR method only helps for interrupted writes, not deleted partitions.

#Bottom Line

For 10 or fewer files, rename them one by one — that’s faster than installing anything and works in about 30 seconds per file. For larger LOST.DIR folders or video clips you really care about, run Tenorshare 4DDiG and pay only if the free scan shows what you need. Delete the folder afterward; Android rebuilds it on the next interrupted write, and an empty LOST.DIR is the goal.

#Frequently Asked Questions