Compress an Image for Email Under 25 MB (Free)
Short answer: your mailbox counts the whole message (body, signature and every attachment together) and Gmail stops it at 25 MB, Outlook.com commonly at 20 MB, corporate accounts often lower. Four modern phone photos are enough to blow that number on their own. The fix takes about a minute: compress each image to roughly 1 MB at 85–90% quality with the free BeeToolify Image Compressor, attach the compressed copies, and the message sends with room to spare. The compression runs in your own browser, so family photos and signed documents never sit on a stranger's server while you wait.
What's the actual attachment limit?
The number belongs to the recipient's mail system as much as yours, and an admin can change it. These are the caps people run into most. The error message is always the source of truth:
| Mailbox | Attachment cap | What happens past it |
|---|---|---|
| Gmail (personal) | 25 MB, whole message | Send button errors; Google offers a Drive link |
| Google Workspace (work/school) | 25 MB default, admin-adjustable | Some organizations raise it; the error names the real number |
| Outlook.com / Hotmail | Commonly 20 MB | Send fails or the larger attachment is redirected to OneDrive |
| Yahoo Mail | 25 MB | Send blocked with a size warning |
| Corporate Microsoft 365 / Exchange | Often 10–20 MB, set by IT | Bounces back with the limit in the text |
| School and university accounts | Varies, frequently 10–25 MB | Older student portals run stricter caps than the inbox does |
The safe default: keep the total message under 20 MB, which clears Gmail with 5 MB to spare, clears Outlook.com, and stays inside most corporate limits too. Below you'll see why that number is easy to reach even with a few photos.
Attachment math: how five photos break the cap
This is where most people get caught, because the files themselves look harmless in the folder:
- Phone photos are heavy now. A 12-megapixel-plus camera writes 4–8 MB JPEGs as standard. Five of them at 5 MB is 25 MB, exactly Gmail's ceiling before a single word of your message is counted.
- The cap covers the whole message. Body text, a long signature, a logo in the signature, quoted history from a reply chain: all of it shares the budget with your attachments.
- Older photos add up too. Scans, PDFs of a contract, a photo of a document photographed at full resolution: each is 2–10 MB, and three of them already look like a problem.
- The 80% rule keeps you out of trouble. Target 80% of whatever the cap is (20 MB for Gmail, 16 MB for Outlook) because the last few megabytes are exactly where a reply chain quietly lives.
The arithmetic is the whole argument for compressing: at 1 MB per photo, a generous ten-image email is around 10 MB and sends everywhere. At native camera size, three images can already fail.
Per-image targets that keep photos sharp
Use these numbers rather than guessing a percentage. They're what fits common mailbox caps while leaving images look sharp on a normal screen:
| What you're sending | Target size | Settings and notes |
|---|---|---|
| Phone photos (JPEG) | 500 KB – 1 MB each | 85–90% quality; sharp enough for printing at postcard size |
| Screenshots and UI captures | 100 – 300 KB | JPEG at 80% is fine; keep PNG only when tiny labels must stay crisp |
| Photos of documents | 300 – 600 KB each | Shoot straight-on, good light: legibility comes from focus, not megabytes |
| Multi-page documents | 1 – 3 MB as one PDF | Merge first, then compress the PDF once |
| Logos and line art with transparency | Keep PNG, reduce pixels | Downsize to the display size; PNG doesn't benefit from quality sliders |
| RAW or TIFF files | Convert first | Most inboxes handle JPEG fine; convert with the Image Converter, then compress |
| Video | Not an attachment | Nothing local shrinks video enough. Use a link, see below |
The HEIC trap: why the picture "disappears"
There's one failure that has nothing to do with size, and it catches iPhone senders constantly. iPhones save photos as HEIC by default. It's a fine format (smaller than JPEG at the same quality), but the recipient on Windows or an older Android phone often can't open it: they see a blank thumbnail, a file they can't preview, or an attachment their mail app silently refuses.
The fix lives on the sending side, and it takes two taps: open the photo, tap Share → Options → Image Format → JPEG, then attach. To stop thinking about it altogether, set Settings → Camera → Formats → Most Compatible so the camera writes JPEG from now on. No web tool can convert HEIC for you (browsers ship no decoder for it, which is why honest ones report the error instead of pretending), so exporting as JPEG on the phone is the reliable route.
Screenshots deserve a similar note: they're mostly flat color and text, so they compress extremely well, but a full-resolution capture of a small window is wasted pixels. Crop or resize first if the dimensions are absurd. The text stays sharper after resizing than after aggressive quality reduction.
The 4-step workflow
- Find out the real cap. Send the message and read the error, ask the recipient, or assume 20 MB if nothing tells you otherwise.
- Export iPhone photos as JPEG with Share → Options → Image Format if they're HEIC. Do this before compressing, not after.
- Open the Image Compressor on phone or desktop, drop in the images, set the target (1 MB for photos, 300 KB for screenshots), keep quality at 85–90%, download the copies. Free, no signup, works offline after the first load.
- Attach the copies and check the total before sending. Documents? Combine them in order with the PDF Merger and compress that single file instead of sending six separate attachments.
One honest caveat: if you're sending the same photos to several people, or they're video or over 50 MB each, compression is the wrong tool. That's what a cloud link is for. Everything under the cap is faster as an attachment.
When a cloud link beats an attachment
Upload a file to your storage service, share a link, and the size limit stops mattering entirely. That's genuinely the right call for video, for hundreds of photos, and for files that several people need over time. But be deliberate about it:
- Permissions are the risk. "Anyone with the link" means exactly that. The file opens for whoever obtains the link, forwarded or leaked, until you revoke it. Restrict to named people when the content matters.
- The files move to a third party. A photo that only ever sat on your device now lives on someone else's server, under their retention rules. For family pictures, signed documents, tax pages or medical records, an attachment compressed locally keeps the trail shorter.
- Recipients have to click, sign in and wait. Under 25 MB, an attachment is faster for everyone involved, which is most everyday email.
The pragmatic split: compress to fit when the files are personal or modest; link out when they're large or shared. Nearly every "this email won't send" moment falls on the first side of that line.
Quick FAQ
What is the attachment size limit for Gmail?
Gmail allows up to 25 MB for a whole message (body, signature and attachments combined). Past that, the send button errors out and Google points you toward a Drive link instead. Outlook.com and Hotmail commonly cap at 20 MB, Yahoo Mail at 25 MB, and corporate Microsoft 365 or Exchange accounts often sit lower (10 to 20 MB) because an admin sets that number. The error or bounce message always names the real limit for your account, which is why it beats any table.
How do I compress a photo so it fits in an email?
Open the Image Compressor, drop in the photos you want to send, set a target around 1 MB (500 KB works well for smaller shots), keep quality at 85–90%, and download the compressed copies. Attach those instead of the originals. The whole process runs inside your browser: the photos are read and re-encoded on your own device, and the download is the only network step. Nothing is uploaded.
Why can't the recipient open my iPhone photo?
Because iPhones save photos as HEIC by default, and Windows and many Android phones cannot open that format without an extra codec, the recipient sees a blank thumbnail or an unreadable file. Fix it on the sending side: open the photo, tap Share, then Options, then Image Format, and choose JPEG before you attach it. To skip the step entirely, set Settings, then Camera, then Formats, to Most Compatible so the camera writes JPEG every time.
What size should each image be?
For phone photos, about 500 KB to 1 MB each at 85–90% quality: four or five of them land near 5 MB, comfortably inside any mailbox cap. Screenshots are mostly flat color and text, so 100–300 KB is normal. JPEG at 80% quality is plenty unless tiny labels must stay razor sharp, and in that case keep PNG and shrink the pixel dimensions instead. Documents are better as one file: combine them with the PDF Merger, then compress a PDF without losing quality if the bundle still runs long.
Does zipping attachments make them smaller?
Barely, for images. JPEG photos, PNG screenshots, PDFs and video files are already compressed, so a ZIP of them comes back only a few percent smaller, sometimes not at all. Zipping helps with spreadsheets, text files, code or RAW photos. When images are what blow the cap, compressing each one to the targets above does far more than any archive will.
Is it safe to send documents as email attachments?
It is how most people work, but email keeps copies: one in your sent folder, one on the recipient's server, and copies in between. For contracts, tax pages, medical records or anything with an account number, use a password-protected PDF and pass the password through a different channel (a text message, not the same thread). Whatever you send, compress locally first: the file is already minimized before it leaves your device, and it never sat on a third-party conversion server in the process.
When should I use a cloud link instead of an attachment?
When the files are far over the cap (video, hundreds of photos, design files over 50 MB each), or when the same set goes to several people. Upload to a storage service you trust and send a link, but set the sharing permission on purpose: 'anyone with the link' means anyone who obtains it can open the files, and they now live on a third-party server. For a handful of photos under 25 MB, an attachment compressed on your own device is both simpler and more private.