You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
These JSON files contain information that might not be stored in the images, such as descriptions, capture dates, and partner images. immich-go matches each JSON file with its corresponding image and enriches Immich with the collected information. When the JSON file corresponding to an image is not found, immich-go skips it, unless forced by an option.
The main causes of this problem are:
1. The takeout is split into several parts, and only one part has been processed
Related JSON files might be stored in another part and can therefore be found. Process all takeout parts together.
Use /path/to/your/files/takeout-*.zip as the file name.
2. The takeout is incomplete
Large photo collections are voluminous. Sometimes, files are left out and not included in any takeout part.
To minimize this problem, request partial takeouts:
Process by album or a few albums at a time
Process by year
Select the largest chunk size: 20GB
3. The JSON files are strangely named
The rules Google uses to name JSON files may change, or there might be unforeseen edge cases.
Check your zip file for potential candidates for image-JSON pairs and open an issue with your findings.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
The final report shows many missing JSON files
These JSON files contain information that might not be stored in the images, such as descriptions, capture dates, and partner images.
immich-go
matches each JSON file with its corresponding image and enriches Immich with the collected information. When the JSON file corresponding to an image is not found,immich-go
skips it, unless forced by an option.The main causes of this problem are:
1. The takeout is split into several parts, and only one part has been processed
Related JSON files might be stored in another part and can therefore be found. Process all takeout parts together.
Use
/path/to/your/files/takeout-*.zip
as the file name.2. The takeout is incomplete
Large photo collections are voluminous. Sometimes, files are left out and not included in any takeout part.
To minimize this problem, request partial takeouts:
3. The JSON files are strangely named
The rules Google uses to name JSON files may change, or there might be unforeseen edge cases.
Check your zip file for potential candidates for image-JSON pairs and open an issue with your findings.
Beta Was this translation helpful? Give feedback.
All reactions