Does Google Drive Compress Photos?

Google documents no image compression step for Google Drive. Drive has no quality setting to choose, and no Google page describes Drive recompressing an image you upload.

That is not the same as a guarantee. Google also publishes no statement anywhere that a file leaves Drive byte for byte identical to the file you put in. The absence of a documented compression step is not a documented promise of fidelity, and anyone telling you Google confirms Drive never touches your photos is quoting a page that does not exist.

The documented recompression story belongs to Google Photos. That is where the named settings live, where the resolution caps are published, and where a photo genuinely can come out smaller than it went in. If your images lost quality inside Google, Photos is the product to look at first.

Google Photos asks you to choose a backup quality. The current setting names on Google's support page are Original quality, Storage saver and Express. Each one behaves differently, and Google states the difference plainly.

Read the Storage saver row carefully, because it is the one people get wrong. Google says the resolution cap applies to photos larger than 16 MP. Google does not say that a photo under 16 MP escapes recompression. A 12 MP frame is not documented as untouched on Storage saver, it is simply not documented as resized. Those are different claims.

Google also publishes no quality number for any of this. There is no JPEG quality setting, no compression percentage and no expected file size reduction on the page. The phrase Google uses is "slightly reduced quality" and nothing more precise. If you see a specific percentage quoted online, it did not come from Google.

Google Photos also has hard ceilings for what it will back up at all: photos up to 200 MB or 200 MP, videos up to 10 GB, and items must be larger than 256 by 256 pixels. The supported photo formats Google lists are .jpg, .heic, .heif, .png, .webp, .gif, .avif and most RAW files. Those limits belong to Photos. They are not Drive limits and should never be quoted as such.

Drive treats a photo as what the Drive API calls a blob file, defined as "a file type that contains raw binary or text content (such as images, videos, and PDFs)." Google's own developer documentation separates that category from Google Workspace documents, which are the files Google formats create. A JPEG is in the first category.

The one conversion Drive does document is the opposite of image compression: an opt-in setting that converts uploads such as Microsoft Word documents into Google Docs format. That setting is about documents. Google describes it as a setting you change, not as something applied to every upload automatically.

Here is the honest boundary, laid out as a list of what is and is not on the record.

• Documented: Drive has no backup quality setting. There is no Storage saver equivalent, no resolution cap to choose, and no page describing a recompression step for images.
• Documented: Google states that "only the files you own count toward your Google storage", and that items in Trash and Spam keep consuming it until they are permanently cleared.
• Not documented: that a file downloaded from Drive is byte for byte identical to the file uploaded. Google's download guide does not say content is returned unchanged.
• Not documented: whether Drive preserves or strips EXIF, ICC profiles or any other metadata on an image.
• Not documented: what the in-browser preview thumbnail is. A preview being softer than the original tells you nothing about the stored file, and Google publishes nothing about how that preview is generated.

So the correct sentence is this: Google documents no compression for Drive, and Google documents no fidelity guarantee for Drive either. If your delivery depends on an exact file arriving, that gap is the thing to plan around, not a setting to switch off.

This is where the two products collide, and it is the single most common way a photographer ends up with quietly reduced images inside a Google account.

The two services are independent. Google states that "any changes you make in Drive will only apply to Drive. Any changes you make in Photos will only apply to Photos." They are separate libraries, not two windows onto the same files.

Copy an image across, though, and it becomes a Photos item governed by Photos rules. Google documents both consequences. First, the new copy is billed again: "if you copy an item from Google Drive to Google Photos, the new copy in Google Photos will also count against your storage." Second, and more important here, "items copied from Google Drive to Google Photos are backed up based on your backup quality."

In plain terms: a file that Drive never had a documented reason to touch can be resized on its way into Photos, because the Photos backup quality setting applies to it. If your account is set to Storage saver, that is the setting the copy inherits. Nobody warns you, and nothing about the Drive side of the account changed.

Most photographers do not go looking for a compression setting. They arrive at it sideways, because storage filled up and something had to give. That is worth understanding before you change any setting in a panic.

Google states that "all Google accounts come with up to 15 GB of storage," and that the quota is shared: "your Google storage is shared across Google Drive, Gmail, Whatsapp backups, and Google Photos." One number covers the mailbox, the document library and the photo library at once. Google states that only the files you own count toward it, and that items in Trash and Spam keep consuming it until they are permanently cleared.

For a photographer that arithmetic gets tight quickly, because the same 15 GB is also holding the mailbox and every phone backup the account collects. The paid tiers Google served to a Canadian visitor on 23 September 2026 looked like this.

Each paid plan can be shared with up to five other people, and the page offers annual billing labelled "save up to 16%". Prices are geo-dependent and change, so check your own account before budgeting against them.

The reason this sits on a compression page: when the quota bites, the tempting fix is to flip Photos to Storage saver. That is a documented quality change, and it is worth making on purpose rather than in a hurry.

Compression is one half of the delivery question. Whether the client can get the file at all is the other half, and Drive documents this part clearly.

A link works without a Google account: "anyone who has the link can use your file, without signing in to their Google Account." People who open it signed out are anonymised, and Google says they "show up as anonymous animals in your file." That is the verified path for a client who does not use Google.

Three roles are documented. Viewer can view and download. Commenter can view, comment and download. Editor can view, comment, edit and download. Downloading is not a separate permission tier, it rides along with all three by default.

It can be turned off, though, and this is the setting that surprises people: "to give viewers and commenters the option to download, print, and copy a file, owners can click Share and then Settings and check the box." If that box is unchecked, your client can look and cannot save. Note also that turning off download has never stopped a determined recipient from capturing what is on screen, and Google does not claim otherwise.

One more documented detail matters when you share a whole folder. Access applied to a folder is inherited by everything inside it, and Google states you "can no longer give someone less access to an individual file if they have higher access to its parent folder."

Four practical conclusions follow from the documentation above, and none of them require guessing.

• Check which product the images are actually in. If quality dropped, look at the Google Photos backup quality setting before blaming Drive. That is where the documented resize lives.
• Do not copy delivery files from Drive into Photos. The copy inherits your backup quality and is billed again. Leave client files where they are.
• Keep your masters on your own drives. Since Google publishes no fidelity guarantee for Drive, no cloud folder is an archive. Your backup discipline does not change because a file is also in the cloud.
• Decide download permission deliberately. The download box is on by default for all three roles. If a client should not be saving the proofs yet, that is a setting to change before you send the link, not after.

A gallery built for client delivery separates the proof from the final deliberately, and tells you which is which. On clientgallery.io, ordinary uploads are browser-compressed proof JPEGs, sized for fast viewing rather than for printing, and we say so plainly rather than implying nothing is re-encoded. Full-resolution delivery is a separate paid feature: you upload a full-resolution ZIP for a gallery, it stays live for three days per handoff, and you can re-upload it any time. One plan, $10 a month or $100 a year, unlimited under fair use with 1,000 photos per gallery and 250 GB of proofs per paid account, 5 GB on the free tier, and 100 GB of standing ZIPs per account. If you want the full argument for moving a delivery workflow off a file drive, that comparison lives on our Google Drive alternative for photo delivery page rather than on this one.

• Google Photos Help, "Choose the backup quality of your photos and videos". https://support.google.com/photos/answer/6220791 Fetched 23 September 2026.
• Google Photos Help, file types and size limits for backup. https://support.google.com/photos/answer/6193313 Fetched 23 September 2026.
• Google Photos Help, Google Photos and Google Drive as independent services. https://support.google.com/photos/answer/6156103 Fetched 23 September 2026.
• Google Drive Help, uploading files and folders, including the opt-in conversion setting. https://support.google.com/drive/answer/2424368 Fetched 23 September 2026.
• Google Drive Help, how Google storage is shared and what counts toward it. https://support.google.com/drive/answer/6374270 Fetched 23 September 2026.
• Google Drive Help, sharing files and folders, roles and the download setting. https://support.google.com/drive/answer/2494822 Fetched 23 September 2026.
• Google One, storage plans page, Canadian pricing as served. https://one.google.com/about/plans Fetched 23 September 2026.
• Google Drive API, "Files and folders overview", blob file definition. https://developers.google.com/workspace/drive/api/guides/about-files Fetched 23 September 2026.
• Google Drive API, "Download and export files". https://developers.google.com/workspace/drive/api/guides/manage-downloads Fetched 23 September 2026.