Keepr Everyone takes the same photo several times. Keepr notices, and tidies the view.
What a stack is#
When several near-identical shots end up in the same album, they collapse behind one tile with a count. Your grid shows the moment once rather than eight times, so a burst doesn't push the rest of the day off the screen.
Nothing is deleted. Every copy is still stored, still yours, and still reachable — this is a display decision, not a cleanup.
What you can do with one#
- Open it to see every photo in the stack.
- Pick a different one to sit on top, if Keepr chose the one where someone blinked.
- Split them apart, permanently, if they shouldn't have been grouped. Once split, they stay separate.
- Remove the ones you don't want, from inside the stack, if you actually do want to tidy up.
What gets grouped, and what doesn't#
Only very close matches — the same picture taken repeatedly — and only within one album, around the same time.
That deliberately narrow scope is what makes it safe. Twelve genuinely different photos from one birthday party stay twelve photos. Two photos of the same person on different days stay separate. Keepr compares what the images look like, not who or what is in them, so it isn't grouping by subject.
If something does get grouped that shouldn't be, splitting it apart is permanent — Keepr won't re-group it later.
Stacks still use storage#
Worth being clear, because "duplicates handled" sounds like space saved: it isn't. Every copy in a stack is a stored file using real space. Stacking cleans the view.
If you want the space back, the storage screen shows how much your stacks are using and lets you review them side by side — the same moment shown together — so you can keep the good one and remove the rest with some confidence about what you're doing.
That's usually the second-biggest saving available after removing originals you've finished with.
Before it uploads: "you already have this"#
Stacking happens after photos arrive. There's an earlier check too — when you pick photos to upload, Keepr looks at what you've already uploaded and flags anything that looks like a repeat, before any of it is sent.
You get your existing copy's thumbnail next to the one you picked, which album it's already in, and when you added it. Matches start ticked to skip, and you can un-tick any of them or choose "Upload all anyway".
It's most useful for the situation everyone eventually hits: a folder of old photos where you genuinely can't remember which half you already put in. Rather than opening thousands of pictures to check, you pick the lot and let Keepr point at the ones it recognises.
How it recognises them. Two ways: by when the photo was taken, and by the file's name and size as it sits on your phone. Not by comparing the pictures themselves — Keepr optimises photos as they upload, so the stored copy is never byte-for-byte what left your phone, and it isn't the same size either.
The name-and-size check only covers photos uploaded from 3 August 2026 onwards, because Keepr didn't record filenames before that. Anything older is matched on capture time alone. That matters most for screenshots and pictures saved out of chats, which carry no capture time at all: they are only recognised against uploads made from that date.
That has one consequence worth knowing: it can occasionally be wrong, which is exactly why it shows you both thumbnails and never skips anything on its own. Burst shots taken in the same second look identical to a capture-time check while being different pictures. Glance at the pair and decide.
It also won't catch everything. A photo that came back to you through WhatsApp was re-encoded on the way: new name, new size and usually no date at all, so it arrives looking new. Picking that same file twice is recognised; tying it back to the original you already had isn't — that's the case duplicate stacks are for, after the fact.
Acting on a stack#
When you delete, move or share a photo that's the top of a stack, Keepr asks whether you mean just that photo or the whole stack. Whichever you choose, the rest stay visible — a stack never quietly loses its remaining photos because the top one went somewhere else.