Does WhatsApp Compress Photos? We Measured Exactly How Much
Yes. We sent the same 26-megapixel, 4.3 MB camera photo through WhatsApp from two Android phones, an iPhone, the Mac app and WhatsApp Web, in standard and HD quality, and measured what arrived. Standard quality came back at 1280 to 1600 pixels on the long side, 4 to 7% of the original's pixels, at between 3% and 17% of its bytes. HD kept anywhere from 17% to 67% of the pixels depending on what sent it. Sent as a document, the file is untouched. The table, the crops, and the method are below so you can repeat it.
- Standard quality: 1280 to 1600 px on the long side depending on the sender, one pixel in fifteen to twenty-four kept, and the camera metadata gone.
- HD is not one setting: the iPhone app kept 5120 px, the Mac app 4160, both Android phones 3120, WhatsApp Web only 2560. All of them re-encode.
- Only Document mode sends the original file. For a whole album, a link to the originals is the practical version of that.
The results: one photo, ten ways
The original is a real camera file, brick buildings under a blue sky by Mat Reding on Pexels: 6240 by 4160 pixels, 4.3 MB, a JPEG at roughly quality 80. Brickwork, lace curtains and a smooth sky are exactly the things compression struggles with, which is why we chose it. The first row is the original as the baseline; every other row is what the receiving phone got. "JPEG q" is the encoder quality read back from each file's own quantization tables, so treat it as approximate. SSIM is how close the received image is to the original at the same size, where 1.000 means identical.
| Sent from | Mode | Received size | Pixels kept | File size | Bytes kept | JPEG q (approx) | Chroma | SSIM |
|---|---|---|---|---|---|---|---|---|
| Original (baseline) | File as shot | 6240 x 4160 | 100% | 4.30 MB | 100% | 80 | 4:2:0 | 1.000 |
| Android app, first phone | Standard | 1560 x 1040 | 6.2% | 203 KB | 4.7% | 74 | 4:2:0 | 0.933 |
| Android app, first phone | HD | 3120 x 2080 | 25.0% | 625 KB | 14.5% | 67 | 4:2:0 | 0.855 |
| Android app, Pixel 9a | Standard | 1280 x 853 | 4.2% | 115 KB | 2.7% | 67 | 4:2:0 | 0.928 |
| Android app, Pixel 9a | HD | 3120 x 2080 | 25.0% | 625 KB | 14.5% | 67 | 4:2:0 | 0.855 |
| iPhone app | Standard | 1600 x 1066 | 6.6% | 249 KB | 5.8% | 89 | 4:2:0 | 0.941 |
| iPhone app | HD | 5120 x 3414 | 67.3% | 2.52 MB | 58.6% | 89 | 4:2:0 | 0.934 |
| Mac app | Standard | 1600 x 1067 | 6.6% | 258 KB | 6.0% | 80 | 4:2:0 | 0.938 |
| Mac app | HD | 4160 x 2773 | 44.4% | 1.58 MB | 36.8% | 75 | 4:2:0 | 0.899 |
| Web (Firefox, Linux) | Standard | 1600 x 1066 | 6.6% | 747 KB | 17.4% | 92 | 4:4:4 | 0.857 |
| Web (Firefox, Linux) | HD | 2560 x 1706 | 16.8% | 1.72 MB | 40.0% | 92 | 4:4:4 | 0.921 |
Three things in that table settle most arguments. Standard quality lands between 1280 and 1600 pixels, and it varies even between two Android phones running the same app: the first phone sent 1560, exactly a quarter of the original's width, and the Pixel 9a sent 1280 at a lower quality factor, the smallest file of the whole test. HD is not one setting either: the iPhone app kept 5120 pixels, the Mac app 4160, both Android phones exactly half the original at 3120, and WhatsApp Web capped at 2560, which is barely above standard. Even the best of them, the iPhone, sent back two pixels in three. The two Android phones' HD files were byte-for-byte identical, same size, same checksum, which says the Android app's HD path is deterministic: same source, same build, same output. And every row is a fresh JPEG with the camera metadata removed, so the capture date and lens are gone whichever way you send.
The SSIM column is worth a second look. The Web sends have the highest JPEG quality and full-colour chroma yet some of the lowest similarity scores, which means Web's resizer is doing more damage than its encoder. On a real photo with grain and fine brick detail, the loss is in the pixels thrown away before the encoder starts, not in the encoding itself.
One caution before you quote a number: the exact ceilings move between runs. In an earlier run with a smaller 17 MP test image, the iPhone app's HD send kept the full resolution and the Android app's HD send came back at 4160 pixels rather than half, so the HD caps appear to depend on the size of the source as well as on the sender, and possibly on the WhatsApp build of the day. The pattern held every time: standard lands near 1600 pixels, HD varies by sender, and nothing but Document sends the file. Treat the table as a dated snapshot and the pattern as the finding.
What it looks like at 100%
The same dormer window from every version, scaled to the original's pixel size so a print or a laptop screen would show it this way. Tap through them; the lace curtain and the brick courses are where to look.
Every file above is exactly as it arrived, not re-saved. Download all eleven files with the results as a ZIP (13 MB) if you want to check the numbers or run your own comparison.
What the HD button actually does
WhatsApp added the HD option in August 2023, and since June 2024 it can be made the default under Settings, Storage and data, Media upload quality, so you no longer have to tap the badge on every batch. Do that on every phone that will send wedding photos. What it buys you depends on the sender, as the table shows: 5120 pixels from the iPhone app, 4160 from the Mac app, half the original from both Android phones, 2560 from WhatsApp Web, with the caveat above that these ceilings shifted between our runs.
What HD does not do, anywhere, is send your file. Every HD row is a fresh JPEG at roughly quality 67 to 92, and every one of them dropped the camera metadata. The underlying reason is the format: JPEG is lossy, and each re-encode discards data the next one can't recover. HD is a much better copy. It is still a copy.
Why WhatsApp compresses photos
Volume. WhatsApp moves billions of messages a day, and the standard pipeline is built so a photo arrives in a second on a weak connection and costs almost nothing in data. A 200 KB file does that; a 4 MB one doesn't. The compression isn't there to spite you, it's the default for people on patchy mobile data, which is most of the world. On Wi-Fi at a venue it just feels like a relic, and it is the wrong default for a wedding album.
The document trick, and why it annoys everyone
The one route that sends the original is Document. Tap the attachment clip or plus button, choose Document (on iPhone, then "Choose Photo or Video"), pick the files, send. WhatsApp's own announcement put the limit plainly: "you can now send files within WhatsApp up to 2GB in size at a time" (WhatsApp blog, May 2022). The bytes arrive untouched, metadata and all.
The catch, per 9to5Mac's walkthrough, is that the photo shows up
as a file icon rather than a preview, lands in the recipient's Documents folder rather than their
gallery, and half of them never find it. Guests see a wall of IMG_9421.JPG and a
download each. For two hero shots the couple wants to print, worth it. For 480 photos to 200
people, nobody has the patience.
Cloud links are a trap for guests
The next instinct is a Google Drive or Dropbox link. "Here guys, all the photos are in this folder!" You feel organised. Your guests open 800 photos of someone else's cousins, scroll for theirs, and give up. Anyone who tries to save the lot runs into their own storage, and the folder sits there unloved. Full quality, delivered to nobody.
How to share wedding photos at full quality without the friction
The practical answer is to keep WhatsApp as the doorway and stop using it as the pipe. That is what AccioPix does. The photographer uploads the album once. Each guest opens the album link, which drops them into a WhatsApp chat, and sends a selfie. Face matching finds every frame they're in and sends the first of them back as messages, at 2048 pixels so they load instantly, followed by a personal album link with all of them. That link serves the full-resolution originals for download, and it re-checks the album every time it's opened, so photos uploaded later show up too. No app, no folder, no forwarding.
For the photographer, it is the end of the morning-after texts. You upload once, each guest pulls their own photos, and the couple stops forwarding your lighting as a 1600-pixel copy. It runs on credits, so the cost tracks the job: a 500-photo event is about ₹100 in credits. The business case, referrals included, is in how to get clients for photography, and the step-by-step setup is in how to share photos on WhatsApp.
Comparison of sharing methods
| Method | What arrives | Guest experience |
|---|---|---|
| WhatsApp standard | 1280 to 1600 px, 3 to 17% of the bytes, no metadata | Instant, and soft on anything bigger than a phone |
| WhatsApp HD | 2560 to 5120 px depending on the sender, 15 to 59% of the bytes, no metadata | Good on screen; still a copy |
| Document attachment | The original file | File icons, no previews, a download each |
| Drive or Dropbox folder | The original file | Scroll through everyone's photos to find yours |
| AccioPix link | Matched photos in the chat, originals from the album link | One selfie, only your photos |
How we tested
One original: a 6240 by 4160 pixel JPEG by Mat Reding,
4,300,799 bytes, encoded at roughly quality 80 with 4:2:0 chroma as downloaded from Pexels, copied
to each sending device without going through WhatsApp. It was received on a second device from
the WhatsApp Android app on two phones (one of them a Pixel 9a), the iPhone app, the Mac desktop
app, and WhatsApp Web running in Firefox on Linux, once in standard quality and once with HD selected, on 7 September 2026 with the current WhatsApp builds
of that date. The received files were saved from the receiving device without re-saving them and
measured with a script that reads dimensions, file size, the JPEG quality factor from each file's
quantization tables using the IJG scaling formula, chroma subsampling, metadata presence, and PSNR
and SSIM against the original resized to the received dimensions. The script and the file-naming
convention are in the AccioPix repository as scripts/whatsapp-quality-test.py. An
earlier run with a different 17 MP image gave different HD ceilings on the iPhone and Android apps,
which is why the text above treats the caps as a snapshot. Not tested this round: forwarding
chains and save-and-resend generations, which is the next run. If a newer WhatsApp changes these
numbers, send us your results and we'll add them.
Frequently asked questions
How much does WhatsApp compress photos?
In standard quality, to between 1280 and 1600 pixels on the long side depending on the sending device, which was one pixel in fifteen to twenty-four and 3 to 17% of the bytes of our 26 MP test file, with the camera metadata removed. HD keeps more, but how much depends on the sender: 5120 pixels from the iPhone app, 4160 from the Mac app, half the original from two Android phones, 2560 from WhatsApp Web, and those ceilings varied between our runs.
Does WhatsApp Web compress photos more than the mobile app?
Differently. In our test WhatsApp Web's standard send was the largest file, 747 KB with full-resolution colour, yet it scored lowest on similarity to the original, and its HD send capped at 2560 pixels, the lowest HD result. The phone apps used 4:2:0 colour and smaller files but kept more pixels in HD. The old assumption that it's all the same pipeline doesn't hold.
Does WhatsApp reduce image quality even in HD mode?
Yes. Every HD send was a new JPEG at roughly quality 67 to 92 with the metadata stripped, and the resolution was capped as well: 5120, 4160, 3120 or 2560 pixels depending on the sender. HD is a much better copy than standard, not the original. Only sending as a document keeps the file itself.
How do I stop WhatsApp from compressing photos?
Set Media upload quality to HD under Settings, Storage and data, so every send uses it. For a photo that has to stay intact, send it as a document. For a whole event, send guests a link to the full-resolution files instead of the photos themselves, so nothing is re-encoded on the way.
Can I send 4K video on WhatsApp without losing quality?
Not as a normal video message. WhatsApp re-encodes video the way it re-encodes photos, and the June 2024 coverage of the HD default setting puts HD video at 720p. Send the file as a document, up to 2 GB, or share a link to the original.
Is there a limit to how many documents I can send at once?
Files are capped at 2 GB each, and the practical limit is your guests' patience: every document is a separate message with no preview. For more than a handful, use a link.
References
- Mat Reding, Pexels, Brick buildings under blue sky. Test image. Read 1 October 2026.
- MacRumors, 18 August 2023, WhatsApp gets 'HD Photos' option for sending high-res images. Read 1 October 2026.
- Techloy, June 2024, WhatsApp users can now set HD quality as default for photos and videos. Read 1 October 2026.
- JPEG committee, JPEG 1 (ISO/IEC 10918). Read 1 October 2026.
- WhatsApp Blog, May 2022, Reactions, 2GB file sharing, 512 groups. Read 1 October 2026.
- 9to5Mac, 4 December 2023, WhatsApp photo and video quality finally being fixed for iOS users. Read 1 October 2026.
Sign in with Google. Your first 20 credits are free, enough for 100 photos, and there's no card to add.