Takeout Date Review

Takeout JSON not matching your photo

The date file and the photo do not have the same name. That is common and usually has a simple pattern.

Pattern 1: a longer JSON suffix

Older exports used photo.jpg.json. Newer ones may use photo.jpg.supplemental-metadata.json, and very long names may end in a shortened .supple.json. The date file still belongs to the same photo.

Pattern 2: names cut to a length limit

Google may truncate long file names. A reliable check is the title field inside the JSON; it should name the photo. Do not assume the first N characters are a match — check the title.

Pattern 3: the number moved

A photo name(1).jpg can have its date file named name.jpg(1).json. The number changes position, not value.

Pattern 4: the JSON is broken

A JSON file can exist but fail to parse. That is different from a missing JSON file, and the app keeps these two cases separate.

ObservationWhat it means
No .json next to the photo at allNo JSON date source
.json exists but is unreadableBroken JSON — keep the photo, review separately
Several JSON candidates disagreeAmbiguous — choose one or leave unresolved
JSON title names a different fileTitle conflict — do not auto-apply

What not to do

Takeout Date Review lists every candidate and requires your confirmation for uncertain matches. It never adopts a neighbour's date silently.

See the 30-day trial