Why WhatsApp ruins your photos, and how to send one properly

You send a photo, it arrives soft and blotchy, and the version on your phone is perfect. Nothing is broken — WhatsApp shrank it on purpose. There is exactly one way to stop it, and it is not the quality setting.

5 min read · last checked 2026-09-04

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.

The tool Compress Image Get photos under an upload limit, by quality or by a size you name. Batch supported.

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.

The same line of text after one, six and twelve rounds of resizing and re-encoding, magnified three times. It gets progressively fuzzier and greyer.
Each round is a real decode, resize and re-encode, run here rather than drawn. It is a model of being sent on repeatedly, not a recording of it — WhatsApp’s exact settings are not published, and every app’s are different. What compounds is the same either way.

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 sendingSend it asWhy
A snapshot, a moment, a jokeA photoThe compression is invisible and the send is instant
A screenshot with text or numbersA documentText is exactly what JPEG destroys first
A photo somebody will printA documentPrinting shows every artefact a screen hides
Something being used as evidenceA documentRe-compression is not what you want on a record
Twenty holiday photosPhotos, HD onTwenty 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.

Common questions

Does WhatsApp reduce photo quality?

Yes, always, for anything sent as a photo. The image is scaled down if it is large and re-encoded as JPEG at a lower quality. A 4 MB photo commonly arrives at around a tenth of that.

How do I send a photo on WhatsApp without losing quality?

Send it as a document rather than a photo. On iPhone: + → Document → Choose file. On Android: paperclip → Document. The file arrives byte-for-byte identical, because WhatsApp does not compress documents.

Does the HD setting stop the compression?

No, it reduces it. HD still resizes and still re-encodes, just less aggressively. It is worth turning on, and it is not a substitute for sending as a document when the detail matters.

Why do screenshots look so much worse than photos?

Because JPEG compression works by smoothing, and text is nothing but hard edges. A photograph hides the damage; a screenshot of small text shows it immediately, which is why numbers and reference codes stop being readable.

What are WhatsApp's exact size and quality limits?

They are not published, they have changed several times, and they differ by platform and by whether HD is on. Any page quoting an exact pixel figure is repeating something unverified. What is reliable is the behaviour: photos are resized and re-compressed, documents are not.

Can I stop WhatsApp compressing profile pictures?

No. Profile pictures are compressed and cropped regardless. Upload something already square and already modest in size — a large original gains nothing.

Is it better to compress the photo myself first?

Often, yes. A picture already at a sensible size and quality gives the app far less to take, and you can look at the result before sending it rather than discovering it afterwards.

More guides

What is a HEIC file, and why will your PC not open it?

Half the size of a JPG, and a patent licence is why Windows refuses it.

How to get a PDF under an upload limit

Most PDFs cannot be compressed at all. Ten seconds tells you which kind you have.

JPG or PNG: which should you use?

Photographs, JPG. Hard edges or transparency, PNG. The reason is worth two minutes.

How to get a photo under a KB limit

The quality slider is the wrong first move. Pixels are the lever that works.

Are QR codes safe? What is actually inside one

Nothing inside one can run. The risks are the destination, the sticker over the original, and who owns the code.

Why video files are so big, and what actually shrinks them

Bitrate times length is the file size. Everything else follows from that.

MP3, WAV or M4A: which audio format, and at what bitrate?

128 kbps is about a megabyte a minute. Everything else follows from that.

Percentages, and the four sums people actually get wrong

20% off then 10% off is not 30% off, and adding 20% then taking it back leaves you short.

How to take a passport photo at home that is not rejected

The rule is the height of your head, not the size of the photo — and the shadow behind you is geometry.

How to make a ringtone, and why the cutting is the easy part

Android takes an MP3 straight. An iPhone wants an M4R, which is an M4A with a different extension.

Compound interest, in both directions

Savings growing and a card balance running away are the same sum. Only the side you are standing on differs.

What actually happens when a password leaks

Why one company’s bad week becomes your problem at forty other sites — and the single habit that breaks the chain.

What you can change in a PDF without Acrobat

Moving pages and stamping them costs nothing. Changing the words is the one genuinely hard edit, and this is why.

Are electronic signatures legally binding?

Valid nearly everywhere — but a drawn signature proves the mark is there, not who put it there. What that changes, and when it is not enough.

Why background removal cuts off hair

Hair, glass and plants come out ragged for a reason that is not fixable by trying another site. What causes it, and what to photograph instead.

Why OCR gets text wrong

Why the mistakes land in invoice numbers rather than in sentences, what actually ruins a scan, and how to photograph a page properly.

What the numbers on a barcode mean

Three fields and a checksum. Why “690 means made in China” is wrong, and how the last digit is worked out from the others.

Why date calculators disagree with each other

One month after 31 January is 28 February, 2 March or 3 March depending on the rule. Why the calendar refuses to be arithmetic.

What fitness numbers actually tell you

Why the level a fitness formula gives you is usually wrong, why the change usually is not, and which of the two is worth watching.

What has to be on an invoice

The blocks nearly every country expects, the two that people get wrong, and why “net 30” gets paid later than a date.

Subtitles: a separate file, or burned into the video?

A file the player draws, or pixels in the picture. What each costs, and why automatic captions get names wrong and sentences right.

Why your final grade is not the average of your grades

The same four marks give 82.5 averaged and 74.0 weighted. How weighting works, and what you really need on the final.

Does decoy pricing actually work?

A real 1982 effect, a famous 84%-vs-32% demonstration, and a 2014 attempt to reproduce it on real products that worked about once in eight tries.

How to save a picture that is only on the clipboard

Why Ctrl+V does nothing in a folder after you copy a picture, what your computer can already save on its own, and the shortest way round it.