You attach four photos from your phone, hit send, and the email bounces back: attachment too large. Modern phone cameras produce files so big that a handful of them blows past what email was ever designed to carry. The fix isn't to send fewer photos — it's to shrink each one so it's a fraction of the size while still looking perfectly good on screen. Here's why the problem happens and exactly how to solve it.
Why photos are too big for email
A single photo from a recent phone can be 3–12 MB straight out of the camera. That's because the sensor captures 12, 48, or even 200 megapixels, and the file stores every one at high quality. But nobody viewing your email needs a 48-megapixel image — their screen can only show a couple of million pixels at once. You're sending twenty times more data than the recipient can ever see.
Email providers cap attachment size to keep servers sane. The common limits:
| Provider | Attachment limit |
|---|---|
| Gmail | 25 MB |
| Outlook / Microsoft 365 | 20–25 MB |
| Yahoo Mail | 25 MB |
| Many corporate servers | 10 MB or less |
Note two things. First, the limit usually applies to the whole email, so four 6 MB photos already breach a 20 MB cap. Second, attachments are encoded for transit in a way that inflates them by roughly a third, so a "24 MB" set of files can actually arrive as ~32 MB and bounce. Aim well under the stated limit.
What size a photo actually needs to be
For a photo someone will simply look at — on a phone, laptop, or in a preview pane — you need far less than the original. Two levers do the work:
- Dimensions. A width of 1600–2000px is plenty for on-screen viewing and even a decent print at postcard size. Your 6000px original can lose three-quarters of its pixels with no visible difference on a screen.
- Quality. Saving as JPEG at 80% quality discards data the eye doesn't notice. Combined with resizing, this is where the big savings come from.
Do both and a 9 MB photo typically lands around 300–600 KB — meaning you could attach thirty of them and still stay under Gmail's limit. The reason resizing matters so much is covered in our guide to resizing for the web, and the quality-slider logic in compressing without losing visible quality.
How to shrink photos for email, step by step
- Open the Image Converter and Compressor tool.
- Drop in all the photos you want to send.
- Set output to JPG, quality around 80%.
- Set a maximum width of 1600–2000px.
- Download the results and attach those to your email instead of the originals.
Everything runs in your browser, so the photos are never uploaded to a third-party server on the way — which matters when you're emailing anything personal.
Shrinking is one-way: you can't rebuild the detail you dropped. Always keep your full-resolution originals and send copies. If you ever need to print large or re-edit, you'll want the untouched file.
How many photos can you actually attach?
Once you've shrunk your photos, the maths becomes reassuring. Say each resized photo lands at around 500 KB. Against a typical 25 MB Gmail limit — and remembering to leave headroom for the roughly one-third encoding overhead, so budget for about 18 MB of real files — you can comfortably attach 30 or more photos in a single email. Compare that to the originals: at 8 MB each, you'd bounce after just two. The table makes the contrast plain:
| Photo size | Fits under ~18 MB budget |
|---|---|
| 8 MB (original) | ~2 photos |
| 2 MB (lightly compressed) | ~9 photos |
| 500 KB (resized + compressed) | ~36 photos |
Why your email app's "resize" often isn't enough
Both Outlook and Apple Mail offer to shrink images when you attach them, and they can help — but they're blunt. Outlook's "Resize large images" picks one fixed dimension for everything and only kicks in for certain attachment types; Apple Mail's small/medium/large picker at the bottom of the window gives you little control over the final size and none over the format. For a couple of casual snaps that's fine. When it matters that the email actually sends — a job application, a set of photos to a client, anything with a hard size ceiling — it's better to resize and compress deliberately first, confirm the total size yourself, and attach files you know will fit. That way there's no surprise bounce after you hit send.
When you shouldn't shrink
If the recipient specifically needs the full-quality file — a designer, a printer, a photo lab, or someone who'll edit the image — don't compress it. Instead, get around the size limit another way: share a link from a cloud drive, or use a file-transfer service. Shrinking is for photos meant to be viewed, not for master files meant to be worked on. For a sense of when compression is safe versus lossy, Google's image optimization guidance is a useful reference.
Sharing full-quality files another way
When shrinking isn't appropriate — the recipient needs the untouched originals, or you're sending far more photos than any inbox will hold — skip the attachment entirely and send a link instead. Upload the full-resolution files to a cloud drive (Google Drive, iCloud, Dropbox, OneDrive) or a dedicated file-transfer service, then paste the share link into your email. There's no attachment limit to worry about, the recipient downloads only what they want, and nothing bounces. It's the right approach whenever the set is large or the quality must stay intact — and it pairs neatly with shrinking: attach small previews so the recipient sees the photos immediately, and link the full-size originals in the same message for anyone who needs them.
In short
Email bounces big photos because phone cameras capture far more detail than any screen can show and email caps total attachment size. Resize to around 1600–2000px, save as JPEG at roughly 80%, and a multi-megabyte photo shrinks to a few hundred kilobytes with no visible loss — small enough to send a whole set at once. Keep your originals, do the shrinking in your browser so nothing is uploaded, and only skip compression when the other person genuinely needs the full-resolution file.
Resize and compress in your browser, then attach the smaller files. No upload, no account.