Compress Photos for Email

What actually limits email attachments

The published limits are friendlier than they look, and two hidden factors shrink them further. Email systems wrap attachments in base64 encoding for transit, which inflates every file by roughly a third: a batch that weighs 18 MB on your disk can occupy about 25 MB on the wire and trip a 25 MB ceiling that appeared comfortable in your mail client. On top of that, any company, university or hosted Exchange server sitting between sender and receiver enforces its own ceiling — often 10 MB — and refuses without negotiation. Compressing to 200 KB sidesteps both traps simultaneously: five photos weigh one megabyte raw and about 1.4 MB encoded, a figure no mail infrastructure anywhere refuses.

The receiving side has limits too, and they are easy to forget because they belong to someone else. A mailbox close to its storage quota may bounce or truncate incoming mail with heavy attachments, and a recipient reading on a metered phone plan feels every extra megabyte as waiting. Keeping each picture near 200 KB makes your message the kind that lands instantly, opens without a spinner, and never leaves anyone wondering whether the file will finish downloading.

Why JPEG is still the safest thing to attach

JPEG has been understood by every mail client, every phone operating system and every webmail interface for as long as email has carried pictures, which means your attachment renders as a preview everywhere without exception. Newer formats have not caught up on the desktop: several current versions of Outlook still refuse to display WebP inline, showing a blank box or a forced download instead. Since you cannot know what the person on the other end runs, attaching JPEG removes the guesswork entirely — the picture simply appears.

The exception worth remembering is screenshots. A capture full of small text stays crisper as a PNG, and PNG is just as universally supported as JPEG for display. The practical rule: photographs and anything with smooth colour transitions travel as JPEG, while captures of interfaces, documents or anything with fine lettering can ride along as PNG. This page defaults to JPEG because photos are the attachments that bloat mail — screenshots are small to begin with and rarely need the help.

The pre-send checklist

• Compress every picture first — five at 200 KB fit inside any mail system’s allowance with room to spare.
• Add up the combined weight of all attachments, not each file individually; the per-message limit applies to the total.
• Rename files before attaching so "scan_final_v3" and "IMG_4072" become names the recipient can actually tell apart.
• For four or more images, use the ZIP button above and attach one tidy archive instead of a pile of loose files.
• Decide whether each picture belongs in the body or as an attachment: things meant for viewing go inline, things meant for filing and printing go as files.
• Keep the uncompressed originals on your disk — the emailed copies are for reading, and any future print job deserves the full-quality versions.

Does Gmail shrink my photos automatically when I attach them?

No — not for true attachments. Gmail offers size choices when you insert images from Google Photos into the body, but files attached the traditional way travel byte-for-byte exactly as you added them, base64 wrapping aside. That is why compressing before attaching is the only step that gives you control: once the draft holds the original 4 MB file, the message carries 4 MB regardless of what the recipient would prefer.

I compressed everything and the message still bounced — what now?

Look past size. The most common remaining causes are a recipient mailbox over its storage quota, a company filter that dislikes batches of image attachments, or one file in the set that is corrupted in a way your mail client tolerated but the server did not. Resend in two smaller messages, attach a single ZIP instead of many loose files, and if one picture is suspect, re-export it from the source before trying again.

Should I compress photos before or after adding them to a draft?

Before, always. Many webmail clients begin uploading attachments the moment you drop them in, so attaching originals means waiting through large uploads that you are about to throw away. Compress first, then attach the finished files: the draft stays light, the upload is quick, and you never pay for bytes you did not intend to send.

Are there pictures that should not be squeezed to 200 KB?

Anything the reader must zoom into. Photographed contracts, dense schedules, whiteboards and handwritten notes need legible fine print, and 200 KB can soften exactly the strokes that matter. For those, either assign a larger target with the size box, or send the document as a PDF, which keeps text vector-sharp. Portraits, rooms, food, scenery and general photo-reportage all hold up well at 200 KB.

Will the pictures look blurry on the recipient’s phone?

No — phones are where 200 KB shines. A phone screen displays far fewer pixels than a desktop monitor, so a compressed photo rendered full-screen there uses nearly all the detail the file contains. The only place softness can appear is aggressive zooming on a large monitor, and even then the preview above lets you judge the trade-off before the file ever leaves your device.