Takeout Date Review

Why your Google Takeout photo dates look wrong

A photo can show three different dates depending on where you look. Most of the time this is not a sign that the date was lost.

1. File modified time (the one Windows shows first)

When you download Takeout, the files are created again on your PC. Windows may list "Date modified" as the download date. This is not the capture date, and it is not used by this app as a photo date.

2. Camera date inside the JPEG (EXIF)

Many cameras write the capture time into the photo itself, usually with a separate UTC offset. Google's export does not strip every EXIF field; whether a photo still has its original camera date depends on how it was uploaded and processed.

3. Google's date in the JSON sidecar

Takeout usually comes with a small JSON file next to each photo. Its photoTakenTime value is a UTC timestamp, which Google keeps for the library. This is often the most reliable date after a messy migration — but the time zone still matters when you display it.

What you seeWhere it comes fromGood for capture date?
Date modifiedDownload/copy timeNo
Camera dateEXIF in the photoYes, if present
Google dateTakeout JSONUsually, with the right time zone

When you do not need to fix anything

No tool can know which date is "truly" correct if two dates disagree. The safest approach is to look at both and decide, rather than accept a global rule.

How Takeout Date Review helps

It separates the cases above, shows the camera date next to the Google date, and only writes copies after you choose. See the download page for the 30-day trial.

Sources: Google Photos Help, "How Google Photos manages photo dates and locations" (support.google.com/photos). Images on this site are synthetic demo files, not personal photos.