Google Takeout JSON files: what they are and why you should not delete them
When you download a Google Photos library through Google Takeout, you may find photos, videos, and many .json files next to them. Those files are not junk: they may hold dates, descriptions, album context, location information, and other data that explains how the media was organized in the original account.
Microsoft Store will be the recommended path once the link is available. The classic installer remains available from the site.
Unsigned .exe noticeThe .exe installer is not signed yet. Windows or the browser may show warnings during download or installation. If you prefer to avoid those messages, use Microsoft Store when the link is available.
Short answer
A Google Takeout JSON file acts like a sidecar: an auxiliary file that travels with a photo or video. In many archives, part of the information you saw in Google Photos is not embedded inside the JPG, HEIC, MP4 or MOV file, but exported beside it.
Deleting JSON files before reviewing the export can turn a simple migration into a library with wrong dates, missing descriptions, and videos that sort incorrectly.
Why these files appear
Cloud services can store metadata outside the original file. That works while the media stays inside the platform, but it becomes a migration problem when you download everything and rely on programs that read only embedded metadata.
In practice, you get folders with similar names: a photo, a video, and a JSON file that may describe one of them. The hard part is matching each sidecar to the right media file, interpreting time fields and documenting what was applied.
What not to do
Do not delete JSON files right after download. Do not rename the whole export before understanding file relationships. Do not import only the images into another cloud service if date order matters. Avoid irreversible batch tools on the original archive until a sample is verified.
- Keep the original export untouched in a separate folder.
- Test with a small group of photos, videos and different albums first.
- Review dates, descriptions and duplicate decisions before processing everything.
How MetaVault Studio uses JSON sidecars
MetaVault Studio works locally: it scans folders and subfolders, finds compatible sidecars, applies metadata when the match is safe, and generates a CSV report for review. If a match is ambiguous, the case should remain visible instead of silently contaminating the output.
That matters for large libraries because the goal is not just editing one image. The goal is rebuilding a verifiable archive with documented decisions.
Where this fits in MetaVault Studio
The app workflow is designed to import a folder, apply metadata with a report, and keep problem cases visible for review.
Related guides
Common questions
Can I delete JSON files later?
Only after confirming the metadata you need has been applied or archived. For important libraries, keep a copy of the original export.
Does every JPG need a JSON file?
Not always. Some files already contain enough embedded metadata, while others rely on the sidecar to recover the date seen in Google Photos.
Does the process upload my photos?
No. MetaVault Studio processes media locally; online services are used for licensing, purchase and support when you choose those flows.
Source and transparency
Also review Google's official help for exporting Google Photos. MetaVault Studio is an independent tool; Google Photos, Google Takeout, OneDrive, and Microsoft are trademarks of their respective owners. Official Google Photos help.