Drive Duplicate Auditor

Google Drive · read-only audit

Proof first.
Cleanup later.

Drive Duplicate Auditor inventories an approved folder, confirms uploaded-file matches with SHA-256 and lays out the evidence in a review Sheet. It has no delete button.

Follow the evidenceSee the safety boundary ↓
Uploaded files
Exact SHA-256
Google-native files
Possible match only
Source changes
None

01

The rule that matters

A similar name is a clue.
An identical hash is evidence.

Copied suffixes help people spot likely clusters, but they never decide a result. Two uploaded files enter an exact group only when their bytes produce the same SHA-256 digest.

A bounded audit route

From folder tree to review evidence.

  1. 01

    Enter through an approved root

    The script scans only configured folders and skips shortcuts that could lead elsewhere.

    Allowlist
  2. 02

    Page the inventory

    One folder page per run keeps execution predictable and leaves continuation state visible.

    100 items
  3. 03

    Hash safe-size uploads

    Uploaded files up to 20 MB receive an exact SHA-256 digest. Larger files remain inventory-only.

    Exact bytes
  4. 04

    Separate native files

    Docs, Sheets and Slides are labelled possible matches because metadata is not byte-level proof.

    Lower confidence
  5. 05

    Propose, never perform

    Deterministic rules nominate a canonical copy, but every approval stays blank.

    Human review

The authoritative review Sheet

Every claim keeps its receipt.

The formatted Sheet links back to each Drive file and keeps confidence, location, sharing warnings, recommendation and approval together.

  • DashboardGroups, space estimate and failures
  • Duplicate ReviewEvidence and blank decisions
  • InventoryEvery file and hash status
  • Run LogBounded progress and retries
Drive Duplicate AuditIllustrative rows
ConfidenceFileCanonicalApproval
Exact SHA-256Statement.pdfYesBlank
Exact SHA-256Statement (2).pdfNoBlank
Possible nativeProject plan (1)ReviewBlank

Safety boundary

The audit can inform a decision. It cannot make one.

No source file is moved, modified, shared, trashed or deleted. A failed file is retried independently, then left visibly marked for manual review.

✓ Approved roots only✓ Per-file failure isolation✓ Blank approvals× No cleanup function

A Drew’s Digest project

Less clutter.
More certainty.

Return to Drew’s Digest ↗