Recovery
Hard disk and SSD HDD, SSD, external drives, flash cards RAID, NAS & SAN All levels, all controllers, virtualisation Smartphones and tablets iPhone, Android, iPad, Huawei Tapes LTO, DAT, DLT and older formats
Access after signing in.
EN · RU · ZH · ES
Software
Deleted files or a formatted drive: with Recover you get your data back yourself. Free, without limits, for Windows, macOS and Linux. The source drive is only read, never written to.
Recover is Datarecuperatie software for getting files back from hard drives, SSDs, USB sticks, memory cards, RAID sets and disk images. It is meant for logical problems: files that were deleted, or a drive that was formatted.
The most important rule is built into the software: the source drive is only ever read. You always write recovered files to a different drive.
A scan reads the entire surface of the drive. With a mechanical or electronic fault, that can cause exactly the damage that makes data unrecoverable. That is why Recover explicitly asks, before every scan, whether the drive is physically sound.
If the drive clicks, ticks or grinds, disappears and comes back, gets very hot, or has been dropped, opened or water damaged, stop right away and have it checked by a lab. If the drive is healthy and the problem is logical, you can continue. Safer still is to make a disk image first and work from that: Recover offers that choice straight away.
Read partitions and the file system, find deleted files and filter them: deleted only, hide unrecoverable, everything in one list, or supplemented from the search index. Recover per file, per folder or the whole list.
Where the file system knows nothing any more, Recover looks for files by their recognisable start and structure (file carving): 334 formats, more than 560 extensions, from photos and documents to databases, video and mail archives.
Make a full copy of the drive and continue working on that, so the original drive is stressed as little as possible. Recover also opens existing image files.
During a scan, Recover reads the file system structures, such as the Master File Table (MFT) on NTFS, and shows the records of deleted files alongside the existing ones. Whether a deleted file can still be fully recovered depends on whether the location of its data is still known and has not been overwritten.
File carving works without a file system: it searches the drive for known file headers and structures. That way it finds files after heavy damage or formatting, but without their original name or folder.
The search indexes of Windows, macOS and Linux keep file names and paths in their own databases. Recover reads those databases and uses them to rebuild the folder structure.
| File system | Where you find it | Deleted files |
|---|---|---|
| FAT12, FAT16, FAT32 | USB sticks, memory cards | yes, with long names |
| exFAT | memory cards, external drives | yes |
| NTFS | Windows | yes, also fragmented and whole folders |
| ext2 | older Linux | yes |
| ext3, ext4 | Linux, many NAS devices | name only |
| XFS | Linux servers, NAS | no |
| Btrfs | Linux, Synology | not yet |
| HFS+ | older macOS | yes |
| APFS | macOS | not yet |
| ReFS | Windows Server, Storage Spaces | folders and names; deleted files not yet |
Partition tables: GPT (also with 4K sectors), MBR with logical partitions, or no table. Compressed NTFS files are flagged but not yet decompressed.
Recover reports to Datarecuperatie which kind of drive is used and which functions are used. File names, paths and file contents are never sent. That is also stated at the top of the software window.
In the settings you see exactly what a report looks like before it is sent. Including the drive serial number is a separate choice, and reporting can be switched off completely.
There is more free recovery software, and each program has its strong points. This table puts the free versions side by side, as downloadable in September 2026. Where Recover falls short, it says so.
| Feature | Recover | Recuva Free | TestDisk / PhotoRec | DMDE Free | R-Studio Demo | UFS Explorer trial |
|---|---|---|---|---|---|---|
| Price and limit | free, no limit | free, personal use only | free, open source | free, personal use; 4,000 files at a time, from the open folder | free; files up to 256 KB | free; files up to 256 KB or 768 KB |
| Platforms | Windows, macOS, Linux | Windows | all | all | all | all |
| File systems with folders and names | 9 | 3 | 4 (undelete) | 5 | 10+ | 15+ |
| Content search (carving) | 334 formats, 560+ extensions | limited | 480+ families | ✅ | ✅ | ✅ |
| Search indexes (Windows, Spotlight, Tracker) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ |
| SMART: refuses a failing drive | ✅ | ❌ | ❌ | ❌ | shows | shows |
| Condition per deleted file | ✅ intact / partly / overwritten | estimate | ❌ | ❌ | ✅ | ✅ |
| Preview | image + hex | limited | ❌ | hex | ✅ | ✅ |
| Disk imaging | ✅ | ❌ | ✅ | ✅ | ✅ | ✅ |
| Virtual disks | VHD, VHDX, VMDK, QCOW2, VDI, DMG | ❌ | ✅ | ✅ | ✅ | ✅ |
| E01 (forensic images) | ✅ incl. compressed | ❌ | ✅ | ✅ | ✅ | ✅ |
| RAID assembly | ✅ 0, 1, 5, 6, 10, JBOD, reads RAID metadata | ❌ | ❌ | ✅ | ✅ | RAID edition |
| Encrypted volumes | ❌ | ❌ | ❌ | partly | ✅ | ✅ |
| Lost partition search | ❌ | ❌ | ✅ strongest | ✅ | ✅ | ✅ |
| Multithreading | ✅ dynamic, based on drive condition | ❌ | ❌ | partly | ✅ | ✅ |
| Command line | ✅ complete | ❌ | ✅ | limited | limited | ❌ |
| Languages | 12 complete, 98 known | 30+ | English | several | several | several |
| Dates on recovered files | ❌ shown, not applied | ✅ | ✅ | ✅ | ✅ | ✅ |
Search indexes: Windows Search, Spotlight and Tracker remember the names and folders of files. Recover reads those databases and puts the files back in their original place, even when the file system has forgotten them.
SMART: the drive keeps track of its own health. Recover reads it and refuses to scan a drive that is failing, because long reads damage a sick drive further. "Shows" means the program displays the values but carries on anyway.
Data on other programs from their own websites, September 2026. The free or demo version counts, not the paid one.
Software helps with logical problems. With a physical fault it does more harm than good. Have the drive checked in these cases:
Recover is free, for Windows, macOS and Linux. Choose the version for your system.
Right-click the file and choose "Run as administrator".
Make the file executable first (chmod +x), then start it with sudo -E.
Do not install Recover on the drive you want to recover data from, and always write recovered files to a different drive.
To read physical drives, Recover needs elevated rights: administrator on Windows, root on macOS and Linux. Without them you see no drives, only image files.
Right-click Recover-gui.exe and choose "Run as administrator". The UAC prompt appears anyway, because Recover requests elevated rights itself. Without them you see no physical drives.
Command line: first open an administrator prompt (right-click Windows Terminal or cmd, "Run as administrator"), then:
recover-cli.exe devices
recover-cli.exe info \\.\PhysicalDrive1
recover-cli.exe ls \\.\PhysicalDrive1 --deleted
Drive names: \\.\PhysicalDrive0, \\.\PhysicalDrive1, … for whole drives, \\.\E: for a single volume.
Once, beforehand: give Terminal Full Disk Access (System Settings → Privacy & Security → Full Disk Access) and restart Terminal. Then start Recover from Terminal:
sudo /Applications/Recover.app/Contents/MacOS/Recover
Before scanning: find the drive and unmount it.
diskutil list
diskutil unmountDisk /dev/disk2
sudo ./recover info /dev/rdisk2 # command line
Do not double-click and do not use "sudo open -a": the app would then run as your user and the drive list stays empty. Keep Terminal open while the app runs.
Choose /dev/rdisk2, with the r: that is the raw device, which reads much faster.
chmod +x Recover-gui-linux recover-cli-linux-static # once after download
sudo -E ./Recover-gui-linux # -E keeps your DISPLAY
sudo ./recover-cli-linux-static info /dev/sdb
Without -E the graphical version may not start, because root does not know your graphical session. Alternative without sudo: add your user to the disk group (sudo usermod -aG disk $USER), then log in again.
Drive names: /dev/sda, /dev/nvme0n1 for whole drives, /dev/sda1 for a single partition.
Images need no elevated rights. If you work on an .img file, simply double-clicking or starting without sudo is enough.
The recommended way remains: first make an image (Disk image tab, or from the command line), then work on that file. Every scan then reads the healthy copy instead of stressing the drive again.
recover image /dev/sdb copy.img
Always recover to a different drive than the original.
When Recover runs as root, the settings (including usage reporting) end up in root's home folder: /var/root/.config/recover/ on macOS, /root/.config/recover/ on Linux, and %APPDATA% of the elevated account on Windows. What you set in the menu therefore applies to the sessions you actually work in, but not to a start without elevated rights.
Handy to set up on macOS and Linux:
echo 'alias recover-gui="sudo /Applications/Recover.app/Contents/MacOS/Recover"' >> ~/.zshrc # macOS
echo 'alias recover-gui="sudo -E /path/to/Recover-gui-linux"' >> ~/.bashrc # Linux For Windows, macOS and Linux. If your drive is physically failing, or the risk is too high, request a free analysis.
Questions about your drive? An engineer is reading.