what_you_need
Prepare the inputs before opening the apps
- A clearly bounded folder to scan
- A current backup or safe working copy
- Rules for choosing the canonical path
- Time to review duplicate groups
step_by_step
The working process
-
1
Set a safe scan boundary
Choose the project or collection that actually needs review instead of treating the entire drive as one cleanup problem. Verify that important data is backed up.
-
2
Scan for exact matches
Use Batch File Organiser to calculate file hashes. Matching hashes identify identical file contents even when the filenames or folder locations differ.
-
3
Review each duplicate group
Compare paths, names, dates, and project context. A duplicate in a backup or delivery folder may be intentional even when its contents are identical.
-
4
Choose the canonical copy deliberately
Decide which location and filename belong in the working structure. Do not assume the newest, shortest-named, or first-listed copy is automatically correct.
-
5
Preview the proposed operation
Inspect the complete plan before moving or reorganising files. Separate duplicate decisions from unrelated folder cleanup when that keeps the action easier to understand.
-
6
Verify while undo context is clear
After applying an approved operation, open representative files and confirm the expected paths. Use undo promptly if the result does not match the preview.
human_checkpoint
Review before you call it finished
- Was the scan scope intentionally bounded?
- Is there a backup or safe working copy?
- Were intentional backup and delivery duplicates recognised?
- Was every canonical path chosen by a person?
honest_boundaries
Limits and privacy
Practical limitation
Hash equality proves that file contents are identical; it does not decide which copy belongs in the archive, whether redundancy is intentional, or which different edit is best.
Privacy boundary
File scanning, hashing, preview, organisation, and undo information remain on the Windows machine.
faq
Questions worth answering
Can two files with different names be exact duplicates?
Yes. Hash comparison uses the file contents rather than the filename.
Does a matching hash mean I should delete one copy?
Not automatically. Backup, delivery, or project-folder duplicates can be intentional; review the paths before deciding.