I just found out that #GoogleTakeOut has a serious bug when it comes to getting exports of #GooglePhotos libraries.

If at any time in the past you enabled Space Saver your originals are gone forever.

Fair enough, but….

in _some_ cases Takeout won’t even download the good-but-not-great (5-16 megapixel from what I can tell) downscaled versions.

Instead, it downloads 320x200 images, which are useless for anything other than hiding the reality of the situation.

#DeGoogle

I have no idea the scale of the problem for my export but it could be thousands of images that I’m missing in my Takeout. #GoogleTakeOut #GooglePhotos #DeGoogle
And for clarity, in the Google Photos web app, the okay resolutions can be seen. So they exist but are not included in the Takeout export. #GoogleTakeOut #GooglePhotos #DeGoogle

Ugggghhh, the problem is actually much worse. Apparently this is related to file names.

I have tons of photos with the same file name because the files were created with a film negative scanner. There were no file name collisions originally because the scanner software would create a new folder for each scanning batch.

#GoogleTakeOut #GooglePhotos #DeGoogle

All of the files got uploaded and Google Photos could handle the file name collision no problem, the timestamps on the files were different even though the names were the same.

#GoogleTakeOut #GooglePhotos #DeGoogle

Butttttt…..

Google Takeout seems to not handle it. There are countless examples where filename001.jpg has many instances in Google Photos, but Google Takeout only downloaded one (1) of them.

How is this reality?!!?!!

#GoogleTakeOut #GooglePhotos #DeGoogle