Windows File Recovery · Open Source

RECOVER. NOT GUESS.

Most tools dump 1,000 fragments of one video and call it a result. Recoverer detects fragment chains, collapses them into one entry, and reads the full span in a single pass.

0
Fragment chains collapsed
32 MB
Chunk size per read
75%
MFT-backed confidence
Rust
Memory-safe engine
01
The Problem

Other tools stop at finding.
Recovery is the hard part.

Other tools
1,000 entries for one fragmented video file
No memory between scan sessions — start from scratch every time
Every file shown at "100% recoverable" regardless of actual state
Reads each fragment separately — hours of disk thrash for one file
Written in C/C++ — silent data corruption on edge-case sectors
Re-scanning recovers the same files you already have
Recoverer
Fragment chains collapse into one entry automatically
SQLite session database persists across scans and reboots
Three-tier confidence: 45% header-only → 75% MFT-backed
Span-based recovery reads full chain in one contiguous pass
Rust engine — memory safety at the type level, not by luck
Cross-session cluster tracking pre-marks already-recovered files
02
Why it's different

Five things nobody
else does.

Not features. Engineering decisions that change what recovery actually means.

01 / 05
Fragment Chain Detection

When a 4 GB video is carved off a drive in a thousand pieces, every other tool shows you 1,000 separate entries. Recoverer detects that they're consecutive same-type clusters within per-format gap tolerances — 50 MB for video, 20 MB for audio — and collapses them into a single chain entry. One click. Whole file.

50MB video gap threshold MIME-aware grouping Sector-adjacent detection
02 / 05
Span-Based Recovery

Other tools read each fragment as a separate I/O job. For a badly fragmented 4 GB video that could mean thousands of separate reads — effectively scanning the entire drive again. Recoverer computes the full contiguous span from first sector to last and reads it in 32 MB chunks. Minutes, not hours.

32MB chunk reads Single contiguous pass Chain span computation
03 / 05
🧠
Cross-Session Memory

Every recovered file is recorded by disk cluster in a persistent sessions.db. Run a surface scan today, a deeper carve next week — Recoverer automatically pre-marks files you already have. "Hide recovered" works across sessions, not just within one run. Stop recovering the same files twice.

SQLite cluster tracking Cross-session dedup ApplyScanHistory command
04 / 05
📊
Honest Confidence Scoring

Most tools show every find at 100% or hide the score entirely. Recoverer scores each file on what's actually known: header-only match = 45%, footer-confirmed = 65%, MFT-record-backed = 75%. You can see exactly how solid each result is and decide whether to bother recovering it.

Header scoring Footer confirmation MFT record match
05 / 05
🦀
Rust Engine

Every major recovery tool — Recuva, PhotoRec, R-Studio — is written in C or C++. They silently corrupt results on edge-case sectors more often than their authors realize. Recoverer's engine is Rust: single binary, no runtime, memory safety enforced at compile time. That whole class of bug doesn't exist here.

Memory-safe by design Single binary No runtime deps
03
How it works

Scan. Identify.
Recover once.

01
Pick your scan mode

Quick scan reads the MFT — recently deleted files, 2–5 minutes. Deep scan adds raw sector carving for older deletions. Raw carve only scans every sector — use when the MFT is gone or the drive was formatted.

02
Review with context

Results are grouped by type with fragment chains collapsed into single entries. Confidence scores tell you which files are solid finds and which are partial. Previously-recovered files are pre-marked so you can filter them out immediately.

03
Recover in one pass

Select files and pick a destination. Recoverer reads each fragment chain as a single contiguous span — no repeated disk thrash. The session is saved so if you need to go deeper later, you pick up exactly where you left off.

04
Comparison

Against the field.

Feature
Recoverer
Recuva / PhotoRec
Fragment chain detection
Span-based recovery (single pass)
Cross-session recovery memory
Honest per-file confidence scoring
Partial
Persistent scan sessions
Memory-safe engine (Rust)
✕ (C/C++)
Native WinUI 3 interface
Open source
PhotoRec only
Engine
Rust
UI Framework
WinUI 3
Session storage
SQLite
IPC
Named Pipe
Read chunk size
32 MB
Platform
Windows 10+
Open Source · MIT License

Your files are still
there. Probably.

The sooner you act, the better the odds. Stop writing new data to the drive and start a scan.

Get Recoverer Download release →

Questions, bugs, or feedback — [email protected]