How to find and remove duplicate files in Google Drive

Duplicate files are the most common source of wasted storage in Google Drive, and they're nearly invisible to the built-in UI. Google Drive has no native duplicate finder. A file named Report-v2.pdf and one named Report-v2-copy.pdf can be byte-for-byte identical, and Drive will show them as two unrelated files with no indication they're the same.

This guide covers why duplicates accumulate, how to find them accurately, and how to remove them without accidentally deleting files you need.

Why duplicate files accumulate in Google Drive

Most people don't add duplicates deliberately. They appear from ordinary usage patterns.

Multiple devices uploading the same file. If you save a file on your laptop and your desktop has Drive for Desktop running on the same folder, both machines may upload the file independently - particularly after a rename, a move, or a reconnection after being offline. You end up with two copies in the same folder or in different folders.

"Add to My Drive" on shared files. When someone shares a file with you and you click "Add to My Drive," a copy of that file gets added to your storage. If you do this across multiple shared folders, or your teammates each share versions of the same document, you can accumulate three or four copies of the same file without realizing it.

Backup tools that re-upload on rename. Several backup utilities treat a renamed file as a new file rather than a modified one. If you rename a folder or tidy up your local directory structure, a backup tool can interpret that as new content and upload everything again.

Google Photos sync. Photos can appear in both Google Photos and Google Drive, depending on your sync settings and how old your account is. Older accounts that had Drive–Photos integration turned on sometimes end up with photos mirrored into a Drive folder, creating duplicates of everything that's also in Photos.

Downloading and re-uploading. A file gets downloaded for editing in a local application, saved, and then re-uploaded - either manually or by a sync tool - alongside the original. The original version stays in Drive; so does the re-uploaded copy.

The result across a few years of use is often dozens or hundreds of duplicate files. Each one individually is small, but the total can consume several gigabytes.

Why Google Drive has no built-in deduplication

Google Drive stores every file as a distinct object with its own permissions, sharing settings, and edit history. Merging two files that happen to contain the same bytes would require collapsing that metadata - deciding whose sharing settings to keep, which history to preserve. Google's product decision has been to keep every file independent.

The search and sort tools Drive provides don't help here. Sorting by name will surface Budget-2025.xlsx and Budget-2025 (1).xlsx next to each other, which catches some obvious cases. But it completely misses Budget-2025.xlsx and Budget-final.xlsx if they contain identical content. Sorting by size gets you the largest files, not the duplicated ones.

There is no "Find duplicates" option anywhere in the Drive UI - not in the web app, not in Drive for Desktop, not in the mobile apps.

The manual approach: what it catches and what it misses

For a small Drive with a handful of files, manual auditing is feasible. Sort your Drive by name and look for files with "(1)", "(2)", or "copy" in the filename. Most of these are duplicates that Drive created when you uploaded a file that already existed.

Sort by modified date to find clusters of files touched around the same time. Drag them into the same folder and compare.

These approaches catch name-based duplicates: files where the duplication is visible in the filename. They fail for content duplicates: files with different names that contain identical bytes. A file you downloaded, renamed, and re-uploaded will never surface in a name-based search. Neither will a PDF that was exported from Docs twice under different names, or a presentation deck that two teammates both saved a copy of.

For a Drive with more than a few hundred files, manual auditing also becomes impractical - you'd need to open each file and compare it against others, which is not feasible at scale.

What makes a file truly a duplicate

The accurate definition of a duplicate is: two files whose content is identical, regardless of their name, location, or creation date.

The standard way to test this is a content hash - a short fingerprint computed from the file's bytes. The most common algorithms are MD5 and SHA-256. Two files with the same hash contain the same content. Two files with different hashes are different files, even if their names match.

This matters in practice:

• photo.jpg and photo (1).jpg - if their hashes match, they are duplicates. The "(1)" was added by Drive when you uploaded a file that already existed; the content is identical.
• Invoice-final-FINAL.pdf and Invoice-final-FINAL-copy.pdf - if their hashes match, they are duplicates. Two exports of the same invoice.
• presentation.pptx and presentation-old.pptx - if their hashes differ, they are not duplicates. One may be an older version with different content.

Filename-based search cannot make this distinction. Only content-hash comparison can.

Three methods for finding duplicates

Method 1: Manual search in Drive

Sort by name, look for "(1)" and "copy" patterns, compare manually. Works for small Drives with obvious naming patterns.

Where it fails: misses same-content-different-name duplicates entirely. Slow and incomplete for Drives with more than a few hundred files.

Method 2: Google Apps Script

Apps Script can access your Drive programmatically, compute MD5 hashes via the Utilities.computeDigest() function, and build a list of files that share a hash. A complete implementation runs to roughly 150–200 lines of code: enumerate files, hash each one, group by hash, write results to a Sheet.

The main limitations: it runs in your browser tab and will time out on large Drives. It requires you to write, debug, and maintain the script. And it handles the scanning part but not the deletion - you'd still need to go through the results manually and delete from the Drive UI.

This approach is viable for developers comfortable with Apps Script who have a reasonably small Drive.

Method 3: GKit Drive Cleaner

Drive Cleaner is a web tool that connects to your Google Drive via OAuth, scans your files, groups duplicates by content hash, and lets you review and delete them from a single interface.

The scan covers My Drive and Shared Drives. Results are grouped by duplicate set - you see all five copies of a file together, with their names, locations, sizes, and last-modified dates. You choose which copy to keep; the others are moved to Trash. Nothing is deleted automatically.

Drive Cleaner also surfaces large files and orphaned files in the same pass, so one scan gives you a complete picture of what's taking up storage.

No files are processed on external servers - the OAuth grant is scoped to what the scan requires. Drive Cleaner is currently free in beta.

Comparison: three methods

	Manual (Drive UI)	Apps Script	Drive Cleaner
Time for a full audit	Hours	30–60 min to write + run	10–20 minutes
Finds content-hash duplicates	No	Yes	Yes
Handles large Drives	No	Partial (timeout risk)	Yes
Safe preview before delete	No	No	Yes - group-level review
Finds large files	Manual sort only	Custom code needed	Yes - included
Works on Shared Drives	Partial	Partial	Yes
No setup required	Yes	No	Yes

Walk through Drive Cleaner

Connect your Google account. Drive Cleaner uses standard Google OAuth. You authorize it from your Google account; it requests a scoped grant covering file list and metadata access. The authorization screen shows exactly what access is being requested.

The scan runs automatically. Once connected, Drive Cleaner indexes your Drive and computes content hashes. The time depends on the number of files. Most Drives complete in a few minutes.

Review duplicate groups. Results are presented as groups - each group contains all files with identical content. For each group, you see the filename, folder path, file size, and last-modified date of each copy. This context is what you need to decide which copy to keep: the one in the active project folder, the most recently modified, the one with the cleaner name.

Select which copy to keep. Mark one file in each group as the one to keep. The others are queued for deletion. You can skip any group you're not sure about - no group has to be resolved in a single session.

Delete. When you confirm, Drive Cleaner moves the selected files to your Trash. Nothing is permanently deleted yet - the files are in Trash and recoverable until you empty it.

After the cleanup: freeing up your quota

Deleting files in Drive does not immediately free up your storage quota. Files moved to Trash still count against your quota until the Trash is emptied.

After your Drive Cleaner session, go to drive.google.com, click the Trash icon in the left sidebar, and select "Empty Trash." The freed storage will be reflected in your quota within a few minutes. If you're close to the storage limit, this is the step that actually moves the needle.

On the GKit dashboard, you can also see a summary of what was removed and how much storage was recovered across sessions.

Preventing duplicates from accumulating again

Cleaning up is a one-time reset. A few habits keep the problem from rebuilding.

Use shortcuts instead of "Add to My Drive." When someone shares a file with you and you want easy access to it, right-click and choose "Add a shortcut to Drive" rather than "Add to My Drive." A shortcut takes up no storage; a copy does. The file still appears in your Drive and opens normally - it just lives in the original owner's storage, not yours.

Use one sync tool, not multiple. If you have Drive for Desktop installed and also use a third-party backup tool that syncs to Drive, you're asking for duplicate uploads. Pick one path to get files into Drive and stick with it.

Turn off redundant backups. Review what Google Photos is syncing and from where. If you have both an Android phone and a tablet uploading the same Photo library, you may be creating duplicates in your Photos storage that count against your Drive quota. One device backing up to one account is the clean configuration.

Do a quarterly check. Duplicates tend to accumulate gradually. A quick scan every three months catches problems while they're small rather than after they've compounded.

The direct path to a clean Drive

Manual search catches some duplicates. Apps Script can catch more, with effort. Content-hash detection catches all of them, accurately, regardless of filename.

If your Drive has been accumulating files for more than a year - across multiple devices, from shared files, from sync tools - there are almost certainly duplicates in it that manual methods will not surface.

Drive Cleaner handles the scan, the grouping, and the safe review workflow in one place. The beta is free - get started and you'll have a complete duplicate report within minutes.

Drive Cleaner is part of GKit, a suite of Google Workspace tools that also includes SheetsAPI for turning any Google Sheet into a REST API. See pricing, browse use cases, or explore free tools.