PhotoRec Free Download for Windows PC

PhotoRec is a file recovery tool that scans storage media for known file signatures, then rebuilds what it finds into usable files. It was built for situations where the normal file system no longer works: accidental deletion, a corrupted partition, a formatted SD card, or a drive that simply stopped mounting.

The name suggests photos, but the tool handles far more than images. The official documentation lists over 480 file extensions across roughly 300 file families, covering office documents, compressed archives, audio clips, video files, raw camera formats, and database exports. Recovery depends entirely on whether the original data blocks are still physically present on the media. If new files have already overwritten those blocks, no tool can bring them back.

PhotoRec reads the source disk in read-only mode during the scan, which means it does not write to the drive it is analyzing. Recovered files go to a separate destination you choose before starting. That design makes it safer than tools that attempt in-place repair, especially when you are dealing with a drive that might fail mid-operation.

No. The official download is a zip archive, not a setup wizard. Inside the zip you get several executables: photorec_win.exe (command-line interface), qphotorec_win.exe (graphical interface), and the TestDisk binaries. Extract the archive to any folder, then run whichever executable you need. No registry entries, no start menu shortcuts, no uninstaller required.

This portable design is actually an advantage for recovery work. You can put the extracted folder on a USB stick and carry it between machines without installing anything on the damaged system. Many data recovery professionals prefer portable tools because installing software onto a drive you want to scan risks overwriting the deleted files you are trying to recover.

If you want a quick way to launch it, just create a desktop shortcut to photorec_win.exe or qphotorec_win.exe yourself. Run it as administrator if you need access to physical drives rather than just partitions.

PhotoRec is the command-line, keyboard-driven interface. It gives you full control over partition selection, file system hints, file family filters, and scan mode (free space only vs. whole partition). If you are comfortable navigating menus with arrow keys, this is the more flexible option.

QPhotoRec is the graphical frontend that ships in the same package. It wraps the same recovery engine in a point-and-click window. You pick the drive, select file types from checkboxes, choose a destination folder, and click Search. It skips some of the lower-level partition controls that PhotoRec exposes.

For most home users recovering photos from an SD card or files from a USB drive, QPhotoRec is the easier starting point. For technicians who need precise partition control or who run recovery from a live Linux environment without a desktop, the command-line PhotoRec is the better pick. Both produce identical recovery results because the file carving engine is the same.

Yes. The current 64-bit Windows build works on Windows 11, Windows 10, Windows 8.1, Windows 8, Windows 7, Windows Vista, and the corresponding Windows Server editions (2022, 2019, 2016, 2012, 2008). A separate 32-bit build is available for older machines that cannot run 64-bit software, with a minimum requirement of Windows Vista or Windows Server 2008.

In practice, any machine running Windows 7 or later should work without issues. If you are on Windows XP or something even older, check the CGSecurity download page for legacy builds or consider booting from a Linux live USB instead. PhotoRec on Linux has fewer compatibility concerns with aging hardware.

Right-click photorec_win.exe (or qphotorec_win.exe) and select “Run as administrator.” Without admin rights, PhotoRec can only see logical drive letters. With admin rights, it can also access physical disks directly, which matters when a partition is damaged or missing from the drive letter list.

If you are scanning an external USB drive or SD card, admin access also ensures PhotoRec can read every sector rather than being blocked by permission restrictions. On Windows 11, you may get a SmartScreen warning the first time because the executable is not code-signed by Microsoft. Click “More info” then “Run anyway” to proceed. The file is safe as long as you downloaded it from the official CGSecurity source.

The official documentation lists more than 480 file extensions grouped into about 300 file families. That covers the common categories most people need:

• Images: JPEG, PNG, GIF, BMP, TIFF, RAW formats from Canon (CR2/CR3), Nikon (NEF), Sony (ARW), and others
• Documents: PDF, DOCX, XLSX, PPTX, ODT, TXT, RTF
• Archives: ZIP, RAR, 7Z, TAR, GZ
• Audio: MP3, FLAC, WAV, AAC, OGG
• Video: MP4, AVI, MOV, MKV, WMV
• Database and misc: SQLite, PST (Outlook), EML, and various system file formats

Recovery success depends on whether the file data is still physically on the disk. If the operating system already wrote new data over those sectors, the file is gone regardless of the tool you use. That is why the single best thing you can do after data loss is stop using the affected drive immediately.

It works on all of those, but results vary by device type. Traditional hard drives (HDDs) tend to give the best recovery rates because deleted data stays on the platters until something else writes over it.

SSDs are trickier. Most modern SSDs run a background process called TRIM that tells the drive to erase deleted blocks for performance. Once TRIM runs, those blocks are zeroed out and no recovery tool can bring them back. If you catch the deletion quickly (before the next TRIM cycle), recovery is possible. On some SSDs with TRIM disabled or on encrypted drives, results can be unpredictable.

USB flash drives and SD cards are the most common recovery targets. They typically do not run TRIM, so deleted files tend to stick around until overwritten by new data. PhotoRec works well here, especially for camera cards where the file format is consistent (mostly JPEG and RAW).

For any storage media: the less you use the device after data loss, the better your chances. Eject it, set it aside, and run PhotoRec from a different computer if possible.

PhotoRec is documented to work with FAT12, FAT16, FAT32, exFAT, NTFS, ext2, ext3, ext4, HFS+, and ReiserFS. But here is the thing that makes PhotoRec different from most recovery tools: it does not depend on the file system being intact.

Most undelete utilities read the file system metadata to find deleted file entries. When the file system itself is corrupted, those tools fail. PhotoRec skips the file system entirely and reads raw data blocks, looking for known file headers (the “signature” in “signature-based recovery”). That means it can recover files even when the partition table is damaged, the filesystem is unrecognizable, or the drive was reformatted with a different filesystem than the original.

During setup, PhotoRec asks you to choose between “ext2/ext3/ext4” and “Other” as a filesystem hint. If you know the drive was formatted as ext4 (Linux), pick that option. For everything else (NTFS, FAT, exFAT, HFS+, or anything you are not sure about), pick “Other.” The hint helps PhotoRec optimize its scan but is not strictly required for recovery to work.

In many cases, yes. Formatting a drive usually erases the directory structure but does not immediately overwrite every data block. A “quick format” on Windows, for example, just clears the file allocation table. The actual file contents remain on the disk until new data takes their place. PhotoRec can scan those leftover blocks and pull out whatever it recognizes.

A full format is harder because some operating systems write zeros across the drive. If you did a full format on a modern version of Windows, recovery rates drop significantly. On older Windows versions or on Linux (where mkfs does not zero the entire drive by default), a full format often leaves data recoverable.

For corrupted partitions where the filesystem metadata is damaged but the drive still spins, PhotoRec is one of the better options. It does not need a working directory tree. The tradeoff is that you lose original file names and folder structure. Recovered files come out with generic numbered names, sorted into folders by type. You will need to manually sort through the results to find what you need.

This is the most common complaint, and it is actually by design. PhotoRec recovers files by reading raw data blocks and matching them against known file signatures (headers and footers). It does not rely on the original directory structure, which means it has no way to know what the file was called or which folder it lived in.

Recovered files get numbered names like f0012345.jpg and are sorted into folders (recup_dir.1, recup_dir.2, etc.) based on when they were found during the scan. Each folder typically holds around 500 files before a new one is created.

To make sense of the output, sort by file type first, then by date modified or file size. For photos, most image viewers can display thumbnails so you can visually scan through the results. For documents, the file content is intact even if the name is gone, so you can open them and check the contents manually. Some users run a batch renaming tool afterward to organize recovered files by EXIF date, creation timestamp, or file hash.

Always save to a different physical disk or partition. This is the single most important rule in data recovery, and the one people break most often.

If you write recovered files back to the same drive you are scanning, you risk overwriting the deleted data that has not been carved yet. PhotoRec reads the source in a sequential pass. If your destination folder sits on the same drive, the act of writing recovered files creates new data that can land on top of blocks PhotoRec has not scanned yet. The result: partial recoveries, corrupted files, or files that simply disappear mid-scan.

Good destination options: a second internal hard drive, an external USB drive, a network share, or a different partition on a separate physical disk. Make sure the destination has more free space than you expect to recover. PhotoRec will write everything it finds, including fragments and false positives, so the output is often larger than the data you actually need.

Yes, and you probably should. Before starting a scan in PhotoRec, open the File Opt screen. It shows a list of every file family the tool can recognize. By default, all families are enabled. You can toggle individual families on or off with the spacebar.

Narrowing the list helps in two ways. First, the scan produces fewer results to sort through. If you only need JPEG photos from an SD card, there is no reason to also recover ZIP archives, MP3 audio, and PDF documents from the same scan. Second, a focused scan can run faster because PhotoRec spends less time matching against signatures you do not care about.

A practical approach: run one focused pass for the file types you need most (photos, for example), review those results, then run a second pass for other types if needed. This keeps each batch of recovered files manageable instead of dumping everything into one massive pile.

This usually means one of three things: the drive has been heavily reused since the deletion, you left too many file families enabled, or you scanned the whole partition when free-space-only would have been enough.

Start troubleshooting by checking your scan settings. Open File Opt and disable file families you do not need. If you only want photos, turn off everything except image formats. Next, confirm you selected the correct partition. Scanning the wrong partition is more common than people admit, especially on drives with multiple volumes.

If the problem is genuinely too many false positives (files that recover but are corrupted or partial), that points to heavy reuse of the disk. When new data has been written over old blocks, PhotoRec still finds partial file headers and tries to rebuild them. The resulting files might be technically valid but contain garbage data. You can reduce this noise by limiting your scan to free space only, which skips sectors currently in use by the file system.

After recovery, sort the output by file size. Files under 1 KB are usually fragments. Files that are exactly the expected size for their type (like a standard JPEG) are more likely to be intact. A quick preview pass through the results saves time compared to opening every file individually.

It depends on the size of the drive, the connection speed, and how many file types you are scanning for. A 32 GB SD card over USB 3.0 usually finishes in 10-30 minutes. A 500 GB external hard drive can take 2-4 hours. A 2 TB internal HDD might run for 6-12 hours or more.

SSDs tend to scan faster than spinning hard drives because they have no physical seek time. USB 2.0 connections are noticeably slower than USB 3.0 for the same drive. If your scan is taking much longer than expected, check your USB port version and try connecting the drive directly rather than through a hub.

You can safely leave PhotoRec running overnight. It does not need user interaction during the scan. If you need to stop early, pressing the quit key saves progress, and some partial results will already be in the output folder. But a complete scan gives the best results, so let it finish if possible.

Yes on both counts. PhotoRec is open source under the GNU GPL v2 or later, which means there is no trial version, no recovery cap, and no paid unlock hiding the actual functionality. The full recovery engine is available from the first run.

On the safety side, PhotoRec scans the source drive in read-only mode. It does not modify, repair, or write anything to the disk being analyzed. All recovered files go to a separate destination folder you choose before the scan starts. This read-only approach makes it one of the safer recovery tools available because there is no risk of the tool itself making things worse on the damaged drive.

The one safety consideration is where you get the software. Always download from the official CGSecurity website. Third-party download sites sometimes bundle PhotoRec with adware installers or outdated versions. The official package is a clean zip file with no bundled extras.

Yes. Official packages are available for Linux (x86_64, kernel 2.6.18+), macOS (Intel 64-bit, with Apple Silicon support through Rosetta), FreeBSD, NetBSD, OpenBSD, and Solaris. Many Linux distributions also include PhotoRec in their package repositories, so you can install it with your package manager (apt, dnf, pacman) rather than downloading the archive manually.

On Linux, running PhotoRec with sudo gives you access to physical drives (/dev/sda, /dev/nvme0n1, etc.). On macOS, you may need to grant Terminal full disk access in System Settings before PhotoRec can see all attached volumes. The macOS Gatekeeper may also block the first launch since the binary is not notarized by Apple. Right-click the executable and choose “Open” to bypass that warning.

For emergency recovery from a dead system, many Linux live USB distributions (like SystemRescue or Ubuntu live) include PhotoRec or let you install it on the fly. Booting from a live USB avoids mounting the damaged drive’s partitions, which is exactly what you want during recovery.

They solve different problems, which is why CGSecurity ships them together in the same package.

TestDisk repairs partition tables, rebuilds boot sectors, and restores filesystem structures. If your drive is not showing up in Windows or a partition disappeared, TestDisk can often fix the issue without losing data. It works at the partition and filesystem level.

PhotoRec recovers individual files by signature. When the filesystem is too damaged for TestDisk to repair, or when the files were deleted and the directory entries are gone, PhotoRec can still pull files off the raw disk. It works at the data block level.

A common recovery workflow: try TestDisk first to see if the partition structure can be repaired. If that works, your files come back with their original names and folders intact. If TestDisk cannot fix the partition, switch to PhotoRec to extract whatever files it can find by signature. You lose file names and folder structure, but you keep the actual file content.

Sometimes, depending on what you value. Paid recovery tools like R-Studio, Disk Drill, or EaseUS Data Recovery often include features that PhotoRec does not: file preview before recovery, original file name preservation (when the filesystem metadata is partially intact), RAID reconstruction, disk imaging with bad-sector handling, and visual interfaces with progress indicators.

PhotoRec is stronger on raw file carving. When the filesystem is completely gone and you just need to pull files off a dead drive, PhotoRec often recovers more file types than consumer-grade paid tools because its signature database is large and the carving engine is mature.

For home users recovering vacation photos from an SD card, PhotoRec is hard to beat because it costs nothing and the recovery is straightforward. For corporate environments where you need chain-of-custody documentation, RAID support, or the ability to preview files before committing to recovery, a paid tool may justify its price. The best approach for critical data: try PhotoRec first (it is free and read-only), then consider a paid tool if the results are incomplete.

The current stable release is PhotoRec 7.2, published on February 22, 2024. This is the version included in the download links on this page.

A beta version labeled 7.3-WIP (work in progress) is also available on the official CGSecurity download page. The beta includes newer file signature updates and bug fixes that have not yet been promoted to a stable release. For most users, the stable 7.2 build is the safer choice. If you are dealing with a newer file format that 7.2 does not recognize, or you hit a bug during scanning, trying the 7.3-WIP beta is worth a shot.

Check the CGSecurity download page directly if version accuracy matters for a forensic case or a time-sensitive recovery job. Version numbers in the archive file name (testdisk-7.2.win64.zip, for example) confirm exactly what you are getting.