How to Compress an Image for Email
Email attachment limits are smaller than the number they advertise, and your recipient is probably on a phone. Here is how to make photos that always arrive and always open.
To email a photo reliably, get each image down to one or two megabytes and keep the whole message under about ten. That is well inside every provider limit, it survives strict corporate mail servers, and it opens instantly for a recipient reading on a phone.
The trouble with email attachments is that the advertised limit is not the real one, and the person receiving your message rarely has the same inbox you do. Once you understand both facts, the fix is simple: compress before you attach, and past a certain size, send a link instead.
The limits, and why they lie
Every provider publishes a maximum attachment size. Gmail says 25 MB, with anything larger pushed to Google Drive automatically. Outlook.com caps at 20 MB. Plenty of corporate Exchange servers are tightened to 10 MB by an administrator you will never meet.
| Service | Stated limit | Real usable file |
|---|---|---|
| Gmail | 25 MB (then Drive) | About 18 MB |
| Outlook.com | 20 MB | About 15 MB |
| Typical corporate Exchange | 10 MB | About 7 MB |
Where does the missing space go? Email cannot send raw binary files, so every attachment is re-encoded into text using Base64, which inflates it by roughly 33 percent. A 25 MB limit is therefore really about 18 MB of actual file. Worse, the limit usually applies to the whole message, so five 4 MB photos plus that inflation can bounce even though each one looked fine on its own.
Your recipient is probably on a phone
There is a second reason to shrink photos that has nothing to do with limits. More than half of email is now read on a phone. A 12-megapixel photo straight from a camera is far larger than any phone screen can show, so all those extra pixels are downloaded, chew through mobile data, and are then thrown away to fit the display. You are making someone pay to receive detail they never see.
A photo resized to around 1600 pixels on its longest edge looks sharp on any screen and weighs a fraction of the original. Start with the image resizer and you will often be under the limit before you compress at all.
Resize photos before emailingCompressing a single photo
For one attachment, the goal is a clean JPG at sensible quality. Here is the order that gives the best result:
- Resize the longest edge to around 1600 to 2000 pixels if the photo is straight from a camera.
- Compress at JPEG quality 80. That is invisible loss for a photo and a big size cut.
- Check the result. One or two megabytes per image is a comfortable target for email.
- If you want a firm ceiling, aim each file at 1 MB and forget the maths.
The image compressor lets you set a quality level or an exact size, and the compress to 1MB page hits that ceiling for you so a handful of photos stays well inside any inbox.
Compress a photo for emailSending a batch without a bounce
Attaching a whole event album is where messages bounce most, because the total climbs fast. Ten untouched phone photos can easily top 40 MB before Base64 even adds its third on top. Compress the set together first.
- Run the whole folder through a batch compressor rather than one photo at a time.
- Keep each image around 1 MB so ten of them still fit a strict 10 MB server.
- Download the results as a ZIP and attach that — one file, cleanly compressed, easy for the recipient to save.
The bulk image compressor does exactly this: many photos in, one ZIP out, all of it processed on your own device.
Compress a whole album at onceWhen to stop attaching and send a link
There is a size past which fighting the compressor is the wrong move. If your compressed message still approaches 10 MB, do not push it — put the files in cloud storage and paste a share link. It sidesteps every server limit, does not clog the recipient inbox, lets them download only what they want, and gives you the original quality on the other end. This is what Gmail already does automatically above 25 MB, and there is no reason to wait for that threshold.
Bundling many images as one PDF
If you are emailing scanned documents, receipts, or a set of pages that belong together, a single PDF is often tidier and smaller than a pile of loose images. The recipient gets one file to open, in order, that prints correctly. The image to PDF tool combines JPGs and PNGs into one document in your browser.
Combine images into one PDFWhich format to attach
For photos, attach JPG. It opens in every mail client, on every phone, and inside every preview pane, and at quality 80 it is small. Save PNG for screenshots and images with sharp text, where JPG would smear the edges — but expect those to be a little heavier. If you are on an iPhone, your camera may be producing HEIC files that many recipients cannot open at all; convert those to JPG before you attach them so nobody has to install a codec just to see your picture.
- Photo of a person, place, or object: JPG at quality 80.
- Screenshot of text or a chat: PNG, so the text stays crisp.
- iPhone HEIC photo: convert to JPG first — some inboxes will not preview it otherwise.
- A stack of pages that belong together: one PDF beats many loose files.
Whatever the source format, the general image compressor auto-detects it and re-encodes to something small and universally readable, so you rarely have to think about the format at all.
Mistakes that cause bounces
- Attaching photos straight off the camera roll — the most common reason a message is rejected.
- Compressing each photo to fit but forgetting the total across all of them, plus the Base64 inflation on top.
- Sending PNG photos, which can be several times heavier than the same picture as JPG.
- Zipping files that are already compressed and assuming the ZIP shrank them — a ZIP of JPGs is barely smaller than the JPGs.
Size for the strictest inbox in the thread, not the one you happen to have open.
The arithmetic behind a surprise bounce usually looks like this — a set of photos that each felt small, plus the Base64 tax on top, crossing the line as a group:
5 photos x 3.9 MB = 19.5 MB of files
+ Base64 encoding ~ 26.0 MB on the wire
Gmail 25 MB limit -> message rejectedQuick answers
Why did my 22 MB attachment fail on Gmail?
Base64 encoding inflated it past the real ceiling, or the total message with headers crossed the line. The stated 25 MB leaves room for only about 18 MB of actual file.
Does compressing a photo ruin it for the recipient?
Not at sensible settings. At quality 80 and a reasonable size the difference is invisible on any screen, and it is far better than a photo that never arrives.
Are my photos uploaded when I compress them here?
No. Every Pixora tool works in your browser, so your photos are compressed locally and only leave your device when you attach them to the email yourself.