Back to Blog

Find Duplicate Files on a NAS or Network Drive

Scan Synology, QNAP, and UNC shares for duplicates without false deletes: exclusions, offline shortcuts, and preview-first review.

Network drives feel local until they do not. A VPN drops, a NAS sleeps, or a shortcut points at \\server\share\photos that is offline today. Duplicate scanning on NAS and UNC paths works, but the safe workflow differs from scanning D:\Photos.

Separate live libraries from backup roots

The most expensive mistake on a network share is treating a backup copy as a duplicate of the live library.

Location Role Scan together?
\\nas\photos\2024 Active library Yes, with siblings on same share
\\nas\backup\photos Cold backup No. Scan separately or exclude
D:\Photos + E:\Backup Local + external backup Compare paths before deleting

If two paths serve different roles, exclude one from the scan or review every cross-root group manually. See also How to Safely Delete Duplicate Photos on Windows for keeper rules.

Unreachable shortcuts are not duplicates

Windows .lnk shortcuts to network targets behave differently when the share is offline:

  • Broken shortcut: target is missing or empty.
  • Unreachable shortcut: network target exists but is not reachable right now.

DupeZappa keeps unreachable shortcuts separate from broken ones so a VPN outage does not look like mass file corruption. Junk scanning handles those categories; duplicate scanning should not confuse them with real file groups.

Scan settings that help on slow shares

  1. Enable recursion on the folder that actually holds files, not the drive root on day one.
  2. Use scan exclusions in Settings for System Volume Information, snapshot folders, and @eaDir (Synology metadata).
  3. Pause or wait if the connection is unstable; partial hashes on interrupted reads produce false negatives, not usually false positives, but wasted time.
  4. Run during off-peak hours on busy household NAS units; content hashing is read-heavy.

DupeZappa targets large local folders and shared drives. Progress feedback and exclusions help when network storage gets heavy.

Preview-first still applies on NAS

Network latency makes blind deletes worse; undo may require re-fetching thousands of files across the wire. For each duplicate group:

  1. Open previews when available.
  2. Confirm the keeper opens from the path you expect (\\nas\... vs a local copy).
  3. Send deletes to Recycle Bin when the share supports it; otherwise apply smaller batches.

Use smart selection rules consistently so keepers do not flip between sessions.

When you are done

Re-scan the same root. Group count should drop. If numbers look wrong, check whether a share was offline during the first pass; unreachable paths can hide files from the index.

NAS duplicate cleanup uses the same steps as local cleanup: find real matches, compare them, keep the best copy, and do not delete without reviewing.

Related reading