Most email attachment size guides give you a single number and call it done. The problem is that the number on the box is not the number that actually sends. A 24 MB file can bounce off a 25 MB limit because Base64 encoding adds 33-40% overhead during transmission. Recipient servers have their own caps that override your provider’s limits. And the total message size — not just the attachment — is what counts against those caps.
This guide covers every major provider’s email attachment size limit as of mid-2026, explains why files inflate during transit, and gives you a decision framework for when to attach versus when to send a link. You will also find compression strategies, cold email attachment best practices, and answers to the most common questions about email file size limits.
What Is an Email Attachment Size Limit?
An email attachment size limit is the maximum file size that an email service provider allows you to send or receive in a single email message. These limits apply to the total message size on the wire — including the attachment, the email body, headers, inline images, signatures, and MIME encoding overhead — not just the file sitting on your hard drive.
Every major email provider enforces these caps. Gmail limits outgoing messages to 25 MB total. Outlook.com caps at 20 MB. Microsoft 365 Exchange Online can go up to 150 MB but is typically configured much lower. The receiving provider’s limit is the one that matters: if your provider lets you send 50 MB but your recipient’s server caps incoming at 20 MB, the effective limit is 20 MB. The smaller cap always wins.
Why Email Attachment Size Limits Exist
Email was designed in the early 1970s as a text-only communication system. The Simple Mail Transfer Protocol (SMTP) that still powers email today was built to handle short text messages, not multi-megabyte binary files. The limits that exist today are a direct consequence of that architectural legacy, combined with modern operational realities.
Server storage and bandwidth. Every email that passes through a mail server consumes storage space, at least temporarily. A single 50 MB attachment multiplied across thousands of recipients can overwhelm a mail queue. Email service providers also pay for bandwidth, and large attachments multiply those costs significantly.
Security scanning overhead. Incoming attachments must be scanned for malware, viruses, and phishing payloads. Scanning a 1 MB PDF takes milliseconds. Scanning a 50 MB archive with embedded files takes seconds per message, and at scale that latency becomes a denial-of-service risk. Many corporate mail servers enforce strict attachment size limits specifically to keep security scanning infrastructure manageable.
Compatibility constraints. Not all email clients handle large attachments gracefully. Mobile email apps, webmail interfaces, and older desktop clients may crash, hang, or silently fail when processing oversized messages. Providers set limits to ensure a consistent experience across all access methods.
Storage quotas. Consumer email accounts come with finite storage. Google provides 15 GB free across Gmail, Drive, and Photos. A single 25 MB attachment every day would consume over 7 GB in a year. Limits prevent individual users from exhausting shared storage pools.
Protocol limitations. SMTP itself does not define a maximum message size, but the Extended SMTP (ESMTP) SIZE extension lets servers advertise their limit during the connection handshake. If your message exceeds the advertised SIZE value, the receiving server can reject it before accepting the full payload. This is why you sometimes get an immediate bounce rather than a delayed failure.
Email Attachment Size Limits by Provider
The table below shows the documented send and receive limits for every major email provider as of June 2026. These limits are subject to change and may be overridden by administrator configuration on business accounts.
| Provider | Send Limit | Receive Limit | Notes |
|---|---|---|---|
| Gmail (personal) | 25 MB | 50 MB | Files over 25 MB auto-upload to Google Drive and send as link |
| Google Workspace (standard) | 25 MB | 50 MB | Admin-configurable within these bounds |
| Google Workspace Enterprise Plus | 50 MB | 70 MB | Increased February 2026, admin-enabled, not on by default |
| Outlook.com / Hotmail | 20 MB | 20 MB | OneDrive integration for larger files |
| Microsoft 365 Exchange Online | Up to 150 MB | Up to 150 MB | Admin-controlled, often capped at 25-50 MB in practice |
| Yahoo Mail | 25 MB | 25 MB | Dropbox integration for larger files |
| Apple iCloud Mail | 20 MB | 20 MB | Mail Drop handles up to 5 GB via expiring link |
| ProtonMail | 25 MB | 25 MB | Encrypted attachments count toward the limit |
| Zoho Mail | 20 MB | 20 MB | Zoho Docs integration for larger files |
| Yandex Mail | 20 MB | 20 MB | Yandex Disk integration for larger files |
| GMX Mail | 50 MB | 50 MB | One of the highest consumer limits available |
| Corporate Exchange (typical) | 10-25 MB | 10-25 MB | Highly variable, often the tightest cap you will hit |
| SMTP relay services | 25-75 MB | Varies | Provider-dependent; check your specific service |
Key insight: The receiving provider’s limit is the binding constraint. If you send from a service that allows 50 MB attachments to a Gmail recipient, the effective limit is 25 MB because Gmail will not accept anything larger. Always plan around the recipient’s cap, not your own.
How Base64 Encoding Affects Attachment Size
Email was designed to carry 7-bit ASCII text, not binary data. To send a PDF, image, or ZIP file through the SMTP system, the file must be encoded into a text-safe format. The standard method is Base64 encoding, which converts binary data into printable ASCII characters. This conversion adds approximately 33% to the original file size, and in practice the overhead is closer to 35-40% once MIME headers and boundary markers are included.
The math in practice:
- A 20 MB file becomes roughly 27 MB on the wire (35% increase)
- A 15 MB file becomes roughly 20 MB on the wire
- A 10 MB file becomes roughly 13.5 MB on the wire
- A 5 MB file becomes roughly 6.75 MB on the wire
- A 1 MB file becomes roughly 1.35 MB on the wire
This encoding overhead is the most common reason that files bounce even when they appear to be under the published limit. A 19 MB PDF attached to a Gmail message will weigh approximately 25.7 MB after Base64 encoding, which exceeds Gmail’s 25 MB total message cap. The bounce is not a glitch — it is the encoding doing its job.
Quoted-Printable encoding is an alternative method used primarily for text-heavy content with special characters. Its overhead is more variable, ranging from 0% to 220% depending on how many non-ASCII characters the content contains. For binary attachments, Base64 is the standard and the 33-40% overhead is the number to plan around.
What this means for your sending strategy: If you want a file to reliably arrive, keep the raw file size at approximately 75% of the provider’s published limit. For Gmail’s 25 MB cap, that means attachments should be no larger than about 18 MB raw. For Outlook.com’s 20 MB cap, aim for 15 MB or less.
What Actually Counts Toward Your Email Size
When a provider says “25 MB attachment limit,” they almost always mean the total size of the message on the wire, not the size of the file on your hard drive. This distinction is where most surprise bounces come from.
Everything that counts toward the total:
- The attachment file itself (after Base64 encoding)
- The text and HTML versions of your message body
- Inline images (logos, screenshots, banner graphics)
- Your email signature, including any embedded image
- Email headers (From, To, Subject, authentication records, tracking pixels, List-Unsubscribe data)
- MIME boundary markers that separate one part of the message from another
- Any calendar invites or vCards attached to the message
A typical business email with a logo signature, two inline screenshots, and a 22 MB PDF attachment can easily push past a 25 MB ceiling even though the PDF alone appears to fit. The body, signature, and inline images might add 1-2 MB of encoded weight, and the PDF itself becomes roughly 29 MB after Base64 encoding. The total lands at 30-31 MB — well past the limit.
HTML body size matters too. Gmail truncates messages with HTML bodies over 102 KB, inserting a “message clipped” notice that hides everything below the fold. This affects deliverability of marketing emails and transactional messages with heavy HTML templates, even when the attachment itself is small.
Why “Small Enough” Files Still Bounce
A bounce is not always a clean rejection. When a message exceeds a size limit, several outcomes are possible, and some are much harder to diagnose than others.
Immediate bounce at submission. Your email provider or SMTP server rejects the message before it leaves your outbox. You receive an error like “552 Message size exceeds maximum allowed” or “554 Transaction failed.” This is the best-case scenario because you know immediately that the message did not send.
Recipient-side rejection. Your provider accepts the message and attempts delivery, but the recipient’s mail server bounces it back minutes or hours later. You receive a non-delivery report (NDR), but the recipient never sees the message. This is the most common outcome for oversized attachments sent to corporate Exchange servers.
Silent drop. In rare cases, especially with older or misconfigured corporate mail servers, the message is accepted but never delivered to the recipient’s inbox, and no bounce is generated. The sender assumes the message landed. The recipient never knew it was sent.
Attachment stripping. Some corporate email security gateways and spam filters remove oversized attachments from incoming messages and deliver the body alone. The recipient gets an email that says “Attachment removed” or receives no notification at all. This is common with Microsoft Exchange Online protection filters.
Spam folder placement. Even when a message is technically under the size limit, an unusually large or oddly structured email can trigger spam filters. Messages with large attachments, especially archives like ZIP or RAR files, are frequently flagged as suspicious and routed to spam rather than the inbox.
Reputation drag. Repeatedly sending oversized messages can erode your sender reputation over time. Mail servers track sending patterns, and a history of large attachments can cause your future messages — even small, legitimate ones — to be treated with suspicion.
For a deeper look at bounce types and how to interpret error codes, see our guide on hard bounce vs soft bounce differences.
Email Attachment Size Limits for Cold Email Outreach
Cold email outreach introduces additional constraints around attachment size that most general guides ignore. When you are sending cold emails at scale, attachment size affects not just deliverability of individual messages but also your overall sender reputation and campaign performance.
The 10 MB rule is not conservative enough for cold email. For cold outreach, the safe target is under 5 MB total message size, and ideally under 1 MB. Here is why:
- Cold emails are more likely to hit corporate Exchange servers with 10 MB incoming caps. After Base64 encoding, a 7 MB attachment becomes 9.5 MB on the wire, and with body and headers you are already past the limit.
- Spam filters are more aggressive with cold email. A large attachment is an additional risk signal that can push an otherwise clean message into spam.
- Recipients on mobile devices are less likely to download large attachments from unknown senders. A 15 MB PDF from a stranger is more likely to be ignored or reported as spam than opened.
Best practices for cold email attachments:
- Keep attachments under 1 MB whenever possible. A one-page PDF proposal or one-sheeter should be 200-500 KB after proper compression.
- Use link-based delivery for anything over 5 MB. Host the file on your website or a cloud storage service and include a download link in the email body.
- Avoid ZIP files in cold email. Many spam filters treat ZIP archives as high-risk because malware is commonly distributed this way. If you must send a ZIP, notify the recipient beforehand.
- Test your attachment size before sending at scale. Send a test message to a Gmail address, an Outlook.com address, and a corporate Exchange address to confirm delivery.
- Monitor bounce codes. If you see elevated “552” or “554” bounce rates, attachment size is likely the cause.
For cold email campaigns that require reliable attachment delivery, using a platform with built-in deliverability monitoring can help. Mystrika provides bounce tracking and delivery analytics that help identify attachment-related failures before they impact your sender reputation.
How to Reduce Email Attachment Size
When you must attach a file and it is too large, follow this order of operations for maximum size reduction with minimum quality loss.
1. Compress images first. Images are almost always the largest component of any attachment. A 5 MB photo can typically be reduced to 400-600 KB with no perceptible quality loss for screen viewing. Resize to 1920 pixels on the longest side and set JPEG quality to 75-85%. For PNG files, consider converting to JPEG if transparency is not required.
2. Re-export PDFs at screen quality. Most PDF authoring tools have a “Save for Web” or “Reduce File Size” option that re-encodes embedded images. A 30 MB image-heavy PDF often drops to 4-6 MB with this single step. In Adobe Acrobat, use File > Save as Other > Reduced Size PDF. In Preview (Mac), use File > Export and select “Reduce File Size.”
3. Trim before you compress. If you only need pages 1, 4, and 7 of a 20-page document, send only those pages. Compression after the fact is no substitute for sending less content. Most PDF tools allow you to extract specific pages before exporting.
4. Remove the signature image. A 200 KB signature image, sent on every reply in a 30-message thread, becomes 6 MB of cumulative dead weight. Use a plain text signature with a small linked logo instead of an embedded image.
5. Use the right file format. For documents, PDF is almost always smaller than DOCX for the same content. For spreadsheets, XLSX is typically smaller than CSV for large datasets. For presentations, export to PDF rather than sending the PPTX file.
6. Consider ZIP compression carefully. ZIP compression works well for text-heavy files like DOCX, XLSX, and plain text. It provides minimal benefit for already-compressed formats like JPEG, PNG, MP4, and PDF (which often contains compressed images). A 50 MB folder of JPEG photos might ZIP down to 49 MB — barely any savings. A 10 MB Word document might ZIP to 2 MB.
7. Use online compression tools for one-off files. Tools like SmallPDF, ILovePDF, and TinyPNG can reduce file sizes significantly with a single upload. For sensitive documents, use a local tool instead of uploading to a third-party service.
Typical compression results by file type:
| File Type | Typical Raw Size | After Compression | Savings |
|---|---|---|---|
| JPEG photo (12 MP) | 4-6 MB | 400-600 KB | 85-90% |
| PDF (image-heavy) | 20-30 MB | 4-8 MB | 70-80% |
| PDF (text-only) | 500 KB-2 MB | 200-800 KB | 50-60% |
| Word document | 1-3 MB | 200-600 KB (ZIP) | 60-80% |
| PowerPoint deck | 10-50 MB | 3-10 MB (PDF export) | 70-80% |
| Excel spreadsheet | 500 KB-5 MB | 100 KB-1 MB (ZIP) | 60-80% |
Attach vs. Link: A Decision Framework
Choosing whether to attach a file or send a link depends on file size, recipient environment, and the nature of your communication. Use this decision matrix:
| File Size | Recommended Action | Rationale |
|---|---|---|
| Under 1 MB | Attach the file | Minimal deliverability risk, convenient for recipient |
| 1 MB to 5 MB | Attach for one-to-one; link for one-to-many | Safe for most recipients; at scale, link to avoid cumulative risk |
| 5 MB to 10 MB | Attach with caution; test first | May exceed corporate Exchange caps after encoding |
| 10 MB to 25 MB | Send a link | Exceeds safe threshold for most recipients after encoding |
| Over 25 MB | Always send a link | Exceeds Gmail and most provider caps even before encoding |
When to always send a link instead of attaching:
- The file exceeds 10 MB raw size
- You are sending to multiple recipients with unknown email environments
- The file contains sensitive data that you may need to revoke access to later
- You are sending cold email or marketing email at scale
- The recipient is on a corporate Exchange server (unknown cap)
- The file is an executable, archive, or uncommon format that may be blocked
Advantages of link-based delivery:
- No encoding overhead — the email stays small and delivers reliably
- Recipients can preview before downloading
- You can revoke access if you sent the wrong file or to the wrong person
- Links do not count against the recipient’s email storage quota
- You can track whether the recipient opened or downloaded the file
- The email renders quickly on mobile devices
Email Attachment Size Limits for Marketing vs. Transactional Emails
The technical limits are the same regardless of email type, but the practical implications differ significantly between marketing and transactional email.
Marketing emails. Attachments in marketing email are almost always a bad idea. Spam filters treat unsolicited attachments as a strong risk signal. Marketing email is built around HTML content and links, not file transfers. If you are sending a brochure, whitepaper, or case study, host it on your website and link to it. The deliverability cost of attaching a file to a marketing email far outweighs any convenience benefit.
Transactional emails. Transactional emails (order confirmations, password resets, receipts, shipping notifications) have higher deliverability expectations because recipients explicitly opt in to receive them. Even so, attachments should be kept under 1 MB. A PDF receipt or invoice should be 100-300 KB. If the attachment is larger, include a link to download it from a customer portal as a fallback.
Cold email outreach. Cold emails sit between marketing and transactional in terms of recipient expectations. The recipient did not ask for the email, so any attachment is an additional trust hurdle. Keep attachments under 1 MB, use PDF format, and always include a link-based alternative. For cold email campaigns, consider using a platform like Mystrika that provides warmup and deliverability optimization to offset the reputation impact of sending attachments to cold recipients.
Common Email Attachment Size Limit Myths
Myth 1: The limit applies only to the attachment file. The limit applies to the total message size including the body, headers, inline images, signature, and the encoded attachment. A 20 MB file in a 25 MB limit leaves only 5 MB of headroom for everything else, and after Base64 encoding that 20 MB file becomes 27 MB on the wire.
Myth 2: You can increase Gmail’s 25 MB limit by upgrading to a paid plan. Google does not allow increasing the 25 MB send limit on any Gmail or Google Workspace plan. The Enterprise Plus plan raised the limit to 50 MB in February 2026, but this must be enabled by an administrator and is not available on standard plans.
Myth 3: ZIP compression always makes files small enough to email. ZIP compression is effective for text-heavy files but provides almost no benefit for already-compressed formats like JPEG, PNG, MP4, and most PDFs. A ZIP of image files may be only 1-2% smaller than the originals.
Myth 4: If your provider allows it, the recipient can receive it. The receiving provider’s limit is the binding constraint. Your 50 MB send limit means nothing if the recipient’s server caps incoming at 20 MB. Always plan around the smaller of the two limits.
Myth 5: Large attachments only cause bounces for the specific message. Repeated oversized sends can damage your sender reputation, making all of your future emails — even small ones — harder to deliver. Mail servers track sending patterns.
Myth 6: Corporate Exchange limits are always 10 MB. Exchange limits are administrator-configurable and vary widely. Some organizations set limits as low as 5 MB, while others allow up to 150 MB. When sending to corporate recipients, assume a 10 MB cap unless you know otherwise.
Myth 7: Email attachment size limits are the same worldwide. Some regional providers have different limits. For example, some Chinese email providers cap attachments at 10 MB or lower. If you are sending internationally, research the recipient’s provider limits.
How to Test Email Attachment Size Limits Before Sending at Scale
Before sending attachments to a large list, verify that your messages will deliver by following this testing protocol.
Step 1: Calculate your total message size. Add up the raw file size of your attachment, the estimated size of your email body and signature, and then multiply the attachment size by 1.35 to account for Base64 encoding. If the total exceeds 10 MB, switch to a link-based approach.
Step 2: Send test messages. Send your email with the attachment to test accounts on Gmail, Outlook.com, Yahoo Mail, and a corporate Exchange address if you have access to one. Verify that all test messages arrive in the inbox, not spam.
Step 3: Check bounce codes. If any test messages bounce, examine the error code. A 552 or 554 error indicates a size-related rejection. A 550 error may indicate a different issue.
Step 4: Monitor deliverability at scale. After sending, review your bounce rate and spam placement rate. A spike in either may indicate that attachment size is causing problems even for recipients whose servers accepted the message.
Step 5: Use a deliverability monitoring tool. Platforms like Mystrika’s email deliverability tools can help track bounce patterns and identify attachment-related failures across your campaigns.
Email Attachment Size Limits for Different File Types
Not all file types are treated equally by email systems. Some formats are more likely to be blocked or flagged regardless of size.
PDF files. PDF is the safest format for email attachments. It is universally readable, preserves formatting, and is less likely to be flagged by spam filters than other formats. Keep PDFs under 10 MB raw size for reliable delivery.
Microsoft Office files (DOCX, XLSX, PPTX). These are generally safe but can be surprisingly large due to embedded media. A PowerPoint deck with high-resolution images can easily exceed 50 MB. Export to PDF before attaching, or compress embedded media within the file.
Image files (JPEG, PNG, GIF). Images are safe to attach but should be compressed before sending. A single high-resolution photo from a modern smartphone can be 5-10 MB. Resize to 1920 pixels and use JPEG quality 80% for a 400-600 KB result.
ZIP and RAR archives. These are the most likely to be blocked by spam filters. Malware is commonly distributed in archive formats, and many email servers reject them outright. If you must send an archive, notify the recipient beforehand and consider password-protecting the file (with the password sent separately).
Executable files (EXE, MSI, DMG, APK). Most email providers block executable attachments entirely, regardless of size. Do not attempt to send executable files via email. Use a file-sharing service or developer-specific distribution method.
Video and audio files (MP4, MOV, MP3, WAV). These are almost always too large to email. A 30-second video clip at 1080p can be 50-100 MB. Use cloud storage links or dedicated file-sharing services.
Key Takeaways
- Email attachment size limits apply to the total message on the wire, not just the file on your hard drive. Base64 encoding adds 33-40% overhead.
- Gmail caps outgoing messages at 25 MB (50 MB for Enterprise Plus with admin enablement). Outlook.com caps at 20 MB. Microsoft 365 Exchange Online can go up to 150 MB but is typically configured at 25-50 MB.
- The receiving provider’s limit is the binding constraint. Always plan around the smaller of the two limits.
- For reliable delivery, keep total message size under 10 MB. For cold email, keep attachments under 1 MB.
- Compress images, re-export PDFs at screen quality, and trim unnecessary pages before attaching.
- Send a link instead of an attachment for files over 10 MB, for one-to-many sends, and for cold email or marketing email.
- ZIP files are often blocked by spam filters and provide minimal benefit for already-compressed formats.
- Test your attachment size before sending at scale by sending to multiple provider test accounts and monitoring bounce codes.
- Use a deliverability monitoring platform to track attachment-related failures and protect your sender reputation.
Frequently Asked Questions
What is the maximum email attachment size for Gmail in 2026?
Gmail’s maximum attachment size is 25 MB for personal accounts and standard Google Workspace plans. Google Workspace Enterprise Plus can send up to 50 MB, but this must be enabled by an administrator and is not available on lower-tier plans. Gmail can receive messages up to 50 MB, and files over 25 MB are automatically uploaded to Google Drive and sent as a shareable link instead of an attachment.
Why did my 24 MB attachment bounce when the limit is 25 MB?
The most likely cause is Base64 encoding overhead. A 24 MB file becomes approximately 32 MB on the wire after encoding, which exceeds Gmail’s 25 MB total message cap. The published limit applies to the encoded message size, not the raw file size. To stay safe, keep raw file sizes at approximately 75% of the published limit, or about 18 MB for Gmail.
Can I increase the email attachment size limit on my account?
For consumer email services, the answer is almost always no. Gmail, Outlook.com, Yahoo Mail, and ProtonMail do not allow users to increase their attachment size limits. Microsoft 365 Exchange Online limits are administrator-configurable, so your organization may be able to raise the cap. Google Workspace Enterprise Plus offers a 50 MB limit, but this requires admin enablement and an Enterprise Plus subscription.
What happens when I send an attachment that is too large?
The outcome depends on where the rejection happens. Your email provider may reject the message immediately with a 552 or 554 error. The recipient’s server may reject it after accepting the message from your provider, generating a delayed bounce. In some cases, the attachment may be stripped and the body delivered alone. In rare cases, the message may be silently dropped with no bounce at all.
Is it safe to send ZIP files via email?
ZIP files are frequently blocked by spam filters and corporate email security gateways because malware is commonly distributed in archive format. ZIP compression also provides minimal benefit for already-compressed file types like JPEG, PNG, and PDF. If you must send a ZIP, notify the recipient beforehand, consider password-protecting the file, and send the password through a separate channel.
What is the safest attachment size for cold email outreach?
For cold email, keep attachments under 1 MB total message size. A one-page PDF proposal or one-sheeter should be 200-500 KB after proper compression. Cold emails are more likely to hit aggressive spam filters and corporate Exchange servers with low caps, so smaller attachments significantly improve deliverability. For anything over 5 MB, use a link-based delivery approach instead.
Do email attachment size limits apply to inline images in the email body?
Yes, inline images count toward the total message size. Every image embedded in your email body, signature, or HTML template is encoded as a MIME attachment and contributes to the total size on the wire. A logo in your signature, a banner image in your template, and screenshots in your message body all add up. Keep inline images compressed and under 100 KB each.
How do I send a file larger than 25 MB via email?
You cannot send a file larger than 25 MB as a direct email attachment through most providers. Instead, upload the file to a cloud storage service like Google Drive, OneDrive, or Dropbox, and include a shareable link in your email body. Gmail automatically offers this option when you attach a file over 25 MB. For files up to 5 GB, Apple iCloud Mail Drop provides an expiring download link. Third-party services like WeTransfer offer temporary links for files up to 2 GB.
What is the difference between send limit and receive limit for email attachments?
The send limit is the maximum size of an outgoing message your provider allows you to send. The receive limit is the maximum size of an incoming message your provider will accept. These are often different values. For example, Gmail’s send limit is 25 MB but its receive limit is 50 MB. The effective limit for any email is the smaller of the sender’s send limit and the recipient’s receive limit.
How does Base64 encoding affect email attachment size?
Base64 encoding converts binary file data into text-safe ASCII characters for transmission through SMTP. This conversion adds approximately 33% overhead to the original file size, and in practice the increase is 35-40% once MIME headers and boundary markers are included. A 20 MB file becomes roughly 27 MB on the wire. This encoding overhead is why files near the published limit often bounce — the limit applies to the encoded size, not the raw file size.