How to compress images for email comes down to one move: re-encode each photo at quality 80 before you attach it. Gmail caps a whole message at 25 MB, Outlook internet accounts at 20 MB, and Exchange business accounts default to 10 MB, and a single phone photo already runs four to six megabytes.
That single fact, the cap covers the whole message and not each file, is the one people miss most. My guide to compressing images for every upload destination walks through email, the web, and document uploads together at a survey level. This page is the inbox deep dive: the exact caps for the mail clients you actually use, why the number that bites you is smaller than the one you read, and the fastest route under any of them.
Email Attachment Size Limits for Every Provider (2026)
Three numbers cover almost every inbox: Gmail allows up to 25 MB per message, Outlook internet accounts cap at 20 MB, and Outlook Exchange business accounts default to 10 MB, all of them counting the whole email, not just the files stapled to it.
Gmail: 25 MB Per Message, Then a Drive Link
Gmail lets you send up to 25 MB in attachments in one message, and if a single file is bigger than that, Gmail switches the attachment to a Google Drive link automatically rather than blocking the send (Google Support, Send attachments with your Gmail message). That auto-fallback is the most forgiving of the three limits on this page, but it also means a batch that sends without an error may have quietly become a link nobody clicks instead of a photo already sitting in the inbox.
Outlook Internet Accounts: 20 MB, Attachment Plus Email
For internet email accounts such as Outlook.com or Gmail connected through Outlook, the email size limit is 20 megabytes (Microsoft Support, Reduce attachment size to send large files with Outlook), and that limit includes both the size of the attachment and the size of the email itself, so a long message with a signature image and a quoted thread eats into the same budget as your photos.
Exchange Business Accounts: 10 MB by Default
Exchange accounts, the kind most workplaces run, default to a 10 MB email size limit (Microsoft Support, Reduce attachment size to send large files with Outlook), and it is often set even lower by an administrator. A single 4.5 MB phone photo clears that cap alone, but attach three of them, an ordinary thing to do, and the message is over the email attachment size limit before you have written a word of the email itself.
| Provider | Published cap | What happens over it |
|---|---|---|
| Gmail | 25 MB per message | Switches to a Google Drive link automatically |
| Outlook, internet account | 20 MB per message | Send fails until the message shrinks |
| Outlook, Exchange (business) | 10 MB by default | Send fails; admins can set it even lower |
Two details in the fine print catch more people than the headline numbers do. Your cap is also not the recipient's cap: a message that fits under your own provider's ceiling can still bounce off a stricter server on the receiving end, particularly a work Exchange account with its own lower limit set by an administrator, which is why the practical target sits under the published number, never right at it.
Why Your Real Limit Is Smaller Than the Number You Read
Your real limit is smaller because the cap counts the whole email, not just the file, and because attaching it makes it heavier than it looks on your disk. Email attachments travel encoded in Base64, a text-safe wrapper that inflates the raw file size by roughly 33 to 35 percent in transit (Cleverly, Outlook attachment size limit), so a batch that looks fine in File Explorer can land heavier than the provider's published number once it is actually sent.
Divide each published cap by roughly 1.34, the middle of that 33 to 35 percent range, and you get the safe raw-file target, the number to aim your compressed photos under, not the number printed on the help page. Gmail's 25 MB cap comes out to about 18.7 MB of real attachments. Outlook's 20 MB internet-account cap comes out to about 14.9 MB. Exchange's 10 MB default comes out to about 7.5 MB. Nobody publishes these three side by side, so here they are.
| Provider | Published cap | Safe target after ~34% encoding overhead |
|---|---|---|
| Gmail | 25 MB | ~18.7 MB |
| Outlook, internet account | 20 MB | ~14.9 MB |
| Outlook, Exchange (business) | 10 MB | ~7.5 MB |
Aim under the safe column, not the published one, and you stop finding out the hard way which number was real.
How Many Photos That Actually Fits
Put the safe targets next to the canonical result of compressing a phone photo at quality 80, roughly 900 KB, and the count gets concrete. At Gmail's 18.7 MB safe target, about 20 compressed photos fit in one message with a little room left over. At Outlook's 14.9 MB safe target, that is closer to 16 photos. At Exchange's 7.5 MB safe target, it drops to around 8, which is a lot less headroom than "10 MB" sounds like on its own.
How to Compress Images for Email
Compress the photo before you attach it, using whichever tool is already open, and the built-in option on your device is usually enough for a single email; reach for something stronger only when you need an exact size.
iPhone Mail: Choose Small or Medium
Select the photos in the Photos app, tap Share, and choose Mail. iOS prompts you to pick a size, Small, Medium, Large, or Actual Size, before the message sends, and choosing Small or Medium cuts the file meaningfully with no extra app. This is the fastest route if you are already on the phone that took the picture.
Android Gmail: Automatic Shrink, Then a Drive Link
Attach a photo directly inside the Gmail app on Android and it already shrinks large photos automatically, generally down to around 1,600 pixels on the long edge, before you notice anything happened. If the file is still too big after that, Gmail offers to send it as a Google Drive link instead of an attachment, the same fallback the 25 MB cap triggers on desktop.
Windows: Send To, Mail Recipient
Close any email client first. Select the image files in File Explorer, right-click, hover Send to, and choose Mail recipient. A dialog box appears offering a smaller photo size before it builds a new message with the resized copies attached, all without opening Paint or Photos separately.
Mac Mail: The Image Size Dropdown
Open Mail, start a new message, and drag your photos into the compose window. An Image Size dropdown appears near the bottom of the window; choose Small or Medium and Mail resizes every attached photo to that setting before sending, the same lever as the iPhone version of the same app.
Compress Image to 500KB for Email
Built-in size prompts are good for one email, but none of them tell you the exact number you landed on, and some forms and providers do publish a hard per-file cap around 500 KB. For that, run the photo through the compressor here and re-encode toward that exact target instead of guessing at Small versus Medium. I built and run this compressor, and the homepage demo is a real result, not a guess: a 497 KB JPEG comes back 214 KB as WebP at quality 80, 56.9 percent smaller, same picture. It needs no signup for files up to 25 MB, and a typical 4.5 MB phone photo comes back around 900 KB at the default quality of 80, most of the way to a 500 KB target already; dropping the quality slightly further from there gets you the rest of the way without a second app.
Do Built-In Email Compression Tools Do Enough?
Usually, yes, for a single photo attached the normal way; the gap shows up with multiple full-resolution photos or a hard per-file limit the built-in prompt cannot target.
None of the four built-in methods above expose a quality slider the way a dedicated compressor does. iPhone's Small, Medium, and Large labels and Android's automatic 1,600 pixel resize both work on pixel dimensions primarily, trading detail for a preset step rather than a number you control, which is why two photos both saved as Medium from two different phones do not always land at the same file size.
iPhone Mail's Small and Medium options and Android Gmail's automatic shrink both work at the message level, not the per-file level, so they solve whether the email sends without ever telling you the resulting file size in kilobytes. That is fine until a web form, a passport photo portal, or a job application wants a number under a hard cap, at which point a size prompt with no number attached stops being useful and a compressor with a real quality setting and a visible result size takes over.
The math changes fast once more than two or three photos are involved, since Gmail, Outlook, and Exchange all count every attachment toward the same one number, not per file. Running a whole folder through a batch compressor before opening the email client turns a slow one-photo-at-a-time chore into a single drag-and-drop pass, already sized under the safe target from the table above before anything gets attached.
Most people learning how to compress photos for email only need the built-in prompt once and never think about it again, and that is the right amount of effort for a single photo to a friend. The moment the destination cares about an exact byte count, reach for the tool covered above instead of guessing between Small and Medium.
Should You Zip Your Photos Before Emailing Them?
Rarely by much: a JPEG is already a compressed file, so zipping a folder of JPEGs usually saves only a few percent, not enough to rescue a batch that is meaningfully over the limit.
JPEG compression already removes the repeating patterns a zip algorithm looks for, so running a second, lossless compressor over an already-lossy file finds almost nothing left to shrink; the same photo zipped and unzipped comes back close to byte-for-byte the size it started, occasionally a few kilobytes smaller from container overhead alone, never a meaningful cut.
Zipping earns its keep for a different reason: bundling many small files under one attachment count, or compressing formats that are not pre-compressed, like a folder of RAW files or uncompressed TIFFs (Microsoft Support, Reduce attachment size to send large files with Outlook). For ordinary JPEGs from a phone, compress the images themselves first and skip the zip step entirely.
When Should You Send a Cloud Link Instead of an Attachment?
Send a link when the recipient needs the file at full resolution, or the batch is too big to be worth compressing at all.
Gmail already builds this in: attach something over 25 MB and it inserts a Google Drive link automatically rather than failing the send, the same behavior already covered above. Outlook does not switch automatically, but OneDrive, Dropbox, and iCloud all offer the same one-click share link, and Microsoft's own guidance points to exactly this option once compressing and zipping stop being enough.
A link is also the better call for volume. Thirty vacation photos are a miserable attachment list even compressed to nothing, and a shared album handles that job better than any inbox was ever built to; if you want to reduce photo size for email instead of switching to a link, that only makes sense for a handful of files, not thirty.
When Is Compressing the Wrong Move?
Do not compress a photo you are sending to be printed, edited, or archived at full quality; every save at quality 80 or below throws away detail permanently that a designer or print shop needs back.
Compression also will not rescue a message that is over the limit because of the text, not the pictures. A long quoted thread carrying six replies of inline images can weigh more than the new photo you just attached, and no amount of recompressing that one file fixes a limit the conversation itself is breaking. In both cases, the fix is a shorter thread or a cloud link, not a lower quality setting.
Everywhere else, the move is the one at the top of this page: compress the batch below the safe target before you hit send, and the resulting size tells you whether the email actually goes.