How to Compress Images for WhatsApp, Telegram & Messaging Apps
· 6 min read
WhatsApp re-compresses everything you send using settings tuned for bandwidth, not appearance. Resize to 1600 pixels on the long edge and compress at quality 80 first, and its own pass has almost nothing left to damage. For anything where quality matters, send the file as a document instead — that skips re-encoding entirely.
WhatsApp already compresses what you send, quite aggressively. Compressing first sounds redundant — it is not, and doing it yourself gives a visibly better result.
On this page
Why WhatsApp's own compression looks worse than yours
WhatsApp re-encodes images to fit a bandwidth budget, not a quality target. It resizes to around 1600 pixels on the long edge and applies a fixed, fairly harsh JPEG setting regardless of what the picture contains.
That fixed setting is the problem. A photograph of a landscape and a screenshot of a spreadsheet get treated identically, even though the screenshot's hard edges and small text are exactly what JPEG handles worst. The app has no idea which one you sent.
If you compress first — resizing to a sensible width and choosing a quality yourself — WhatsApp has far less work left to do, so its own pass damages the image far less. The result at the other end is noticeably cleaner than sending the untouched original.
Settings that survive the second pass
Resize to about 1600 pixels on the longest edge and compress at quality 80. That is close enough to what WhatsApp wants that its own compression barely bites.
For Telegram, which is more generous, 2000 pixels at quality 85 holds up well. For anything where quality genuinely matters, send it as a document rather than a photo — both apps skip re-encoding entirely for documents.
- WhatsApp photo: 1600px long edge, quality 80
- Telegram photo: 2000px long edge, quality 85
- Signal photo: 1600px long edge, quality 80 — similar handling to WhatsApp
- Either app, quality critical: send as a document instead
Step by step
The whole sequence takes under a minute, and nothing leaves your phone or computer while you do it.
- Open the compress tool and drop the photo in.
- Set the long edge to 1600 pixels. On a modern phone photo that alone removes most of the file size.
- Set quality to 80 and check the preview at full size, not the thumbnail — artefacts are invisible when scaled down.
- Download, then send the compressed copy rather than the original from your camera roll.
What the numbers actually look like
A typical 12-megapixel phone photo lands somewhere around 4 MB. The table below is what happens to it at each step, and why the last row is the one worth avoiding.
| What you send | Size sent | What WhatsApp does | Result |
|---|---|---|---|
| Untouched original | 4 MB | Resize + heavy re-encode | Softest result |
| 1600px at quality 80 | ~380 KB | Almost nothing left to do | Cleanest result |
| As a document | 4 MB | Nothing | Exact original, slow to send |
Sending as a document
In both apps, attaching a file as a document rather than a photo bypasses the re-encoding completely. The recipient gets the exact bytes you sent. It is the right choice for anything being printed, forwarded onward, or looked at closely.
The trade-off is that documents do not show a preview in the chat, and the recipient has to tap to download rather than seeing the picture inline. For a single important image that is a fair price. For holiday snaps it is an annoyance.
Why the image looks worse on the other phone
What the recipient sees has been through two compressions: yours and WhatsApp's. If you sent the untouched original, WhatsApp did all of it at once with settings tuned for bandwidth rather than appearance.
Pre-compressing to something close to what WhatsApp wants means its own pass has almost nothing left to remove, so it removes almost nothing.
There is a third compression people forget about: forwarding. Every time an image is forwarded as a photo it may be re-encoded again, which is why a picture that has travelled through several chats looks so much worse than the one that started the chain.
Screenshots and images with text
Screenshots are the worst case for messaging apps. JPEG compression works by discarding high-frequency detail, and text is nothing but high-frequency detail, so small type smears and coloured fringes appear around letters.
For a screenshot, send it as a document if the text needs to be readable. If it has to go as a photo, do not resize below the original width — shrinking text is far more destructive than compressing it.
Profile pictures and status images
Profile pictures are cropped to a circle from a square, so anything near the corners is lost. Crop to 1:1 yourself and keep the subject central.
Status images use the full screen at 9:16. A landscape photo posted as a status gets letterboxed or cropped, neither of which is likely to be what you intended.
Common questions
Does WhatsApp compress images?
Yes. WhatsApp re-encodes every image sent as a photo, resizing to roughly 1600 pixels on the long edge and applying a fixed JPEG setting. Compressing to those dimensions yourself first leaves its pass with almost nothing to remove.
What size should images be for WhatsApp?
Around 1600 pixels on the longest edge at quality 80, which usually lands between 300 KB and 600 KB for a photo. WhatsApp's hard limit is far higher, but sending anything much larger just means the app throws the extra detail away itself.
Does compressing images reduce quality?
Lossy compression does reduce quality slightly, but at quality 80 the difference is invisible at normal viewing sizes. You lose file size, not visible detail. Check the preview at full size rather than as a thumbnail if you want to judge it honestly.
What is the best image format for WhatsApp?
JPEG. WhatsApp converts photos to JPEG regardless, so sending PNG only means a larger upload for the same end result. The exception is an image with transparency, which JPEG cannot store at all.
How do I send a photo on WhatsApp without losing quality?
Attach it as a document rather than a photo. Documents are delivered byte-for-byte with no re-encoding. The recipient sees a file to tap rather than an inline preview, which is the trade-off.
Why do forwarded photos look so bad?
Each forward as a photo can trigger another re-encode, and JPEG loss accumulates — every pass discards detail the previous pass left behind. A picture that has been through several chats has been compressed several times over.
Does compressing first actually help, or is it doing the same job twice?
It helps. Compression is not a fixed amount of damage applied once — the harm comes from how far the encoder has to push. Arriving already close to WhatsApp's target means its encoder barely has to push at all.
Is it safe to compress private photos on a website?
On FileCrisp, yes, because nothing is uploaded — the compression runs inside your browser and the file never leaves your device. Any tool that asks you to upload first is a different proposition entirely.