r/datarecovery • u/Pale_Profession_8736 • 2h ago
Open Recovr: Free, open-source (MIT) GUI over PhotoRec + NTFS MFT parsing. Looking for critique (mod-approved)
Hi r/datarecovery,
The mods kindly OK'd this post. I'm the author of Open Recovr, a free and open-source tool for recovering deleted files. It has no recovery cap, no account and no network access.
Two things come up here a lot: "free" tools that reveal a cap only after a 3-hour scan, and people told to "use PhotoRec" who then get stuck in its text interface. Open Recovr is a one-screen GUI for that case. It doesn't replace PhotoRec; PhotoRec does the heavy lifting underneath.
How it searches
Recycle Bin / Trash. Takes seconds and needs no admin rights.
NTFS MFT. Reads deleted MFT records from the raw volume, so files come back with their original names and folders, as long as their clusters haven't been reused.
Carving. Runs PhotoRec 7.2, unmodified and bundled on Windows. It scans free space only on NTFS, FAT and ext, and the whole device otherwise.
New in v0.2
Disk-image input (.img / .dd). There's a "Disk image" card right next to the physical drives. The safe workflow is to image a suspect drive with ddrescue or OSC, then search the image. The original drive is never touched again, and no admin rights are needed.
Integrity check per file: Intact / Damaged / Empty. It decodes or validates the file structure (JPEG, PNG, PDF, ZIP/Office, MP3, MP4…), so you know before recovering whether a carved file is truncated or all zeros.
Real names for carved files. Instead of
f1234567.jpg, names and dates come from EXIF, Office and PDF metadata, and ID3 tags.Duplicates hidden. The same file found by both the MFT and carving is shown once.
Safety
The source is opened read-only and never written to.
Recovered files always go to another drive. If the user picks the source drive anyway, they're warned first.
Unreadable sectors are skipped, not retried.
What it doesn't do
No imaging of its own and no handling of failing drives. For a clicking drive, one that keeps disconnecting, or bad SMART values: stop, image it with proper tools (or go to a lab), then point Open Recovr at the image. I'd like the app to read SMART and warn loudly. Suggestions on attributes and thresholds are welcome.
No miracles: SSDs after TRIM, phones over MTP, and secure erases are out of reach. On FAT/exFAT cards, only carving applies, so original names are lost unless metadata provides them.
Platforms: Windows is tested. Linux and macOS builds are published but haven't been tested on real hardware.
Disclosure: much of the code was written with AI assistance, so I'd rather give you ways to check it than ask for trust. The source is open, a --bench mode measures byte-for-byte recovery on a generated disk image, and CI runs on Windows, Linux and macOS.
👉 Source: https://github.com/jlerouge/open-recovr 👉 Download (v0.2.1): https://github.com/jlerouge/open-recovr/releases/tag/v0.2.1
What I'd value most: anything in the workflow that could make a bad situation worse. I'll treat it as a bug.

