3 ms·

If you use Google takeout to export your photos you get a lossy version of the original. IIUC the only way to get the original photo is to click on each indivi

by buro9 3y ago

If you use Google takeout to export your photos you get a lossy version of the original. IIUC the only way to get the original photo is to click on each individual photo in the web app and choose to "Download original", there is no other way. If you do use the Google Takeout approach you will need to re-stitch the JSON and EXIF back together via one of the tools mentioned elsewhere on this page. Lesson: if you care about your photos do not _only_ use Google Photos as the place to store them, put Syncthing on your phone and sync photos directly to your laptop / NAS and treat that as the primary location. Google Photos is a convenient viewer, nothing more.

fifteen1506 3y ago
I think you're wrong. Only those you download via Google Photos API (think: rclone) suffer from that "feature". EDIT: I think Google Photos API "only" strips EXIF. Seen on: https://github.com/daneroo/gphotos-puppeteer https://github.com/daneroo/gphotos-puppeteer
andyjohnson0 3y ago
> If you use Google takeout to export your photos you get a lossy version of the original. I'm fairly sure that, unless something has changed recently, this is incorrect. Last year I went through the process of figuring out how to re-create my photos from a takeout archive. It is frustrating to a level that is almost cruel - mangled/truncated filenames, arbitrarily stripped metadata, unnecessarily ambiguous naming - but the photos themselves always seemed to be original quality. I've recently started using the filters and tools that come with a Google One subscription and I suspect that they're not fully compatible with whatever the storage schema is that takeout is exposing. The relationship between an original image and one edited uaing the filters seems to get lost. I need to dig into this before my next semi-annual photo exfiltration is due. Actually, I just need to stop using google photos...

by buro9 3y ago

fifteen1506 3y ago

I think you're wrong. Only those you download via Google Photos API (think: rclone) suffer from that "feature". EDIT: I think Google Photos API "only" strips EXIF. Seen on: https://github.com/daneroo/gphotos-puppeteer https://github.com/daneroo/gphotos-puppeteer

andyjohnson0 3y ago

> If you use Google takeout to export your photos you get a lossy version of the original. I'm fairly sure that, unless something has changed recently, this is incorrect. Last year I went through the process of figuring out how to re-create my photos from a takeout archive. It is frustrating to a level that is almost cruel - mangled/truncated filenames, arbitrarily stripped metadata, unnecessarily ambiguous naming - but the photos themselves always seemed to be original quality. I've recently started using the filters and tools that come with a Google One subscription and I suspect that they're not fully compatible with whatever the storage schema is that takeout is exposing. The relationship between an original image and one edited uaing the filters seems to get lost. I need to dig into this before my next semi-annual photo exfiltration is due. Actually, I just need to stop using google photos...