Back to Blog

Disk Usage Triage Before Duplicate Cleanup

Find space hogs first, then scan hotspots for duplicates: a two-step workflow WizTree and WinDirStat users rarely get in one app.

Running a duplicate scan on the entire D:\ drive works. It is also slow, noisy, and hard to review. Most recoverable space sits in a few heavy folders: video exports, old VM images, photo backups, npm caches.

Disk usage tools show where space goes. Duplicate scanners show what repeats. Run them in that order.

Step 1: Map the tree

DupeZappa Disk Usage provides a size-ranked hierarchical view:

  • Configurable traversal depth and top-children limits.
  • Scan exclusions from Settings (skip node_modules, system dirs).
  • Toggle file visibility to focus on folder hotspots.
  • Summary metrics: total size, file count, directory count.

WizTree and WinDirStat are strong at this step too. The difference is what you do next without switching apps.

Step 2: Target duplicate scans

From the disk map, pick one or two folders worth more than the review time:

Open Duplicate Scanner on that subtree only. Resolve the largest groups first for the best GB per minute of review.

Why order matters

Duplicate scanning every small file on a 4 TB drive wastes IO. Disk triage answers:

  1. Is the problem duplication or single huge files? VM disks and ISOs may dominate without any duplicate groups.
  2. Which subtree owners should approve deletes? Shared NAS folders need different rules than personal Downloads.
  3. Are exclusions configured? Skip caches you will regenerate anyway.

WinDirStat's treemap and WizTree's MFT speed do not show duplicate overlap. DupeZappa keeps disk triage and dedup in one preview-first app so you do not switch tools between steps.

Pair with junk cleanup

Zero-byte files and corrupt images rarely show up as duplicate groups but still consume attention in large trees. After disk triage, run Junk & Corrupt Finder on the same hotspot; see Junk and Corrupt Files.

Suggested session plan

  1. Disk Usage on D:\ or \\nas\media: note top three folders by size.
  2. Duplicate scan on folder #1 only.
  3. Preview-first delete or move; undo in small batches.
  4. Re-check Disk Usage; folder size should drop.
  5. Repeat for folder #2 if payoff justifies it.

Cleanup is a prioritization problem before it is a hashing problem.

Related reading