Duplicate files.
A careful review.

Choose a useful scope

Start with two folders you understand, such as an export folder and a personal archive. Avoid starting with every application, Windows folder and backup drive at once. The point is to make a decision you can explain, not to maximize the number of matches.

Keep an independent backup outside the set you intend to prune. An exact copy stored elsewhere can be deliberate protection against a damaged drive.

Ask what “duplicate” means

Same name or size

A candidate worth checking. Different documents can share both.

Matching full-content hashes

Strong evidence of equal file contents at the time of reading. This does not establish that either location is redundant.

Similar-looking image

A different task: resized, cropped or edited images can look alike while containing different data. Review their resolution, edits and intended use.

The Czkawka project distinguishes name, size and hash matching from similar-image and similar-video tools. Its current README recommends Krokiet as the newer desktop interface. Choose the matching mode that answers your actual question.

Check two files yourself

For a small comparison, PowerShell can compute each file’s SHA-256 hash. Replace these example paths with the two files you want to inspect. The command reads the files; it does not delete them.

Get-FileHash -LiteralPath 'D:\Photos\photo.jpg', 'E:\Archive\photo.jpg' -Algorithm SHA256

Compare the complete Hash values. Different values mean different contents. A failed read is an error to resolve, not an empty or matching file. Content reads of cloud-only files can trigger downloads. Microsoft documents Get-FileHash and its LiteralPath option. Recheck if a file changes after the comparison.

Choose what stays

1. Check the role of each location. A project may reference a particular path. A backup may intentionally preserve another copy.
2. Open the retained file. Confirm that it is readable and is the version you intended to keep.
3. Inspect the removal selection. Keep at least the intended retained copy in each group. Review the full paths rather than relying on filenames.
4. Decide group by group. Skip ambiguous groups. There is no benefit in forcing a decision when the evidence is incomplete.

Two paths can also refer to shared filesystem data, so adding up apparent duplicate sizes can overstate the space a removal would recover.

Read the removal method

In WhimRoom 0.266, open Review matching copies, choose the relevant scope, inspect matching evidence and review the selected copies before approval. Explicit duplicate recycling uses Windows confirmation and stored-content checks. Restore recycled items through the Recycle Bin where available; recycling alone may not increase free space.

Other cleanup workflows can permanently remove files and provide no automatic backup or Undo. Read the exact confirmation and recovery explanation. After any removal, check the result and the retained files.