Why Google Takeout Photo Dates Look Wrong After Export
See why Google Takeout exports can separate metadata into JSON sidecars and how that changes what other apps show after extraction.
Tested against the current IMGLoader workflow and provider UI available as of March 29, 2026. Where platform rules or API limits affect results, this guide calls them out explicitly.
A common complaint about Google Takeout is that the photo dates look wrong after download. Usually the original media is still there, but the metadata workflow changed underneath you: other apps are reading file timestamps or embedded metadata while some Google Photos details are sitting in separate JSON sidecar files.
If you expected a straightforward folder of photos and instead got media plus matching JSON files, this is the mismatch you are seeing.
Why the dates feel wrong after extraction
Many apps only look at the media file itself or at the file system timestamp you see after extraction. If some of the descriptive or time-related data lives in a separate JSON file, the receiving app may not re-associate that information automatically.
That creates the impression that Google changed the photo dates, when the more accurate description is that Takeout packaged metadata in a way your next tool may not be reading.
How IMGLoader changes the export experience
IMGLoader is not a Takeout clone. It is designed for selected media exports, not full-account archive packaging. That means the output is a direct ZIP of the files you chose rather than a Takeout-style archive built around sidecar JSON and delayed processing.
If your main problem is "I need selected photos in a clean ZIP that another tool can work with immediately," that is exactly where IMGLoader feels better than Takeout.
When Takeout is still the right call
If your goal is a broad account archive and you want Google's own export packaging, Takeout is still valid. The point is not that Takeout is broken. The point is that it produces archive-oriented output, and archive-oriented output is often inconvenient when your next step is immediate reuse.
How to troubleshoot a confusing Takeout archive
- Look for matching JSON files beside the media and confirm whether the metadata you expected lives there.
- Check whether your receiving app reads sidecar metadata at all.
- Separate "wrong displayed date" from "missing media" because they are different problems.
- If you only need a working batch of selected files, rerun the job with IMGLoader instead of rebuilding the whole archive workflow.