
The JSON files in a Google Takeout photo export can carry additional Google Photos information that was not part of the original image file. They are not extra photographs, and their presence does not mean the JPEG is broken. Keep the intact export as your archive, then prepare a separate, documented set of images for editing. Do not delete companion files merely because an image editor does not display them.
Key Takeaways
- Embedded original metadata and extra Google Photos metadata are different layers.
- Your computer’s file date can reflect downloading rather than photographing.
- Preserve the archive before renaming or importing a working subset.
Understand the three places a date may appear
Google’s Takeout download guidance distinguishes metadata embedded in the original file from additional information, such as Google Photos comments, downloaded in a secondary JSON file. It also warns that the operating system may assign a new timestamp to the file when it is downloaded.
Consequently, a recent Modified or Created date in a desktop file browser does not automatically show that Google rewrote the photographed event’s date. Inspect the actual image metadata and accompanying information before changing anything. For historical scans, the event date and scan date guide adds another distinction: digitizing an old print and photographing the original event happened at different times.
Preserve the exported relationship
Keep the downloaded archive and its extracted folder structure in a retained location before preparing an editor’s delivery. Work on a copy of the specific photographs needed for the assignment. Avoid renaming all photos first and trying to match JSON later from memory. A shared subject or similar timestamp may not uniquely identify an edited derivative or duplicate.
Create a small handoff record with the source relative path, working filename, and any relevant caption or date decision. This record is an editorial aid, not a claim that every Takeout export uses one universal naming pattern. The portable filename guide helps when a destination cannot accept the source’s original path or characters.
Send useful context without the whole private archive
An editor may need the chosen image and a confirmed caption, but not every private comment attached to the family library. Review the specific JSON information before sharing it. Supply the minimum context needed for the job in a readable brief, while retaining the full unmodified export privately.
Location also deserves a separate check. Do not assume that leaving a JSON file behind removes coordinates already embedded in the image. Follow the location metadata export check on the actual delivery file when location disclosure matters. Conversely, deleting image metadata does not prove that every associated private note disappeared from all companion files.
Verify the destination instead of assuming automatic import
Open the working images in the intended application and check a few representative subjects, rotations, and captions. If the application advertises a particular sidecar importer, evaluate its documented supported format before using it on a copy. A generic JSON extension alone does not establish compatibility. This guide does not provide a universal merge command.
Finish by retaining both the archive and the small handoff record. The archive preserves what was exported; the working folder contains the material approved for this edit. That separation gives a later collaborator a clear way to trace an image back to its source without treating download dates, embedded capture metadata, and Google-added context as interchangeable.
Related tasks
- How Do I Date Scanned Family Photos When Every File Says Today?
- How Do I Check a Photo for Location Metadata Before Sharing It?
- Why Does My Artwork Package Work Here but Fail on the Recipient’s File Path?
Sources and scope
- Google Account: How to download your Google data: Operating-system download timestamps, preserved embedded original metadata, and secondary JSON for additional metadata such as Google Photos comments.
Based on the complete supplied Google Takeout capture, reviewed October 29, 2026. No export was requested, no JSON merger was tested, and no universal sidecar import support is claimed.
Prepared by Imagild Editorial, the company editorial team responsible for these guides. AI assisted research and drafting. This is documentation-based guidance with proposed examples, not a claim of hands-on testing or an independent product review. Report a correction.
Cover: AI-generated conceptual editorial illustration; not a real application screenshot, observed output or before-and-after test.