Deleted the wrong file? We read the disk before we promise anything.

Three routes back to a deleted file: the Recycle Bin, a read-only scan of the drive, and the copies Windows keeps. A file is listed only after its bytes are read.

Free · no file-count or size cap · Windows 10/11 · 64-bit
Sample values: a USB stick read without writing to it, restoring to a second disk. Everything in Recover files →
Proof

The copy is checked after it is written.

A file counts as back only when the bytes on the far side match what was read.

Read firstIts blocks are read before a file is listed.
Hash matchesThe copy is read back and compared.
Not offeredA file found without proof is shown with its reason.
Limits

What it can't do.

Worth knowing before you start, not halfway through.

A drive you formattedA format writes a fresh filesystem, so the records are gone. Use PhotoRec.
A drive Windows can't readRAW volumes and lost partitions are outside this. Use TestDisk.
A physically failing driveImage it first with a tool built for that, or use a recovery service.
RAID, Storage Spaces, dynamic disksNot supported.
Phones over USB, network drives, NASThese expose files, not blocks. Check the device's own trash.
ext4, APFS, HFS+, ReFSNTFS, FAT32 and exFAT only.
Very large NTFS drivesAbove roughly 8 TB we cannot load the drive's allocation map, and rather than guess whether a file's blocks are free we refuse them. Expect very little from a scan of a drive that size.
Fragmented exFAT, compressed, sparse or encrypted filesDetected and refused, never approximated.

For a formatted or unreadable drive, PhotoRec and TestDisk are free, open source and the right tools.

What we refuse to ship Carving free space for file signatures Listing a file before reading it Writing to the drive being read A recovery success rate Why we refuse them →
Questions

Before you scan.

All questions →

Can it recover files after I emptied the Recycle Bin?

On a hard drive, a memory card or a USB stick, usually yes. On an internal SSD, usually not: Windows tells the drive to discard deleted blocks, and once it has, no software can read them back. The filename and size can outlive the data, so we read the blocks before listing a file and tell you when it is gone.

Which drives and formats does it work on?

Internal drives, memory cards and USB sticks formatted NTFS, FAT32 or exFAT that Windows can still mount with a drive letter. ext4, APFS, HFS+ and ReFS volumes, and drives that show as RAW in Disk Management, are outside it.

Can it get back a file I saved over?

Sometimes, through the copies Windows keeps: the same ones behind Previous Versions in Explorer. What comes back is the whole file as it was when the copy was taken. It works when System Protection is on and a copy was taken while your file still existed.

Will it write to the drive I'm recovering from?

The scan and the restore don't. The drive being read is opened read-only, recovered files go to a different physical disk (judged on the disk, not the drive letter), and nothing is ever deleted. Recovery-safe mode also switches off the app's own background work. Windows itself keeps writing to the drive it runs from, so if the file was on C:, use the PC as little as you can until it is back.

ProRecover files is free. Pro adds Guardian automation and the deep-tuning modules; Ultra adds Smart Route.

Pro $4.99 (charged as ₹499)/year · Ultra $9.99 (charged as ₹899)/year · each renews yearly until you cancel.

Read the drive first. Then decide.

Free, with no file-count or size cap. If you can, install onto a different drive from the one you're recovering.