JSON sidecars
Photos can have companion metadata files. They are useful evidence, not disposable noise, and should not be mistaken for a second photo.
Evidence guide · Google Photos Takeout
Why is my Google Takeout larger than my library?
A Takeout is not always a folder of one original file per photo. JSON sidecars, edited copies, album paths, and split ZIP parts can make the export look duplicated or unexpectedly large before you have even opened it.
Independent RomeoApps software. It maps a customer-owned export locally, leaves the original files unchanged, and never uploads a photo library.
What changes the size
Separate related files from accidental overwrites.
The size difference is a clue, not a diagnosis. Keep the source export intact while you identify what each path represents.
Edited and repeated paths
Edited representations and album paths can make the same underlying moment appear more than once. Compare content and provenance before choosing a policy.
Split ZIP sequences
Numbered parts must be checked for gaps, unreadable members, and conflicts before a reconstruction is written.
A safer reconstruction
Review the write boundary before anything is combined.
The paid reconstructor turns a messy export into a decision record rather than silently choosing the last file it saw.
- Select the complete ZIP sequence or declare a full export plus later increment.
- Review missing parts, duplicate-looking entries, content conflicts, path collisions, and sidecar matches.
- Choose an explicit keep/skip policy for each real content conflict.
- Write a new reconstruction with CRC/SHA-256 checks and an audit; the source export remains untouched.
Search questions
Questions worth answering before you delete or merge anything.
Why does Google Takeout contain a JSON file for every photo?
Sidecars carry metadata associated with exported media. The correct relationship depends on the export paths and content; do not delete them merely because they are not images.
Can I combine multiple Google Takeout ZIP files?
Yes, when the parts belong to a declared sequence and the gaps, conflicts, and write policy are reviewed first. A tool cannot infer that unrelated exports belong together.
How do I remove duplicates without deleting originals?
Keep the original export immutable, compare exact bytes and provenance locally, and make a new output with an explicit decision record.
How do I reconstruct a Google Photos Takeout locally?
Use the bounded local workflow in Takeout Export Reconstructor; it is designed for ZIP/ZIP64, sidecar history, conflicts, and resumable output.
Scope boundary
Keep your export local and review every write.
- The workflow uses no Google account connection, cloud import, or photo upload.
- Ambiguous sidecar or incremental relationships stay visible for your decision rather than being guessed.
- The original export remains unchanged; you review the new output before using or sharing it.
- Google Photos and Google Takeout are Google trademarks; this is an independent RomeoApps tool.