How to remove duplicate downloads with Downloads Detective

1. Why cleaning Downloads by filename is mostly guesswork

The normal approach is to open Downloads in File Explorer, sort by name or date, and decide that files with names such as report (1).pdf are probably duplicates.

That is useful for spotting clutter, but it cannot answer the most important question: are the contents actually identical? A website can publish a changed file tomorrow under exactly the same original filename, causing the browser to create another numbered copy.

2. Open Downloads Detective and let it scan the folder automatically

Downloads Detective opens on the current Downloads folder and scans it automatically. Normal mode is the everyday package-aware view; Deep mode exposes more nested-file duplicate detail when you need forensic inspection.

The Review workflow keeps strong cleanup opportunities separate from findings that still require judgement.

3. Use Filename variants to find the obvious “(1), (2), (3)” families

The Filename variants tab groups browser-style families such as:

• report.pdf
• report (1).pdf
• report (2).pdf
• report (3).pdf

This is faster than visually scanning a long Downloads folder, but Downloads Detective deliberately does not call the family an exact duplicate just because the names match.

4. Let content verification separate duplicates from lookalikes

Exact duplicate files and folders use content checks including SHA-256 verification. Folder packages can be recognised even when an outer folder was copied or renamed.

Near-duplicate and contained-folder relationships stay review-only when differences may matter. That is a major advantage over cleanup tools or manual workflows that reduce everything to “same-looking name” or “same size”.

• Verified evidence: content supports an exact relationship.
• Review evidence: useful similarity or containment exists, but Downloads Detective does not claim it is safe to remove.

5. Find the clutter that a simple duplicate-file list misses

Downloads folders accumulate packages, not just loose duplicate files. Downloads Detective recognises several higher-level patterns:

• ZIP + extracted folder: a same-stem ZIP can be compared against its extracted folder by relative path, size and SHA-256. If every meaningful file matches, the archive becomes a confirmed cleanup signal.
• Copied folders: an exact copied folder tree can be represented as one package finding instead of thousands of repetitive internal duplicates.
• Installer families: version-looking installers are grouped so older/newer candidates are easy to review, while architecture stays part of the family identity.
• Stale incomplete downloads: strong stale-download signals can contribute to potential cleanup.

This makes the result list more useful than a simple “duplicate filenames” view because it explains why the clutter exists.

6. Re-verify confirmed duplicates immediately before recycling

When you clean a confirmed duplicate group, choose the copy to keep. Full byte-for-byte re-verification is the recommended default immediately before the Recycle Bin action.

A faster tree/size safety check is available for very large items, but only as an explicit trade-off because a same-size content change could be missed.

7. Stop “(1), (2), (3)” files from becoming normal

Basic cleanup solves yesterday's mess. Downloads Detective also includes a Naming Assistant designed to reduce tomorrow's.

• Ask Once: choose the target filename the first time a repeated browser filename family appears; later copies can reuse that remembered decision.
• Auto Replace: repeated browser-style names can target the clean filename automatically.

Previous targets are staged for rollback and sent to the Recycle Bin only after the new replacement succeeds.

8. Add the Browser Companion for website-aware rules

The optional Chrome/Edge Browser Companion can choose the clean filename before the browser commits the download. Ask Once rules can be website-aware, so the same generic filename from different sites does not have to share one blind global rule.

It also provides Move original… for completed browser downloads, moving the actual downloaded file out of Downloads instead of leaving a second copy behind.

Browser Companion information used for these local rules is not uploaded to Friction Tamer.