A library archive is not a sharing package
Google Takeout Photo JSON: Review Before Sharing
Google Takeout can deliver photos alongside secondary JSON containing additional library information. Checking a JPEG does not inspect that JSON or the rest of the archive. Keep the complete export private and build a separate sharing folder containing only deliberately selected, reviewed images.
By Qingxin Studio, the developer of HushPic · Updated
Keep the archive intact as a private source
Examine your downloaded export locally. Google distinguishes information embedded in the original photo from additional library information delivered in secondary JSON, including comments. Do not assume every field lives in the image or that every export has identical contents.
Preserve the archive rather than bulk-deleting JSON to make a sharing package. Those files may matter to your own records or migration workflow. This guide does not repair timestamps, merge metadata, or prescribe deleting library data.
Inspect the companion file without uploading it
If JSON accompanies an image you are considering, open that text locally in a trusted viewer. Read the actual fields rather than inferring contents from the extension. Do not paste it into an online repair service or public support request just to identify it.
Treat any names, comments, dates, or locations you actually find according to your audience. This checklist does not claim that every field exists in every export. Keep matching and migration questions separate from deciding what a recipient needs.
Build a destination folder from an explicit selection
Start with an empty sharing folder and copy only selected prepared images into it. Do not copy the whole Takeout directory and rely on removing obvious extras afterward. Check the listing for JSON, originals, alternate versions, videos, and unrelated images.
Use neutral filenames and an expected count. If you need to deliver a preservation archive instead of a few photos, agree on that different scope with the recipient first. A private backup and a public attachment have different requirements.
Check each image, not just its file date
Google explains that a downloaded file’s filesystem timestamp may differ from embedded capture information. A new file date is not evidence that private metadata was cleared. Inspect the exact sharing image’s supported categories and visible details; retain your original export unchanged.
The browser checker reads a selected supported image locally, not archives or JSON. It does not inspect pixels, clean files, or create verified output. HushPic prepares separate supported copies on-device with bounded post-write checks; review suggestions and regenerate after edits. Neither tool audits a complete Takeout archive or certifies a migration.
Sources
This guide is published by Qingxin Studio, the developer of HushPic. Product claims describe our supported workflow, not independent certification. Our review checklists are practical first-party guidance; linked platform sources support only the mechanisms they describe. Automatic checks may miss details. Read our content and corrections policy.