Preserve Photo Timestamps After a Google Takeout Export

You export your Google account with Takeout, unzip the archive, and open your photo library. Photos from 2014 show up as taken last Tuesday. Your vacation pictures are sorted by the day you downloaded them. The images are all there, but the dates are wrong, and a photo library with the wrong dates is hard to use.

This happens to a lot of people, and it usually isn't one single bug. It's several small things that each touch a date and quietly change it.

Where a photo's date actually lives

A photo can carry its date in more than one place, and different programs read different ones:

• Embedded metadata (EXIF). The date the camera or phone wrote inside the image file itself. Most photo apps prefer this when it exists.
• File system timestamps. The created and modified dates your operating system attaches to the file. These are easy to overwrite by accident.
• Archive entry timestamps. A zip stores a modified time for each file it contains. What happens to that time on extraction depends on the tool.
• Sidecar files. Takeout exports often include separate JSON files next to your photos, holding information like when the photo was taken. If the photo and its JSON get separated, or you only keep the image, that information goes with the JSON.

The first rule of preserving timestamps is to know which of these a given photo actually has. A photo with intact EXIF data will survive most mishandling. A screenshot, a downloaded image, or an edited export may have no EXIF date at all and rely entirely on file timestamps.

How timestamps get lost

Most date problems come from ordinary file handling:

• Copying instead of moving. Many copy operations give the new file a fresh created date.
• Extracting nested zips with a tool that ignores stored times. Takeout often produces several zips, sometimes with folders inside them. Each round of extraction is another chance to reset dates.
• Re-zipping and re-uploading. Repackaging a folder with a tool that doesn't carry timestamps over loses the dates again.
• Editing and re-exporting. Opening a photo in an editor and saving it can strip metadata or replace it, depending on the app and its export settings.
• Sorting scripts and sync tools. Anything that rewrites files, even just to rename them, can touch the modified date.

None of these feel risky when you do them, which is why the damage usually shows up later, after you've deleted the original export.

Duplicates make the problem worse

A Takeout export of a big photo library tends to contain duplicates. The same photo can appear in an album folder and in a by-year folder. A photo you edited or re-exported may sit next to the original under a different filename.

Cleaning these up by hand, or with a tool that only compares filenames, creates a timestamp risk. Filename matching misses renamed copies and can lump together different photos that happen to share a name, like IMG_0001.jpg from two different phones. If you delete the wrong copy, you may keep the one with the wrong date.

Comparing the contents of the files avoids this. Two files with identical content are true duplicates no matter what they're called, and you can decide which to keep on purpose rather than by accident.

A manual approach

If you want to handle this yourself, here is a reasonable order of operations:

1. Keep the original Takeout zips untouched until you've verified the result.
2. Extract with a tool that preserves modified times, and spot-check a few old photos afterward.
3. Check dates in two places: the file's properties and a photo app that reads EXIF.
4. Identify duplicates by content, not filename, before deleting anything.
5. When repackaging, use an archiver that stores timestamps, then extract a small sample from the new archive to confirm the dates held.

This works, but it's slow across tens of gigabytes and thousands of files, and each step is a chance to make a mistake.

How Takeout Champ handles it

Takeout Champ takes a Google Takeout export, or any zip, folder, or batch of files, and turns it into an organized archive with duplicates removed. Preserving original timestamps and metadata is part of how it works, not an add-on.

In practice, the process looks like this:

• It sorts files into categories: Photos, Videos, Gmail, Contacts, Calendar, Documents, and Audio.
• It finds true duplicates using content-based fingerprinting, so renamed or re-exported copies are caught and not just files with matching names.
• It remembers duplicates across sessions, which helps if you process an export in several batches.
• It preserves original timestamps and metadata through the process.
• It flags files it can't process, so nothing disappears silently.
• It repackages everything into a clean, organized zip.

All scanning and hashing happens locally in your browser. Your files are never uploaded. The only thing that persists is a small local fingerprint of each file (a hash plus metadata, not the file itself), and you can clear it whenever you like. It's free for up to 3GB, and you don't need an account.

That local processing matters for a photo archive. A Takeout export often holds years of personal photos, emails, and contacts, which is not something most people want to hand to another service just to find duplicates.

Verify before you delete anything

No tool replaces checking the result. After processing, open a handful of old photos, ideally some from different years and different sources, and confirm the dates look right. Keep your original export until you're satisfied.

If you're staring at a pile of nested zips and want the dates to survive the cleanup, Takeout Champ is built for that job.