Notes from NestFiles

Similar photos, audio, and video are now reviewable

Exact duplicates were never the whole picture — a resized photo, a re-encoded song, or a trimmed video clip can still be the same content in spirit. NestFiles now has a separate, opt-in mode that flags these near-matches using perceptual image comparison, audio fingerprinting, and video keyframe matching. It's review-only: nothing found this way is ever auto-selected, quarantined, or deleted.

In our own testing against Czkawka on a small corpus, NestFiles caught 100% of true audio-duplicate pairs versus roughly half for Czkawka; photo results were close, and video matches were equal in count though Czkawka ran faster. Small test sets — read as a data point, not a general claim.

Duplicates hiding inside ZIP, 7z, and RAR archives

Downloads and backup folders tend to accumulate archives, and duplicates can hide inside them just as easily as outside. NestFiles can now look inside ZIP, 7z, and RAR files to find exact-match entries without extracting them to disk. It's a read-only inspection for now — it tells you what's duplicated inside an archive, but quarantine and delete actions on archive contents aren't offered yet.

How NestFiles compares to Czkawka, with real numbers

We publish an honest, numbers-included comparison against Czkawka rather than a vague "we're better" claim. On a 200,120-file benchmark, Czkawka finished about 2.5x faster on a cold cache and about 3x faster warm — we don't hide that. What we optimize for instead is the moment after the scan: preview, reversible quarantine, and restore. Read the full comparison for the complete picture, including where each tool wins.

How to clean up duplicate files without losing something you needed

Most duplicate-finder guides jump straight to “scan and delete.” That's how people lose a file they meant to keep. A few habits make duplicate cleanup safe, regardless of which tool you use.

Back up before a big cleanup. Even a reversible tool can't undo a mistake made outside it — an external drive or cloud copy is five minutes of insurance for a folder you've never sorted before.

Know the difference between exact and similar duplicates. A byte-for-byte match is safe to remove automatically; a resized photo or re-encoded song only looks like a duplicate. Treat them as two different decisions, not one.

Preview before you delete anything. If a tool can't show you what it found before it acts, you're trusting its judgment over yours.

Delete in two steps, not one. A quarantine or recycle step between “selected” and “gone forever” catches the one file a rule matched by accident.

Start with your safest folder. Downloads and old backups are usually full of true duplicates; photo libraries usually aren't — start where a mistake costs the least.

This is the same order NestFiles follows internally: preview, quarantine, then delete.

Where duplicate files actually come from

Duplicates rarely happen on purpose. They build up from a handful of everyday habits, and recognizing the pattern makes them easier to prevent going forward.

Camera uploads syncing more than once. A phone connected to two backup services, or reconnected after a sync failure, often re-uploads photos that were already saved — sometimes under a slightly different filename.

Downloads folder as a holding pen. Files get downloaded again "just in case" the original got moved, and the Downloads folder rarely gets cleared once something has been used.

Manual backups layered on top of automatic ones. A folder copied to an external drive "to be safe," on top of a cloud sync that's already covering it, doubles every file it touches.

Renaming instead of moving. Saving a new version as "report_final_v2" next to "report_final" keeps both around — technically different filenames, often identical or near-identical content.

Shared folders with multiple contributors. The same photo saved by two people who both downloaded it from a group chat ends up in the same folder twice, under two different names.

None of these are mistakes exactly — they're just what happens when files move between more than one device or person. The fix isn't stricter habits; it's periodically checking for exact duplicates content-first, not by filename.

A simple folder structure that prevents most duplicates

Most duplicate problems come from having more than one place a file could reasonably go. A folder structure with a single, obvious home for each type of file removes most of that ambiguity before it starts.

One inbox, not several. Downloads, phone imports, and email attachments all landing in the same "Inbox" folder means there's one place to sort from, instead of three places that might already overlap.

Sort by date once, not by project repeatedly. A top-level year/month structure for photos and documents means a file only has one correct location — sorting the same photo into both "Vacation 2026" and "July 2026" is how duplicates start.

Archive instead of re-save. When a project wraps up, move its folder to an archive location rather than copying the final files elsewhere "for easy access" — a shortcut or link does the same job without a second copy.

Empty the inbox on a schedule. Weekly or monthly, whichever is realistic — an inbox that's cleared regularly stays small enough to sort by hand; one that's ignored for a year needs a duplicate scan more than it needs willpower.

The goal isn't a perfect system — it's removing the everyday decision of "where does this go" that leads to saving the same file in two places without noticing.