How to reduce image size for email and WhatsApp

The real attachment limits you're fighting

Most "file too large" errors come from one of a few well-known ceilings. Email providers cap the total size of a message including all attachments, and the smallest cap in the chain wins. If you send a 30 MB photo from a provider that allows it to a recipient whose mailbox only accepts 20 MB, it bounces on their side. The numbers below are the commonly published limits; providers occasionally adjust them and corporate mail servers often set lower caps.

Why WhatsApp blurs your photos (and how to stop it)

When you share a picture in a WhatsApp or Messenger chat the normal way, the app re-encodes it to save bandwidth. It downscales the resolution and applies heavy JPEG compression, which is why a crisp 4 MB photo can arrive as a soft 200 KB version with visible blocky artefacts. The loss happens at the messenger's end, not yours.

The fix is to send the file as a document rather than a photo. In WhatsApp, use the attach (paperclip or +) menu, choose Document, then pick your image. Sent this way it transfers as-is, at full resolution, with no extra compression. The trade-off is that the recipient sees a file to download rather than an inline preview, and the file counts toward their storage. Use it when quality genuinely matters (a contract scan, a high-detail product shot) and the normal photo path for casual snaps.

• Photo / inline share: convenient, shows a preview, but re-compressed and downscaled. Fine for everyday pictures.
• Document share: keeps the original resolution and quality untouched, up to a very large per-file ceiling. Best for anything that must stay sharp.
• If the file is too big even as a document, shrink it deliberately first so you control the quality loss instead of letting the app decide.

Resize first, then compress

There are two independent ways to make an image smaller, and using them in the right order gives the best quality at a given file size. Resizing reduces the pixel dimensions (a 4032 × 3024 phone photo down to 1920 × 1440, say). Compressing keeps the dimensions but lowers JPEG quality to cut the file weight. For sharing, you almost always want to do both: resize to a sensible viewing size, then compress.

Why order matters: a 12-megapixel photo is wildly larger than anyone needs to view on a phone or laptop screen. Dropping it to around 1600–2048 px on the long edge throws away resolution nobody will see, which removes most of the file weight before you even touch quality. Then a light compression pass gets you the rest of the way, instead of crushing a huge image with brutal compression and visible artefacts.

1. Decide the longest edge you actually need: ~1080 px for chat, ~1600–2048 px for email someone might view on a laptop, full resolution only if it will be printed.
2. Resize the image in pixels to that long edge, and the other dimension scales automatically to keep the proportions.
3. Compress it toward your target size: for email, anything from 300 KB to 2 MB per photo looks great on screen.
4. Check the result, and nudge the quality up a little if you over-shrank and it looks soft.

Sending many photos in one email

A single 5 MB photo fits comfortably under a 25 MB cap, but ten of them do not, and that is the usual reason a multi-photo email refuses to send. The total of all attachments has to clear the limit, so the practical move is to shrink every photo a little rather than agonising over one. Doing them one at a time is slow, so process the batch together.

Drop the whole folder into the bulk image compressor, set a target, and download the lot as a zip. If your photos are different sizes, you can also resize a batch of images to a common long edge first, then compress. Ten 5 MB photos becoming ten 800 KB photos turns a 50 MB email that bounces into an 8 MB email that sends instantly.

Picking the right format to share

Format affects both file size and whether the recipient can even open the file. For photographs you share by email or chat, JPG is the safe default: it compresses photos efficiently and opens everywhere. Save PNG for screenshots, logos, or anything with sharp text or transparency, but expect PNG photos to be several times heavier than the JPG equivalent.

• Photographs → JPG. Smallest size for the quality, and universally supported.
• Screenshots, diagrams, text, transparency → PNG, accepting the larger file.
• Sharing where you control both ends and want the smallest file → convert to WebP, which beats JPG at the same quality. Confirm the recipient's app can open WebP, as a few older ones still cannot.
• Photo straight off an iPhone that won't open for the recipient → it's probably HEIC; convert it to JPG before sending (see the HEIC to JPG guide).

If you only need a smaller file and not a different format, you don't have to convert at all. Compressing the JPG in place keeps the format and only lowers the weight.

Avoiding common quality mistakes

Most disappointing results come from a handful of avoidable habits rather than the tools themselves. A few rules keep your shared images sharp.

• Don't re-compress an already-compressed JPG repeatedly, because each save throws away more detail. Start from the original, shrink once, and send that.
• Don't compress, then forward the small version, then compress again. Generational loss compounds fast and shows as muddy colour and blocky edges.
• Don't screenshot a photo to make it smaller — you lose resolution and add the screen's own compression. Resize the original file instead.
• Don't over-shrink for email. A 300 KB–2 MB photo looks great on any screen; squeezing to 50 KB is only worth it for a strict upload form, not a message.
• Keep the original. Once you've sent the small copy, the high-resolution version is gone if you overwrote it, so save the compressed file under a new name.

When the target is a strict number, such as a form that demands "under 100 KB" rather than a friendly email, switch from eyeballing quality to hitting an exact KB size, which lets you type the ceiling and download a file that lands just under it.