Jul 1, 2021
Storage Saver doesn't compress uploaded image to 16MP
1. my storage settings is Storage Saver (High Quality).
2. i have image (6000*4000, 24MP, 13.1Mb), i upload it using Chrome into Google Photos.
3. i expect that Google Photos compress it to 16MP as it described in the Docs.
4. BUT after i download uploaded image - i see that it has original size, resolution.
5. also i downloaded old files with 24 MP (uploaded before 01.06.2021) and they also have not compressed resolution.
so GP didn't compress my image and i don't have understanding about the reasons.
i repeated my experiment using Android-app - same result.
i repeated my experiment using web and another empty GP account - same result.
please help,
thanks!

Informational notification.
This question is locked and replying has been disabled.
Community content may not be verified or up-to-date. Learn more.
Jul 20, 2021
Google have advised that
- In some circumstances, certain photos and videos may not be able to be compressed and will be stored at their original file size.
A couple of workarounds if required.
- Use a utility to remove the MPF tags from the photos
- Batch convert using https://www.faststone.org/FSViewerDetail.htm
- I personally batch convert to 16MP before uploading at Storage Saver
- Picasa and IrfanView both have batch export functions and all three do not retain the MPF tags in the output file, but do retain all the core Exif and GPS data.
Marked as Recommended to highlight this reply, this is not an Answer
For those asking what can be done to raise the priority with Google support, If you have any thoughts about this behaviour please reach out to Google using the feedback option--> Leave Feedback (click here to see full article)
We are advised that this feedback goes directly to the Google development team and is used in management reports to drive the roadmap for new or modified features.
Unfortunately it is a one way process.
Last edited Jun 18, 2022
Diamond Product Expert PeteranDi recommended this
Helpful?Upvote Downvote
All Replies (25)
Jul 3, 2021
Hello Sergey,
Welcome to the Google Photos Community.
I would like to apologise because this appears have slipped through the net. Is it possible to share a link to that photo so that I can try to replicate the problem.
Thanks,
Peter
Jul 21, 2021
> Use a utility to remove the MPF tags from the photos
maybe you know some example of such utility? can it work with photos in batch?
> Batch convert using https://www.faststone.org/FSViewerDetail.htm
don't have experience in comparing the quality/filesize between Google-made compression vs FSViewer (or alternative). do you have some notes? Google said that their approach as much as possible effective in getting smaller filesize with the best visual quality
Last edited Jul 22, 2021
Jul 21, 2021
@Sergey
I use ExifToolGUI which is a fairly easy utility with pre-set batch commands that unfortunately do not include removing the MPF tags. One of our German colleagues advises that there is a command line method which I have asked for details about.
FastStone has a Batch convert mode which is infinitely customisable and can be set up to re-use the same quality settings as the original. Quality is subjective, but I use Google Photos for viewing and sharing and find that a wide variety of settings has absolutely no visible affect. I upload at Storage saver after passing through FastStone
Picasa and Irfanview both have batch export functions and all three do not retain the MPF tags in the output file, but do retain all the core Exif and GPS data.
Jul 21, 2021
Jul 23, 2021
Jul 28, 2021
Last edited Aug 2, 2021
Aug 1, 2021
Aug 16, 2021
Last edited Aug 16, 2021
Sep 6, 2021
Sep 6, 2021
Last edited Sep 7, 2021
Sep 28, 2021
Dec 14, 2021
I've been working with Google support for months and provided endless examples, links, originals, re-uploads, logs, screenshots, various sources, tests, using their apps and web browsers drag/drop..etc..etc..etc..
The amount of storage space Google must be waisting as so many of my old photo's uploaded during the 'free' storage' periods are still stored in full 42MP sizes consuming over 10x the space (a conservative estimate, example included below)
I also have images that are saved 4 times in various quality's some the same when Google switched between Picasa, Google Photo backup, Backup and Sync...etc and some are Duplicated due to very minor EXIF modifications which I'm surprised Google has not to address as they re-upload based on a minor change such as adding a star rating to an image, adding a person name or correcting the location data... Google should track the image data and not the entire file including EXIF before uploading I believe to track changes correctly and if needed simply update only EXIF data if the image data has not changed )..
To give you an idea if I look at a sample 42MP image, the original JPG size is 31.7MB but when uploaded to Google it should be getting resized to 16MP with an approx size of 2.2MB that's a 14.4x storage saving for this file. Essentially means customers who select the resize option are potentially being overcharged by approx 14x due to the resize bug, as well as the re-upload bug, also mentioned above with minor EXIF changes!
P.S. MFP JPEG files are very common and used by all the top camera manufacturers nowadays so why Google is not supporting this still after so many years I do not understand... I've not found any other applications that don't support it other than Goolge Photo's having this resize issue... Please help escalate this as I've gone in circles with Google Support...