Check on your computer.
The proposed tool reads an unpacked folder locally. No account connection. No uploading your photo library to us.
LEAVING GOOGLE PHOTOS?
Good memories.
Messy exit.
Let’s change that.
A downloaded archive shouldn’t become another project. We’re exploring a browser-local check that helps you understand your Takeout export before you move it.
2-minute research form · No photo uploads · No payment
MEMORIES, NOT JUST FILES.
Make sense of the mess.EXAMPLE
Dates already present1,240
Missing dates to review86
Uncertain matches12
SYNTHETIC DATA · NOT A WORKING SCAN
Less guesswork.
More keeping.
More keeping.
NOT A RELEASED TOOL
We’re testing the need first. Your experience will decide what gets built.
A SMALL INTERACTIVE THOUGHT EXPERIMENT
Same memory.
A little more clarity.
What if your archive told you what it knows—and what it doesn’t? Explore three made-up cases. No files are read or repaired.
THE LONG WAY HOME / SYNTHETIC EXAMPLE
The illustration stays identical. Only the example metadata changes.
ONE CLEAR MATCH
A date in the wrong place.
In this example, a JPEG has no embedded date. One matching JSON sidecar contains a capture date.
Keep the original. Change only what’s clear.
Is this your kind of mess? Tell usTHE IDEA WE’RE TESTING
Before you move it,
make sense of it.
For people with an already-unpacked Takeout export—especially a large one. Planned first for desktop Chrome and Edge.
Separate facts from guesses.
Distinguish embedded photo dates, JSON dates, missing dates and uncertain matches. Existing dates shouldn’t be overwritten blindly.
Only fix what’s clear.
A possible first release would create repaired copies of supported JPEGs. Videos, HEIC and Live Photos would stay out of scope.
A local check can inspect what you downloaded. It cannot prove that every cloud photo was exported. Large-library performance is still unverified.
HELP SHAPE THE FIRST VERSION
What made
your move
harder?
Tell us about the task you’re actually trying to finish—not the features you think we want to hear about.
Already found a solution?
We’d like to hear that too.
Independent early-stage project.
Not affiliated with Google.
RESPONSE SAVED
That’s useful.
Thank you.
Your experience helps us decide whether this deserves to exist. No tool or launch date is promised.
Your deletion receipt
Keep this receipt if you want to remove your response later. It isn’t emailed automatically.
A FEW STRAIGHT ANSWERS
Before you ask.
Can I use the tool now?
No. This is a research page, not a launched product. The preview is illustrative. We’re checking whether an install-free workflow solves a real problem before developing a full repair tool.
Does Google remove all my photo dates?
No. Google says timestamps embedded in original files are retained. Downloading can change operating-system file timestamps, and additional metadata may be stored in JSON files. These are different things. Read Google’s explanation ↗
Why not use an existing tool?
You may not need a new one. Free and paid alternatives already exist. We’re investigating whether checking a large export in a browser, without splitting batches or installing software, would be meaningfully easier. That isn’t established yet.
What information does this page collect?
Your form answers and optional email are sent to our server. No photos, filenames or Google account access are requested. We also count page loads, form starts and saved responses by campaign, without analytics cookies or stored visitor IP addresses. Page loads are not unique visitors. Hosting providers may retain operational access logs.
Answers and campaign counts are retained for up to 90 days. If you provide an email and consent, it is used only for this research and early-test contact. Your deletion receipt lets you remove your response using the “Delete my response” button; save a copy because we don’t email it automatically. Aggregate counts do not identify your response.