Somebody sends you a photo of a document, a whiteboard, a price tag — and it arrives just blurry enough to be useless. Or you send a picture you are proud of and it comes back looking like it was faxed.
The original on your phone is perfect. What arrived is not the same file.
What WhatsApp actually does
Every image sent as a photo goes through two changes on the way out.
It is resized. If the longest edge is bigger than WhatsApp's ceiling, the picture is scaled down. A modern phone shoots something like 4000 pixels across; what arrives is a fraction of that.
It is re-encoded as JPEG at a lower quality. This is the part that produces the blotches around text and the muddy patches in skies. And because your photo was already a JPEG, this is a second generation of lossy compression on top of the first — the artefacts of the original get compressed along with everything else.
A 4 MB photo commonly arrives somewhere around a tenth of that.
You will find pages stating WhatsApp's exact pixel ceiling and quality setting to the decimal. WhatsApp does not publish those numbers, they have changed several times, and they differ between platforms and between "standard" and "HD". Anyone quoting a precise figure is repeating something they read. What is reliable is the behaviour: sent as a photo, it is resized and re-compressed, every time.
Why it does it
Not to annoy you. WhatsApp carries an enormous number of images a day, and a great many of its users are on connections and data plans where a 4 MB photo is a real cost. Shrinking aggressively is what makes the app usable on a slow network, and for the overwhelming majority of messages — a snapshot glanced at once — nobody can tell.
The trouble is the minority of cases where the detail was the entire point.
The one reliable fix: send it as a document
WhatsApp compresses photos. It does not touch documents. Send the same file as a document and it arrives byte-for-byte identical.
- On iPhone: tap the + in the chat, choose Document, then Choose file, and pick the image from Files or Photos.
- On Android: tap the paperclip, choose Document, then browse to the picture.
Two things to know before you rely on it. The recipient gets a file to tap rather than a picture in the conversation, which is slightly less pleasant. And the file is the full size, so on a slow connection it is a slow send — which is exactly the problem WhatsApp was solving.
The HD setting helps, and is not the same thing
Newer versions offer a higher-quality option, either as an HD toggle when you attach a photo or under Settings → Storage and data → Media upload quality.
It is worth turning on and it is worth understanding: HD compresses less, it does not compress nothing. The picture is still resized and still re-encoded, just less brutally. For a photograph that is usually enough. For a screenshot of small text, it usually is not.
Why screenshots suffer most
This is the case people notice, and there is a reason it is always the same one.
JPEG compression works by smoothing — it discards the high-frequency detail your eye is bad at noticing. In a photograph of a face or a landscape, there is very little that qualifies, so the damage hides. Text and interface edges are nothing but high-frequency detail: hard black-to-white transitions, everywhere.
So a screenshot of a receipt, a bank transfer, a booking reference or a whiteboard gets exactly the treatment it can least afford, and the numbers stop being readable. If what you are sending is text, send it as a document — or better, turn it into a PDF first, which is both smaller and obviously a document to whoever receives it.
What to do in each case
| What you are sending | Send it as | Why |
|---|---|---|
| A snapshot, a moment, a joke | A photo | The compression is invisible and the send is instant |
| A screenshot with text or numbers | A document | Text is exactly what JPEG destroys first |
| A photo somebody will print | A document | Printing shows every artefact a screen hides |
| Something being used as evidence | A document | Re-compression is not what you want on a record |
| Twenty holiday photos | Photos, HD on | Twenty full-size files is a slow, expensive send |
Compress it yourself instead
There is a middle path people rarely consider: shrink the picture deliberately before you send it, so that WhatsApp has nothing left to take.
If a photo is already at a sensible size — say 1600 pixels on its longest edge and a couple of hundred kilobytes — it is at or under whatever ceiling the app applies, and the re-encode has far less to damage. You chose the trade-off instead of an algorithm choosing it for you, and you can look at the result first.
That is the difference between compressing on purpose and being compressed: one of them you can check.
Two related annoyances
Profile pictures. Compressed regardless of anything you do, and cropped to a circle. Upload something already square and already small; a 4 MB portrait gains nothing, and cropping it yourself is the only way to choose what the circle keeps.
Status updates. Same treatment as photos, with the same fix unavailable — there is no document option. Shrink it yourself beforehand if it matters.
The general lesson
Every messaging app does some version of this — Messenger, Instagram DMs, Telegram unless you tick "send as file", Discord above a size limit. The question is never whether an app re-compresses, it is whether it gives you a way out.
WhatsApp does, and it is called Document.