Find exact Google Drive duplicates without downloading every file.
ClearCopies reads the metadata Google Drive already exposes, prioritizes SHA-256, SHA-1, then MD5 checksums, and groups only files with the same byte size and comparable fingerprint. You review the evidence; the first connection cannot change your files.
Implementation verification · August 2026
Tested against Google Drive API behavior
The integration tests read Drive quota, reconstruct nested paths, retain sharing context, and normalize the strongest available SHA-256, SHA-1, or MD5 checksum. The first OAuth request is verified as read-only.
- Read-only
- initial OAuth
- 3
- checksum fallbacks
- 0
- name-only exact claims
Google-native Workspace files do not always expose comparable binary evidence; the tested workflow leaves those items outside exact groups instead of inflating recoverable storage.
Written by ClearCopies Editorial · Technical review by ClearCopies Engineering
A Google Drive scan built around checksum evidence
Google Drive has its own mix of uploaded binaries, native Docs files, shared items and nested folders. The scan keeps those differences visible instead of forcing every item into an exact-match result.
- 01
Authorize metadata access
Google asks you to approve drive.metadata.readonly alongside sign-in scopes. ClearCopies receives no Drive write permission in this step.
- 02
Map files and folder paths
The adapter enumerates non-trashed items, reconstructs their folder paths and records sizes, timestamps, sharing state and available checksums.
- 03
Review defensible groups
Uploaded files become exact candidates only when byte size and a checksum from the same algorithm agree. Unsupported items remain for manual review.
Why Google checksums are stronger than matching names
Google may expose more than one checksum for an uploaded binary. ClearCopies normalizes the strongest available value into one fingerprint while retaining the algorithm name, so an MD5 value is never compared as though it were SHA-256.
- 1
Drive metadata
size + sha256Checksum / sha1Checksum / md5Checksum
- 2
Normalized signal
algorithm name + content fingerprint
- 3
Exact candidate
same byte count + same comparable fingerprint
Google-native Docs, Sheets and Slides may not expose a binary checksum or meaningful byte size. ClearCopies does not promote those items to an exact group without reliable fingerprint evidence.
What ClearCopies can see in Google Drive
The Google authorization screen is intentionally narrow. It supports inventory and duplicate analysis, not cleanup actions.
Reads for the scan
File identity and location
Names, IDs, MIME types, parent folders and reconstructed paths.
Duplicate evidence
Byte sizes and Google-provided SHA-256, SHA-1 or MD5 values when available.
Review context
Created and modified times, sharing state, ownership hints and available thumbnail links.
Does not do
Download file bodies for hashing
Exact grouping uses checksums returned with Drive metadata rather than transferring each file to ClearCopies.
Rename, move or trash files
drive.metadata.readonly does not authorize changes to Google Drive content.
Call a name match an exact duplicate
A repeated filename or byte count can create a review lead, but neither proves identical content.
Trash requires separate permission
Moving a reviewed Google Drive copy to trash is a separate step. It requests explicit Google Drive write consent only after review and must pass ClearCopies' server-side cleanup gate; it is never part of the read-only scan.
Plan a Google Drive review before changing anything
Use these local tools to inspect checksum evidence and turn candidate groups into a keep-first checklist, then use the guides to understand the limits of metadata matching.
Free tools
- Scan Google Drive read-onlyRun the connected metadata scan with Google checksums and a review-first result.
- Draft a keep-first review planTurn candidate groups into a checklist that retains at least one copy.
- Measure duplicate file shareEstimate how much of an inventory consists of reviewed extra copies.
Questions about scanning Google Drive
Straight answers about fingerprints, permissions and the boundary between review and cleanup.
Does ClearCopies download my Google Drive files?
No. Duplicate grouping uses file metadata and Google-provided checksums. ClearCopies does not download every file body to calculate its own hash.
Which Google Drive checksum does ClearCopies use?
It prioritizes sha256Checksum, then sha1Checksum, then md5Checksum when Google exposes them. The algorithm travels with the value so different checksum types are never treated as interchangeable.
What happens to Google Docs, Sheets and Slides?
Google-native workspace files may not include a binary checksum or byte size. Without reliable fingerprint evidence, ClearCopies does not classify them as exact duplicates.
Can the first Google connection delete or move files?
No. The initial OAuth request uses drive.metadata.readonly. Any future trash action would require a separate write authorization after review and remains independently gated on the server.
Can ClearCopies inspect shared Google Drive items?
The adapter includes items visible to the connected account and records Google's sharing indicator. Actual visibility still depends on that account's Drive permissions.
Google Drive public access is coming soon
The integration is complete and under Google OAuth verification. Public connections open after approval, without exposing launch users to an unverified-app warning.