In Storage saver, yes. In Original quality, no. Does Google Photos compress images the same way for every file? Not even close. On 2026-07-18 I backed up a 4.13 MB iPhone photo and a 1.78 MB transparent PNG through both settings. Storage saver took 35.1% off the photo and left the PNG completely alone.
| My test, 2026-07-18 | Uploaded | Came back | Change |
|---|---|---|---|
| iPhone photo, Storage saver | 4.13 MB | 2.68 MB at 4032x3024 | 35.1% smaller |
| iPhone photo, Original quality | 4.13 MB | 4.13 MB, same sha256 | untouched |
| Transparent PNG, Storage saver | 1.78 MB | 1.78 MB, same sha256 | untouched |
| Transparent PNG, Original quality | 1.78 MB | 1.78 MB, same sha256 | untouched |
Scope, stated up front: two files, one day, one upload path, backed up from a computer and downloaded again. That is what these numbers prove and nothing more. The rest of this page covers the settings behind those results, why one file shrank and one did not, and what happens to photos you uploaded years ago.
Does Google Photos Compress Images? What My Test Found
Storage saver recompressed my camera photo hard and did not touch my PNG at all. Original quality returned both files byte for byte. That split is the finding, and no page ranking for this question currently reports it.
The two reference files
Every platform in this series gets the same two files, so the results line up across pages. REF-A is a real iPhone photo: 4,332,705 bytes, 4032x3024, JPEG, with its EXIF metadata intact. REF-B is a photographic cutout with real transparency: 1,863,465 bytes, 1240x930, PNG with an alpha channel. One is what a phone produces, the other is what a designer sends, and platforms treat the two very differently.
What Storage saver did to the photo
REF-A came back at 2.68 MB, 35.1% smaller, still 4032x3024 pixels. Nothing was resized. That detail is the useful part: 4032x3024 is 12.2 megapixels, comfortably under the 16 MP ceiling where Google says Storage saver starts shrinking dimensions. So every one of those missing bytes came from a lossy re-encode, not from throwing away pixels. Google recompressed a file that was already a compressed JPEG and found another third of it to remove.
What Storage saver did to the PNG
Nothing. The downloaded file hashed to the same sha256 as the file I uploaded, identical bytes, identical alpha channel. I ran Original quality on both files as a control, and both came back identical there too, which is exactly what Original quality promises.
The lesson generalises across this whole series, which is why I run the same two files through every major platform for the hub on which apps compress your images: the headline setting rarely tells you what will actually happen to your specific file.
Storage Saver vs Original Quality vs Express, Explained
Three backup settings, three different deals between storage space and pixels. Google documents what each one does to dimensions, and my test shows what the middle one does to bytes.
| Setting | What it does to photos | Video | Print size Google claims |
|---|---|---|---|
| Original quality | stored at the resolution you shot, no quality change | unchanged | any size the file supports |
| Storage saver | recompressed; over 16 MP resized to 16 MP; may convert to .jpg | over 1080p resized to 1080p | good up to 24 by 16 inches |
| Express | over 3 MP resized to 3 MP | over 480p resized to 480p | good up to 6 by 8 inches |
Those thresholds come straight from Google's backup quality documentation, which is the most authoritative page on this SERP and also the thinnest. It tells you the megapixel caps and stops there.
The storage saver vs original quality decision in one line
Pick Original quality if the photo is going to be printed large, edited later, or is the only copy you will ever have. Pick Storage saver for the other 95% of a phone camera roll. Express exists for constrained data plans and small screens, and 3 MP is genuinely small, roughly the resolution of a 2007 phone.
Everything counts against your quota now
All three settings consume your shared 15 GB across Google Photos, Drive, and Gmail. The one exception is grandfathered: High quality and Express backups made before 1 June 2021 still sit outside the quota. Storage saver does not make backups free, it makes them smaller, which is a different promise than the one most people remember from the free-storage era.
Why Does Google Photos Recompress Your Photos?
Because storage costs Google money at a scale where a third of every photo adds up. Storage saver is a server-side lossy re-encode tuned so the loss stays below what you notice on a phone screen.
The compression happens after upload, not on your device
Your phone sends the original file, Google's servers do the re-encoding, and the compressed version is what comes back when you download. Your local copy stays untouched until you delete it, which is why people who clear their phone after backing up are the ones who lose the original for good.
Why my PNG came back untouched
Google does not publish a rule for this, and my single test cannot prove one. What is documented is that the pipeline has exceptions: users have reported files stored at original size under Storage saver because of what Google's staff described as exceptional metadata in the file, in a Google Photos community thread on Storage saver skipping compression. That thread is about a particular kind of JPEG, not about PNGs, so treat it as evidence that exceptions exist rather than an explanation of mine. My working read is the simpler one: a 1240x930 PNG is small, already lossless, and there is little for a perceptual JPEG encoder to gain by touching it.
What Google will not tell you
There is no published compression ratio, no target bitrate, and no named codec. Independent testing has landed in the range of 20 to 50% smaller depending on image content, in Zack Apiratitham's investigation into Google Photos compression. My 35.1% sits in the middle of that range, which is a good sign for both numbers. The only editorial before and after measurement that ranks for this query is from 2021 and predates several policy changes, so the field has been running on one four year old data point.
How Much Does Google Photos Reduce File Size?
On my camera photo, by 35.1%, from 4.13 MB down to 2.68 MB with every pixel still in place. On my PNG, by nothing at all. The spread between those two numbers is bigger than the spread most articles report between settings.
| File | Original quality | Storage saver | Reduction |
|---|---|---|---|
| iPhone photo, 4032x3024 JPEG | 4.13 MB | 2.68 MB | 35.1% |
| Transparent PNG, 1240x930 | 1.78 MB | 1.78 MB | 0% |
Compress it yourself if you want the number to be yours
Storage saver decides how much quality to spend on your behalf, once, with no slider. If the goal is a smaller file you control, do it before the upload: run the photo through the compressor at quality 80 and a typical phone photo comes back 60 to 80% smaller with nothing visible lost, which is roughly double what Storage saver achieved on mine. Then back up in Original quality and Google stores exactly what you decided.
Does Google Photos Compress Photos You Already Uploaded?
Only if you tell it to, and then it cannot be undone. The Recover storage tool in Settings converts existing Original quality items to Storage saver across your whole library, and the originals are gone from Google's copy afterwards.
What Recover storage actually does
It is a one way batch conversion, available roughly once per day, described in Google's community documentation on recovering storage. Every Original quality photo and video in the account gets re-encoded to Storage saver quality. There is no revert button and no grace period. If your phone no longer holds the originals, the compressed version is now the only version.
The Drive exception people miss
Items that arrived in your library through Google Drive are explicitly excluded from Recover storage, so a mixed library can end up with two different quality tiers and no obvious way to tell them apart in the interface. Check what you actually have before running it, not after.
What Happens to Resolution, Format, and EXIF Metadata
Resolution survived both settings in my test, format survived both, and metadata is where the honest answer gets shorter than most pages admit.
| Property | Original quality | Storage saver |
|---|---|---|
| Pixel dimensions | unchanged, 4032x3024 | unchanged, 4032x3024 |
| File format | unchanged | unchanged in my test, may become .jpg |
| File size | identical bytes | 35.1% smaller on the photo |
| EXIF metadata | intact, same sha256 | not verifiable from my test |
What I can prove about EXIF and what I cannot
Original quality returned an identical hash, so every EXIF field survived, GPS coordinates and camera model and timestamp included. That is proof, not inference. Storage saver re-encoded the JPEG, and my test compared bytes and dimensions rather than individual fields, so I will not tell you which tags survived that path. Google does not document it either.
Strip the metadata before it leaves your phone
If the GPS point where a photo was taken matters to you, handle it yourself rather than hoping a backup service does. Our compressor strips EXIF by default, the hidden data block carrying coordinates, camera model, and the exact timestamp of the shot, on every file that passes through. Uploading first and worrying later is the wrong order, because the copy in the cloud is already the copy you no longer control.
How to Keep Your Originals in Google Photos
Set the backup quality to Original before the next backup runs, and keep an archive somewhere that is not a photo service. The setting lives in the same place on every platform and takes about fifteen seconds to change.
On the phone
Open Google Photos, tap your profile picture, then Photos settings, then Backup, then Backup quality. Pick Original quality. The change applies to future backups; anything already uploaded in Storage saver stays as it is, because compression only runs one direction. If the quota is what pushed you to Storage saver in the first place, the guide on compressing photos on an iPhone covers shrinking them before they ever reach the backup queue.
On the web
Go to photos.google.com, open Settings from the gear icon, and choose Original quality under backup quality. The same screen shows your storage usage, and the Recover storage button sits close enough that it is worth reading twice before clicking.
Keep the real archive somewhere else
Google Photos and Google Drive have run as independent products since 2019, so uploading to one does nothing to the other, as covered in Google's community guidance on Drive versus Photos. Drive does not apply photo specific compression tiers, which makes it the more predictable place for files you want byte identical. Two copies in two places, one of them not a photo service, is the version of this advice that survives contact with a full quota.
How Does Google Photos Compare to Other Apps?
Google Photos in Storage saver sits in the middle of the platforms I have measured: harder on your files than a chat app, far gentler than a social network. Same photo, same method every time, upload through the standard path and compare the stored copy byte for byte.
| App | Same photo came back | Change | Dimensions |
|---|---|---|---|
| Google Drive | 4.13 MB | untouched, same sha256 | kept 4032x3024 |
| Discord | 497 KB | 0.3% smaller | kept 4032x3024 |
| 3.91 MB | 5.4% smaller | kept 4032x3024 | |
| Google Photos, Storage saver | 2.68 MB | 35.1% smaller | kept 4032x3024 |
| Gmail, inline image | 1.86 MB | 55.1% smaller | kept 4032x3024 |
| 0.57 MB | 86.3% smaller | resized to 2048x1536 |
Two things stand out in that table. Google's own products disagree with each other: the same file that Drive stored untouched lost a third of itself in Photos, which tells you the compression is a Photos product decision and not a Google infrastructure default. And Discord, which barely touched the file, is a chat app nobody thinks of as archival, while Photos, which people trust with the only copy of their children's baby pictures, is the one re-encoding. Every app in this cluster gets its own measured page in the hub.
Common Myths About Google Photos Compression
Most advice on this topic dates from the free-storage era and was never measured. These are the claims I keep meeting, checked against my own numbers and Google's current documentation.
"Storage saver is basically lossless"
It is lossy, and a third of the file is not a rounding error. My photo lost 35.1% of its bytes with no pixels removed, which means the loss was spent entirely on image detail. You will not see it on a phone screen. You may well see it if you crop in hard or print at size. If you want a fuller explanation of what that tradeoff costs, the guide on lossy versus lossless compression covers the mechanism.
"Photos under 16 megapixels are left alone"
Wrong for JPEGs, and my test is the proof: 12.2 MP, no resizing, 35.1% smaller anyway. The 16 MP threshold governs resizing, which is a separate operation explained in the guide on reducing image resolution, not recompression. A photo can keep every pixel and still lose a third of its data.
"Everything gets recompressed the same way"
Also wrong, in the other direction. My PNG came back with an identical hash under the same setting that took a third off my JPEG. Anyone telling you Storage saver applies uniformly to every file has not hashed the output.
"Backing up to Drive protects the Photos copy"
The two products have been separate since 2019. A file in Drive is not a file in Photos, quota is consumed twice if you keep both, and Recover storage skips the Drive sourced items while converting everything else.