Drop the photos
Phone photos are 3–5 MB each — twelve of them and you are already blocked.
Gmail caps attachments at 25 MB and Outlook at 20 MB. A handful of phone photos blows past both. Batch-compress before you hit send.
Drop images here
or · JPG, PNG, WebP, GIF
Phone photos are 3–5 MB each — twelve of them and you are already blocked.
Pre-filled. This lands most photos around 150–400 KB each with no visible loss at normal viewing size.
The summary shows the before/after total so you know you are under the limit before sending.
Gmail is 25 MB, Outlook.com is 20 MB, and most corporate mail servers cap at 10–25 MB. Those limits count the encoded size, which is about 33% larger than the raw file.
For photos you are just sharing, quality 70–80 at 1600px is indistinguishable on a phone screen. For images people will print, stay at 90.
Yes — it downscales to the max dimensions you set. If the recipient needs full resolution, send a link instead of an attachment.
No. Compression runs locally in your browser. Nothing is transmitted.
Every provider quotes a raw file limit, but attachments are base64-encoded, which inflates them by roughly 33%. The real usable size is about three-quarters of the headline number.
| Case | Value | Why it matters |
|---|---|---|
| Gmail | 25 MB per message | ~18 MB of actual attachment bytes after base64 overhead. |
| Outlook.com / Microsoft 365 | 20 MB default | 33 MB with OneDrive sharing instead of a true attachment. |
| Yahoo Mail | 25 MB per message | Same encoding overhead applies. |
| iCloud Mail | 20 MB per message | Larger files route through Mail Drop automatically. |
| Corporate Exchange | Often 10 MB | The strictest common cap. Assume 10 MB for any workplace address. |
| iPhone Mail default | Provider dependent | iOS offers to resize images when sending five or more photos. |
Each 5 MB photo is 5 MB of someone else's storage and a slow download on mobile data. Use a link for anything over five images.
A 6000 px photo at quality 60 is still 2 MB. Cutting to 1600 px at quality 75 gets it under 300 KB with plenty of detail for email.
They are, and they are better for large sets. Attachments are for one or two images a recipient needs to keep.
The per-file report here tells you the exact byte count. Guessing is how you get a bounce-back after hitting send.
Screenshots are flat colour. PNG or WebP beats JPEG badly, and JPEG adds ringing around text you need to read.
| Free, this page | Bulk Image Kit $19 | |
|---|---|---|
| Batch limit | 20 images | Unlimited |
| Preset 1600 px / quality 75 | Yes | Yes, plus per-image tuning |
| Exact output size reported | Yes | Yes |
| Rename | Suffix | Pattern-based rename |
| Offline | After first load | Always |
25 MB total per message including encoding overhead, so roughly 18 MB of files. Practically, keep the whole message under 10 MB so it arrives instantly on mobile.
Base64 encoding inflates attachments by about a third, and the recipient's server may have a lower cap than yours. Compress to under 10 MB total to be safe.
One or two images: attach. More than five: share a link. Email was never designed for photo delivery.
Yes. EXIF, including GPS location, is dropped by the re-encode. When emailing photos to strangers that is usually the right outcome.
Bulk Image Kit is the same engine as a single offline file — unlimited images, resize + compress + watermark + rename, one-time $19, no subscription.
See Bulk Image Kit — $19