Google Takeout Photo Organizer
Share tool
Only this public address is included. Your files, inputs and results stay out of the link.
Match exported photos with their JSON sidecars and review which dates to use. Create an organized copy of your selected Google Takeout files.
Preparing your tool…
A visual example
Match first, organise second
The picture and its companion JSON file have different jobs.
- photo.jpgphoto.jpg.json
Review the pair
A photo supplies the pixels. Its JSON sidecar may supply a recorded date; similar names alone need checking.
Confirm the date source Source Role photo.jpg Picture JSON sidecar Date to review Confirm the date source
Check the proposed association and date before creating an organised copy. Resolve ambiguous matches explicitly.
Keep the original export. Only supported JPEG date fields can be written; other media are copied unchanged.
Illustrative example. Synthetic filename example, not a guaranteed match. Exported folders do not promise changed filesystem dates.
How to use it
- Choose a small, complete Takeout batch of media and JSON sidecars, supported ZIP archives, or the example files.
- Compare suggested associations, embedded JPEG capture times, JSON photoTakenTime and filesystem modification times. Resolve conflicting or ambiguous matches.
- Choose unchanged copying, an explicitly confirmed supported JPEG capture-time edit, or exclusion for each file. Choose the date source for folders/names and whether to include original JSON files.
- Review source identities and checksums, then build and confirm the exact plan with paths, collisions and exclusions. Create the ZIP; its contents and changed JPEGs are rechecked. Review the optional migration report and keep the original export.
The example includes an existing JPEG date that differs from its JSON, a numbered name, two competing JSON sidecars and a missing sidecar. Files begin as unchanged copies; no metadata overwrite is chosen automatically.
Details & limits
Up to 200 entries, 10 MiB per medium, 1 MiB per JSON, 30 MiB per ZIP and 60 MiB total. Confirm ambiguous matches and JSON dates. Supported JPEG EXIF dates can be written; other media are copied unchanged. No filesystem date promise.
Which dates and metadata can actually be changed?
Only supported JPEG DateTimeOriginal, OffsetTimeOriginal (+00:00) and SubSecTimeOriginal (0) are written from the confirmed JSON capture time. Other media and unsupported JPEG metadata are copied unchanged. JSON creationTime is never substituted for capture time; GPS and captions are not imported. Dated copies use year/month folders and unique names. Browser downloads cannot guarantee operating-system timestamps. Archive verification covers only the selected readable sources; it does not establish the completeness of a cloud library. SHA-256 verification and the export plan require local workers and Web Crypto; browsers without them retain the clearly marked basic organizer. Limits: 200 selected/extracted entries, 10 MiB per medium, 1 MiB per JSON, 30 MiB per ZIP and 60 MiB combined/expanded input; output at most 64 MiB.