Quick Answer: Check an independent backup first, review exact file matches before similar pictures, and keep the version in the right folder with its companions. Work in a small batch and verify the keepers and recovery route before permanent deletion.
A repeated import can leave hundreds of unnecessary copies. A RAW file beside its JPEG, however, may be a useful pair. Safe cleanup starts by distinguishing those two situations. The method below works from protected originals toward small, checked deletions, without giving a cleaner permission to decide which family memories matter.
Before You Delete, Protect Your Originals
Make an independent copy before scanning. A separate external drive, a versioned backup with a tested restore, or an original-file export outside the library being changed gives you a recovery route. A second folder inside the same synchronised library may receive the same deletion. Our 3-2-1 photo backup guide explains how to separate working files from recovery copies.
Open several recent and older photos from the backup at full size, and play a representative video. Check that an online-only thumbnail has actually downloaded as an original. If your library uses a catalogue, edits or sidecar metadata, back those up as well as the visible pictures. Keep this backup out of the cleanup scan.
Decide what counts as a duplicate
An exact duplicate has the same file contents. Two copies can have different names and still match. A near-duplicate merely looks similar: a resized export, a crop, a re-compressed JPEG, a burst frame or an edited version may all differ in useful ways.
Keep RAW/JPEG pairs, original/edited pairs, Live Photo companions and sidecar files together unless you understand their roles. A tool’s largest-file or newest-file rule cannot decide whether you need the original for editing and the smaller export for sharing.
Identical pixels are not identical files
Two JPEGs can display the same picture but carry different dates, captions, location information or compression. A similarity result therefore needs more review than a file-content match. Conversely, two byte-identical files can still occupy different folders used by a catalogue or family project. Check both content and the job each copy performs.
A hash comparison is useful for unchanged ordinary files; it is not a quality score. If one copy was re-saved or its embedded metadata changed, a different hash does not tell you whether it is a worse photograph. Do not strip metadata or recompress the originals simply to make them match.
Choose keeper rules before marking results
For each batch, write down its preferred home, which originals and edits must stay together, and any folders that a project references. Keep the highest useful source quality, but also retain a finished edit when it has a separate purpose. If two people contributed the same image with different captions or dates, resolve that context before discarding either version.
No → stop and make one.
Yes → choose the matching branch below.
Check the intended keeper opens, sits in the right folder and preserves catalogue links and companion files.
All checks pass: send surplus copies to recoverable Trash.
Anything uncertain: keep both while you investigate.
Compare the original, edit, resolution, burst moment and file format.
Different useful version: keep it.
Truly unwanted version: review manually before moving it to Trash.
Before permanent deletion: open the keepers, check albums and restore a sample from the independent backup.
Find Duplicate Photos in a Controlled Batch
Use this workflow for an ordinary photo folder only after making an independent backup. App-managed libraries need their own duplicate controls, described below.
-
Choose one ordinary event folder or import batch you recognise. Exclude the independent backup, system folders and application support files. For a managed Photos library, use the photo app’s own controls rather than pointing a general file cleaner inside its library package.
-
Record the folder’s location. A project or catalogue may refer to a particular path, so keeping identical image data elsewhere can still leave a broken reference.
-
Scan for exact content matches first. A name-only match is insufficient: filenames such as IMG_0001 recur on different cameras.
-
Review each exact-match group and open the proposed keeper. Check its dimensions and confirm that it is the version you intend to retain.
-
Check the keeper’s destination folder and any catalogue references before marking surplus copies. Identical bytes do not resolve folder organisation or app dependencies.
-
Compare near-duplicates separately after handling exact matches. Use a conservative picture-similarity setting and inspect each group at a useful magnification for focus, expression, movement and edits; the biggest file or latest timestamp may not be the best photograph.
-
Retain useful edits alongside their originals or label them clearly. Do not discard an original because an edited preview looks sharper; consider image dimensions, file format and editability.
-
Move only reviewed surplus files to recoverable Trash or a separate review location supported by your tool. Read the confirmation: permanent deletion, network volumes and some external-drive workflows may offer different recovery behaviour.
-
Check the remaining files and the albums or projects that use them for missing images or broken references.
-
Restore a small selection from the independent backup into a temporary folder and open the restored files to check that recovery works.
-
Empty Trash only when the keepers and recovery copy are usable. A service’s automatic retention period is a limit, not a backup strategy.
Choose the Method for Your Device
iPhone and iPad: merge within Photos
In the current Photos interface, open Collections, find Utilities and open Duplicates when it is available. Inspect a group, choose Merge and confirm the selection. Detection happens automatically; the merge is your decision. Apple explains that merging keeps the highest image quality and relevant data, with surplus items moved to Recently Deleted. Menu placement can differ on older systems.
An absent Duplicates album does not prove that every import or resized copy is unique. Give detection time and review deliberate edits separately. Avoid bulk-merging a library you have not backed up. With iCloud Photos, a deletion can also affect other devices signed in to the same Apple Account.
Android: review Files by Google suggestions
Google’s documented route is Files by Google → Menu → Clean → Duplicate files → Select files. Review the selection, then choose Move to Trash and confirm. Google marks a preferred keeper with an Original badge; check that before selecting anything.
A manufacturer’s Gallery or file manager may have different cleanup tools. Follow the instructions for your actual app and version rather than borrowing steps from another Android phone. A local-file scan also does not establish that an online Google Photos library has been cleaned.
Check whether both supposed copies are fully downloaded local files. A cloud preview, shortcut or cached image is not a replacement for the original. If the goal is only more phone space, use the service’s documented device-space workflow after checking the uploaded copy, rather than deleting from the cloud library as a substitute.
Mac: distinguish Photos from folders
For pictures managed by Apple Photos, use its Duplicates view and supported merge controls. For ordinary exported folders outside Photos, use a folder comparison tool. Keep those jobs separate so a cleaner does not alter the internal files of the managed library.
Check whether a folder contains full originals, reduced exports or both. An exported JPEG can be useful without replacing the original RAW file or the adjustments stored in the photo app.
Windows and ordinary Mac folders: a local finder
For a large folder collection, dupeGuru is one documented example. Its scanning documentation distinguishes Contents scans from Picture mode. Use the former for file-content matches and the latter when intentionally reviewing visual similarity. A filename scan answers a different question.
Download software from its genuine publisher, check platform and format support, and begin with one copied folder. Preview the groups, choose keeper locations and verify the deletion action before proceeding. Reference-folder settings and automatic selection rules help organise a scan; they are not substitutes for your own backup and review.
Read the mode and action, not just the match percentage
dupeGuru’s documentation is versioned 4.0.3: Standard-mode file-content comparison and Picture-mode visual comparison answer different questions. EXIF Timestamp scanning is another option and can match useful edits with the same capture timestamp. Check the mode in the version you installed; a high percentage alone is not a reason to discard files.
Its results guide also separates highlighted files from files marked for an action. Inspect the reference path and the marked set before proceeding. Removing a row from results is not deleting the file, and moving marked files is a different action from sending them to Trash. Leave unfamiliar linking and direct-deletion options off rather than using them to chase a space-saving estimate.
Keep the independent backup out of every scan, including recursive scans of a parent folder. Do not mix a test folder with a live Photos package, a working catalogue’s internal support files or an account-synchronised folder whose deletion behaviour you have not checked.
Cloud Photo Libraries Need a Separate Check
First decide whether you want to remove an image from the library everywhere or free space only on one device. Those are different operations. Removing a photo from an album may leave it in the main library, while deleting from the library can affect albums and connected devices.
Google’s deletion guidance describes where removals propagate and how Trash works. Check the current policy for your account and exact action rather than assuming every photo has the same recovery period. Grouping similar photos into a stack is a browsing feature; it does not itself remove the unwanted files.
Apple normally provides a Recently Deleted recovery period, but its iCloud guidance includes exceptions when storage limits are exceeded. Do not rely on a future recovery window as permission to delete the only independent original today.
If you need a local copy before cleanup, our Google Photos export guide explains the download stage. Verify that export before changing the cloud library.
Agree on shared-library changes
For a shared household collection, tell the other contributors which batch is being cleaned and pause competing moves or imports. Check whether an album contains a separate file or merely points to a library item. Deleting the library item can remove it from the album as well.
Apple’s Shared Photo Library allows participants to delete items, while recovery or permanent-deletion controls depend on who added them. Agree on keepers with the contributor and use the current app’s recovery controls. Do not assume another participant’s device is an independent backup of the shared state.
What to Look for in a Duplicate Photo Cleaner
Choose a tool for the controls it gives you: content matching, a separate similarity mode, usable previews, visible paths and dimensions, and a reversible removal option. Check HEIC, RAW and video support for your own collection. A tool that skips an unsupported format cannot establish that the whole library is duplicate-free.
Find out whether it processes files locally or uploads them. That matters for private family photos and large libraries. Price alone says little about deletion safety; a paid cleaner can still apply a rule that does not fit your keeper choices.
Before buying, test an ordinary copied folder containing known examples: an exact copy with a different name, an original plus an edit, and two genuinely different burst frames. Check whether the results distinguish them. This is a way to assess the workflow, not a reason to trust automatic deletion across the entire drive.
Keep a removal record you can reverse
Before confirming a batch, retain the scan scope, chosen matching mode, keeper paths and marked removals. In dupeGuru, the documented Export Results to XHTML action saves the visible result columns. Include the details that let you find the files again, then keep the record privately with the batch backup. A list of filenames alone is ambiguous when several cameras have reused the same names.
Check the complete marked set immediately before the action. A highlighted row is not the same as a marked file, and changing the filtered view can make a result list look smaller without explaining every existing mark. Review the action confirmation and the intended paths. Do not send a broad marked set to Trash merely because the currently visible group looks correct.
| Where cleanup happened | If a needed item is missing | Before continuing |
|---|---|---|
| Ordinary local folders | Use the recorded removal location or restore from the independent backup into a separate folder | Check the keeper, original path and any project references |
| An app-managed photo library | Use that app’s recovery controls or documented library restore | Confirm the recovered item and albums inside the app |
| A synced or shared library | Check the service’s current recovery controls and contributor permissions | Confirm the intended shared state with other participants |
If a project reports a missing image, preserve the remaining files and stop the next cleanup batch. Restore the expected file to a separate location first, then use the catalogue or project’s supported locate or relink control. An identical photograph elsewhere may solve the content loss without automatically repairing the reference. Avoid changing a managed library’s internal files in an attempt to fix its database.
Keep uncertainty visible in your own record: an exact-content match with a working keeper can be cleared, while an unexplained caption, edit or project dependency stays unresolved. Retaining a small review set is preferable to guessing. Exclude that set from the next cleanup so an automatic scan does not select it again before you have made a decision.
Calculate surplus copies before expecting free space
Count the copies you remove, not every file shown in a duplicate group. In a hypothetical batch of ten groups containing three identical 8MB files each, keeping one per group leaves two surplus copies: 10 × 2 × 8MB = 160MB. Five more pairs of 4MB files add 5 × 1 × 4MB = 20MB, giving 180MB of surplus file data in total. This is a calculation from the example, not a measured cleaner result.
That amount is not guaranteed immediate free space. Files held in Trash on the same volume can still occupy storage, and a review folder on the same drive keeps the bytes there too. A cloud account and a phone also measure different storage pools. Check the actual location and storage reading after the intended safe action; do not empty recovery bins early just to match an estimate.
For a phone-space problem, first decide whether you want fewer local copies or fewer items in the online library. Use the service’s documented local-space feature only after checking the uploaded originals and an independent backup. A cloud photo deletion is a different decision, and repeating it across several devices is not a way to create more independent copies.
Keep the Right Copy, Not Just Fewer Files
Finish by choosing one normal home for each keeper and recording what you changed. Our digital photo organisation guide covers folders, albums and future imports. Avoid renaming or moving catalogue-managed files outside the application that owns their references.
Reconcile the first batch before expanding the scan
Record what was moved and where it went, including original paths if your tool preserves them. Open the retained images, edited versions, paired clips and catalogue projects. Restore a few removed test copies into a separate folder to check that you can reverse a mistake without overwriting the keepers.
For example, removing one surplus 8MB file from each of 100 exact-match pairs represents 800MB of file data, not 1.6GB. Keeping those files in Trash on the same drive may not free that space immediately. Judge success by correct keepers and usable recovery, then check the device’s actual storage reading; a cleaner’s estimate is not guaranteed reclaimed capacity.
The useful outcome is a smaller working library with the originals, deliberate edits and recovery copies you need. If a group remains uncertain, keep it and return later. Once the checked batch is stable, prevent another repeated import by recording which source folders have already been added.
Frequently Asked Questions
Can my iPhone remove duplicate photos for free?
Yes. Apple Photos can identify duplicates and offer a Merge action. Review each group before confirming. The feature does not replace an independent backup or decide whether you need an original and a deliberate edit.
How do I delete duplicate photos on Android without losing originals?
Make a separate backup, then review the Duplicate files card in Files by Google. Keep the file marked Original unless you have checked a good reason to choose another location. Move selected copies to Trash rather than choosing permanent deletion.
Is it always safe to delete exact duplicate photos?
No. Identical file contents do not tell you which folder a catalogue, album or project references. Check the keeper’s location, open it, preserve any companions and confirm an independent backup before removing another copy.
Will deleting a photo remove it from the cloud too?
It can. Deletion in a synced library may reach the cloud and other connected devices. Check the exact service and action: deleting from a library, removing only a device copy and removing an album entry are different operations.
Should I keep RAW files and JPEG copies of the same picture?
Keep both when you need the editable original and a finished or widely compatible version. They are different files with different jobs. Apply the same care to edited exports, Live Photo companions, videos and metadata sidecars.
Why has deleting duplicate photos not freed the expected space?
Check where the removed files went and which storage pool you are measuring. Trash or a review folder on the same drive can still occupy space. A cleaner’s estimate may also count more than the surplus copies. Verify keepers and recovery before permanent deletion.
What should I do if a photo project cannot find an image after cleanup?
Stop the next batch, preserve the remaining files and check your removal record. Restore the expected file into a separate folder, then use the project’s supported locate or relink controls. Do not modify the internal files of a managed photo library.
Sources and image credits
Platform guidance: Apple duplicate merging, deletion and recovery, Files by Google duplicate cleanup, dupeGuru scanning modes and dupeGuru results and actions. The file-type, cleanup and keeper diagrams explain distinct decisions; the opening photograph illustrates a home photo collection.
Related Posts
Share this article
Stuart Kerr Spindlow is Pixoneye’s Publisher, Editor-in-Chief and Lead Product Reviewer. He tests consumer products and leads coverage of practical gadgets and personal-media preservation. His reviews focus on usability, limitations, value and the trade-offs that matter when choosing a product. Read Stuart’s full profile.
Leave a Reply