How to Compress Photos for Email Attachments
Shrink photos for Gmail, Outlook, and Apple Mail without wrecking detail. Use native resize first, then compress only what email needs.
Contents
To compress photos for email, keep the whole message under the strictest service in the chain, not just under your own outbox limit. For Gmail, that usually means staying below 25 MB; for Outlook internet accounts, aim lower. I treat 1 MB per photo as the boring target.
What size should photos be before you email them?
For normal screen viewing, make each photo about 1200 to 1600 px on the long edge and under 1 MB if you can. That gives Gmail, Outlook, and the recipient’s company mail server room for the message body and attachment encoding. Small wins here matter.
Google’s Gmail help lists 25 MB for personal accounts and says larger total attachments are replaced with a Google Drive link. Microsoft is tighter in its own wording: Outlook support says internet mail accounts such as Outlook.com or Gmail use a 20 MB email size limit, while Exchange defaults to 10 MB.
That is the part people miss. A 19 MB folder of photos can still be a bad email because the message itself adds overhead, the recipient may have a smaller cap, and some corporate filters simply hate large attachments. If you are sending proofs to a client, I would rather send eight 700 KB images than two 9 MB originals.
First, try the native resize option
Use the tool already on the device before you open a website. On iPhone Photos or Android Gallery, share the image and look for a size picker in the share sheet; on desktop, macOS Preview and classic Outlook can reduce exported or attached image size. It is not fancy. It often works.
Native tools are fastest when the photo only needs to be seen, not printed. For a LinkedIn headshot approval, a real-estate preview, or a Shopify product draft, the recipient doesn’t need a 4032 px original from your phone. They need enough detail to judge the crop, expression, edge cleanup, and color.
Almost. The catch is that some resize controls change only the displayed size inside the message, not the file behind it. Microsoft says new Outlook for Windows can change how large an inserted image appears in the email body but can not reduce that image’s file size. If the attachment panel still says 6.8 MB, believe the panel.
Then compress the photo in the browser
When native resize leaves the file too large, use an in-browser compressor and check the output at 100 percent before attaching it. The right result is not the smallest possible file. It’s the smallest file that still keeps skin texture, product edges, and small text readable.
I ran a local test for this article using a 1600 x 1200 JPG fixture: 465,150 bytes before compression. After resizing to 1280 x 960 and exporting WebP at quality 70, the file landed at 280,344 bytes in 0.21 seconds. That is a 39.7 percent drop without changing the visible subject.
You can do the same with RoundCut’s in-browser image compressor when the file needs to stay on your device. The downside: browser tools still need your phone or laptop to do the work, so a very old device can feel slow with a batch of large camera shots. One photo is fine. Fifty is a different mood.
If the file is still too large, cut pixels before you squeeze quality. The resize an image online path usually beats dragging the quality slider down until faces look waxy. For a longer breakdown of quality settings, I wrote a separate guide on how to compress images without losing quality.
Should you use JPG, WebP, or PNG for email?
Use JPG for the safest email attachment, WebP when you know the recipient can open it, and PNG only when transparency or sharp interface text matters. Email is old plumbing (which is why boring compatibility still wins). The best format depends on who opens the file.
JPG is still the safe bet for photos going to a mixed audience: clients on Outlook, vendors on Gmail, someone forwarding the thread from an iPhone. It handles natural photos well and almost every preview pane understands it. The trade-off is visible artifacts if you push quality too low.
WebP often gets smaller for web use, and it’s useful when you’re emailing images that will later go into a site, product page, or ad mockup. If that is the job, convert a JPG to WebP and send both only when the recipient needs the original too. Don’t make a nontechnical client guess which one to open.
PNG is the specialist. Logos, screenshots, and transparent cutouts can look worse as JPG because edges smear and flat color blocks pick up noise. For e-commerce teams, I usually keep the master PNG and email a compressed JPG preview; the heavier original goes by Drive, Dropbox, or the project folder. That same logic shows up in our guide to smaller product images.
What if the photo still will not send?
If the email still fails, stop fighting the attachment box and send a link. Apple Mail Drop can send files up to 5 GB, but the recipient’s app may still impose a smaller message limit, and the link expires after 30 days. Good fallback. Not always the right deliverable.
For a one-off approval, a link is fine. For invoice records, legal review, or a marketplace support ticket, a real attachment is often easier to archive (boring, but searchable later). That is why I still compress first for Gmail and Outlook instead of assuming a cloud link will behave.
For batches, split the job: compress previews for email, keep originals in a shared folder, and name files so nobody has to open all of them to find the hero shot. If you’re handling many product photos, the bulk compression workflow is the cleaner pattern.
Next email, aim for under 1 MB per photo, attach three or four, then send the originals only when someone asks. Less drama, fewer surprise Drive links, and a message that opens before the client has time to wonder why the thread stalled.
