What to Do With Thousands of Photos in Google Photos
· 4 min read
If you have thousands of photos sitting in Google Photos, don’t organize them. Don’t make more albums. Don’t buy more storage and promise to sort it “someday.” The reason those photos feel like a weight is not that they’re disorganized — it’s that none of them have been chosen. The fix isn’t more sorting. It’s subtraction: finding the small number of images that actually matter and turning them into something you can hold. Everything below is how to do that without spending a weekend you don’t have.
First, stop treating this as a storage problem
Google Photos is very good at keeping everything. That’s the trap. When keeping everything is free and takes no effort, you never decide, and a memory you never decide about slowly stops being a memory at all. It becomes inventory.
A camera roll is not a memory. It’s a pile. Ten thousand photos is proof that something happened, but proof isn’t the same as remembering. You remember a handful of images. The rest are quietly disappearing — not because Google will delete them, but because you will never look at them again.
So the goal is not to manage the pile. The goal is to get the real book out of it.
The book already exists in your photos. You’re not going to create it. You’re going to find it.
The reason you’re stuck (it isn’t laziness)
You’ve probably tried. You opened Google Photos, felt the scroll go on forever, and closed it again. That’s not a discipline problem. It’s a design problem: there are too many choices, no one is deciding with you, and nothing forces the project to ever end.
What you’re missing isn’t an app. It’s an editor and a deadline. An editor makes the hard cuts so you don’t have to agonize over each one. A deadline makes the book finish instead of drifting for another three years. Hold onto that — it’s the whole game.
The one test that does all the work: “Would you miss it?”
Forget “is this a good photo.” Good photos are the wrong filter — they leave you with 900 technically-fine images and no book.
Ask instead: remove this photo — does the memory get worse?
If the year, the trip, or the person survives without it, it doesn’t belong in the book. If cutting it leaves a real hole, keep it. That’s the Would you miss it? test, and it’s brutal on purpose. It’s the difference between a considered book and a data dump with a cover.
Most people are shocked how few photos pass. That’s not a failure. That’s the book revealing itself.
Find, Cut, Finish: a method that actually ends
Find — Pick one story, not “everything.” Not “my whole life in Google Photos.” One story your photos already tell: last year, one trip, one child’s early years, your parents before you were born. A book needs a spine. “Everything” has no spine, which is exactly why “everything” never gets made.
Cut — Run the Would you miss it? test hard. A useful working ratio: a beautiful 40–80 page book holds roughly 60–120 images. If you’re starting from 3,000, you are keeping around 3%. Say that out loud — you’re cutting 97% — and the task suddenly feels possible, because you’re no longer trying to honor every photo. You’re trying to keep the ones you’d miss.
Finish — This is where every DIY attempt dies. The photos get roughly chosen, the file gets half-built, and it sits. Finishing means committing to a version, printing it, and putting it on a shelf — the shelf test: would this earn a place on your shelf, or in a drawer? A finished, imperfect book beats a perfect one that never exists. Every time.
A worked example
Real numbers make this concrete. A family exports a year from Google Photos: 3,240 photos.
- Cut every duplicate, blurry, screenshot, receipt, and near-identical burst → down to ~600.
- Keep one frame per moment, not five → down to ~180.
- Run Would you miss it? on those 180 → 74 images.
- Arranged into 9 chapters (roughly a season and a few key events each) → a 48-page book.
Nobody misses the other 3,166. They were never the memory. The 74 are.
What to do this week (if you do nothing else)
Open Google Photos, pick one story, and make a single album of the images you’d genuinely miss — cap it at 100. Don’t caption, design, or perfect anything. Just find the ones that matter. You’ll have done the hard 90% of the work, and you’ll have felt, for the first time, that the book was in there all along.
Questions people ask
- Should I delete the rest of my photos?
- No. Keep the archive — storage is cheap and there's no reason to destroy anything. Just stop mistaking the archive for the memory. The archive is the raw material. The book is the memory.
- Is it worth paying for more Google storage?
- If it buys you peace of mind, sure — but understand what it does and doesn't do. More storage keeps more photos safe. It does nothing to turn them into something you'll actually revisit. Those are two different problems.
- How many photos do I actually need for a book?
- Fewer than you think. A strong 40–80 page book runs about 60–120 images. Beyond that, books get heavy and lose their edit. Restraint is what makes it feel considered.
- What if I can't decide what to cut?
- That's the normal state, and it's exactly the thing an outside editor solves. Deciding with someone is far easier than deciding alone in front of an endless scroll. It's the entire reason this project stays unfinished for most people.
- Can't Google Photos just auto-create a book for me?
- It can auto-assemble one, and it will feel auto-assembled — everything included, nothing chosen, no story. Automatic selection optimizes for "included," not for "would you miss it." Those produce very different objects.