18 November 2026
Recuva vs PhotoRec: Two Free File Recovery Tools Tested on a Real Deleted Invoice

PhotoRec got the invoice back. Recuva did not, and it was not close.
That is the short version of a test we ran last month after a genuine accident: a supplier invoice saved to the wrong folder, then wiped when someone cleared out what looked like a junk directory. No backup covered that folder yet, so we were on our own. We had two free options worth trying, Recuva from Piriform (the CCleaner people) and PhotoRec, which ships as part of the open source TestDisk package. Both cost nothing. Only one of them returned a usable file.
Why the invoice was a fair test
A deleted PDF is not the easiest recovery job. It is not the hardest either. It sits in the middle, which is what made it useful to compare against.
Photo is a bad word for PhotoRec, by the way. The name makes it sound like it only hunts JPEGs. It recovers documents, archives, and plenty else. What matters is how each tool finds the file, and that difference decided our test.
How the two tools work, and why it matters
Recuva reads the file system. On an NTFS drive it looks at the master file table, sees the leftover entry for a deleted file, and tries to pull the data back from the clusters that entry still points to. That works beautifully when the entry is intact and the clusters have not been overwritten.
PhotoRec ignores the file system completely. It scans the raw drive sector by sector, looking for the internal signatures that mark where a PDF or a Word document begins and ends. It does not care whether Windows still remembers the file at all.
Those two approaches fail in different situations. If the file system entry is gone, Recuva has nothing to work with. If the drive is heavily fragmented, PhotoRec can stitch a file back together badly because the pieces are no longer in order. We hit the first problem.
What happened with Recuva
We installed Recuva on the machine and pointed it at the drive. The wizard is friendly, almost too friendly, with a file-type picker that lets you narrow the scan to documents, pictures, or everything. We chose everything and let it run.
The scan finished quickly. Recuva listed a long tail of deleted files with names and paths, which is its strength. You can see exactly what it found and tick the ones you want. Our invoice was not on the list.
We ran the deep scan next. That is slower and more thorough, and on this drive it took a good while. It surfaced more entries, but the invoice still did not appear with a recoverable state. Several files came back flagged as unrecoverable, meaning the clusters had already been reused. Ours was simply absent.
Nothing was wrong with Recuva. It did what it promises. The file system record for our invoice had been overwritten by later activity on the drive, so there was nothing for it to read. A tool that trusts the file system cannot help when the file system has forgotten.
What happened with PhotoRec
PhotoRec is not pretty. It runs in a text interface, and you navigate it with arrow keys. If you expect a window with a big green button, you will be disappointed. We selected the drive, chose to scan the whole partition rather than just free space, and picked a folder on a separate USB drive as the destination.
That last part matters. You must never write recovered files back to the drive you are recovering from. PhotoRec will warn you about this. Take the warning seriously, because writing to the source drive is exactly how you turn a recoverable file into a permanent loss.
The scan was slower than Recuva’s deep scan. It ground through the drive looking for signatures, and on a large disk you should plan to leave it running. When it finished we had a folder full of files with names like f0123456.pdf. No original filenames, no folder structure, just raw carved files sorted by extension.
Our invoice was among them, intact and readable. We found it by opening the PDFs one by one until the right one turned up. Tedious, but it worked.
The trade-off in plain terms
Recuva gives you names and paths when it can find them, which makes recovery fast and unambiguous. It also gives you a proper Windows interface and a preview for some file types. When it works, it is the nicer tool by a wide margin.
PhotoRec gives you a pile of unnamed files. It does not care about names because it never reads them. What it gives you in return is a much better chance on a drive where the file system no longer has the answer. It also handles a wider range of storage situations, including memory cards and drives whose file systems are damaged enough that Windows will not mount them.
Neither tool is better in the abstract. They answer different questions. Recuva asks the file system what it remembers. PhotoRec asks the raw disk what is physically still there.
Practical notes from the test
- Stop using the drive the moment you realise a file is gone. Every write, every temp file, every browser cache nibbles at the free space where your deleted data still sits.
- Run recovery tools from a USB stick or another machine if you can, so you are not loading a program onto the very disk you are hoping to save.
- Recuva’s deep scan is worth the wait before you give up on it. The quick scan misses a lot.
- PhotoRec needs a destination drive with enough free space for the carved files. Budget generously, since it recovers everything it can find, not just what you wanted.
- Both tools lean on the same principle: recover first, sort later. Do not try to be selective during the scan.
Where each one fits in a small business
For the everyday case, a file deleted an hour ago on a healthy drive, Recuva is the first thing we reach for. It is quick, it shows names, and it usually just works. Keep it on a utility USB drive alongside the rest of your toolkit.
PhotoRec is the fallback for the harder cases, when the file system has moved on and the easy tool comes up empty. It is clunky and it hands you a heap of unnamed files, but it pulled back the invoice when nothing else would. We now keep TestDisk and PhotoRec on the same USB stick.
Worth saying plainly: neither of these is a backup. Recovery is what you do when the backup failed, and ours had a gap that let this happen in the first place. We closed that gap the same week. If you are relying on a recovery tool to protect your books, you are one overwritten cluster away from a very bad afternoon.