PhotoFixer

Why Google Takeout Photos Have the Wrong Date

By Josep Mampel Marques, updated

Google Takeout photos show the wrong date because Takeout keeps the date in two places that most apps do not read: inside the original file (only if the camera wrote it there) and in a separate .json file next to each photo. The file's own date becomes the day you downloaded the export. Any photo without a date inside the file, such as a screenshot or a scan, then sorts by the export date. The fix is to copy the date from the .json back into the photo and onto the file date, which is what PhotoFixer does in your browser.

What Google says happens to dates

Google's Takeout help page has two short notes for Google Photos. First, the file's timestamp may change to the download date, while the original timestamp remains in the embedded metadata. Second, extra information goes into a separate JSON file. Both are true, and together they explain almost every "wrong date" complaint:

Which photos end up with the wrong date

What the .json file keeps

Each photo usually has a sidecar named after it, for example IMG_1234.jpg.json or, in newer exports, IMG_1234.jpg.supplemental-metadata.json. The fields that matter for dates are:

The full list of fields, the 0, 0 location values and the truncated file names are covered in Google Takeout JSON files explained.

How to put the real dates back

  1. Download your library with Google Takeout, selecting only Google Photos and the zip format. See how to download Google Photos with Takeout.
  2. Do not unzip anything. Open PhotoFixer and choose all the zip parts at once (takeout-...-001.zip, -002.zip and so on). A photo and its .json can be in different parts, so give it every part.
  3. Choose the time zone where most photos were taken. Google stores the time in UTC and EXIF expects local time, so the zone is used for the conversion and the offset is saved too.
  4. Choose how to arrange folders: by year and month, or keeping the Takeout album folders.
  5. Press Fix my photos. The zips are read and written in the browser tab; nothing is uploaded.
  6. Unzip the result and import it into your photo app or copy it to a drive.

What changes: JPEG photos without EXIF get the capture date, the location and the description from the .json. MP4 and MOV videos get their creation date. Every file in the result gets its capture time as the file date. JPEG photos that already have EXIF keep their own data and only get the fields they lack, and HEIC files are copied as they are with the correct file date.

Other tools that do this

PhotoFixer is not the only option, and sometimes it is not the best one:

Before you delete anything

Check a handful of photos from different years in the destination app before removing the library from Google Photos. Look at a screenshot, an old scan and a video in particular, since those are the files most likely to have had no date of their own.

For the difference between the date inside a photo and the date of the file, see EXIF date vs file date.

FAQ

Does Google Takeout remove the date from my photos?

No. Google says the original timestamp stays in the photo's embedded metadata. What changes is the file date, which may become the download date, and anything Google Photos knows that is not inside the file ends up in a separate .json file.

Why are only some photos wrong?

Photos from a camera or phone usually carry their date inside the file (EXIF), so apps that read EXIF show them correctly. Screenshots, scans and many images saved from apps or the web have no date inside, so apps fall back to the file date, which is now the export date.

Is the time in the .json file local time?

No. The photoTakenTime value is a Unix timestamp, and its formatted text is written in UTC. To turn it into the local time that photo apps expect, you need to know the time zone where the photo was taken.

Sources