Find duplicate photos after Google Drive sync

Sync conflict patterns to expect

When bytes match, DupShelf groups them regardless of Drive metadata.

• Copy of… and (1) suffix files next to originals
• Two folders with the same vacation export after restore
• Laptop + desktop both syncing the same manual copy
• Shared drive where teammates drop the same asset twice

Online-only vs downloaded files

Drive’s “online only” placeholders are not readable as image bytes. Right-click → Available offline, or copy files to a local working folder, then scan. This is the most common reason a scan “misses” expected photos.

Local scan workflow

Point DupShelf at your Google Drive folder path on disk (e.g. G:\My Drive\Photos or ~/Google Drive/Photos). Review groups, keep the file in the canonical path, move duplicates to dupshelf-duplicate-images, verify, delete quarantine.

Relationship to Google Photos cloud dedup

Google Photos may group similar items after upload. DupShelf cleans disk before upload or alongside sync folders. They solve different layers: filesystem hygiene vs cloud library intelligence.

Before sharing a Drive folder with family

Dedup locally so you do not upload the same wedding ZIP twice and waste shared quota.

Backup and sync timing

Pause heavy uploads while you move duplicates on disk, or finish cleanup before leaving Wi-Fi so Drive does not sync half-moved groups. After you delete the quarantine folder, allow sync to propagate. On metered connections, local dedup saves more data than cloud-side cleanup alone.

Workspace and school Google accounts

Shared drives that sync to your laptop behave like local folders when files are mirrored. Scan the synced path you use daily. If IT restricts Drive for desktop, export a copy to a personal working folder, dedup, then upload the lean set through approved channels.

Conflicts after restore or ransomware recovery

After restoring from backup or recovery tools, you may see duplicated folder trees side by side. Scan the parent that contains both trees; byte-identical files across conflict folders group together even when Drive renamed them. Verify keepers before delete—recovery folders sometimes mix old and new versions with different bytes.

Drive for desktop vs browser Drive

DupShelf needs the synced folder on disk, not drive.google.com in a tab. Install Drive for desktop or download folders first.

Team Drives and shared folders

If files sync locally, scan works. Permission errors mean you lack read access—ask admin or copy to a personal working folder.

Summary and next steps

Drive sync duplicates are a filesystem problem even when the cloud looks fine. Local dedup before upload saves quota and argument with family members about who uploaded the same ZIP twice. Understand mirror versus stream: scanning requires bytes on disk. After cleanup, give sync time to settle before unplugging laptop on hotel Wi-Fi. Workspace admins may prefer you dedup in a personal staging folder then upload—respect IT rules. Takeout exports deserve the same scan as live sync folders. Google Photos similarity features do not replace this pass; they operate after upload with different rules. Keep a changelog if multiple people maintain the same shared drive. Communication plus exact hashes beats blaming sync silently eating space. Mirror files locally, scan, then let sync propagate a leaner tree. Placeholders are not scannable.