No. Does Google Drive compress images at all? On 2026-07-18 I uploaded a 4.13 MB iPhone photo and a 1.78 MB transparent PNG to Drive, downloaded both, and got back files with the same sha256 hash as the originals. Not similar. Identical. Drive stored my bytes and handed them back untouched, which is the cleanest result anywhere in this test series.
| My test, 2026-07-18 | Went in | Came out | Change |
|---|---|---|---|
| iPhone photo (JPEG) | 4.13 MB, 4032x3024 | 4.13 MB, 4032x3024 | 0%, byte identical |
| Transparent PNG | 1.78 MB, 1240x930 | 1.78 MB, 1240x930 | 0%, byte identical |
| EXIF metadata | present | present | untouched |
Scope, before anything else: that is two reference files, one day, one account, through a direct web upload and a direct download. It does not cover every path into Drive, and the mobile app has its own setting that changes the answer. Both of those live further down, with the same honesty.
Does Google Drive Compress Images? The Measured Answer
It does not, on the path most people use. Two files, two formats, one with an alpha channel and one with a full EXIF block, both came back with hashes matching the originals, which is a stronger statement than "roughly the same size."
The two reference files
Every platform in this series meets the same two files, so the numbers line up across pages. REF-A is a real iPhone photo: 4,332,705 bytes, 4032x3024, JPEG, EXIF intact. REF-B is a photographic cutout with real transparency: 1,863,465 bytes, 1240x930, PNG with an RGBA alpha channel. Using one pair of files across a dozen apps is the only way to say Drive is gentler than Google Slides without hand waving, because the input is identical in both tests.
What byte identical actually means
A file size that looks the same is not proof. Two JPEGs can both read "4.13 MB" in a file browser and differ by a re-encode that quietly cost you detail. A matching sha256 hash cannot happen by accident: every byte is in the same place, which means no re-encode, no rescale, no metadata rewrite, no format normalisation. Drive treated my photo the way it treats a spreadsheet or a zip file, as an opaque blob to store and return.
That matches what Google's own product experts say in the Drive help community, where the answer to this exact question is that photos in Drive are "saved as they are" with image quality unchanged, per the Google Drive Help Community thread on uploaded photo quality. My hashes are the version of that claim you can verify.
What this result does not prove
It does not prove every route into Drive behaves this way. It does not cover the mobile app's own upload setting, and it says nothing about what Google Photos does to a photo that later shows up in your Drive storage quota. Those are different products sharing one storage pool, which is where most of the confusion on this topic comes from. Every app in this series gets the same treatment on the hub for which apps compress your images, and the honest version of each result includes what it leaves out.
Does Google Drive Compress Photos Uploaded From a Phone?
It can, if you leave one setting on. The Drive mobile app ships an optional upload toggle that shrinks photos on their way up, and it is the single biggest reason people arrive at this question convinced Drive compressed something.
The Google Drive compress photos setting on mobile
The Google Drive compress photos setting lives in the mobile app under Settings, then General, as a toggle labelled something close to "Compress photos." Turn it off and the app uploads the file as it is. Leave it on and the app hands Drive a smaller file, at which point Drive stores that smaller file faithfully, exactly as it stored mine.
That distinction matters more than it sounds. The compression happened on your phone before the upload, not on Google's servers after it. Drive is still not the thing that touched your photo. The fix is documented in the Google Drive Help Community thread on photos being compressed on upload, which is the same source Google's own AI summary cites for this query.
Why the toggle exists at all
Mobile uploads happen on cellular data, often on a weak signal, and a 4 MB photo is a slow and expensive thing to push through a bar and a half of LTE. A pre-upload shrink is a reasonable default for a phone. It is a bad default for anyone using Drive as an archive, and Google never tells you which one you are.
My test ran through a direct web upload, so the toggle was not in play. If you have only ever uploaded from the Drive app and your files came back smaller, that setting is the first place to look, not a server side compressor that does not exist.
Google Drive vs Google Photos: Which One Actually Compresses
Google Photos compresses. Google Drive does not. Nearly every "Drive ruined my photo" story is a Photos story wearing a Drive costume, because the two products bill against the same storage quota and people reasonably assume they are the same service.
Here is the same test through both, same day, same file:
| Google product and path | 4.13 MB photo came back | Change |
|---|---|---|
| Google Drive, direct upload | 4.13 MB, byte identical | 0% |
| Google Photos, original quality | 4.13 MB, byte identical | 0% |
| Google Photos, storage saver | 2.68 MB | 35.1% smaller |
| Google Slides, inserted in a deck | 937.8 KB, resized to 2048x1536 | 77.8% smaller |
Storage saver is a Photos setting, not a Drive setting
Photos has a backup quality choice: original quality stores what your camera made, storage saver re-encodes it smaller. On storage saver my photo lost 35.1% of its bytes while keeping all 4032x3024 pixels, so the loss came out of fine detail rather than resolution. The tiers and what each one costs you are documented in Google's backup quality reference for Photos. There is no equivalent control anywhere in Drive, because there is nothing for it to control. The full Photos measurement lives on my measured Google Photos result.
Recover storage does not touch Drive uploads
Photos also offers a "recover storage" action that converts existing original quality items to storage saver in bulk. It is the closest thing Google has to a button that retroactively compresses your library, and Google states plainly that it does not alter items uploaded through Drive, per the Google Photos Help thread on recovering storage. Drive files are outside its reach. That is a useful boundary to know if you keep masters in Drive and casual shots in Photos.
What Google Drive Changes: File Size, Dimensions, Format, and Metadata
Nothing, on the measured path. Four properties, four unchanged results, which is a short table because there is genuinely nothing to report.
| Property | What my 2026-07-18 test found |
|---|---|
| File size | 4.13 MB in, 4.13 MB out, identical hash |
| Pixel dimensions | unchanged at 4032x3024 |
| Format | JPEG in, JPEG out; PNG in, PNG out |
| EXIF metadata | present on upload, present on download |
| Transparency | RGBA alpha channel survived intact |
EXIF survives, and that cuts both ways
The metadata block your camera writes carries GPS coordinates, the camera model, and the exact timestamp of the shot. Instagram removes it. Facebook removes it. Drive kept every byte of mine.
If Drive is your archive, that is the right behaviour and one of the better reasons to use it over a social platform. If you are about to share a Drive folder with a client, a contractor, or the internet, understand that the location of your house is riding along inside the file. Our own compressor strips EXIF by default for exactly that reason.
Drive will not make your file smaller, so that part is on you
The flip side of a storage service that touches nothing is that it solves none of your size problems. A folder of 4 MB camera originals stays a folder of 4 MB camera originals, and your storage fills at exactly the rate the camera decided. If you want those files smaller, that decision is yours to make before they go up. Run the photo through the compressor at quality 80 and a typical phone photo comes back 60 to 80% smaller with nothing visible lost.
Why Does Google Drive Leave Your File Alone When Other Apps Do Not?
Because Drive is a file system, not an image service, and rewriting a user's bytes would break its core promise. A product whose job is "the file you put in is the file you get out" cannot re-encode JPEGs on the way through without becoming a different product.
Storage products and display products want different things
Instagram, Facebook and LinkedIn serve one photo to millions of screens, so every kilobyte they strip is multiplied by an enormous delivery bill. Drive serves your file back to you and a handful of collaborators, usually once. There is no delivery economics arguing for a re-encode, and there is a very loud correctness argument against it, because Drive also stores PSDs, RAW files, contracts and code.
Google's product experts put it flatly in the help community: there is no general file compression in Drive, and the only extra compression path in the ecosystem is uploading to Photos and choosing the reduced quality tier. That statement sits in the Google Drive Help Community thread on file compression and matches every byte I measured.
The distinction most pages miss
There is a real difference between compressing data and compressing an image. Data level compression is lossless and reversible, the kind a zip file does, and it never changes what the file decodes to. Image level compression is a re-encode that throws away detail permanently. Storage systems apply the first kind routinely and invisibly, at the block level, without altering the file you get back. Only the second kind is what people mean when they ask this question, and Drive does not do it. If that boundary is fuzzy, lossy versus lossless compression covers what each kind actually costs you.
Why Do My Google Drive Images Look Blurry Then?
Because you are looking at a preview, not your file. Drive generates low resolution thumbnails and viewer renders so a folder of high resolution photos loads in a browser without stalling, and those renders are what you see until you download.
Previews are not your file
Open an image in the Drive viewer and Drive serves a display copy sized for a browser window. It looks softer than the original because it is smaller than the original. The stored file is untouched underneath: the copy I downloaded was the same 4,332,705 bytes I uploaded, hash for hash. Download it, open it locally, and the sharpness is all still there.
This is the single most common false alarm on this topic. A soft preview is read as evidence of compression, the reader searches for a setting to turn it off, and there is no setting because there was no compression.
The other three causes worth checking
If the downloaded file really is smaller than what you uploaded, work through these in order. The mobile app's compress photos toggle, covered above. A Photos backup on storage saver that put a reduced copy into your Google storage. Or a third party app, a scanner, or a messaging app that shrank the photo before it ever reached Drive, which is common enough that the app that touched it last is worth tracing.
How to Stop Google Drive From Compressing Photos
There is nothing to stop on the web and desktop paths, so how to stop Google Drive from compressing photos comes down to three checks and one habit.
Turn off the mobile app toggle
Open the Drive app, go to Settings, then General, and switch off the compress photos option. This is the only compression control that exists in Drive itself, and it acts on your phone before upload rather than on Google's servers after it.
Set Photos to original quality if you use Photos at all
If your camera roll backs up through Google Photos, open the Photos backup settings and choose original quality rather than storage saver. Storage saver cost my file 35.1% of its bytes. Original quality cost it nothing, verified by the same hash test I ran on Drive.
Use the desktop sync folder or the web uploader for anything that matters
A browser drag and drop is the path I measured, and it returned both files byte identical. Drive for desktop is the other route with no compression control anywhere in it, though I have not put a file through it myself. For a master file, a print original, or anything you would be upset to lose detail from, use one of those and skip the phone entirely.
The habit: compress on purpose, once, before it goes up
Because Drive stores whatever you hand it, the file you upload is the file you live with. Deciding the tradeoff yourself, once, on a file you control, beats discovering later that some app in the chain made the decision for you. That is the same principle behind compressing images for email, where an attachment limit forces the question earlier.
How Google Drive Compares to the Other Apps I Measured
Drive sits at the absolute gentle end of this series, tied with nothing because nothing else returned a byte identical file across both reference files. Same photo, same day, same method: in, out, compared on disk.
| App and path | Same 4.13 MB photo came back | Change | Dimensions |
|---|---|---|---|
| 22.0 KB | 99.5% smaller | resized to 480x360 | |
| Google Slides | 937.8 KB | 77.8% smaller | resized to 2048x1536 |
| 1.70 MB | 58.9% smaller | kept 4032x3024 | |
| Google Photos, storage saver | 2.68 MB | 35.1% smaller | kept 4032x3024 |
| 3.91 MB | 5.4% smaller | kept 4032x3024 | |
| Discord | 497 KB | 0.3% smaller | kept 4032x3024 |
| Google Drive | 4.13 MB | 0%, byte identical | kept 4032x3024 |
The split is not Google versus everyone else, because Google's own products land at three different points on that chart. It is storage versus display. Dropbox returned my files byte identical too, and Discord came within 0.3% of it, because all three are handing a file back to a person. LinkedIn threw away 99.5% of the photo because it is publishing an image to a feed, and a feed does not need 12 megapixels.