iPhone Duplicates Album Not Working? Here's Why

You went to Photos, tapped through to Utilities, and the Duplicates album wasn’t there. Or it was there, you opened it hopefully, and it showed you three photos when your camera roll clearly contains hundreds of copies of the same thing.

Those are two completely different problems. Almost every guide on this treats them as one and hands you the same eight-step checklist, which is why people end up resetting all their settings over an album that was working correctly the whole time.

So let’s split them apart, because only one of them is actually a bug.

First: is the album even supposed to be there?

The Duplicates album lives under Photos → Collections → Utilities → Duplicates. On older versions of iOS you’ll find it at Albums → Utilities instead. You need iOS 16 or later; duplicate detection didn’t exist before that, so there’s nothing to look for on iOS 15.

The part almost nobody mentions: the album only exists when iOS has actually found duplicates. No duplicates, no album. And once you’ve merged or deleted them all, it vanishes again.

So “the Duplicates album is missing” is sometimes just iOS telling you it found nothing. That’s a result, not an error.

Before you troubleshoot anything, then, ask yourself the honest question: do you definitely have exact duplicates, or do you have a lot of very similar photos? Hold that thought, because it comes back later and it matters more than you’d think.

The real reason it’s stuck: indexing only runs locked and on power

If the album genuinely should be there and isn’t, this is almost certainly your answer, and it comes straight from Apple.

Before iOS can show you duplicates, it has to index your entire photo library. That scan has conditions attached. In Apple’s words:

“For the Duplicates album to appear, your iPhone has to first index the photo library and find duplicates… this detection process requires your iPhone to be locked and connected to power.”

Read that twice. Locked, and connected to power. Both conditions at once, for a sustained stretch. Plugged in while you scroll doesn’t count. Sitting unlocked on the desk doesn’t count.

Apple is equally blunt about the timeline: “Depending on what tasks are running in the background and the size of your photo library, the process could happen quickly or take up to a few days to complete.”

Up to a few days. Apple means that literally. Users with big libraries on the Apple Support Community routinely report waiting several nights before the album showed up.

What to actually do

Plug the phone into a charger.
Lock the screen.
Walk away. Overnight is the minimum.
Check Utilities in the morning.
If you have a large library (tens of thousands of items), repeat for two or three nights before you conclude anything is wrong.

That’s it. That’s the fix for most people. It doesn’t feel like a fix because it asks you to do nothing, and doing nothing feels less like troubleshooting than tapping through Settings menus. But tapping through Settings menus is what interrupts the scan.

Other things that block detection

If you’ve genuinely given it several plugged-in, locked nights and the album still hasn’t appeared, work through these in order.

Optimize iPhone Storage

Detection works from what’s physically on the device. With Optimize iPhone Storage on, iOS keeps space-saving versions locally and parks your originals in iCloud, and duplicate detection on a heavily offloaded library is widely reported to be unreliable.

The standard advice is to switch to Download and Keep Originals (Settings → your name → iCloud → Photos). The caveat nobody else gives you: that pulls your entire library back down onto the phone. If you have a 200 GB library and a 128 GB iPhone, it simply cannot happen, and you’ll spend a day watching a progress bar fail. Check the numbers before you flip that switch.

An iCloud sync that hasn’t finished

If you’ve just enabled iCloud Photos, or you’re setting up a new phone, the initial sync has to complete before detection settles. Photos will usually tell you at the bottom of the Library view if it’s still working. Let it finish.

iOS version

Update to the latest release. A handful of point releases across iOS 16 and 17 had reported Duplicates regressions, and the fix for those was always the next update.

A restart

Worth exactly one try. Restarting re-kicks the indexing job, which occasionally shakes a stuck scan loose. It does not let you skip indexing. Afterwards you still have to plug in, lock, and wait.

Low Power Mode or a nearly full phone

Both cause iOS to deprioritize background work, and indexing is background work. Turn Low Power Mode off and free up a little breathing room before you leave the phone to scan.

Notice what isn’t on this list: Reset All Settings, restoring from a backup, DFU mode. Those show up in a lot of listicles and none of them address the actual mechanism.

If the album works but it’s empty, that’s not a bug

This is the one that sends people in circles, and it’s the most important section here.

Apple’s duplicate detection flags essentially identical items. It does not group merely similar ones. That distinction sounds small, and it’s the whole ballgame, because “similar” is exactly what most people’s clutter actually is.

Here’s what the Duplicates album will quietly walk straight past:

Burst frames and retakes. The eleven shots of the same sunset, taken four seconds apart. As far as iOS is concerned, those are eleven different photos.
An original and its edited version. You cropped it, you bumped the exposure. Now they’re two distinct images.
The same screen, screenshotted twice. A second apart, a pixel of scroll offset between them.
Photos re-encoded by messaging apps. Someone sent your own photo back to you through WhatsApp. It looks identical to you. It isn’t the same file.
The same photo at different resolutions. AirDropped, downloaded, re-saved, exported.

Every one of those reads as an obvious duplicate to a human being. None of them are what iOS is looking for.

So the reframe is this: an empty Duplicates album usually means you don’t have exact duplicates, you have near-duplicates. That’s a different problem, and there is no iOS setting that solves it. You can restart the phone all week. The album is working perfectly and it is never going to find them, because it was never designed to.

How to clear the near-duplicates iOS won’t flag

You have two options, and the first one is free.

Do it by hand. Open Photos, go month by month, and delete the obvious redundancy on sight. This genuinely works for a small library and it costs you nothing. It also collapses completely somewhere around the two-thousand-photo mark, when select mode turns into a tapping endurance test and you lose your place for the third time.

Or use a tool that compares what photos look like. That’s what perceptual hashing does. Instead of matching files, it generates a fingerprint of the visual content of an image, so two shots that look alike score as a near-match even when their files have nothing in common. Which is precisely the category Apple’s album skips.

That’s the gap Swipe44 is built for. It hashes your library on-device and groups visually similar shots so you can compare a whole cluster side by side and keep the one you actually want, and then it hands you the rest of the camera roll as a swipe deck: right to keep, left to mark. Everything you mark lands in a pending pile you review before anything is destroyed, the whole batch goes in one system confirmation, and you get a real freed-space number at the end.

Two things worth being precise about. It runs entirely on-device (no account, nothing uploaded), and it works from thumbnails and metadata, so it never downloads your iCloud originals just to inspect them. If Optimize iPhone Storage is on and you didn’t want to pull 200 GB back onto your phone, that matters. And to be honest about scope: Apple’s Duplicates album is free, it’s built in, and you should use it first. Swipe44 is what you reach for when the album comes back empty and your camera roll obviously isn’t. Grab it here if that’s where you’ve landed.

After you delete: the step everyone forgets

Merging or deleting duplicates does not free up a single byte. Not yet.

Deleted photos go to Recently Deleted, where Apple holds them for 30 days. For that whole month they’re still on your device, still counted, still occupying the same space they did before. Plenty of guides walk you through a merge and then congratulate you on the storage you saved, which you have not actually saved.

To finish the job: Photos → Collections → Utilities → Recently Deleted (Albums → Utilities on older iOS) → unlock with Face ID → Select → Delete All.

Then restart the phone before you read Settings → General → iPhone Storage, because iOS caches that panel and it lies for a while. (There’s a longer post on exactly why the storage number won’t move if you’re stuck on that.)

One reassurance while you’re at it: Merge doesn’t do anything strange to your images. Apple’s documentation is clear that it keeps the highest-quality version and combines the relevant metadata, then moves the rest to Recently Deleted. It doesn’t blend photos together. You’re not going to end up with a composite of your own face.

And set your expectations on the payoff. True exact duplicates are usually a small slice of a library. If the Duplicates album finds forty of them, you’ll get a few hundred megabytes back, not ten gigabytes. The gigabytes are hiding in the bursts, the screenshots and the videos, which is the whole reason the empty-album problem is worth solving properly rather than working around.

Frequently Asked Questions

Why is the Duplicates album missing from my iPhone Photos app?

Either your iPhone hasn’t finished indexing your library yet (that indexing only runs while the phone is locked and connected to power), or iOS genuinely found no duplicates, in which case the album doesn’t appear at all.

How long does the iPhone take to find duplicate photos?

Apple says it can happen quickly or take up to a few days, depending on the size of your library and what else is running in the background. Leave the phone plugged in and locked overnight. On a very large library, give it a few nights.

Why is my Duplicates album empty when I obviously have duplicates?

Because iOS only groups essentially identical items. Burst frames, retakes, edited-versus-original pairs, and photos re-sent through messaging apps look like duplicates to you but not to iOS. An empty album usually means you have near-duplicates, not exact ones.

Does Optimize iPhone Storage stop duplicate detection from working?

It can. Detection works from what’s actually on the device, so a heavily offloaded library may not surface duplicates reliably. Switching to Download and Keep Originals is the usual advice, but only do it if your entire library actually fits on the phone.

Does restarting my iPhone bring the Duplicates album back?

Sometimes, because it re-kicks the indexing job. But it doesn’t skip indexing. You still need to leave the phone locked and on power afterward.

What does Merge actually do to my duplicate photos?

It keeps the highest-quality version, combines the relevant metadata from the set, and moves the rest to Recently Deleted. It does not blend the images together.

Do I need iOS 16 for the Duplicates album?

Yes. Duplicate detection arrived in iOS 16. Older versions have no Duplicates album at all.

How do I get rid of similar photos that the Duplicates album ignores?

You need a tool that compares what photos look like rather than matching files, which is what perceptual hashing does. Swipe44 scans on-device, groups visually similar shots for side-by-side review, and lets you swipe through the rest of your camera roll, batch-deleting everything you marked with a single confirmation.

The short version

If the album is missing: plug the phone in, lock it, and leave it alone overnight. Apple’s indexing only runs under those conditions and can take up to a few days. That’s the fix, and it’s free.

If the album is empty: nothing is broken. iOS found no essentially identical items because you don’t have many, and what you actually have is a camera roll full of near-duplicates it was never built to catch.

Different problem, different tool. More on getting a camera roll back under control over on the blog.

Frequently Asked Questions

Why is the Duplicates album missing from my iPhone Photos app?

Either your iPhone hasn't finished indexing your library yet (that indexing only runs while the phone is locked and connected to power), or iOS genuinely found no duplicates, in which case the album doesn't appear at all.

How long does the iPhone take to find duplicate photos?

Why is my Duplicates album empty when I obviously have duplicates?

Does Optimize iPhone Storage stop duplicate detection from working?

It can. Detection works from what's actually on the device, so a heavily offloaded library may not surface duplicates reliably. Switching to Download and Keep Originals is the usual advice, but only do it if your entire library actually fits on the phone.

Does restarting my iPhone bring the Duplicates album back?

Sometimes, because it re-kicks the indexing job. But it doesn't skip indexing. You still need to leave the phone locked and on power afterward.

What does Merge actually do to my duplicate photos?

It keeps the highest-quality version, combines the relevant metadata from the set, and moves the rest to Recently Deleted. It does not blend the images together.

Do I need iOS 16 for the Duplicates album?

Yes. Duplicate detection arrived in iOS 16. Older versions have no Duplicates album at all.

How do I get rid of similar photos that the Duplicates album ignores?