WhatsApp re-compresses everything you send as a photo. You cannot turn that off — but you can stop it happening twice, and you can bypass it entirely.
In the attachment menu choose Document rather than Gallery or Photos, then pick your image file. WhatsApp treats it as an arbitrary file and transfers it byte for byte. The recipient sees a file to tap rather than an inline preview, which is the trade-off.
In Settings → Storage and data → Media upload quality, choose HD if your version offers it. This raises the ceiling WhatsApp compresses to. It still re-compresses — it simply does less damage.
Resize to around 1600 pixels on the longest edge and compress at quality 85 before sending. WhatsApp then has little left to remove, so its own pass changes far less. This is the best route when you want a normal inline photo rather than a document.
WhatsApp carries an enormous volume of images across networks of wildly varying quality, much of it on prepaid mobile data. Compressing aggressively keeps messages delivering quickly on a poor connection and keeps costs down for everyone in the chain.
That is a reasonable trade for a chat app, and it is not something you can switch off. What you can do is choose a path that does not go through the photo pipeline at all.
Sending an image as a document bypasses the image pipeline entirely — the file arrives exactly as it left, at full resolution with metadata intact.
Two things to know. The recipient gets a file attachment rather than an inline thumbnail, which is less convenient and occasionally confusing. And metadata travels with it, so if the photograph was taken at home, its GPS coordinates go too. Strip the metadata first if that matters.
Each pass through WhatsApp's encoder re-quantises data that has already been quantised. The second encoder treats the first one's artefacts as real detail and adds its own on top.
This is generation loss, and it accumulates in one direction only. A photograph forwarded through several chats has been through several lossy encodes, which is exactly why those images look smeared and blotchy in a way no single compression pass produces.
Sending the original rather than forwarding a received copy avoids it entirely.
Photos sent normally through WhatsApp generally have metadata stripped as a side effect of re-encoding. Photos sent as documents do not — they arrive complete with camera model, timestamps and, if location services were on, coordinates accurate to a few metres.
If you are using the document route for quality, strip the metadata first. The EXIF remover on this site does it in the browser, so the file containing your location never travels anywhere to be cleaned.
These run in your browser on any device, so nothing is uploaded and there is nothing to install.
By pixels or percentage, aspect ratio locked, across a whole batch.
Open the toolShrink JPG and JPEG photographs with a quality slider or an exact target size.
Open the toolStrip GPS coordinates, camera model and timestamps before you publish.
Open the toolPortfolio and email-friendly, near-indistinguishable.
Open the toolQuestions
Every answer below is present in the page source, expanded, so it can be read without opening anything.
Not for photos sent as photos — that pipeline always re-encodes. The only genuine bypass is to send the image as a document, which transfers the file untouched at the cost of it arriving as an attachment rather than an inline preview.
Yes. WhatsApp treats it as an arbitrary file and does not decode or re-encode it, so it arrives byte for byte identical — including any metadata, which is worth stripping first if the photograph was taken somewhere private.
It raises the quality ceiling WhatsApp compresses to, so the result is noticeably better than the standard setting. It does not disable compression — your photo is still re-encoded, just less destructively.
Generation loss. Each pass re-compresses already-compressed data, treating the previous encoder's errors as real detail. Several forwards means several lossy encodes stacked on top of each other. Send the original rather than forwarding a received copy.
If you are sending as a normal photo, yes. Resizing to about 1600 pixels and compressing at quality 85 leaves WhatsApp's encoder very little to remove, so its pass does far less damage than it would to a full-resolution original.
Photos sent through the normal pipeline generally lose metadata as a side effect of re-encoding. Photos sent as documents keep everything, including coordinates. Strip the metadata yourself if you are using the document route.
From the blog
More background from the blog.
A photograph from a phone can carry the coordinates of the place it was taken, the camera serial number and the exact timestamp. Removing that data is straightforward. Removing it carelessly rotates your photos sideways.
9 min read
Attachments are base64-encoded in transit, which inflates them by about a third. A 20 MB limit is really a 15 MB limit. Resize to 1600 pixels on the long edge and encode at quality 80, and a photograph lands near 150 KB.
9 min read
Quality 80 is not 80% of anything. It is an index into a quantisation table. Measured on one photograph: dropping from 100 to 90 removes 77% of the file and 4.2 dB of fidelity; dropping from 40 to 30 removes 17% and costs almost as much.
8 min read