Clean local folders before you rely on Google Photos dedup

What Google Photos duplicate features actually do

Inside Google Photos (and related Google One storage tools), Google analyzes photos you have already backed up. It may surface similar faces, memories, and storage-saving suggestions. Those features depend on your Google account, Google’s servers, and their similarity models—not on folders sitting only on your laptop. They also do not run on arbitrary directories like Downloads or an external hard drive that is not synced.

• Works after photos are in Google’s ecosystem
• Similarity and grouping rules are Google’s, not byte-exact
• Subject to storage plans, sync settings, and account privacy policies
• Does not scan unrelated local folders on disk

What DupShelf does on your computer

DupShelf runs in your browser and reads image files from a folder you choose—Downloads, Pictures, a copied phone backup, or a Google Drive folder that is fully downloaded (not online-only placeholders). It hashes file content with SHA-256 and groups exact duplicates. You review groups, pick one keeper per group, and either move extras into a dupshelf-duplicate-images subfolder or export a CSV for manual cleanup. DupShelf does not connect to your Google account and does not upload your photos for scanning.

• Exact byte matches—including renamed copies
• No Google sign-in required
• Folder-scoped: you control which path is read
• Move or export; DupShelf never auto-deletes

Google Drive folder on disk (important detail)

If you use Google Drive for desktop, photos may appear in a local sync folder. DupShelf can scan that folder only if files are stored on disk (available offline). Online-only placeholders are not readable as image bytes. Before a big cleanup, run Drive’s “available offline” for the album you care about, or copy photos to a separate folder, then scan.

Why clean locally before uploading

Uploading duplicates wastes time on slow home broadband, burns mobile data on hotspots, and fills Google storage faster. A local exact-dedup pass can remove gigabytes of true copies—same file saved from WhatsApp twice, backup restored on top of backup—before the next sync. You also keep sensitive shots off Google until you are ready to upload the lean set.

• Smaller uploads and faster backups
• Fewer surprises in Google storage meter
• You decide what enters the cloud
• Works when Google’s similar-item grouping is too aggressive or too loose

Step-by-step workflow

A practical order that avoids deleting unique photos:

• Locate the folder: Downloads, Pictures, or exported Google Takeout / phone copy
• Open DupShelf in Chrome or Edge → Choose folder
• Wait for hashing to finish; review duplicate groups
• Pick keepers (often largest resolution or best filename)
• Move non-keepers to dupshelf-duplicate-images
• Open that folder in Explorer or Finder; confirm thumbnails; delete when sure
• Upload or sync the cleaned library to Google Photos if you want

What DupShelf will not do relative to Google Photos

DupShelf will not merge people across years in Memories, will not edit cloud libraries directly, and will not find perceptually similar burst shots unless the files are byte-identical. Google’s face grouping and “similar items” are different products. Use Google for cloud library intelligence; use DupShelf for folder hygiene on disk.

Scenario: phone backup + Google Photos double-save

Many users save camera rolls locally and also enable Google backup—ending up with the same bytes in Downloads exports and in a Drive sync folder. Scan the local export folder with DupShelf, remove exact copies, then let Google sync the leaner set. You avoid paying for storage twice for the same file.

Scenario: shared family Google account

Multiple people forward the same festival album into chats; each save creates a new filename. Google Photos may or may not dedupe in cloud. A local DupShelf scan of the shared Downloads folder gives a clear byte-identical list everyone can review before anyone deletes unique shots.