Email Attachment Size Limits: What Actually Sends in 2026

Most email attachment size guides give you a number and call it done. The problem is that the number on the box isn’t the number that actually sends. Encoding adds weight, recipient servers have their own caps, and a 24 MB file can bounce off a 25 MB limit without ever reaching an inbox.

This guide cuts through that. Here’s what every major provider allows in 2026, what really counts toward your email size, and a simple decision rule for when to attach a file versus when to send a link instead.

Quick answer

• Email attachment limits apply to your entire message, not just the file. That includes the body, signatures, headers, inline images, and tracking markup.
• Files grow by roughly 33% to 40% during transit because of Base64 encoding. A 20 MB file becomes about 27 MB on the wire.
• Most major providers cap incoming messages between 20 MB and 25 MB. Microsoft 365 and Google Workspace can go higher with admin configuration.
• The safest universal target is to keep total message size under 10 MB. Above that, send a link.
• A high published limit (yours or your provider’s) doesn’t override the recipient’s limit. The smaller of the two always wins.
  

  Email attachment size limits by provider (2026)

These are the documented caps as of April 2026. Limits are subject to admin overrides and provider updates.

A note that catches most people off guard: if your provider lets you send 50 MB but your recipient’s provider caps incoming at 20 MB, the effective limit is 20 MB. The smaller cap always decides. That’s why universal targets matter more than your own ceiling.

What actually counts toward 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 sitting on your hard drive. That distinction is where most surprise bounces come from.

Total message size, not just the attachment

Every email you send is a package. The package includes:

• The text and HTML versions of your message body
• Inline images (logos, screenshots, banner graphics)
• Your signature, including any embedded image
• The headers (from, to, subject, authentication records, tracking pixels, list-unsubscribe data)
• The attachment itself, after encoding
• MIME boundaries that separate one part from another
  A simple business email with a logo signature, a couple of inline images, and a 22 MB PDF attachment can easily push past a 25 MB ceiling.

How Base64 encoding inflates files

Email was designed to carry text, not binary files. To move a PDF or an image through the SMTP system, the file gets encoded into Base64, which represents binary data using only printable text characters. That conversion adds overhead.

The math, in practice:

• A 20 MB file becomes roughly 27 MB on the wire after Base64 encoding (about a 35% increase)
• A 15 MB file becomes roughly 20 MB
• A 10 MB file becomes roughly 13.5 MB
  SMTP2GO’s How to Speed Up Email Delivery doc notes that attachments grow by about 40% under Base64. Other encoding methods (Quoted-Printable) add a more variable amount, between 0% and 220%, depending on how text-heavy the file is.

This is why a 19 MB file sometimes won’t send through a 20 MB cap. The cap measures the encoded size, not the raw file size.

Headers, HTML, signatures, and other invisible weight

Bloated HTML can clip an email even when the attachment is small. Gmail truncates messages with bodies over 102 KB, leaving a “message clipped” notice that hides everything below the fold (including unsubscribe links and final calls to action). Heavy inline images and elaborate signatures add up faster than people expect.

If you’re a marketer wondering why your beautifully designed campaign is getting half-read, message size and HTML clipping are usually the first place to check. Our guide to improving email deliverability goes deeper on this.

Why “small enough” files still bounce

A bounce isn’t always a clean rejection. Here’s what actually happens when a message exceeds a limit, in roughly the order of how recoverable each outcome is:

1. Immediate bounce. Your provider rejects the message at submission. You get an error like “552 Message size exceeds maximum allowed.” This is the best case, because you know right away.
2. Recipient-side rejection. Your provider accepts the send, but the recipient’s server bounces it back minutes (or hours) later. You get a non-delivery report, but the recipient never sees the message.
3. Silent drop. In rare cases, especially with older corporate mail servers, the message is accepted but never delivered, with no bounce. You assume it landed. The recipient never knew it was sent.
4. Attachment stripping. Some corporate filters remove oversized attachments and deliver the body alone, sometimes with a note, sometimes without.
5. Spam folder placement. Even when a message is technically under the limit, an unusually large or oddly structured email can look suspicious to filters and end up in spam.
6. Reputation drag. Repeated oversized sends can erode your sender reputation over time, making your smaller, legitimate emails harder to deliver too.
   For a deeper look at how bounces actually work and how to read the codes, see our breakdown of hard bounces, soft bounces, and rejected emails.

Safe attachment sizes by use case

The “right” attachment size depends on what you’re sending and who you’re sending it to. Here’s a more useful framework than a single number.

Invoices, receipts, and short business documents

Target: under 1 MB. A clean PDF invoice is usually 50 to 300 KB. If yours is bigger, it’s almost always because of an embedded high-resolution scan or logo. Compress it. Invoices that bounce are awkward, and they’re easy to keep small.

Proposals, decks, and image-heavy PDFs

Target: under 5 MB. This is the sweet spot for one-to-one business sends to mixed recipient environments. It’s small enough to clear corporate Exchange caps (which are often 10 MB), encoded weight stays comfortable, and it loads fast on mobile. If the deck is bigger, compress images to 1080p resolution and re-export the PDF.

Internal-only transfers and large files

Target: don’t email it. If both sides of the conversation are inside an organization with known infrastructure, you might get away with 20 to 30 MB attachments. But internal email isn’t the right tool for large file transfer. Use a shared drive, a secure link, or a dedicated file-sharing service. Email queues, mail server storage, and bandwidth all suffer when teams normalize huge attachments.

Marketing emails (where attachments rarely belong)

Target: don’t attach anything. Marketing email is built around HTML and links. Attachments in marketing email signal one of three things to spam filters: a phishing attempt, a careless sender, or both. If you’re sending a brochure or a whitepaper, host it and link to it.

Attach the file, or send a link? A simple decision rule

Use this:

• Under 1 MB: Attach it. The convenience is worth it, and there’s almost no deliverability risk.
• 1 MB to 5 MB: Attach it for one-to-one sends. For one-to-many, consider linking, especially if your list might include corporate recipients.
• 5 MB to 10 MB: Attach with caution. Test it. Confirm the recipient can receive it.
• Over 10 MB: Send a link. Always.
  This aligns with SMTP2GO’s standing recommendation in our support documentation: don’t use email to move files larger than about 10 MB, and consider a link once an attachment crosses 1 MB. The published cap is 50 MB because we want to give you headroom for the legitimate edge cases. It’s not a target.

A link-based workflow has practical advantages too. The recipient can preview before downloading, you can revoke access if you sent the wrong file, and your message stays small enough to render fast on a phone.

How to shrink emails without losing quality

When you have to attach something and it’s too big, here’s the order of operations that gets the most savings with the least pain.

1. Compress images first. A 5 MB photo can usually become a 500 KB photo with no perceptible quality loss for screen viewing. Resize to 1920 pixels wide, set JPEG quality to 75 to 85%, done.
2. Re-export PDFs at “screen” or “web” quality. Most PDF tools have a one-click setting that re-encodes embedded images. A 30 MB image-heavy PDF often drops to 4 to 6 MB.
3. Trim before you compress. If you only need pages 1, 4, and 7, send pages 1, 4, and 7. Compression after the fact is no substitute for sending less.
4. Drop the signature image. A 200 KB signature image, sent on every reply in a 30-message thread, becomes 6 MB of dead weight. Use text and a small linked logo.
5. Be careful with ZIP files. ZIPs can reduce size for non-image documents, but some spam filters flag them as suspicious. ZIP only when there’s a real benefit and the recipient knows it’s coming. For image-heavy files, ZIP barely helps anyway because JPEGs and PNGs are already compressed.
   For a longer treatment of attachment optimization, see our guide on optimizing your attachments for email.

How SMTP2GO handles attachment-heavy sending

If you’re sending business email at scale, attachment handling becomes infrastructure, not etiquette. Here’s how SMTP2GO approaches it.

We support up to 50 MB per email through SMTP or our API, including all content, attachments, and headers. That’s higher than most receiving providers will accept, which is intentional. It gives you headroom for legitimate edge cases (signed contracts with embedded images, technical documents, internal-only sends) without making oversized email the default behavior.

What matters more than the cap is what happens around it:

• Visible bounces. When a recipient server rejects an oversized message, you see the bounce in your dashboard with the actual error code, not a vague failure notice. Diagnosing a 552 message size error takes seconds, not hours.
• Predictable encoding. Our infrastructure handles MIME and Base64 encoding consistently, so you can plan around the 33 to 40% overhead instead of guessing.
• Reputation protection. We monitor sending patterns and flag senders pushing oversized messages before it damages domain reputation.
• Free attachment optimization in the docs. Our Maximum Attachment Size and How to Speed Up Email Delivery guides give you the actual mechanics.
  If your team is troubleshooting bounces and oversized messages keeps coming up, see our bounce rate survival guide for the broader playbook.

FAQ

Why did my 24 MB attachment bounce when the limit is 25 MB?
Most likely because the encoded size pushed past the cap. A 24 MB file becomes roughly 32 MB after Base64 encoding, which exceeds Gmail’s 25 MB ceiling. Aim for a raw file size around 75% of the published limit and you’ll stay safe.

Does sending a ZIP file hurt deliverability?
Sometimes. Some spam filters treat ZIPs as suspicious because malware is occasionally distributed that way. ZIPs also don’t compress images much (they’re already compressed), so the deliverability risk often outweighs the size benefit. ZIP for non-image documents when you actually save meaningful space, and only when the recipient is expecting it.

What’s the safest attachment size if I don’t know the recipient’s setup?
Stay under 10 MB total message size. That clears almost every corporate Exchange cap, leaves room for encoding overhead, and renders quickly on mobile. If you regularly need to send larger files, switch to link-based sharing.

Should I attach a PDF or send a cloud link?
Under 5 MB, attach it. Over 10 MB, link it. Between those, judgment call: lean toward attaching for one-to-one sends with known recipients, lean toward linking for one-to-many or unknown recipient environments.

Do attachment size limits affect transactional emails differently?
The limits themselves are the same, but the impact is bigger. Transactional emails (password resets, receipts, order confirmations) need to be reliable above all else. Avoid attachments where you can; if you must include one (a PDF receipt, for example), keep it under 1 MB and inline a link to the customer portal version as a fallback.

The bottom line

Email attachment limits are about more than the number a provider publishes. They’re about the gap between what’s allowed and what actually gets delivered, and that gap is filled with encoding overhead, recipient caps, and reputation considerations.

The simple version of the rule:

• Stay under 10 MB total message size whenever you can.
• Send a link for anything bigger.
• Test the recipient experience for anything important.
• Use sending infrastructure that gives you visibility when something fails.
  If you’re hitting bounces on attachments, or you just want sending infrastructure that handles encoding and reporting properly so you can stop guessing, try SMTP2GO free. You can send up to 1,000 emails a month at no cost, and you’ll see exactly what’s happening with each message, attachments included.

Last updated: April 2026. Provider limits change. We refresh this article when they do.