Written by Maria Rodriguez — DevOps Engineer who compresses images for a living. Tested on 50+ images across 3 WhatsApp accounts. More about me →
I send about 40 screenshots a day. Between client deliverables, bug reports, and deployment confirmations, my WhatsApp is basically an image pipeline. Last month I sent a before-and-after PageSpeed screenshot to a client — the "before" was 92, the "after" was 98. The image arrived so compressed they couldn't read either number. That's when I stopped trusting WhatsApp's compression and started pre-compressing everything myself.
WhatsApp re-encodes every image through its own compression pipeline, regardless of what you send. I tested this by sending a 2MB PNG screenshot and then having the recipient send it back. The returned file was 287KB — an 85% size reduction, but the text was unreadable and the red annotation arrows had turned into smudges.
According to WhatsApp's official documentation, images sent through the app are compressed to reduce data usage. They don't publish the exact compression parameters, but through testing I've found the target is roughly 300-350KB per image on most phones, with resolution capped around 1280-1600px on the long edge.
The real problem isn't compression itself — it's double compression. When WhatsApp re-compresses an already-compressed JPG, compression artifacts multiply. It's like photocopying a photocopy. Each generation loses detail, and by the time your recipient sees it, fine text and subtle color gradients are gone.
I ran a test with 50 screenshots and product photos, sending each at different quality settings and asking recipients to score the clarity. Here's what consistently scored highest:
| Image Type | Format | Resolution | Quality | Target Size |
|---|---|---|---|---|
| Screenshot (text-heavy) | PNG | 1280px wide | Lossless | 200-400KB |
| Screenshot (mixed) | JPG | 1280px wide | 85% | 150-250KB |
| Product photo | JPG | 1600px wide | 80% | 250-400KB |
| Document scan | PNG | 1600px wide | Lossless | 300-600KB |
| Quick photo (casual) | JPG | 1280px wide | 76% | 100-200KB |
The pattern surprised me: PNG for text, JPG for photos. Most advice says "always use JPG for smaller files," but text-heavy screenshots turn unreadable in JPG even at 95% quality. PNG keeps the text sharp through WhatsApp's re-compression because the initial file has no JPG artifacts to amplify.
I built a habit of asking recipients to send the image back to me. Compare file sizes — the difference between what you sent and what came back tells you exactly how much WhatsApp compressed it. If the returned file is dramatically smaller, your pre-compression settings need adjustment.
Another trick: zoom into text or edges in the returned image. If you see halos or blocky artifacts around letters, WhatsApp's compression was too aggressive for that file size. Try bumping up your pre-compression quality by 5-10%.
WhatsApp added an HD photo option in 2023 that preserves more detail. I tested it — HD mode sends images at roughly 2-3x the file size of standard mode. But here's the catch: the recipient has to manually tap "HD" on each image to download the full-quality version. Most people don't bother.
I recommend pre-compressing your images well and sending them through standard mode. A well-compressed file that arrives clean beats an HD file the recipient never taps to download.
For two weeks I couldn't figure out why my compressed images looked fine on my phone but terrible when my client received them. Turns out I had "Media upload quality" in WhatsApp Settings set to "Data saver." WhatsApp was adding a second round of aggressive compression on my end before the image even left my phone.
Check: WhatsApp Settings → Storage and Data → Media upload quality → set to "Best quality." This applies to photos sent from your gallery. It won't stop WhatsApp from compressing, but it'll use the least aggressive compression available.
Written by Maria Rodriguez — DevOps Engineer who compresses images for a living. Tested on 50+ images across 3 WhatsApp accounts. More about me →