Home · Community report
Clean up duplicate files and photos
Facing Google Drive and 18 years of Google Photos with no built-in tool for the job, one X user had Muse clear out duplicate files and photos: about 13k files and folders (56GB), then about 18k duplicate pictures. How duplicates were matched and whether anything was reviewed go unstated, so ask for a list before deletion.
What you can get
What it is
Duplicate file and photo report
A list of duplicate files and photos found in your Drive and Photos library, with duplicates removed only after you can see what is being deleted.
It came back right when
- A list or count of duplicates was reviewed before deletion.
- Only files or photos confirmed as duplicates were removed, not originals.
- The matching method (exact file vs. visually similar) was stated.
- A post-cleanup spot-check turned up no missing originals.
The checks are editorial, not from the source.
- Scope the scanStops for your approval
Which Drive folders or your whole Drive; which Photos library or date range.
- Match duplicates
Exact file match first; visual similarity only if you ask for it.
- Review the listStops for your approval
See what would be deleted before anything is removed.
- Delete and spot-checkStops for your approval
Remove approved duplicates, then check a sample of what remains.
Editorial, not from the source
Works when
- You have years of accumulated files or photos and no idea how much is duplicated.
- You are willing to review a list before anything is deleted.
- Your duplicates are largely exact copies, not just similar-looking photos.
Does not work when
- You need every near-duplicate (burst shots, slightly cropped versions) kept intact.
- You cannot review a list before deletion and want it fully automatic.
- The files in question are shared with others who might be using separate copies intentionally.
Clean up duplicate files and photos: review template
| Item | What it is based on | Status |
|---|---|---|
| [Drive duplicates found] | [Exact-match or similarity scan] | [Reviewed before deletion] |
| [Photos duplicates found] | [Exact-match or similarity scan] | [Reviewed before deletion] |
| [Storage freed] | [Trash/bin emptied] | [Confirmed in account total] |
The source case
On X, @MrLitefoot reports having Muse remove roughly 13,000 duplicate files and folders (about 56GB) from Google Drive, and separately scan 18 years of Google Photos to find and remove about 18,000 duplicate photos. The post adds that neither Google Drive nor Google Photos has a built-in tool for either task. No detail is given on how duplicates were identified (exact file match, similar image, same filename) or whether anything was reviewed before deletion. This is one attributed report, checked on 2026-10-09, describing an individual cleanup rather than a guaranteed result.
A public report by someone outside this library. Not independently reproduced here.
From the source
Source excerpt
@Muse removing 13k(56gb) duplicate files/folders in Google Drive and organizing it. then it scanned thru 18yrs of pics in Google Photos found and removed 18k duplicates. Google does not have a tool tackle either tasks. thankful for my Muse
Quoted from the original posts. Not written by this guide, and not a result produced here.
Suggested prompt
Bring Access to the Google Drive and/or Google Photos account to scan, How you want duplicates matched (exact file vs. visually similar). Acts Scans Google Drive and Google Photos for duplicates. Reports what it finds before deleting anything. Deletes only the duplicates you approve, not originals. Source community report, checked 2026-10-09.
Written by this guide as a starting point, not quoted from the source. Your edits stay in this browser.
Other ways to ask
Editorial rewrites of the brief above, for a different emphasis. Copy them separately.
What you need
Editorial, not from the source
You supply
- Access to the Google Drive and/or Google Photos account to scan
- How you want duplicates matched (exact file vs. visually similar)
Connected
- Google Drive account access
- Google Photos account access
Approved by you
- Review of the duplicate list before deletion
- No deletion of anything not confirmed as a duplicate
How to try it
Editorial, not from the source
- Scope the scan: which Drive folders or your entire Drive, and which Photos library or date range.
- Ask for duplicates to be identified by exact match first (same file, same size) before any looser matching is used for photos that merely look similar.
- Get a list or count of what would be deleted before anything is removed, broken down by folder or by photo date range.
- Approve the deletion, then spot-check a sample of what remains to confirm nothing you wanted was removed.
Scope the scan before it touches anything
Years of accumulated files and photos rarely live in one tidy place, so decide up front whether the scan covers your entire Drive or specific folders, and whether Photos should be checked across its full history or a narrower date range. The report behind this page describes scanning eighteen years of photos at once, which is a large scope to trust on a first attempt without having seen how the matching behaves. Start narrower if you are uneasy, confirm the results make sense, and widen the scope once you trust the method. Being explicit about boundaries also makes the resulting list easier to review, since a report broken into folders or date ranges is far more checkable than one giant undifferentiated count.
Exact matches first, visual similarity with caution
An exact file match, where two files are genuinely identical in content and size, is a safe basis for deletion because there is no judgment call involved. A visual-similarity match for photos is a different and riskier category, since two photos can look alike (a burst sequence, a slightly cropped export, a screenshot and the image within it) without being duplicates in any meaningful sense. The source gives no detail on which method produced its counts, so ask directly and insist on exact matching as the default, only allowing similarity-based matching where you have reviewed what it would catch and are comfortable with the trade-off between a cleaner library and an occasional false positive.
Review before deletion, then check what is left
Bulk deletion across thousands of files is not something to approve blindly, however confident the count looks. Ask for a list or a breakdown before anything is removed, sorted by folder or date range so you can scan it for anything that looks wrong at a glance. Once you approve and the deletion runs, spot-check a sample of what remains: open a few folders or albums you care about and confirm the originals are still there and intact. If anything looks off, check the relevant trash or bin immediately, since most services hold deleted items for a limited recovery window before they are gone for good, and that window is the only real safety net once a bulk deletion has already run.
Open Muse to try it. That is the product's own site; this guide is not part of it.
Limits and confirmation points
Limits to confirm
- One attributed report, citing round numbers (about 13,000 files, 56GB, and about 18,000 photos) with no detail on how duplicates were defined or matched.
- Deleting the wrong file as a false duplicate, especially photos that look alike but are not identical, is a real risk with bulk cleanup; nothing here claims the matching method was exact.
- This does not restore storage space automatically or fix sync issues; it only removes duplicate files and photos that are found, pending your review.
Stop and check
Editorial, not from the source
- Before it starts: scope which folders or libraries are in bounds, and how duplicates should be matched.
- Before anything is deleted: review the list or count of what would be removed.
- After deletion: spot-check a sample of remaining files and photos.
If it goes wrong
Editorial, not from the source
- You are not sure if a deleted photo was actually a duplicate
- Check Google Photos trash (items are typically recoverable for a limited time) before it empties, and restore anything uncertain.
- The duplicate count seems too high or too low
- Ask how matching was done; a method based on visual similarity will find more "duplicates" than one requiring an exact file match, and the two give very different counts.
- Storage space did not change after deletion
- Check that the trash or bin was also emptied; many services hold deleted items temporarily, where they still count against your storage quota.
Common questions
Can an agent really clean up thousands of duplicate files and photos?
One X user reports exactly that: about 13,000 duplicate files and folders removed from Google Drive, and about 18,000 duplicate photos removed from Google Photos. That is one account with no detail on method, not a guaranteed result for every library.
How does it tell a duplicate from a similar-but-different photo?
The source does not say. Ask for exact-match comparison as the default, and treat any visual-similarity matching as something to review carefully, since similar-looking photos are not always true duplicates.
Will it delete things without asking me first?
It should not. Require a reviewed list or count before anything is deleted; the source gives no detail on whether review happened in that particular case.
What if it deletes something I actually wanted?
Check the relevant trash or bin right away; most services hold deleted items for a limited recovery window. Spot-check your library after any bulk cleanup.
Will this immediately free up storage space?
Only once the trash or bin is also cleared, since many services count deleted-but-not-yet-purged items against your storage quota in the meantime.
Next
Related to this task
More in Home
Similar tasks
Get recurring task recommendations — ask your own agent to check for relevant updates.