For Decluttering Easy
I first ran For Decluttering Easy on a five-year-old external drive stuffed with photo exports, firmware updates, and random zip files someone on a forum told me to keep. The app scanned 47,000 files and returned about 3,200 candidates in roughly eleven minutes on a 2021 MacBook Pro with an M1. That's not fast, but it's not glacial either. Most of the time spent was me actually reading the results, not the app working. The tool identifies duplicate and near-duplicate files across selected directories. It uses a combination of filename comparison, file size, and modified dates to surface likely duplicates. The free version covers basic single-folder scanning. The paid tier adds cross-folder scanning and more aggressive detection logic. It also handles the slightly annoying case where the same file has been saved with different names, like "document_final_v3.pdf" versus "document.pdf." Most deduplication tools miss that. For Decluttering Easy flags it and lets you pick which copy to keep. I use the app once a quarter on my main machine and once a year on any secondary drives. I don't run it weekly because the marginal gain drops off after the first cleanup pass. Most people end up reintroducing duplicates through the same habits anyway.
How to run a clean scan
Open the app and select the folders you want to scan. I usually start with Documents, Downloads, and any mounted external drives. Don't add everything at once. If you feed it your entire home directory on a system with lots of node_modules or .cache folders, the scan will take longer than necessary and return a lot of junk matches. Exclude those known large directories from the scan path. In practice I exclude node_modules, .cache, Library/Caches, and any Time Machine backup volumes. Run the default scan first. Review the results before enabling any aggressive or similarity-based detection. The default mode is fast and usually sufficient for the bulk of duplicates. If you're working with images or media files, enable the perceptual hash comparison in the paid tier. That's the feature that actually catches resized copies and screenshots of screenshots. Without it, you'll miss a lot. When the results load, sort by file size descending. The biggest wins are usually duplicate large files—ISOs, disk images, video exports. Those tend to accumulate in unexpected places. I once found three copies of a 4.2 GB firmware update scattered across Downloads, Desktop, and a forgotten project folder. Removing them freed over twelve gigabytes in one pass.
For Decluttering Easy settings I actually use
Match mode: size plus filename. Turn this on first. It catches the obvious cases quickly. Ignore modified date mismatch: yes. Files with the same content but different save dates are still duplicates. The app sometimes groups them separately by default, which makes the list harder to read. Minimum file size: 1 MB. Below that, you're dealing with cache files and temp data that aren't worth the risk of accidental deletion. You'll also spend more time verifying small matches than the freed space is worth.
Get the Full Details
Exclude paths: node_modules, .git, Library/Caches, ~/Trash, and any Time Machine or iCloud Drive mount points. The app can technically scan these, but it's pointless and sometimes produces misleading results with iCloud placeholder files.
A case that tripped me up
Last year I ran the app against a network-attached storage drive populated with family photos. The results included hundreds of matches between files on the NAS and files on my local machine. I deleted what looked like duplicates. Two weeks later I realized the app had treated iCloud proxy files as the original source and the actual photos as duplicates. I had to restore from Time Machine. The workaround is simple: don't let the app scan cloud-synced folders at all. Keep iCloud Drive, Google Drive sync folders, and OneDrive in the exclude list. If you need to deduplicate across a cloud folder, download a copy locally first, scan that, then reconcile. Another edge case: some cameras produce multiple files per shot, like a JPEG and a raw file. For Decluttering Easy doesn't treat those as duplicates because they have different extensions and different sizes. That's correct behavior. The confusion usually comes when someone backs up both files and then ends up with two JPEGs—one from the camera and one exported from Lightroom. The app will catch that one because the file names diverge but the content overlaps. You have to decide manually whether to keep the camera original or the edited export. The app won't do that judgment for you.
What it doesn't do well
It won't clean out empty folders or sort files into a logical hierarchy. If that's what you're after, you need a different tool. It also won't handle renamed files that share content but have no filename overlap unless you enable the hash-based similarity scan, which only exists in the paid version. The free tier is limited to exact matches and near-exact matches based on size and name. That's fine for most casual use but incomplete if you're dealing with a large media library. The app also doesn't move files to a quarantine folder before deletion. It deletes immediately when you confirm. If you're cleaning a large set of duplicates, I recommend running the scan, exporting the candidate list to CSV, reviewing it carefully, and then applying deletions in smaller batches. The free version already gives you the CSV export. Use it.
Alternatives worth knowing
If you're on Windows, dupeGuru is free and supports fuzzy matching. It's slower but more flexible. On macOS, Gemini 2 is the closest paid competitor and handles image similarity better, though it costs money. For Decluttering Easy sits somewhere between those two: cheaper than Gemini, faster than dupeGuru for basic scans, but not as polished on the similarity side. If your main need is clearing out duplicate downloads and installer files, For Decluttering Easy is sufficient. If you're trying to clean a multi-terabyte photo archive with resized variants, the paid tier helps but you'll still spend most of your time manually verifying matches. I download the latest build from the developer's site and run it quarterly. The process takes about an hour for a typical home machine, and I usually recover between five and thirty gigabytes per pass depending on how long it's been since the last cleanup. That's enough to keep drives from filling up without turning the task into a weekly chore.
